[geogig-dev] Build failed in Jenkins: geoserver-2.9.x-geogig-plugin #106

[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 #106
From: monitor@xxxxxxxxxxxxxxxx
Date: Thu, 23 Feb 2017 19:57:06 +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.9.x-geogig-plugin/106/>

------------------------------------------
[...truncated 102932 lines...]
  Scenario: Supplying the add parameter without a remote url issues a 500 status code: java.io.IOException
  Given There is a default multirepo server with remotes(Scenario: Supplying add with valid parameters adds a new remote): java.io.IOException
  Scenario: Supplying add with valid parameters adds a new remote: java.io.IOException
  Given There is an empty repository named repo1(Scenario: Verify wrong HTTP method issues 405 "Method not allowed"): java.io.IOException
  Scenario: Verify wrong HTTP method issues 405 "Method not allowed": java.io.IOException
  Given There is an empty repository named repo1(Scenario: Removing outside of a transaction issues 500 "Transaction required"): java.io.IOException
  Scenario: Removing outside of a transaction issues 500 "Transaction required": java.io.IOException
  Given There is an empty repository named repo1(Scenario: Removing with no path issues a 500 status code): java.io.IOException
  Scenario: Removing with no path issues a 500 status code: java.io.IOException
  Given There is a default multirepo server(Scenario: Removing with a feature path removes the specified feature): java.io.IOException
  Scenario: Removing with a feature path removes the specified feature: java.io.IOException
  Given There is a default multirepo server(Scenario: Removing with a tree path and no recursive parameter issues a 400 status code): java.io.IOException
  Scenario: Removing with a tree path and no recursive parameter issues a 400 status code: java.io.IOException
  Given There is a default multirepo server(Scenario: Removing with a tree path and the recursive parameter removes the specified feature tree): java.io.IOException
  Scenario: Removing with a tree path and the recursive parameter removes the specified feature tree: java.io.IOException
  Given There is a default multirepo server(Scenario: Calling rename on a repo using the wrong HTTP method issues 405 "Method not allowed"): java.io.IOException
  Scenario: Calling rename on a repo using the wrong HTTP method issues 405 "Method not allowed": java.io.IOException
  Given There is a default multirepo server(Scenario: Trying to assign a duplicated name to a repo issues 400 "Bad request"): java.io.IOException
  Scenario: Trying to assign a duplicated name to a repo issues 400 "Bad request": java.io.IOException
  Given There is a default multirepo server(Scenario: Renaming a repository returns a link to the new location issues 301 "Moved permanently"): java.io.IOException
  Scenario: Renaming a repository returns a link to the new location issues 301 "Moved permanently": java.io.IOException
  Given There is a default multirepo server(Scenario: Calling rename on a repo using the wrong HTTP method issues 405 "Method not allowed", JSON requested response): java.io.IOException
  Scenario: Calling rename on a repo using the wrong HTTP method issues 405 "Method not allowed", JSON requested response: java.io.IOException
  Given There is a default multirepo server(Scenario: Trying to assign a duplicated name to a repo issues 400 "Bad request", JSON requested response): java.io.IOException
  Scenario: Trying to assign a duplicated name to a repo issues 400 "Bad request", JSON requested response: java.io.IOException
  Given There is a default multirepo server(Scenario: Renaming a repository returns a link to the new location issues 301 "Moved permanently", JSON requested response): java.io.IOException
  Scenario: Renaming a repository returns a link to the new location issues 301 "Moved permanently", JSON requested response: java.io.IOException
  Given There is an empty repository named repo1(Scenario: Verify wrong HTTP method issues 405 "Method not allowed"): java.io.IOException
  Scenario: Verify wrong HTTP method issues 405 "Method not allowed": java.io.IOException
  Given There is an empty repository named repo1(Scenario: Calling ReportMergeScenario with no "our" commit issues a 500 status code): java.io.IOException
  Scenario: Calling ReportMergeScenario with no "our" commit issues a 500 status code: java.io.IOException
  Given There is an empty repository named repo1(Scenario: Calling ReportMergeScenario with no "their" commit issues a 500 status code): java.io.IOException
  Scenario: Calling ReportMergeScenario with no "their" commit issues a 500 status code: java.io.IOException
  Given There is a repository with multiple branches named repo1(Scenario: Calling ReportMergeScenario with an invalid "our" commit issues a 500 status code): java.io.IOException
  Scenario: Calling ReportMergeScenario with an invalid "our" commit issues a 500 status code: java.io.IOException
  Given There is a repository with multiple branches named repo1(Scenario: Calling ReportMergeScenario with an invalid "their" commit issues a 500 status code): java.io.IOException
  Scenario: Calling ReportMergeScenario with an invalid "their" commit issues a 500 status code: java.io.IOException
  Given There is a repository with multiple branches named repo1(Scenario: ReportMergeScenario with two valid commits returns the details of the merge): java.io.IOException
  Scenario: ReportMergeScenario with two valid commits returns the details of the merge: java.io.IOException
  Given There is a repository with multiple branches named repo1(Scenario: ReportMergeScenario with conflicting commits returns the details of the merge): java.io.IOException
  Scenario: ReportMergeScenario with conflicting commits returns the details of the merge: java.io.IOException
  Given There is a default multirepo server(Scenario: ReportMergeScenario supports paging): java.io.IOException
  Scenario: ReportMergeScenario supports paging: java.io.IOException
  Given There is an empty repository named repo1(Scenario: Verify wrong HTTP method issues 405 "Method not allowed"): java.io.IOException
  Scenario: Verify wrong HTTP method issues 405 "Method not allowed": java.io.IOException
  Given There is an empty repository named repo1(Scenario: ResolveConflict outside of a transaction issues 500 "Transaction required"): java.io.IOException
  Scenario: ResolveConflict outside of a transaction issues 500 "Transaction required": java.io.IOException
  Given There is an empty repository named repo1(Scenario: ResolveConflict without a path issues a 500 status code): java.io.IOException
  Scenario: ResolveConflict without a path issues a 500 status code: java.io.IOException
  Given There is an empty repository named repo1(Scenario: ResolveConflict without an object ID issues a 500 status code): java.io.IOException
  Scenario: ResolveConflict without an object ID issues a 500 status code: java.io.IOException
  Given There is an empty repository named repo1(Scenario: ResolveConflict with an invalid path issues a 400 status code): java.io.IOException
  Scenario: ResolveConflict with an invalid path issues a 400 status code: java.io.IOException
  Given There is an empty repository named repo1(Scenario: ResolveConflict with valid parameters resolves the conflict): java.io.IOException
  Scenario: ResolveConflict with valid parameters resolves the conflict: java.io.IOException
  Given There is an empty repository named repo1(Scenario: Verify wrong HTTP method issues 405 "Method not allowed"): java.io.IOException
  Scenario: Verify wrong HTTP method issues 405 "Method not allowed": java.io.IOException
  Given There is an empty repository named repo1(Scenario: RevertFeature outside of a transaction issues 500 "Transaction required"): java.io.IOException
  Scenario: RevertFeature outside of a transaction issues 500 "Transaction required": java.io.IOException
  Given There is an empty repository named repo1(Scenario: RevertFeature without a path issues a 500 status code): java.io.IOException
  Scenario: RevertFeature without a path issues a 500 status code: java.io.IOException
  Given There is an empty repository named repo1(Scenario: RevertFeature without a new commit ID issues a 500 status code): java.io.IOException
  Scenario: RevertFeature without a new commit ID issues a 500 status code: java.io.IOException
  Given There is a default multirepo server(Scenario: RevertFeature without an old commit ID issues a 500 status code): java.io.IOException
  Scenario: RevertFeature without an old commit ID issues a 500 status code: java.io.IOException
  Given There is a default multirepo server(Scenario: RevertFeature with an invalid path issues a 500 status code): java.io.IOException
  Scenario: RevertFeature with an invalid path issues a 500 status code: java.io.IOException
  Given There is a default multirepo server(Scenario: RevertFeature on an added feature removes that feature): java.io.IOException
  Scenario: RevertFeature on an added feature removes that feature: java.io.IOException
  Given There is an empty repository named repo1(Scenario: RevertFeature on a modified feature undoes the change): java.io.IOException
  Scenario: RevertFeature on a modified feature undoes the change: java.io.IOException
  Given There is a repository with multiple branches named repo1(Scenario: RevertFeature on a removed feature adds it back): java.io.IOException
  Scenario: RevertFeature on a removed feature adds it back: java.io.IOException
  Given There is a repository with multiple branches named repo1(Scenario: If a feature has changed since the 'new' commit id, conflicts may be thrown): java.io.IOException
  Scenario: If a feature has changed since the 'new' commit id, conflicts may be thrown: java.io.IOException
  Given There is an empty repository named repo1(Scenario: Supplying author information applies to the reverted commit as well as the merge commit): java.io.IOException
  Scenario: Supplying author information applies to the reverted commit as well as the merge commit: java.io.IOException
  Given There is an empty repository named repo1(Scenario: Supplying a commit message applies to the revert commit): java.io.IOException
  Scenario: Supplying a commit message applies to the revert commit: java.io.IOException
  Given There is an empty repository named repo1(Scenario: Supplying a merge message applies to the merge commit): java.io.IOException
  Scenario: Supplying a merge message applies to the merge commit: java.io.IOException
  Given There is an empty repository named repo1(Scenario: Verify wrong HTTP method issues 405 "Method not allowed"): java.io.IOException
  Scenario: Verify wrong HTTP method issues 405 "Method not allowed": java.io.IOException
  Given There is a default multirepo server(Scenario: Statistics summarizes the changes made to the repository): java.io.IOException
  Scenario: Statistics summarizes the changes made to the repository: java.io.IOException
  Given There is a default multirepo server(Scenario: Statistics summarizes the changes since a particular timestamp up to a specific commit): java.io.IOException
  Scenario: Statistics summarizes the changes since a particular timestamp up to a specific commit: java.io.IOException
  Given There is a default multirepo server(Scenario: Statistics can summarize the changes made to a specific path): java.io.IOException
  Scenario: Statistics can summarize the changes made to a specific path: java.io.IOException
  Given There is an empty repository named repo1(Scenario: Verify wrong HTTP method issues 405 "Method not allowed"): java.io.IOException
  Scenario: Verify wrong HTTP method issues 405 "Method not allowed": java.io.IOException
  Given There is an empty repository named repo1(Scenario: Status shows the current branch and all staged and unstaged features): java.io.IOException
  Scenario: Status shows the current branch and all staged and unstaged features: java.io.IOException
  Given There is an empty repository named repo1(Scenario: Status shows conflicted features): java.io.IOException
  Scenario: Status shows conflicted features: java.io.IOException
  Given There is an empty repository named repo1(Scenario: Verify wrong HTTP method issues 405 "Method not allowed"): java.io.IOException
  Scenario: Verify wrong HTTP method issues 405 "Method not allowed": java.io.IOException
  Given There is an empty repository named repo1(Scenario: Issuing a POST request to tag without a name issues a 500 status code): java.io.IOException
  Scenario: Issuing a POST request to tag without a name issues a 500 status code: java.io.IOException
  Given There is an empty repository named repo1(Scenario: Issuing a POST request to tag without a commit issues a 500 status code): java.io.IOException
  Scenario: Issuing a POST request to tag without a commit issues a 500 status code: java.io.IOException
  Given There is an empty repository named repo1(Scenario: Issuing a POST request to tag with an invalid commit issues a 500 status code): java.io.IOException
  Scenario: Issuing a POST request to tag with an invalid commit issues a 500 status code: java.io.IOException
  Given There is a default multirepo server(Scenario: Issuing a POST request to tag with valid parameters creates a tag): java.io.IOException
  Scenario: Issuing a POST request to tag with valid parameters creates a tag: java.io.IOException
  Given There is a default multirepo server(Scenario: Issuing a GET request to tag lists all tags): java.io.IOException
  Scenario: Issuing a GET request to tag lists all tags: java.io.IOException
  Given There is an empty repository named repo1(Scenario: Issuing a DELETE request to tag without a name issues a 500 status code): java.io.IOException
  Scenario: Issuing a DELETE request to tag without a name issues a 500 status code: java.io.IOException
  Given There is a default multirepo server(Scenario: Issuing a DELETE request to tag deletes the tag): java.io.IOException
  Scenario: Issuing a DELETE request to tag deletes the tag: java.io.IOException
  Given There is an empty repository named repo1(Scenario: Verify wrong HTTP method on begin transaction issues 405 "Method not allowed"): java.io.IOException
  Scenario: Verify wrong HTTP method on begin transaction issues 405 "Method not allowed": java.io.IOException
  Given There is an empty repository named repo1(Scenario: Verify wrong HTTP method on end transaction issues 405 "Method not allowed"): java.io.IOException
  Scenario: Verify wrong HTTP method on end transaction issues 405 "Method not allowed": java.io.IOException
  Given There is an empty repository named repo1(Scenario: Ending a transaction outside of a transaction issues 500 "Transaction required"): java.io.IOException
  Scenario: Ending a transaction outside of a transaction issues 500 "Transaction required": java.io.IOException
  Given There is a repository with multiple branches named repo1(Scenario: Work on a transaction does not affect the main repository): java.io.IOException
  Scenario: Work on a transaction does not affect the main repository: java.io.IOException
  Given There is a repository with multiple branches named repo1(Scenario: Ending a transaction moves the work to the main repository): java.io.IOException
  Scenario: Ending a transaction moves the work to the main repository: java.io.IOException
  Given There is a repository with multiple branches named repo1(Scenario: Canceling a transaction leaves the main repository without changes): java.io.IOException
  Scenario: Canceling a transaction leaves the main repository without changes: java.io.IOException
  Given There is a repository with multiple branches named repo1(Scenario: Ending a transaction with conflicting changes returns details of the conflict): java.io.IOException
  Scenario: Ending a transaction with conflicting changes returns details of the conflict: java.io.IOException
  Given There is a repository with multiple branches named repo1(Scenario: Fixing transaction conflicts and ending again is successful): java.io.IOException
  Scenario: Fixing transaction conflicts and ending again is successful: java.io.IOException
  Given There is an empty repository named repo1(Scenario: Verify wrong HTTP method issues 405 "Method not allowed"): java.io.IOException
  Scenario: Verify wrong HTTP method issues 405 "Method not allowed": java.io.IOException
  Given There is an empty repository named repo1(Scenario: Calling UpdateRef without a ref name issues a 500 status code): java.io.IOException
  Scenario: Calling UpdateRef without a ref name issues a 500 status code: java.io.IOException
  Given There is an empty repository named repo1(Scenario: Calling UpdateRef without a new value or delete specified issues a 500 status code): java.io.IOException
  Scenario: Calling UpdateRef without a new value or delete specified issues a 500 status code: java.io.IOException
  Given There is an empty repository named repo1(Scenario: Calling UpdateRef without a nonexistent name issues a 500 status code): java.io.IOException
  Scenario: Calling UpdateRef without a nonexistent name issues a 500 status code: java.io.IOException
  Given There is a default multirepo server(Scenario: Calling UpdateRef with a new value updates the ref): java.io.IOException
  Scenario: Calling UpdateRef with a new value updates the ref: java.io.IOException
  Given There is a default multirepo server(Scenario: Calling UpdateRef with the delete parameter deletes the ref): java.io.IOException
  Scenario: Calling UpdateRef with the delete parameter deletes the ref: java.io.IOException
  Given There is an empty repository named repo1(Scenario: Verify wrong HTTP method issues 405 "Method not allowed"): java.io.IOException
  Scenario: Verify wrong HTTP method issues 405 "Method not allowed": java.io.IOException
  Given There is an empty repository named repo1(Scenario: Version returns geogig version details): java.io.IOException
  Scenario: Version returns geogig version details: java.io.IOException
  Given There is an empty repository named repo1(Scenario: Verify wrong HTTP method issues 405 "Method not allowed"): java.io.IOException
  Scenario: Verify wrong HTTP method issues 405 "Method not allowed": java.io.IOException
  Given There is an empty repository named repo1(Scenario: AffectedFeatures with no commit issues a 400 status code): java.io.IOException
  Scenario: AffectedFeatures with no commit issues a 400 status code: java.io.IOException
  Given There is an empty repository named repo1(Scenario: AffectedFeatures with an invalid commit issues a 400 status code): java.io.IOException
  Scenario: AffectedFeatures with an invalid commit issues a 400 status code: java.io.IOException
  Given There is a default multirepo server(Scenario: AffectedFeatures lists all features changed in a commit): java.io.IOException
  Scenario: AffectedFeatures lists all features changed in a commit: java.io.IOException
  Given There is an empty repository named repo1(Scenario: Verify wrong HTTP method issues 405 "Method not allowed"): java.io.IOException
  Scenario: Verify wrong HTTP method issues 405 "Method not allowed": java.io.IOException
  Given There is a default multirepo server(Scenario: Depth with an invalid commit issues a 400 status code): java.io.IOException
  Scenario: Depth with an invalid commit issues a 400 status code: java.io.IOException
  Given There is a default multirepo server(Scenario: Depth with no commit returns no depth for a non-shallow repository): java.io.IOException
  Scenario: Depth with no commit returns no depth for a non-shallow repository: java.io.IOException
  Given There is a default multirepo server with a shallow clone(Scenario: Depth with no commit returns the depth of a shallow repository): java.io.IOException
  Scenario: Depth with no commit returns the depth of a shallow repository: java.io.IOException
  Given There is a default multirepo server(Scenario: Depth with a commit returns the number of ancestors that commit has): java.io.IOException
  Scenario: Depth with a commit returns the number of ancestors that commit has: java.io.IOException
  Given There is an empty repository named repo1(Scenario: Verify wrong HTTP method issues 405 "Method not allowed"): java.io.IOException
  Scenario: Verify wrong HTTP method issues 405 "Method not allowed": java.io.IOException
  Given There is a default multirepo server(Scenario: Manifest lists all of the branches in the repository): java.io.IOException
  Scenario: Manifest lists all of the branches in the repository: java.io.IOException
  Given There is a default multirepo server with remotes(Scenario: Manifest also lists remote branches when the remotes parameter is specified): java.io.IOException
  Scenario: Manifest also lists remote branches when the remotes parameter is specified: java.io.IOException
  Given There is an empty repository named repo1(Scenario: Verify wrong HTTP method issues 405 "Method not allowed"): java.io.IOException
  Scenario: Verify wrong HTTP method issues 405 "Method not allowed": java.io.IOException
  Given There is an empty repository named repo1(Scenario: MergeFeature with no json payload issues a 400 status code): java.io.IOException
  Scenario: MergeFeature with no json payload issues a 400 status code: java.io.IOException
  Given There is an empty repository named repo1(Scenario: MergeFeature with an invalid json payload issues a 400 status code): java.io.IOException
  Scenario: MergeFeature with an invalid json payload issues a 400 status code: java.io.IOException
  Given There is an empty repository named repo1(Scenario: MergeFeature without a feature issues a 400 status code): java.io.IOException
  Scenario: MergeFeature without a feature issues a 400 status code: java.io.IOException
  Given There is an empty repository named repo1(Scenario: MergeFeature without an "ours" id issues a 400 status code): java.io.IOException
  Scenario: MergeFeature without an "ours" id issues a 400 status code: java.io.IOException
  Given There is a default multirepo server(Scenario: MergeFeature without a "theirs" id issues a 400 status code): java.io.IOException
  Scenario: MergeFeature without a "theirs" id issues a 400 status code: java.io.IOException
  Given There is a default multirepo server(Scenario: MergeFeature without any merges issues a 400 status code): java.io.IOException
  Scenario: MergeFeature without any merges issues a 400 status code: java.io.IOException
  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)): java.io.IOException
  Scenario: MergeFeature builds a new feature from provided merges using ours and theirs (both features are the same): java.io.IOException
  Given There is a default multirepo server(Scenario: MergeFeature builds a new feature from provided merges with custom values (both features are the same)): java.io.IOException
  Scenario: MergeFeature builds a new feature from provided merges with custom values (both features are the same): java.io.IOException
  Given There is a default multirepo server(Scenario: MergeFeature builds a new feature from provided merges (different versions of the same feature)): java.io.IOException
  Scenario: MergeFeature builds a new feature from provided merges (different versions of the same feature): java.io.IOException
  Given There is an empty repository named repo1(Scenario: Verify wrong HTTP method issues 405 "Method not allowed"): java.io.IOException
  Scenario: Verify wrong HTTP method issues 405 "Method not allowed": java.io.IOException
  Given There is an empty repository named repo1(Scenario: ObjectExists with no object id issues a 400 status code): java.io.IOException
  Scenario: ObjectExists with no object id issues a 400 status code: java.io.IOException
  Given There is an empty repository named repo1(Scenario: ObjectExists with an invalid object id issues a 400 status code): java.io.IOException
  Scenario: ObjectExists with an invalid object id issues a 400 status code: java.io.IOException
  Given There is a default multirepo server(Scenario: ObjectExists with a nonexistent object id returns "0"): java.io.IOException
  Scenario: ObjectExists with a nonexistent object id returns "0": java.io.IOException
  Given There is a default multirepo server(Scenario: ObjectExists with an existing object id returns "1"): java.io.IOException
  Scenario: ObjectExists with an existing object id returns "1": java.io.IOException
  Given There is an empty repository named repo1(Scenario: Verify wrong HTTP method issues 405 "Method not allowed"): java.io.IOException
  Scenario: Verify wrong HTTP method issues 405 "Method not allowed": java.io.IOException
  Given There is a default multirepo server(Scenario: Parents with an invalid commit issues a 400 status code): java.io.IOException
  Scenario: Parents with an invalid commit issues a 400 status code: java.io.IOException
  Given There is a default multirepo server(Scenario: Parents with no commit returns no parents): java.io.IOException
  Scenario: Parents with no commit returns no parents: java.io.IOException
  Given There is a default multirepo server(Scenario: Parents with a commit returns the parents of that commit): java.io.IOException
  Scenario: Parents with a commit returns the parents of that commit: java.io.IOException
  testRemoveSingleFeature(org.geogig.geoserver.gwc.GWCIntegrationTest): java.io.IOException
  createDataStoreCustomURIWithName(org.geogig.geoserver.rest.GeoGigGeoServerRESTntegrationTest)
  createDataStoreNewConfig(org.geogig.geoserver.rest.GeoGigGeoServerRESTntegrationTest)
  testGetBatchedObjects(org.geogig.geoserver.rest.GeoGigWebAPIIntegrationTest): java.io.IOException
  testRevObjectExists(org.geogig.geoserver.rest.GeoGigWebAPIIntegrationTest): java.io.IOException
  testRemoteRemove(org.geogig.geoserver.rest.GeoGigWebAPIIntegrationTest): java.io.IOException
  testRemoteUpdate(org.geogig.geoserver.rest.GeoGigWebAPIIntegrationTest): java.io.IOException
  testGetObject(org.geogig.geoserver.rest.GeoGigWebAPIIntegrationTest): java.io.IOException
  testGetManifest(org.geogig.geoserver.rest.GeoGigWebAPIIntegrationTest): java.io.IOException
  testRemoteAdd(org.geogig.geoserver.rest.GeoGigWebAPIIntegrationTest): java.io.IOException
  testUpdateDoesntChangeFeatureType(org.geogig.geoserver.wfs.WFSIntegrationTest)
  testInsertDoesntChangeFeatureType(org.geogig.geoserver.wfs.WFSIntegrationTest)
  testInsert(org.geogig.geoserver.wfs.WFSIntegrationTest)
  testUpdate(org.geogig.geoserver.wfs.WFSIntegrationTest)
  testCommitsSurviveShutDown(org.geogig.geoserver.wfs.WFSIntegrationTest)
  testAddGeogigLayerForcesCreationOfRootAuthURL(org.geogig.geoserver.wms.GeogigLayerIntegrationListenerTest): java.io.IOException
  testAddGeogigLayerAddsLayerIdentifierWithExplicitBranch(org.geogig.geoserver.wms.GeogigLayerIntegrationListenerTest): java.io.IOException
  testAddGeogigLayerAddsLayerIdentifier(org.geogig.geoserver.wms.GeogigLayerIntegrationListenerTest): java.io.IOException
  testRenameStore(org.geogig.geoserver.wms.GeogigLayerIntegrationListenerTest): java.io.IOException
  testRenameWorkspace(org.geogig.geoserver.wms.GeogigLayerIntegrationListenerTest): java.io.IOException
  testAddGeogigLayerAddsLayerIdentifierWithExplicitHead(org.geogig.geoserver.wms.GeogigLayerIntegrationListenerTest): java.io.IOException

Tests run: 3065, Failures: 0, Errors: 589, Skipped: 2028

[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 06:50 min
[INFO] Finished at: 2017-02-23T19:57:02+00:00
[INFO] Final Memory: 62M/342M
[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
Prev by Date: Re: [geogig-dev] LIDAR format support
Next by Date: [geogig-dev] Build failed in Jenkins: geoserver-2.10.x-geogig-plugin #57
Previous by thread: [geogig-dev] LIDAR format support
Next by thread: [geogig-dev] Build failed in Jenkins: geoserver-2.10.x-geogig-plugin #57
Index(es):
- Date
- Thread
Breadcrumbs
