[geogig-dev] Build failed in Jenkins: geogig-master-nightly #391

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[geogig-dev] Build failed in Jenkins: geogig-master-nightly #391
From: monitor@xxxxxxxxxxxxxxxx
Date: Thu, 16 Aug 2018 11:54:36 +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 <https://build.geoserver.org/job/geogig-master-nightly/391/display/redirect?page=changes>

Changes:

[Gabriel Roldan] Allow to query diff features from different repositories

------------------------------------------
[...truncated 868.49 KB...]
    And the response should contain "Changes not staged for commit"                              # DefaultStepDefinitions.the_response_should_contain(String)
    And the response should contain "2 total."                                                   # DefaultStepDefinitions.the_response_should_contain(String)
    And the response should contain 11 lines                                                     # DefaultStepDefinitions.the_response_should_contain_x_lines(int)
Limit must be 0 or greater.
[main] INFO org.locationtech.geogig.cli.test.functional.DefaultStepDefinitions - 'Try the get the status of a repository with unmerged elements': Using URIBuilder DefaultTestRepoURIBuilder

  Scenario: Try to get the status of a repository with a negative limit # Status.feature:147
    Given I have a repository                                           # DefaultStepDefinitions.I_have_a_repository()
    When I run the command "status --limit -2"                          # DefaultStepDefinitions.I_run_the_command_X(String)
    Then the response should contain "Limit must be 0 or greater"       # DefaultStepDefinitions.the_response_should_contain(String)
    And it should exit with non-zero exit code                          # DefaultStepDefinitions.it_should_exit_with_non_zero_exit_code()
# On branch master# Changes to be committed:#   (use "geogig reset HEAD <path/to/fid>..." to unstage)##      modified  Points#      added  Points/Points.2# 2 total.## Unmerged paths:#   (use "geogig add/rm <path/to/fid>..." as appropriate to mark resolution##      unmerged  Points/Points.1# 1 total.

  Scenario: Try the get the status of a repository with unmerged elements # Status.feature:153
    Given I have a repository                                             # DefaultStepDefinitions.I_have_a_repository()
    And I have a merge conflict state                                     # DefaultStepDefinitions.I_have_a_merge_conflict_state()
    When I run the command "status"                                       # DefaultStepDefinitions.I_run_the_command_X(String)
    Then the response should contain "unmerged  Points/Points.1"          # DefaultStepDefinitions.the_response_should_contain(String)
Feature: "tag" command
  In order to store defined versions of my repository
  As a Geogig User
  I want to be create tags
[main] INFO org.locationtech.geogig.cli.test.functional.DefaultStepDefinitions - 'List the available tags': Using URIBuilder DefaultTestRepoURIBuilder
mytag
[main] INFO org.locationtech.geogig.cli.test.functional.DefaultStepDefinitions - 'Create a new tag': Using URIBuilder DefaultTestRepoURIBuilder

  Scenario: List the available tags          # Tag.feature:6
    Given I have a repository                # DefaultStepDefinitions.I_have_a_repository()
    And I have several commits               # DefaultStepDefinitions.I_have_several_commits()
    And I run the command "tag mytag -m msg" # DefaultStepDefinitions.I_run_the_command_X(String)
    When I run the command "tag"             # DefaultStepDefinitions.I_run_the_command_X(String)
    Then the response should contain "mytag" # DefaultStepDefinitions.the_response_should_contain(String)
Created tag mytag -> 935ed01df922ba126d95076efe7875a3d0e5c27c
[main] INFO org.locationtech.geogig.cli.test.functional.DefaultStepDefinitions - 'Create a new tag for a given commit': Using URIBuilder DefaultTestRepoURIBuilder

  Scenario: Create a new tag                                              # Tag.feature:13
    Given I have a repository                                             # DefaultStepDefinitions.I_have_a_repository()
    And I have several commits                                            # DefaultStepDefinitions.I_have_several_commits()
    When I run the command "tag mytag -m msg"                             # DefaultStepDefinitions.I_run_the_command_X(String)
    Then the response should contain "Created tag mytag ->"               # DefaultStepDefinitions.the_response_should_contain(String)
    And the response should contain variable "{@ObjectId|localrepo|HEAD}" # DefaultStepDefinitions.checkResponseTextContains(String)
Created tag mytag -> ef7262f8d11398cdb553d7646f051a9c8d9cc209
[main] INFO org.locationtech.geogig.cli.test.functional.DefaultStepDefinitions - 'Delete a tag': Using URIBuilder DefaultTestRepoURIBuilder

  Scenario: Create a new tag for a given commit                            # Tag.feature:20
    Given I have a repository                                              # DefaultStepDefinitions.I_have_a_repository()
    And I have several commits                                             # DefaultStepDefinitions.I_have_several_commits()
    When I run the command "tag mytag HEAD^ -m msg"                        # DefaultStepDefinitions.I_run_the_command_X(String)
    Then the response should contain "Created tag mytag ->"                # DefaultStepDefinitions.the_response_should_contain(String)
    And the response should contain variable "{@ObjectId|localrepo|HEAD^}" # DefaultStepDefinitions.checkResponseTextContains(String)
Deleted tag mytag
[main] INFO org.locationtech.geogig.cli.test.functional.DefaultStepDefinitions - 'Delete an inexistent tag': Using URIBuilder DefaultTestRepoURIBuilder

  Scenario: Delete a tag                                 # Tag.feature:27
    Given I have a repository                            # DefaultStepDefinitions.I_have_a_repository()
    And I have several commits                           # DefaultStepDefinitions.I_have_several_commits()
    And I run the command "tag mytag -m msg"             # DefaultStepDefinitions.I_run_the_command_X(String)
    When I run the command "tag -d mytag"                # DefaultStepDefinitions.I_run_the_command_X(String)
    Then the response should contain "Deleted tag mytag" # DefaultStepDefinitions.the_response_should_contain(String)
Wrong tag name: wrongtag
[main] INFO org.locationtech.geogig.cli.test.functional.DefaultStepDefinitions - 'Try to create a tag with too many parameters provided': Using URIBuilder DefaultTestRepoURIBuilder

  Scenario: Delete an inexistent tag                            # Tag.feature:34
    Given I have a repository                                   # DefaultStepDefinitions.I_have_a_repository()
    And I have several commits                                  # DefaultStepDefinitions.I_have_several_commits()
    And I run the command "tag mytag -m msg"                    # DefaultStepDefinitions.I_run_the_command_X(String)
    When I run the command "tag -d wrongtag"                    # DefaultStepDefinitions.I_run_the_command_X(String)
    Then the response should contain "Wrong tag name: wrongtag" # DefaultStepDefinitions.the_response_should_contain(String)
    And it should exit with non-zero exit code                  # DefaultStepDefinitions.it_should_exit_with_non_zero_exit_code()
Too many parameters provided
[main] INFO org.locationtech.geogig.cli.test.functional.DefaultStepDefinitions - 'Try to delete a tag with too many parameters provided': Using URIBuilder DefaultTestRepoURIBuilder

  Scenario: Try to create a tag with too many parameters provided   # Tag.feature:42
    Given I have a repository                                       # DefaultStepDefinitions.I_have_a_repository()
    And I have several commits                                      # DefaultStepDefinitions.I_have_several_commits()
    When I run the command "tag mytag HEAD^ extraparam -m msg"      # DefaultStepDefinitions.I_run_the_command_X(String)
    Then the response should contain "Too many parameters provided" # DefaultStepDefinitions.the_response_should_contain(String)
    And it should exit with non-zero exit code                      # DefaultStepDefinitions.it_should_exit_with_non_zero_exit_code()
Too many parameters provided
[main] INFO org.locationtech.geogig.cli.test.functional.DefaultStepDefinitions - 'Try to create a tag with no message': Using URIBuilder DefaultTestRepoURIBuilder

  Scenario: Try to delete a tag with too many parameters provided   # Tag.feature:49
    Given I have a repository                                       # DefaultStepDefinitions.I_have_a_repository()
    And I have several commits                                      # DefaultStepDefinitions.I_have_several_commits()
    When I run the command "tag -d mytag HEAD^"                     # DefaultStepDefinitions.I_run_the_command_X(String)
    Then the response should contain "Too many parameters provided" # DefaultStepDefinitions.the_response_should_contain(String)
    And it should exit with non-zero exit code                      # DefaultStepDefinitions.it_should_exit_with_non_zero_exit_code()
No tag message provided
[main] INFO org.locationtech.geogig.cli.test.functional.DefaultStepDefinitions - 'Try to create a tag with a wrong commit ref': Using URIBuilder DefaultTestRepoURIBuilder

  Scenario: Try to create a tag with no message                # Tag.feature:56
    Given I have a repository                                  # DefaultStepDefinitions.I_have_a_repository()
    And I have several commits                                 # DefaultStepDefinitions.I_have_several_commits()
    When I run the command "tag mytag HEAD^"                   # DefaultStepDefinitions.I_run_the_command_X(String)
    Then the response should contain "No tag message provided" # DefaultStepDefinitions.the_response_should_contain(String)
    And it should exit with non-zero exit code                 # DefaultStepDefinitions.it_should_exit_with_non_zero_exit_code()
Wrong reference: aaaaaaaa

  Scenario: Try to create a tag with a wrong commit ref          # Tag.feature:63
    Given I have a repository                                    # DefaultStepDefinitions.I_have_a_repository()
    And I have several commits                                   # DefaultStepDefinitions.I_have_several_commits()
    When I run the command "tag mytag aaaaaaaa -m msg"           # DefaultStepDefinitions.I_run_the_command_X(String)
    Then the response should contain "Wrong reference: aaaaaaaa" # DefaultStepDefinitions.the_response_should_contain(String)
    And it should exit with non-zero exit code                   # DefaultStepDefinitions.it_should_exit_with_non_zero_exit_code()
@Version
Feature: "version" command
    In order to view GeoGig version information
    As a Geogig User
    I want to display information about it
[main] INFO org.locationtech.geogig.cli.test.functional.DefaultStepDefinitions - 'I want to view the GeoGig version': Using URIBuilder DefaultTestRepoURIBuilder
         Project Version : 1.4-SNAPSHOT              Build Time : August 16, 2018 at 11:51:20 UTC         Build User Name : Boundless DevOps        Build User Email : devops@xxxxxxxxxxxxxxxx              Git Branch : origin/master           Git Commit ID : c277ec0ae13070bf1b2a1f3c52dc7a98eae94365         Git Commit Time : August 15, 2018 at 15:00:13 UTC  Git Commit Author Name : Gabriel Roldan Git Commit Author Email : groldan@xxxxxxxxxxxxxxxx      Git Commit Message : Merge branch 'feature/cross_repo_diff_features'
         Project Version : 1.4-SNAPSHOT              Build Time : August 16, 2018 at 11:51:20 UTC         Build User Name : Boundless DevOps        Build User Email : devops@xxxxxxxxxxxxxxxx              Git Branch : origin/master           Git Commit ID : c277ec0ae13070bf1b2a1f3c52dc7a98eae94365         Git Commit Time : August 15, 2018 at 15:00:13 UTC  Git Commit Author Name : Gabriel Roldan Git Commit Author Email : groldan@xxxxxxxxxxxxxxxx      Git Commit Message : Merge branch 'feature/cross_repo_diff_features'
         Project Version : 1.4-SNAPSHOT              Build Time : August 16, 2018 at 11:51:20 UTC         Build User Name : Boundless DevOps        Build User Email : devops@xxxxxxxxxxxxxxxx              Git Branch : origin/master           Git Commit ID : c277ec0ae13070bf1b2a1f3c52dc7a98eae94365         Git Commit Time : August 15, 2018 at 15:00:13 UTC  Git Commit Author Name : Gabriel Roldan Git Commit Author Email : groldan@xxxxxxxxxxxxxxxx      Git Commit Message : Merge branch 'feature/cross_repo_diff_features'

  Scenario: I want to view the GeoGig version          # Version.feature:7
    Given I am in an empty directory                   # DefaultStepDefinitions.I_am_in_an_empty_directory()
    When I run the command "version"                   # DefaultStepDefinitions.I_run_the_command_X(String)
    Then the response should contain "Project Version" # DefaultStepDefinitions.the_response_should_contain(String)
    And the response should contain "Build Time"       # DefaultStepDefinitions.the_response_should_contain(String)
    And the response should contain "Git Commit ID"    # DefaultStepDefinitions.the_response_should_contain(String)

Failed scenarios:
Diff.feature:31 # Scenario: Show diff between working tree and index, for a single modified tree

263 Scenarios (1 failed, 262 passed)
1765 Steps (1 failed, 5 skipped, 1759 passed)
3m4.143s

java.lang.IllegalArgumentException: refSpec HEAD did not resolve to a tree
	at com.google.common.base.Preconditions.checkArgument(Preconditions.java:210)
	at org.locationtech.geogig.plumbing.DiffIndex._call(DiffIndex.java:93)
	at org.locationtech.geogig.plumbing.DiffIndex._call(DiffIndex.java:30)
	at org.locationtech.geogig.repository.AbstractGeoGigOp.call(AbstractGeoGigOp.java:169)
	at org.locationtech.geogig.repository.impl.StagingAreaImpl.getStaged(StagingAreaImpl.java:383)
	at org.locationtech.geogig.porcelain.AddOp.stage(AddOp.java:92)
	at org.locationtech.geogig.porcelain.AddOp._call(AddOp.java:69)
	at org.locationtech.geogig.porcelain.AddOp._call(AddOp.java:43)
	at org.locationtech.geogig.repository.AbstractGeoGigOp.call(AbstractGeoGigOp.java:169)
	at org.locationtech.geogig.cli.porcelain.Add.runInternal(Add.java:113)
	at org.locationtech.geogig.cli.AbstractCommand.run(AbstractCommand.java:67)
	at org.locationtech.geogig.cli.GeogigCLI.executeInternal(GeogigCLI.java:531)
	at org.locationtech.geogig.cli.GeogigCLI.execute(GeogigCLI.java:367)
	at org.locationtech.geogig.cli.test.functional.CLIContext.runCommand(CLIContext.java:159)
	at org.locationtech.geogig.cli.test.functional.CLIContext.runCommand(CLIContext.java:145)
	at org.locationtech.geogig.cli.test.functional.CLIContext.insertAndAdd(CLIContext.java:210)
	at org.locationtech.geogig.cli.test.functional.CLIContext.insertAndAddFeatures(CLIContext.java:180)
	at org.locationtech.geogig.cli.test.functional.DefaultStepDefinitions.I_stage_6_features(DefaultStepDefinitions.java:586)
	at ✽.And I stage 6 features(Diff.feature:33)

Tests run: 2028, Failures: 0, Errors: 2, Skipped: 5, Time elapsed: 189.195 sec <<< FAILURE! - in org.locationtech.geogig.cli.test.functional.RunPorcelainFunctionalTest
And I stage 6 features(Scenario: Show diff between working tree and index, for a single modified tree)  Time elapsed: 0.006 sec  <<< ERROR!
java.lang.IllegalArgumentException: refSpec HEAD did not resolve to a tree
	at com.google.common.base.Preconditions.checkArgument(Preconditions.java:210)
	at org.locationtech.geogig.plumbing.DiffIndex._call(DiffIndex.java:93)
	at org.locationtech.geogig.plumbing.DiffIndex._call(DiffIndex.java:30)
	at org.locationtech.geogig.repository.AbstractGeoGigOp.call(AbstractGeoGigOp.java:169)
	at org.locationtech.geogig.repository.impl.StagingAreaImpl.getStaged(StagingAreaImpl.java:383)
	at org.locationtech.geogig.porcelain.AddOp.stage(AddOp.java:92)
	at org.locationtech.geogig.porcelain.AddOp._call(AddOp.java:69)
	at org.locationtech.geogig.porcelain.AddOp._call(AddOp.java:43)
	at org.locationtech.geogig.repository.AbstractGeoGigOp.call(AbstractGeoGigOp.java:169)
	at org.locationtech.geogig.cli.porcelain.Add.runInternal(Add.java:113)
	at org.locationtech.geogig.cli.AbstractCommand.run(AbstractCommand.java:67)
	at org.locationtech.geogig.cli.GeogigCLI.executeInternal(GeogigCLI.java:531)
	at org.locationtech.geogig.cli.GeogigCLI.execute(GeogigCLI.java:367)
	at org.locationtech.geogig.cli.test.functional.CLIContext.runCommand(CLIContext.java:159)
	at org.locationtech.geogig.cli.test.functional.CLIContext.runCommand(CLIContext.java:145)
	at org.locationtech.geogig.cli.test.functional.CLIContext.insertAndAdd(CLIContext.java:210)
	at org.locationtech.geogig.cli.test.functional.CLIContext.insertAndAddFeatures(CLIContext.java:180)
	at org.locationtech.geogig.cli.test.functional.DefaultStepDefinitions.I_stage_6_features(DefaultStepDefinitions.java:586)
	at ✽.And I stage 6 features(Diff.feature:33)

Scenario: Show diff between working tree and index, for a single modified tree  Time elapsed: 0.008 sec  <<< ERROR!
java.lang.IllegalArgumentException: refSpec HEAD did not resolve to a tree
	at com.google.common.base.Preconditions.checkArgument(Preconditions.java:210)
	at org.locationtech.geogig.plumbing.DiffIndex._call(DiffIndex.java:93)
	at org.locationtech.geogig.plumbing.DiffIndex._call(DiffIndex.java:30)
	at org.locationtech.geogig.repository.AbstractGeoGigOp.call(AbstractGeoGigOp.java:169)
	at org.locationtech.geogig.repository.impl.StagingAreaImpl.getStaged(StagingAreaImpl.java:383)
	at org.locationtech.geogig.porcelain.AddOp.stage(AddOp.java:92)
	at org.locationtech.geogig.porcelain.AddOp._call(AddOp.java:69)
	at org.locationtech.geogig.porcelain.AddOp._call(AddOp.java:43)
	at org.locationtech.geogig.repository.AbstractGeoGigOp.call(AbstractGeoGigOp.java:169)
	at org.locationtech.geogig.cli.porcelain.Add.runInternal(Add.java:113)
	at org.locationtech.geogig.cli.AbstractCommand.run(AbstractCommand.java:67)
	at org.locationtech.geogig.cli.GeogigCLI.executeInternal(GeogigCLI.java:531)
	at org.locationtech.geogig.cli.GeogigCLI.execute(GeogigCLI.java:367)
	at org.locationtech.geogig.cli.test.functional.CLIContext.runCommand(CLIContext.java:159)
	at org.locationtech.geogig.cli.test.functional.CLIContext.runCommand(CLIContext.java:145)
	at org.locationtech.geogig.cli.test.functional.CLIContext.insertAndAdd(CLIContext.java:210)
	at org.locationtech.geogig.cli.test.functional.CLIContext.insertAndAddFeatures(CLIContext.java:180)
	at org.locationtech.geogig.cli.test.functional.DefaultStepDefinitions.I_stage_6_features(DefaultStepDefinitions.java:586)
	at ✽.And I stage 6 features(Diff.feature:33)


Results :

Tests in error: 
  refSpec HEAD did not resolve to a tree
  refSpec HEAD did not resolve to a tree

Tests run: 3098, Failures: 0, Errors: 2, Skipped: 5

[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO] 
[INFO] GeoGig ............................................. SUCCESS [  7.913 s]
[INFO] GeoGig Core API .................................... SUCCESS [ 15.883 s]
[INFO] GeoGig Core ........................................ SUCCESS [01:51 min]
[INFO] Replication and synchronization .................... SUCCESS [ 47.317 s]
[INFO] GeoGig DataStore Implementation .................... SUCCESS [02:26 min]
[INFO] Storage backends ................................... SUCCESS [  1.906 s]
[INFO] RocksDB storage backend ............................ SUCCESS [ 37.088 s]
[INFO] GeoGig Command Line Interface ...................... SUCCESS [  1.735 s]
[INFO] GeoGig Command Line Interface Core ................. FAILURE [03:12 min]
[INFO] geogig-cli-remoting ................................ SKIPPED
[INFO] PostgreSQL Storage Backend ......................... SKIPPED
[INFO] GeoTools Extension ................................. SKIPPED
[INFO] GeoGig CLI GeoTools ................................ SKIPPED
[INFO] Web modules ........................................ SKIPPED
[INFO] GeoGig Web API ..................................... SKIPPED
[INFO] GeoGig WebApp ...................................... SKIPPED
[INFO] GeoGig Web API Automated Functional Tests .......... SKIPPED
[INFO] GeoGigi CLI Postgres Storage Commands .............. SKIPPED
[INFO] GeoGig CLI App ..................................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 09:22 min
[INFO] Finished at: 2018-08-16T11:54:31+00:00
[INFO] Final Memory: 99M/1438M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.17:test (default-test) on project geogig-cli-core: There are test failures.
[ERROR] 
[ERROR] Please refer to <https://build.geoserver.org/job/geogig-master-nightly/ws/src/cli/core/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
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <goals> -rf :geogig-cli-core
Build step 'Invoke top-level Maven targets' marked build as failure
[Cucumber Tests] Parsing results.
[Cucumber Tests] parsing cucumber.json
[Cucumber Tests] parsing cucumber.json
Follow-Ups:
- [geogig-dev] Jenkins build is back to normal : geogig-master-nightly #392
  - From: monitor
Prev by Date: [geogig-dev] Build failed in Jenkins: geogig-plugins-master #83
Next by Date: [geogig-dev] Build failed in Jenkins: geoserver-master-geogig-plugin #980
Previous by thread: [geogig-dev] Build failed in Jenkins: geogig-master-nightly #372
Next by thread: [geogig-dev] Jenkins build is back to normal : geogig-master-nightly #392
Index(es):
- Date
- Thread
Breadcrumbs
