[geogig-dev] Build failed in Jenkins: geoserver-2.11.x-geogig-plugin #11

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[geogig-dev] Build failed in Jenkins: geoserver-2.11.x-geogig-plugin #118
From: monitor@xxxxxxxxxxxxxxxx
Date: Fri, 16 Jun 2017 01:48:13 +0000 (UTC)
Delivered-to: geogig-dev@xxxxxxxxxxxxxxxx
List-archive: <https://dev.locationtech.org/mailman/private/geogig-dev>
List-help: <mailto:geogig-dev-request@locationtech.org?subject=help>
List-subscribe: <https://dev.locationtech.org/mailman/listinfo/geogig-dev>, <mailto:geogig-dev-request@locationtech.org?subject=subscribe>
List-unsubscribe: <https://dev.locationtech.org/mailman/options/geogig-dev>, <mailto:geogig-dev-request@locationtech.org?subject=unsubscribe>
See <http://ares.boundlessgeo.com/jenkins/job/geoserver-2.11.x-geogig-plugin/118/>

------------------------------------------
[...truncated 213476 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/junit7842320745320629028/repo1/'
  Scenario: Verify wrong HTTP method issues 405 "Method not allowed": Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit7842320745320629028/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/junit8776389744030451788/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/junit8776389744030451788/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/junit86628751891269190/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/junit86628751891269190/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/junit6598088483330861696/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/junit6598088483330861696/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/junit5518666893187320328/repo1/'
  Scenario: Issuing a POST request to tag with valid parameters creates a tag: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit5518666893187320328/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/junit4312089111761882448/repo1/'
  Scenario: Issuing a GET request to tag lists all tags: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit4312089111761882448/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/junit8553203993013914129/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/junit8553203993013914129/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/junit2866556576165529441/repo1/'
  Scenario: Issuing a DELETE request to tag deletes the tag: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit2866556576165529441/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/junit1435832216971240580/repo1/'
  Scenario: Verify wrong HTTP method on begin transaction issues 405 "Method not allowed": Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit1435832216971240580/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/junit1606160522046954175/repo1/'
  Scenario: Verify wrong HTTP method on end transaction issues 405 "Method not allowed": Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit1606160522046954175/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/junit4811814002546603346/repo1/'
  Scenario: Ending a transaction outside of a transaction issues 500 "Transaction required": Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit4811814002546603346/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/junit6615295068499872553/repo1/'
  Scenario: Work on a transaction does not affect the main repository: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit6615295068499872553/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/junit8317482112936900166/repo1/'
  Scenario: Ending a transaction moves the work to the main repository: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit8317482112936900166/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/junit2371584043201288844/repo1/'
  Scenario: Canceling a transaction leaves the main repository without changes: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit2371584043201288844/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/junit5975673949655947735/repo1/'
  Scenario: Ending a transaction with conflicting changes returns details of the conflict: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit5975673949655947735/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/junit2616182014681175743/repo1/'
  Scenario: Fixing transaction conflicts and ending again is successful: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit2616182014681175743/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/junit5176539581204097317/repo1/'
  Scenario: Verify wrong HTTP method issues 405 "Method not allowed": Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit5176539581204097317/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/junit8601704108323367655/repo1/'
  Scenario: Calling UpdateRef without a ref name issues a 500 status code: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit8601704108323367655/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/junit4689641704784029199/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/junit4689641704784029199/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/junit5989537509255213571/repo1/'
  Scenario: Calling UpdateRef without a nonexistent name issues a 500 status code: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit5989537509255213571/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/junit5174918875625099586/repo1/'
  Scenario: Calling UpdateRef with a new value updates the ref: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit5174918875625099586/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/junit7698410048804087592/repo1/'
  Scenario: Calling UpdateRef with the delete parameter deletes the ref: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit7698410048804087592/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/junit6958360101105499302/repo1/'
  Scenario: Verify wrong HTTP method issues 405 "Method not allowed": Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit6958360101105499302/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/junit6488755701478300695/repo1/'
  Scenario: Version returns geogig version details: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit6488755701478300695/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/junit394675100291222339/repo1/'
  Scenario: Verify wrong HTTP method issues 405 "Method not allowed": Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit394675100291222339/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/junit8593622465500321145/repo1/'
  Scenario: AffectedFeatures with no commit issues a 400 status code: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit8593622465500321145/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/junit3804639204638906330/repo1/'
  Scenario: AffectedFeatures with an invalid commit issues a 400 status code: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit3804639204638906330/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/junit3198633783130471649/repo1/'
  Scenario: AffectedFeatures lists all features changed in a commit: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit3198633783130471649/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/junit1667650822261710848/repo1/'
  Scenario: Verify wrong HTTP method issues 405 "Method not allowed": Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit1667650822261710848/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/junit9167007708619529019/repo1/'
  Scenario: Depth with an invalid commit issues a 400 status code: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit9167007708619529019/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/junit3900083688664780185/repo1/'
  Scenario: Depth with no commit returns no depth for a non-shallow repository: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit3900083688664780185/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/junit8645751019071652484/full/'
  Scenario: Depth with no commit returns the depth of a shallow repository: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit8645751019071652484/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/junit1637833110734599537/repo1/'
  Scenario: Depth with a commit returns the number of ancestors that commit has: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit1637833110734599537/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/junit8349914972308153735/repo1/'
  Scenario: Verify wrong HTTP method issues 405 "Method not allowed": Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit8349914972308153735/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/junit444193810419807247/repo1/'
  Scenario: Manifest lists all of the branches in the repository: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit444193810419807247/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/junit7960092764780139620/repo1/'
  Scenario: Manifest also lists remote branches when the remotes parameter is specified: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit7960092764780139620/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/junit883590628264730349/repo1/'
  Scenario: Verify wrong HTTP method issues 405 "Method not allowed": Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit883590628264730349/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/junit4787816597662444067/repo1/'
  Scenario: MergeFeature with no json payload issues a 400 status code: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit4787816597662444067/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/junit3494238937188001499/repo1/'
  Scenario: MergeFeature with an invalid json payload issues a 400 status code: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit3494238937188001499/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/junit7768404094857374380/repo1/'
  Scenario: MergeFeature without a feature issues a 400 status code: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit7768404094857374380/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/junit4740894802803805704/repo1/'
  Scenario: MergeFeature without an "ours" id issues a 400 status code: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit4740894802803805704/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/junit2097597818822707262/repo1/'
  Scenario: MergeFeature without a "theirs" id issues a 400 status code: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit2097597818822707262/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/junit8305917816306892168/repo1/'
  Scenario: MergeFeature without any merges issues a 400 status code: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit8305917816306892168/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/junit1545743593012665549/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/junit1545743593012665549/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/junit5418431527706239334/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/junit5418431527706239334/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/junit5391930975140305989/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/junit5391930975140305989/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/junit5018551903207890825/repo1/'
  Scenario: Verify wrong HTTP method issues 405 "Method not allowed": Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit5018551903207890825/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/junit859251445865781222/repo1/'
  Scenario: ObjectExists with no object id issues a 400 status code: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit859251445865781222/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/junit1430825739386525233/repo1/'
  Scenario: ObjectExists with an invalid object id issues a 400 status code: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit1430825739386525233/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/junit4399390376883681956/repo1/'
  Scenario: ObjectExists with a nonexistent object id returns "0": Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit4399390376883681956/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/junit5865360282772660863/repo1/'
  Scenario: ObjectExists with an existing object id returns "1": Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit5865360282772660863/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/junit6664953025710773432/repo1/'
  Scenario: Verify wrong HTTP method issues 405 "Method not allowed": Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit6664953025710773432/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/junit7721082838765346/repo1/'
  Scenario: Parents with an invalid commit issues a 400 status code: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit7721082838765346/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/junit6936886235343345228/repo1/'
  Scenario: Parents with no commit returns no parents: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit6936886235343345228/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/junit1386995235392375441/repo1/'
  Scenario: Parents with a commit returns the parents of that commit: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit1386995235392375441/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/junit2473307616545436493/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/junit2473307616545436493/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/junit3845727506139968251/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/junit3845727506139968251/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/junit4722855565856528287/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/junit4722855565856528287/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/junit2200051118546410518/repo1/'
  Scenario: Calling rename issues a 400 status code: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit2200051118546410518/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/junit4065458747085904927/repo1/'
  Scenario: Calling rename with json format issues a 400 status code: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit4065458747085904927/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/junit827770268196915974/repo1/'
  Scenario: Import of non existent repository fails: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit827770268196915974/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/junit17580521028061942/repo1/'
  Scenario: Import of existent repository succeeds with an XML response: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit17580521028061942/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/junit6948817667998178063/repo1/'
  Scenario: Import of existent repository succeeds with a JSON response: Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit6948817667998178063/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/junit6536264820924339937/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/junit6536264820924339937/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/junit4636716554307479447/testrepo/'
  createDataStoreCustomURIWithName(org.geogig.geoserver.rest.GeoGigGeoServerRESTntegrationTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit7183498868409132768/testrepo/'
  createDataStoreNewConfig(org.geogig.geoserver.rest.GeoGigGeoServerRESTntegrationTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit6371256892826784376/new_repo/'
  testGetBatchedObjects(org.geogig.geoserver.rest.GeoGigWebAPIIntegrationTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit2930143869702676896/testrepo/'
  testRevObjectExists(org.geogig.geoserver.rest.GeoGigWebAPIIntegrationTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit6486768190261289784/testrepo/'
  testRemoteRemove(org.geogig.geoserver.rest.GeoGigWebAPIIntegrationTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit2476765380827288845/testrepo/'
  testRemoteUpdate(org.geogig.geoserver.rest.GeoGigWebAPIIntegrationTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit7170142102298912713/testrepo/'
  testGetObject(org.geogig.geoserver.rest.GeoGigWebAPIIntegrationTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit1807808215800938667/testrepo/'
  testGetManifest(org.geogig.geoserver.rest.GeoGigWebAPIIntegrationTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit6601176784406506664/testrepo/'
  testRemoteAdd(org.geogig.geoserver.rest.GeoGigWebAPIIntegrationTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit4308497909695661824/testrepo/'
  testImportExistingRocksDBRepo(org.geogig.geoserver.web.repository.RepositoryImportPanelTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit6634411887325445089/junit7233877800182052555/.geogig'
  testUpdateDoesntChangeFeatureType(org.geogig.geoserver.wfs.WFSIntegrationTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit8660944717075428939/repo964383381/'
  testInsertDoesntChangeFeatureType(org.geogig.geoserver.wfs.WFSIntegrationTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit319848087255306798/repo-18185671/'
  testInsert(org.geogig.geoserver.wfs.WFSIntegrationTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit612926304385486381/repo-165209602/'
  testUpdate(org.geogig.geoserver.wfs.WFSIntegrationTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit5932744607228427334/repo1123549875/'
  testCommitsSurviveShutDown(org.geogig.geoserver.wfs.WFSIntegrationTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit505619236272415258/repo1392195347/'
  testGetAttribute_SpatialIndexWithExtraAttributes(org.geogig.geoserver.wms.GeoGigCatalogVisitorTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit1601648124778506510/testrepo/'
  testGetAttribute_SapitalIndexOnly(org.geogig.geoserver.wms.GeoGigCatalogVisitorTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit8134463127929059090/testrepo/'
  testAddGeogigLayerForcesCreationOfRootAuthURL(org.geogig.geoserver.wms.GeogigLayerIntegrationListenerTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit860257001330783868/testrepo/'
  testAddGeogigLayerAddsLayerIdentifierWithExplicitBranch(org.geogig.geoserver.wms.GeogigLayerIntegrationListenerTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit3724938486460610999/testrepo/'
  testAddGeogigLayerAddsLayerIdentifier(org.geogig.geoserver.wms.GeogigLayerIntegrationListenerTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit3670503480228152959/testrepo/'
  testRenameStore(org.geogig.geoserver.wms.GeogigLayerIntegrationListenerTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit7621717413044044496/testrepo/'
  testRenameWorkspace(org.geogig.geoserver.wms.GeogigLayerIntegrationListenerTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit3859902175637115303/testrepo/'
  testAddGeogigLayerAddsLayerIdentifierWithExplicitHead(org.geogig.geoserver.wms.GeogigLayerIntegrationListenerTest): Can't access repository at 'file:/mnt/memtmp/geogig-geoserver/junit3975613022891775892/testrepo/'

Tests run: 3457, Failures: 21, Errors: 974, Skipped: 2148

[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 05:31 min
[INFO] Finished at: 2017-06-16T01:48:11+00:00
[INFO] Final Memory: 66M/552M
[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.11.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
Prev by Date: [geogig-dev] Build failed in Jenkins: geoserver-2.10.x-geogig-plugin #196
Next by Date: [geogig-dev] Jenkins build is back to stable : geogig-plugins-master » Openstreetmap extension #137
Previous by thread: [geogig-dev] Build failed in Jenkins: geoserver-2.10.x-geogig-plugin #196
Next by thread: [geogig-dev] Build failed in Jenkins: geoserver-2.10.x-geogig-plugin #199
Index(es):
- Date
- Thread
Breadcrumbs
