[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[geogig-dev] Build failed in Jenkins: geoserver-2.9.x-geogig-plugin #192
|
See <http://ares.boundlessgeo.com/jenkins/job/geoserver-2.9.x-geogig-plugin/192/>
------------------------------------------
[...truncated 213491 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/junit1977481124021621045/repo1/'
Scenario: Verify wrong HTTP method issues 405 "Method not allowed": Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit1977481124021621045/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/junit941221495950188563/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/junit941221495950188563/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/junit1418255170281115291/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/junit1418255170281115291/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/junit6062960113207724656/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/junit6062960113207724656/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/junit2292132380467372741/repo1/'
Scenario: Issuing a POST request to tag with valid parameters creates a tag: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit2292132380467372741/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/junit1499280921836121346/repo1/'
Scenario: Issuing a GET request to tag lists all tags: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit1499280921836121346/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/junit2953550243338190446/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/junit2953550243338190446/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/junit5797035981487794538/repo1/'
Scenario: Issuing a DELETE request to tag deletes the tag: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit5797035981487794538/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/junit3782393973406740632/repo1/'
Scenario: Verify wrong HTTP method on begin transaction issues 405 "Method not allowed": Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit3782393973406740632/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/junit2757016474489387169/repo1/'
Scenario: Verify wrong HTTP method on end transaction issues 405 "Method not allowed": Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit2757016474489387169/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/junit2115875616183688964/repo1/'
Scenario: Ending a transaction outside of a transaction issues 500 "Transaction required": Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit2115875616183688964/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/junit1922157619922166518/repo1/'
Scenario: Work on a transaction does not affect the main repository: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit1922157619922166518/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/junit2744937103663825656/repo1/'
Scenario: Ending a transaction moves the work to the main repository: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit2744937103663825656/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/junit4967675950372245340/repo1/'
Scenario: Canceling a transaction leaves the main repository without changes: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit4967675950372245340/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/junit3333313932205314789/repo1/'
Scenario: Ending a transaction with conflicting changes returns details of the conflict: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit3333313932205314789/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/junit3315324652241425466/repo1/'
Scenario: Fixing transaction conflicts and ending again is successful: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit3315324652241425466/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/junit4352470400715724233/repo1/'
Scenario: Verify wrong HTTP method issues 405 "Method not allowed": Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit4352470400715724233/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/junit4680841091848403014/repo1/'
Scenario: Calling UpdateRef without a ref name issues a 500 status code: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit4680841091848403014/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/junit1302914369745108252/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/junit1302914369745108252/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/junit3587059258556592151/repo1/'
Scenario: Calling UpdateRef without a nonexistent name issues a 500 status code: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit3587059258556592151/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/junit8523872578163875623/repo1/'
Scenario: Calling UpdateRef with a new value updates the ref: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit8523872578163875623/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/junit7131821367993538396/repo1/'
Scenario: Calling UpdateRef with the delete parameter deletes the ref: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit7131821367993538396/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/junit7189794700087220842/repo1/'
Scenario: Verify wrong HTTP method issues 405 "Method not allowed": Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit7189794700087220842/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/junit2548919581794694579/repo1/'
Scenario: Version returns geogig version details: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit2548919581794694579/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/junit7932307792610555770/repo1/'
Scenario: Verify wrong HTTP method issues 405 "Method not allowed": Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit7932307792610555770/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/junit2418956208925904691/repo1/'
Scenario: AffectedFeatures with no commit issues a 400 status code: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit2418956208925904691/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/junit2197312524674702353/repo1/'
Scenario: AffectedFeatures with an invalid commit issues a 400 status code: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit2197312524674702353/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/junit7423928249995193574/repo1/'
Scenario: AffectedFeatures lists all features changed in a commit: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit7423928249995193574/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/junit2975247146065237444/repo1/'
Scenario: Verify wrong HTTP method issues 405 "Method not allowed": Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit2975247146065237444/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/junit707466727402957613/repo1/'
Scenario: Depth with an invalid commit issues a 400 status code: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit707466727402957613/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/junit4086658893082589257/repo1/'
Scenario: Depth with no commit returns no depth for a non-shallow repository: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit4086658893082589257/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/junit7269604849065984148/full/'
Scenario: Depth with no commit returns the depth of a shallow repository: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit7269604849065984148/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/junit3339897117130629205/repo1/'
Scenario: Depth with a commit returns the number of ancestors that commit has: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit3339897117130629205/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/junit8684158512316947678/repo1/'
Scenario: Verify wrong HTTP method issues 405 "Method not allowed": Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit8684158512316947678/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/junit5205619459309293275/repo1/'
Scenario: Manifest lists all of the branches in the repository: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit5205619459309293275/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/junit7825510964281635067/repo1/'
Scenario: Manifest also lists remote branches when the remotes parameter is specified: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit7825510964281635067/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/junit8580085009680957037/repo1/'
Scenario: Verify wrong HTTP method issues 405 "Method not allowed": Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit8580085009680957037/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/junit1836043442601902319/repo1/'
Scenario: MergeFeature with no json payload issues a 400 status code: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit1836043442601902319/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/junit613794865938281302/repo1/'
Scenario: MergeFeature with an invalid json payload issues a 400 status code: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit613794865938281302/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/junit5610867857443850404/repo1/'
Scenario: MergeFeature without a feature issues a 400 status code: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit5610867857443850404/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/junit4872068718534730562/repo1/'
Scenario: MergeFeature without an "ours" id issues a 400 status code: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit4872068718534730562/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/junit9119533286559402579/repo1/'
Scenario: MergeFeature without a "theirs" id issues a 400 status code: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit9119533286559402579/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/junit4490470546114908055/repo1/'
Scenario: MergeFeature without any merges issues a 400 status code: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit4490470546114908055/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/junit5348243799973568160/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/junit5348243799973568160/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/junit6618514943740228551/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/junit6618514943740228551/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/junit9181368796423102338/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/junit9181368796423102338/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/junit8263163847801583598/repo1/'
Scenario: Verify wrong HTTP method issues 405 "Method not allowed": Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit8263163847801583598/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/junit4118807775026462696/repo1/'
Scenario: ObjectExists with no object id issues a 400 status code: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit4118807775026462696/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/junit4049731269150185707/repo1/'
Scenario: ObjectExists with an invalid object id issues a 400 status code: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit4049731269150185707/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/junit4843124693574110238/repo1/'
Scenario: ObjectExists with a nonexistent object id returns "0": Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit4843124693574110238/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/junit2102379875475374736/repo1/'
Scenario: ObjectExists with an existing object id returns "1": Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit2102379875475374736/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/junit719016745708544297/repo1/'
Scenario: Verify wrong HTTP method issues 405 "Method not allowed": Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit719016745708544297/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/junit3105883397638725447/repo1/'
Scenario: Parents with an invalid commit issues a 400 status code: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit3105883397638725447/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/junit744473403785050591/repo1/'
Scenario: Parents with no commit returns no parents: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit744473403785050591/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/junit3222006444952082034/repo1/'
Scenario: Parents with a commit returns the parents of that commit: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit3222006444952082034/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/junit6730439122530931485/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/junit6730439122530931485/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/junit4806878075806448962/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/junit4806878075806448962/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/junit1558508569597636619/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/junit1558508569597636619/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/junit257462952278897949/repo1/'
Scenario: Calling rename issues a 400 status code: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit257462952278897949/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/junit9099492721857531447/repo1/'
Scenario: Calling rename with json format issues a 400 status code: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit9099492721857531447/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/junit266596670292901954/repo1/'
Scenario: Import of non existent repository fails: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit266596670292901954/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/junit8408918626449764280/repo1/'
Scenario: Import of existent repository succeeds with an XML response: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit8408918626449764280/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/junit1431885029832021556/repo1/'
Scenario: Import of existent repository succeeds with a JSON response: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit1431885029832021556/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/junit2389468244289083296/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/junit2389468244289083296/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/junit6511691224530282995/testrepo/'
createDataStoreCustomURIWithName(org.geogig.geoserver.rest.GeoGigGeoServerRESTntegrationTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit6614988097872871503/testrepo/'
createDataStoreNewConfig(org.geogig.geoserver.rest.GeoGigGeoServerRESTntegrationTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit1283529491109693822/new_repo/'
testGetBatchedObjects(org.geogig.geoserver.rest.GeoGigWebAPIIntegrationTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit2366401624043534890/testrepo/'
testRevObjectExists(org.geogig.geoserver.rest.GeoGigWebAPIIntegrationTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit1917605190435500974/testrepo/'
testRemoteRemove(org.geogig.geoserver.rest.GeoGigWebAPIIntegrationTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit5075575368254037456/testrepo/'
testRemoteUpdate(org.geogig.geoserver.rest.GeoGigWebAPIIntegrationTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit2513138551800810774/testrepo/'
testGetObject(org.geogig.geoserver.rest.GeoGigWebAPIIntegrationTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit4056234711231195037/testrepo/'
testGetManifest(org.geogig.geoserver.rest.GeoGigWebAPIIntegrationTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit4414585555401894064/testrepo/'
testRemoteAdd(org.geogig.geoserver.rest.GeoGigWebAPIIntegrationTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit6435569304812598266/testrepo/'
testImportExistingRocksDBRepo(org.geogig.geoserver.web.repository.RepositoryImportPanelTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit2327014486998822079/junit8961708145474588438/.geogig'
testUpdateDoesntChangeFeatureType(org.geogig.geoserver.wfs.WFSIntegrationTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit7253397272980427775/repo-160429343/'
testInsertDoesntChangeFeatureType(org.geogig.geoserver.wfs.WFSIntegrationTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit6909610716584287736/repo-816818865/'
testInsert(org.geogig.geoserver.wfs.WFSIntegrationTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit6218340927540152439/repo367240553/'
testUpdate(org.geogig.geoserver.wfs.WFSIntegrationTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit6477663133242337095/repo-1781985320/'
testCommitsSurviveShutDown(org.geogig.geoserver.wfs.WFSIntegrationTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit8525590286038568355/repo1907773284/'
testGetAttribute_SpatialIndexWithExtraAttributes(org.geogig.geoserver.wms.GeoGigCatalogVisitorTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit8818038414496996674/testrepo/'
testGetAttribute_SapitalIndexOnly(org.geogig.geoserver.wms.GeoGigCatalogVisitorTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit5328257001371315811/testrepo/'
testAddGeogigLayerForcesCreationOfRootAuthURL(org.geogig.geoserver.wms.GeogigLayerIntegrationListenerTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit8137751119418797485/testrepo/'
testAddGeogigLayerAddsLayerIdentifierWithExplicitBranch(org.geogig.geoserver.wms.GeogigLayerIntegrationListenerTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit887240396328331470/testrepo/'
testAddGeogigLayerAddsLayerIdentifier(org.geogig.geoserver.wms.GeogigLayerIntegrationListenerTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit86983181240314767/testrepo/'
testRenameStore(org.geogig.geoserver.wms.GeogigLayerIntegrationListenerTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit2442106524625930447/testrepo/'
testRenameWorkspace(org.geogig.geoserver.wms.GeogigLayerIntegrationListenerTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit8219956158183361751/testrepo/'
testAddGeogigLayerAddsLayerIdentifierWithExplicitHead(org.geogig.geoserver.wms.GeogigLayerIntegrationListenerTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit1529029777395846065/testrepo/'
Tests run: 3457, Failures: 21, Errors: 974, Skipped: 2148
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 05:55 min
[INFO] Finished at: 2017-06-16T01:36:17+00:00
[INFO] Final Memory: 65M/563M
[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.9.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
