[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[geogig-dev] Build failed in Jenkins: geoserver-2.10.x-geogig-plugin #196
|
See <http://ares.boundlessgeo.com/jenkins/job/geoserver-2.10.x-geogig-plugin/196/>
------------------------------------------
[...truncated 213473 lines...]
Given There is an empty repository named repo1(Scenario: Verify wrong HTTP method issues 405 "Method not allowed"): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit3792595561679959910/repo1/'
Scenario: Verify wrong HTTP method issues 405 "Method not allowed": Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit3792595561679959910/repo1/'
Scenario: Verify wrong HTTP method issues 405 "Method not allowed": org/locationtech/geogig/repository/RepositoryResolverTestUtil
Scenario: Tag outside of a repository issues 404 "Not found": org/locationtech/geogig/repository/RepositoryResolverTestUtil
Given There is an empty repository named repo1(Scenario: Issuing a POST request to tag without a name issues a 500 status code): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit5091651599703253074/repo1/'
Scenario: Issuing a POST request to tag without a name issues a 500 status code: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit5091651599703253074/repo1/'
Scenario: Issuing a POST request to tag without a name issues a 500 status code: org/locationtech/geogig/repository/RepositoryResolverTestUtil
Given There is an empty repository named repo1(Scenario: Issuing a POST request to tag without a commit issues a 500 status code): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit8745326130575157055/repo1/'
Scenario: Issuing a POST request to tag without a commit issues a 500 status code: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit8745326130575157055/repo1/'
Scenario: Issuing a POST request to tag without a commit issues a 500 status code: org/locationtech/geogig/repository/RepositoryResolverTestUtil
Given There is an empty repository named repo1(Scenario: Issuing a POST request to tag with an invalid commit issues a 500 status code): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit804206047848987121/repo1/'
Scenario: Issuing a POST request to tag with an invalid commit issues a 500 status code: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit804206047848987121/repo1/'
Scenario: Issuing a POST request to tag with an invalid commit issues a 500 status code: org/locationtech/geogig/repository/RepositoryResolverTestUtil
Given There is a default multirepo server(Scenario: Issuing a POST request to tag with valid parameters creates a tag): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit356483817599892302/repo1/'
Scenario: Issuing a POST request to tag with valid parameters creates a tag: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit356483817599892302/repo1/'
Scenario: Issuing a POST request to tag with valid parameters creates a tag: org/locationtech/geogig/repository/RepositoryResolverTestUtil
Given There is a default multirepo server(Scenario: Issuing a GET request to tag lists all tags): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit9203389878481509044/repo1/'
Scenario: Issuing a GET request to tag lists all tags: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit9203389878481509044/repo1/'
Scenario: Issuing a GET request to tag lists all tags: org/locationtech/geogig/repository/RepositoryResolverTestUtil
Given There is an empty repository named repo1(Scenario: Issuing a DELETE request to tag without a name issues a 500 status code): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit1308396080625987811/repo1/'
Scenario: Issuing a DELETE request to tag without a name issues a 500 status code: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit1308396080625987811/repo1/'
Scenario: Issuing a DELETE request to tag without a name issues a 500 status code: org/locationtech/geogig/repository/RepositoryResolverTestUtil
Given There is a default multirepo server(Scenario: Issuing a DELETE request to tag deletes the tag): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit968024580319976437/repo1/'
Scenario: Issuing a DELETE request to tag deletes the tag: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit968024580319976437/repo1/'
Scenario: Issuing a DELETE request to tag deletes the tag: org/locationtech/geogig/repository/RepositoryResolverTestUtil
Given There is an empty repository named repo1(Scenario: Verify wrong HTTP method on begin transaction issues 405 "Method not allowed"): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit7078708078237767318/repo1/'
Scenario: Verify wrong HTTP method on begin transaction issues 405 "Method not allowed": Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit7078708078237767318/repo1/'
Scenario: Verify wrong HTTP method on begin transaction issues 405 "Method not allowed": org/locationtech/geogig/repository/RepositoryResolverTestUtil
Scenario: Beginning a transaction outside of a repository issues 404 "Not found": org/locationtech/geogig/repository/RepositoryResolverTestUtil
Given There is an empty repository named repo1(Scenario: Verify wrong HTTP method on end transaction issues 405 "Method not allowed"): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit1783654344868924034/repo1/'
Scenario: Verify wrong HTTP method on end transaction issues 405 "Method not allowed": Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit1783654344868924034/repo1/'
Scenario: Verify wrong HTTP method on end transaction issues 405 "Method not allowed": org/locationtech/geogig/repository/RepositoryResolverTestUtil
Scenario: Ending a transaction outside of a repository issues 404 "Not found": org/locationtech/geogig/repository/RepositoryResolverTestUtil
Given There is an empty repository named repo1(Scenario: Ending a transaction outside of a transaction issues 500 "Transaction required"): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit3420245837358467293/repo1/'
Scenario: Ending a transaction outside of a transaction issues 500 "Transaction required": Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit3420245837358467293/repo1/'
Scenario: Ending a transaction outside of a transaction issues 500 "Transaction required": org/locationtech/geogig/repository/RepositoryResolverTestUtil
Given There is a repository with multiple branches named repo1(Scenario: Work on a transaction does not affect the main repository): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit1887700089364637523/repo1/'
Scenario: Work on a transaction does not affect the main repository: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit1887700089364637523/repo1/'
Scenario: Work on a transaction does not affect the main repository: org/locationtech/geogig/repository/RepositoryResolverTestUtil
Given There is a repository with multiple branches named repo1(Scenario: Ending a transaction moves the work to the main repository): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit7345277501932735593/repo1/'
Scenario: Ending a transaction moves the work to the main repository: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit7345277501932735593/repo1/'
Scenario: Ending a transaction moves the work to the main repository: org/locationtech/geogig/repository/RepositoryResolverTestUtil
Given There is a repository with multiple branches named repo1(Scenario: Canceling a transaction leaves the main repository without changes): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit6324297727946934617/repo1/'
Scenario: Canceling a transaction leaves the main repository without changes: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit6324297727946934617/repo1/'
Scenario: Canceling a transaction leaves the main repository without changes: org/locationtech/geogig/repository/RepositoryResolverTestUtil
Given There is a repository with multiple branches named repo1(Scenario: Ending a transaction with conflicting changes returns details of the conflict): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit6317571631943622239/repo1/'
Scenario: Ending a transaction with conflicting changes returns details of the conflict: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit6317571631943622239/repo1/'
Scenario: Ending a transaction with conflicting changes returns details of the conflict: org/locationtech/geogig/repository/RepositoryResolverTestUtil
Given There is a repository with multiple branches named repo1(Scenario: Fixing transaction conflicts and ending again is successful): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit5990878938019440001/repo1/'
Scenario: Fixing transaction conflicts and ending again is successful: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit5990878938019440001/repo1/'
Scenario: Fixing transaction conflicts and ending again is successful: org/locationtech/geogig/repository/RepositoryResolverTestUtil
Given There is an empty repository named repo1(Scenario: Verify wrong HTTP method issues 405 "Method not allowed"): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit5000174775642419278/repo1/'
Scenario: Verify wrong HTTP method issues 405 "Method not allowed": Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit5000174775642419278/repo1/'
Scenario: Verify wrong HTTP method issues 405 "Method not allowed": org/locationtech/geogig/repository/RepositoryResolverTestUtil
Scenario: UpdateRef outside of a repository issues 404 "Not found": org/locationtech/geogig/repository/RepositoryResolverTestUtil
Given There is an empty repository named repo1(Scenario: Calling UpdateRef without a ref name issues a 500 status code): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit1735819238123993895/repo1/'
Scenario: Calling UpdateRef without a ref name issues a 500 status code: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit1735819238123993895/repo1/'
Scenario: Calling UpdateRef without a ref name issues a 500 status code: org/locationtech/geogig/repository/RepositoryResolverTestUtil
Given There is an empty repository named repo1(Scenario: Calling UpdateRef without a new value or delete specified issues a 500 status code): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit4078221820441086675/repo1/'
Scenario: Calling UpdateRef without a new value or delete specified issues a 500 status code: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit4078221820441086675/repo1/'
Scenario: Calling UpdateRef without a new value or delete specified issues a 500 status code: org/locationtech/geogig/repository/RepositoryResolverTestUtil
Given There is an empty repository named repo1(Scenario: Calling UpdateRef without a nonexistent name issues a 500 status code): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit6639419513884345805/repo1/'
Scenario: Calling UpdateRef without a nonexistent name issues a 500 status code: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit6639419513884345805/repo1/'
Scenario: Calling UpdateRef without a nonexistent name issues a 500 status code: org/locationtech/geogig/repository/RepositoryResolverTestUtil
Given There is a default multirepo server(Scenario: Calling UpdateRef with a new value updates the ref): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit8990864116529315232/repo1/'
Scenario: Calling UpdateRef with a new value updates the ref: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit8990864116529315232/repo1/'
Scenario: Calling UpdateRef with a new value updates the ref: org/locationtech/geogig/repository/RepositoryResolverTestUtil
Given There is a default multirepo server(Scenario: Calling UpdateRef with the delete parameter deletes the ref): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit7787117342482268436/repo1/'
Scenario: Calling UpdateRef with the delete parameter deletes the ref: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit7787117342482268436/repo1/'
Scenario: Calling UpdateRef with the delete parameter deletes the ref: org/locationtech/geogig/repository/RepositoryResolverTestUtil
Given There is an empty repository named repo1(Scenario: Verify wrong HTTP method issues 405 "Method not allowed"): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit7519069961375943363/repo1/'
Scenario: Verify wrong HTTP method issues 405 "Method not allowed": Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit7519069961375943363/repo1/'
Scenario: Verify wrong HTTP method issues 405 "Method not allowed": org/locationtech/geogig/repository/RepositoryResolverTestUtil
Scenario: Version outside of a repository issues 404 "Not found": org/locationtech/geogig/repository/RepositoryResolverTestUtil
Given There is an empty repository named repo1(Scenario: Version returns geogig version details): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit982442009911384118/repo1/'
Scenario: Version returns geogig version details: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit982442009911384118/repo1/'
Scenario: Version returns geogig version details: org/locationtech/geogig/repository/RepositoryResolverTestUtil
Given There is an empty repository named repo1(Scenario: Verify wrong HTTP method issues 405 "Method not allowed"): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit981304179800706353/repo1/'
Scenario: Verify wrong HTTP method issues 405 "Method not allowed": Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit981304179800706353/repo1/'
Scenario: Verify wrong HTTP method issues 405 "Method not allowed": org/locationtech/geogig/repository/RepositoryResolverTestUtil
Scenario: AffectedFeatures outside of a repository issues 404 "Not found": org/locationtech/geogig/repository/RepositoryResolverTestUtil
Given There is an empty repository named repo1(Scenario: AffectedFeatures with no commit issues a 400 status code): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit3007754865710567520/repo1/'
Scenario: AffectedFeatures with no commit issues a 400 status code: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit3007754865710567520/repo1/'
Scenario: AffectedFeatures with no commit issues a 400 status code: org/locationtech/geogig/repository/RepositoryResolverTestUtil
Given There is an empty repository named repo1(Scenario: AffectedFeatures with an invalid commit issues a 400 status code): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit8050390921008507299/repo1/'
Scenario: AffectedFeatures with an invalid commit issues a 400 status code: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit8050390921008507299/repo1/'
Scenario: AffectedFeatures with an invalid commit issues a 400 status code: org/locationtech/geogig/repository/RepositoryResolverTestUtil
Given There is a default multirepo server(Scenario: AffectedFeatures lists all features changed in a commit): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit4344140158639601690/repo1/'
Scenario: AffectedFeatures lists all features changed in a commit: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit4344140158639601690/repo1/'
Scenario: AffectedFeatures lists all features changed in a commit: org/locationtech/geogig/repository/RepositoryResolverTestUtil
Given There is an empty repository named repo1(Scenario: Verify wrong HTTP method issues 405 "Method not allowed"): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit2393271572291006683/repo1/'
Scenario: Verify wrong HTTP method issues 405 "Method not allowed": Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit2393271572291006683/repo1/'
Scenario: Verify wrong HTTP method issues 405 "Method not allowed": org/locationtech/geogig/repository/RepositoryResolverTestUtil
Scenario: Depth outside of a repository issues 404 "Not found": org/locationtech/geogig/repository/RepositoryResolverTestUtil
Given There is a default multirepo server(Scenario: Depth with an invalid commit issues a 400 status code): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit6747472646059700274/repo1/'
Scenario: Depth with an invalid commit issues a 400 status code: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit6747472646059700274/repo1/'
Scenario: Depth with an invalid commit issues a 400 status code: org/locationtech/geogig/repository/RepositoryResolverTestUtil
Given There is a default multirepo server(Scenario: Depth with no commit returns no depth for a non-shallow repository): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit7326558916697437468/repo1/'
Scenario: Depth with no commit returns no depth for a non-shallow repository: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit7326558916697437468/repo1/'
Scenario: Depth with no commit returns no depth for a non-shallow repository: org/locationtech/geogig/repository/RepositoryResolverTestUtil
Given There is a default multirepo server with a shallow clone(Scenario: Depth with no commit returns the depth of a shallow repository): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit519243349840614407/full/'
Scenario: Depth with no commit returns the depth of a shallow repository: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit519243349840614407/full/'
Scenario: Depth with no commit returns the depth of a shallow repository: org/locationtech/geogig/repository/RepositoryResolverTestUtil
Given There is a default multirepo server(Scenario: Depth with a commit returns the number of ancestors that commit has): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit6053523691144179772/repo1/'
Scenario: Depth with a commit returns the number of ancestors that commit has: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit6053523691144179772/repo1/'
Scenario: Depth with a commit returns the number of ancestors that commit has: org/locationtech/geogig/repository/RepositoryResolverTestUtil
Given There is an empty repository named repo1(Scenario: Verify wrong HTTP method issues 405 "Method not allowed"): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit285682419839068655/repo1/'
Scenario: Verify wrong HTTP method issues 405 "Method not allowed": Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit285682419839068655/repo1/'
Scenario: Verify wrong HTTP method issues 405 "Method not allowed": org/locationtech/geogig/repository/RepositoryResolverTestUtil
Given There is a default multirepo server(Scenario: Manifest lists all of the branches in the repository): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit2888034720157508603/repo1/'
Scenario: Manifest lists all of the branches in the repository: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit2888034720157508603/repo1/'
Scenario: Manifest lists all of the branches in the repository: org/locationtech/geogig/repository/RepositoryResolverTestUtil
Given There is a default multirepo server with remotes(Scenario: Manifest also lists remote branches when the remotes parameter is specified): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit2032155920529268351/repo1/'
Scenario: Manifest also lists remote branches when the remotes parameter is specified: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit2032155920529268351/repo1/'
Scenario: Manifest also lists remote branches when the remotes parameter is specified: org/locationtech/geogig/repository/RepositoryResolverTestUtil
Given There is an empty repository named repo1(Scenario: Verify wrong HTTP method issues 405 "Method not allowed"): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit435398207238928390/repo1/'
Scenario: Verify wrong HTTP method issues 405 "Method not allowed": Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit435398207238928390/repo1/'
Scenario: Verify wrong HTTP method issues 405 "Method not allowed": org/locationtech/geogig/repository/RepositoryResolverTestUtil
Scenario: MergeFeature outside of a repository issues 404 "Not found": org/locationtech/geogig/repository/RepositoryResolverTestUtil
Given There is an empty repository named repo1(Scenario: MergeFeature with no json payload issues a 400 status code): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit4263642264247556742/repo1/'
Scenario: MergeFeature with no json payload issues a 400 status code: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit4263642264247556742/repo1/'
Scenario: MergeFeature with no json payload issues a 400 status code: org/locationtech/geogig/repository/RepositoryResolverTestUtil
Given There is an empty repository named repo1(Scenario: MergeFeature with an invalid json payload issues a 400 status code): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit5495716395008772796/repo1/'
Scenario: MergeFeature with an invalid json payload issues a 400 status code: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit5495716395008772796/repo1/'
Scenario: MergeFeature with an invalid json payload issues a 400 status code: org/locationtech/geogig/repository/RepositoryResolverTestUtil
Given There is an empty repository named repo1(Scenario: MergeFeature without a feature issues a 400 status code): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit8629408529376740145/repo1/'
Scenario: MergeFeature without a feature issues a 400 status code: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit8629408529376740145/repo1/'
Scenario: MergeFeature without a feature issues a 400 status code: org/locationtech/geogig/repository/RepositoryResolverTestUtil
Given There is an empty repository named repo1(Scenario: MergeFeature without an "ours" id issues a 400 status code): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit2910073085238126811/repo1/'
Scenario: MergeFeature without an "ours" id issues a 400 status code: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit2910073085238126811/repo1/'
Scenario: MergeFeature without an "ours" id issues a 400 status code: org/locationtech/geogig/repository/RepositoryResolverTestUtil
Given There is a default multirepo server(Scenario: MergeFeature without a "theirs" id issues a 400 status code): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit6420752942749599699/repo1/'
Scenario: MergeFeature without a "theirs" id issues a 400 status code: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit6420752942749599699/repo1/'
Scenario: MergeFeature without a "theirs" id issues a 400 status code: org/locationtech/geogig/repository/RepositoryResolverTestUtil
Given There is a default multirepo server(Scenario: MergeFeature without any merges issues a 400 status code): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit6405347158971720041/repo1/'
Scenario: MergeFeature without any merges issues a 400 status code: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit6405347158971720041/repo1/'
Scenario: MergeFeature without any merges issues a 400 status code: org/locationtech/geogig/repository/RepositoryResolverTestUtil
Given There is a default multirepo server(Scenario: MergeFeature builds a new feature from provided merges using ours and theirs (both features are the same)): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit7302783700142652394/repo1/'
Scenario: MergeFeature builds a new feature from provided merges using ours and theirs (both features are the same): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit7302783700142652394/repo1/'
Scenario: MergeFeature builds a new feature from provided merges using ours and theirs (both features are the same): org/locationtech/geogig/repository/RepositoryResolverTestUtil
Given There is a default multirepo server(Scenario: MergeFeature builds a new feature from provided merges with custom values (both features are the same)): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit1448136354515148142/repo1/'
Scenario: MergeFeature builds a new feature from provided merges with custom values (both features are the same): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit1448136354515148142/repo1/'
Scenario: MergeFeature builds a new feature from provided merges with custom values (both features are the same): org/locationtech/geogig/repository/RepositoryResolverTestUtil
Given There is a default multirepo server(Scenario: MergeFeature builds a new feature from provided merges (different versions of the same feature)): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit773690821169476077/repo1/'
Scenario: MergeFeature builds a new feature from provided merges (different versions of the same feature): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit773690821169476077/repo1/'
Scenario: MergeFeature builds a new feature from provided merges (different versions of the same feature): org/locationtech/geogig/repository/RepositoryResolverTestUtil
Given There is an empty repository named repo1(Scenario: Verify wrong HTTP method issues 405 "Method not allowed"): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit681039507413021074/repo1/'
Scenario: Verify wrong HTTP method issues 405 "Method not allowed": Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit681039507413021074/repo1/'
Scenario: Verify wrong HTTP method issues 405 "Method not allowed": org/locationtech/geogig/repository/RepositoryResolverTestUtil
Scenario: ObjectExists outside of a repository issues 404 "Not found": org/locationtech/geogig/repository/RepositoryResolverTestUtil
Given There is an empty repository named repo1(Scenario: ObjectExists with no object id issues a 400 status code): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit7178314155505018562/repo1/'
Scenario: ObjectExists with no object id issues a 400 status code: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit7178314155505018562/repo1/'
Scenario: ObjectExists with no object id issues a 400 status code: org/locationtech/geogig/repository/RepositoryResolverTestUtil
Given There is an empty repository named repo1(Scenario: ObjectExists with an invalid object id issues a 400 status code): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit7910166201207062043/repo1/'
Scenario: ObjectExists with an invalid object id issues a 400 status code: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit7910166201207062043/repo1/'
Scenario: ObjectExists with an invalid object id issues a 400 status code: org/locationtech/geogig/repository/RepositoryResolverTestUtil
Given There is a default multirepo server(Scenario: ObjectExists with a nonexistent object id returns "0"): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit5018914854415325990/repo1/'
Scenario: ObjectExists with a nonexistent object id returns "0": Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit5018914854415325990/repo1/'
Scenario: ObjectExists with a nonexistent object id returns "0": org/locationtech/geogig/repository/RepositoryResolverTestUtil
Given There is a default multirepo server(Scenario: ObjectExists with an existing object id returns "1"): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit7140038969861135324/repo1/'
Scenario: ObjectExists with an existing object id returns "1": Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit7140038969861135324/repo1/'
Scenario: ObjectExists with an existing object id returns "1": org/locationtech/geogig/repository/RepositoryResolverTestUtil
Given There is an empty repository named repo1(Scenario: Verify wrong HTTP method issues 405 "Method not allowed"): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit6812317847202247998/repo1/'
Scenario: Verify wrong HTTP method issues 405 "Method not allowed": Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit6812317847202247998/repo1/'
Scenario: Verify wrong HTTP method issues 405 "Method not allowed": org/locationtech/geogig/repository/RepositoryResolverTestUtil
Scenario: Parents outside of a repository issues 404 "Not found": org/locationtech/geogig/repository/RepositoryResolverTestUtil
Given There is a default multirepo server(Scenario: Parents with an invalid commit issues a 400 status code): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit6448000408458055225/repo1/'
Scenario: Parents with an invalid commit issues a 400 status code: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit6448000408458055225/repo1/'
Scenario: Parents with an invalid commit issues a 400 status code: org/locationtech/geogig/repository/RepositoryResolverTestUtil
Given There is a default multirepo server(Scenario: Parents with no commit returns no parents): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit5535670808850383784/repo1/'
Scenario: Parents with no commit returns no parents: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit5535670808850383784/repo1/'
Scenario: Parents with no commit returns no parents: org/locationtech/geogig/repository/RepositoryResolverTestUtil
Given There is a default multirepo server(Scenario: Parents with a commit returns the parents of that commit): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit1662206177381264136/repo1/'
Scenario: Parents with a commit returns the parents of that commit: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit1662206177381264136/repo1/'
Scenario: Parents with a commit returns the parents of that commit: org/locationtech/geogig/repository/RepositoryResolverTestUtil
Given There is a default multirepo server(Scenario: Verify trying to create a repo issues 409 "Conflict" when a repo with the same name already exists): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit3610726165358590951/repo1/'
Scenario: Verify trying to create a repo issues 409 "Conflict" when a repo with the same name already exists: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit3610726165358590951/repo1/'
Scenario: Verify trying to create a repo issues 409 "Conflict" when a repo with the same name already exists: org/locationtech/geogig/repository/RepositoryResolverTestUtil
Given There is a default multirepo server(Scenario: Verify trying to create a repo issues 409 "Conflict" when a repo with the same name already exists, with parentDirectory): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit7128326525209296774/repo1/'
Scenario: Verify trying to create a repo issues 409 "Conflict" when a repo with the same name already exists, with parentDirectory: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit7128326525209296774/repo1/'
Scenario: Verify trying to create a repo issues 409 "Conflict" when a repo with the same name already exists, with parentDirectory: org/locationtech/geogig/repository/RepositoryResolverTestUtil
Given There is a default multirepo server(Scenario: Verify trying to create a repo issues 409 "Conflict" when a repo with the same name already exists, with arbitrary parentDirectory): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit7908850352920709197/repo1/'
Scenario: Verify trying to create a repo issues 409 "Conflict" when a repo with the same name already exists, with arbitrary parentDirectory: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit7908850352920709197/repo1/'
Scenario: Verify trying to create a repo issues 409 "Conflict" when a repo with the same name already exists, with arbitrary parentDirectory: org/locationtech/geogig/repository/RepositoryResolverTestUtil
Given There is a default multirepo server(Scenario: Calling rename issues a 400 status code): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit1799637397380945462/repo1/'
Scenario: Calling rename issues a 400 status code: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit1799637397380945462/repo1/'
Scenario: Calling rename issues a 400 status code: org/locationtech/geogig/repository/RepositoryResolverTestUtil
Given There is a default multirepo server(Scenario: Calling rename with json format issues a 400 status code): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit1334155734053402785/repo1/'
Scenario: Calling rename with json format issues a 400 status code: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit1334155734053402785/repo1/'
Scenario: Calling rename with json format issues a 400 status code: org/locationtech/geogig/repository/RepositoryResolverTestUtil
Given There is a default multirepo server(Scenario: Import of non existent repository fails): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit2290922593331588123/repo1/'
Scenario: Import of non existent repository fails: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit2290922593331588123/repo1/'
Scenario: Import of non existent repository fails: org/locationtech/geogig/repository/RepositoryResolverTestUtil
Given There is a default multirepo server(Scenario: Import of existent repository succeeds with an XML response): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit8411165381665065696/repo1/'
Scenario: Import of existent repository succeeds with an XML response: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit8411165381665065696/repo1/'
Scenario: Import of existent repository succeeds with an XML response: org/locationtech/geogig/repository/RepositoryResolverTestUtil
Given There is a default multirepo server(Scenario: Import of existent repository succeeds with a JSON response): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit2688808773175826389/repo1/'
Scenario: Import of existent repository succeeds with a JSON response: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit2688808773175826389/repo1/'
Scenario: Import of existent repository succeeds with a JSON response: org/locationtech/geogig/repository/RepositoryResolverTestUtil
Given There is a default multirepo server(Scenario: Import of existent repository with a name already in use fails with a 409 Conflict): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit3075523557077831546/repo1/'
Scenario: Import of existent repository with a name already in use fails with a 409 Conflict: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit3075523557077831546/repo1/'
Scenario: Import of existent repository with a name already in use fails with a 409 Conflict: org/locationtech/geogig/repository/RepositoryResolverTestUtil
testRemoveSingleFeature(org.geogig.geoserver.gwc.GWCIntegrationTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit66033481267771885/testrepo/'
createDataStoreCustomURIWithName(org.geogig.geoserver.rest.GeoGigGeoServerRESTntegrationTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit3037088018737075725/testrepo/'
createDataStoreNewConfig(org.geogig.geoserver.rest.GeoGigGeoServerRESTntegrationTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit4907045344526473598/new_repo/'
testGetBatchedObjects(org.geogig.geoserver.rest.GeoGigWebAPIIntegrationTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit4903664035954875003/testrepo/'
testRevObjectExists(org.geogig.geoserver.rest.GeoGigWebAPIIntegrationTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit284361919469713054/testrepo/'
testRemoteRemove(org.geogig.geoserver.rest.GeoGigWebAPIIntegrationTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit356532610270577678/testrepo/'
testRemoteUpdate(org.geogig.geoserver.rest.GeoGigWebAPIIntegrationTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit7405560229321753410/testrepo/'
testGetObject(org.geogig.geoserver.rest.GeoGigWebAPIIntegrationTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit5599547868518433873/testrepo/'
testGetManifest(org.geogig.geoserver.rest.GeoGigWebAPIIntegrationTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit1960405516705831912/testrepo/'
testRemoteAdd(org.geogig.geoserver.rest.GeoGigWebAPIIntegrationTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit6809837114442052920/testrepo/'
testImportExistingRocksDBRepo(org.geogig.geoserver.web.repository.RepositoryImportPanelTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit2557759596529956465/junit72417021685528573/.geogig'
testUpdateDoesntChangeFeatureType(org.geogig.geoserver.wfs.WFSIntegrationTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit8632811826344150661/repo-1326985400/'
testInsertDoesntChangeFeatureType(org.geogig.geoserver.wfs.WFSIntegrationTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit6904265809636968568/repo-1669194369/'
testInsert(org.geogig.geoserver.wfs.WFSIntegrationTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit1359718759631302885/repo-1651475147/'
testUpdate(org.geogig.geoserver.wfs.WFSIntegrationTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit241944664366347831/repo1153532248/'
testCommitsSurviveShutDown(org.geogig.geoserver.wfs.WFSIntegrationTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit8058545616676441871/repo1189361959/'
testGetAttribute_SpatialIndexWithExtraAttributes(org.geogig.geoserver.wms.GeoGigCatalogVisitorTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit6955387037353225466/testrepo/'
testGetAttribute_SapitalIndexOnly(org.geogig.geoserver.wms.GeoGigCatalogVisitorTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit7437015648500852281/testrepo/'
testAddGeogigLayerForcesCreationOfRootAuthURL(org.geogig.geoserver.wms.GeogigLayerIntegrationListenerTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit8487861046515920411/testrepo/'
testAddGeogigLayerAddsLayerIdentifierWithExplicitBranch(org.geogig.geoserver.wms.GeogigLayerIntegrationListenerTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit2073809661726472696/testrepo/'
testAddGeogigLayerAddsLayerIdentifier(org.geogig.geoserver.wms.GeogigLayerIntegrationListenerTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit7156536384392456144/testrepo/'
testRenameStore(org.geogig.geoserver.wms.GeogigLayerIntegrationListenerTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit1498965070753218379/testrepo/'
testRenameWorkspace(org.geogig.geoserver.wms.GeogigLayerIntegrationListenerTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit5111956658951532702/testrepo/'
testAddGeogigLayerAddsLayerIdentifierWithExplicitHead(org.geogig.geoserver.wms.GeogigLayerIntegrationListenerTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit5223380185158030612/testrepo/'
Tests run: 3457, Failures: 21, Errors: 974, Skipped: 2148
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 05:48 min
[INFO] Finished at: 2017-06-16T01:42:17+00:00
[INFO] Final Memory: 66M/551M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.12.3:test (default-test) on project gs-geogig: There are test failures.
[ERROR]
[ERROR] Please refer to <http://ares.boundlessgeo.com/jenkins/job/geoserver-2.10.x-geogig-plugin/ws/src/community/geogig/target/surefire-reports> for the individual test results.
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
Build step 'Invoke top-level Maven targets' marked build as failure
[Cucumber Tests] Parsing results.
[Cucumber Tests] parsing cucumber.json
