Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[geogig-dev] Build failed in Jenkins: geogig-master-nightly #454

See <https://build.geoserver.org/job/geogig-master-nightly/454/display/redirect>

------------------------------------------
[...truncated 889.48 KB...]
    When I run the command "status --limit 3"                                         # DefaultStepDefinitions.I_run_the_command_X(String)
    Then the response should contain "Changes not staged for commit"                  # DefaultStepDefinitions.the_response_should_contain(String)
    And the response should contain "8 total."                                        # DefaultStepDefinitions.the_response_should_contain(String)
    And the response should contain 9 lines                                           # DefaultStepDefinitions.the_response_should_contain_x_lines(int)
# On branch master# Changes to be committed:#   (use "geogig reset HEAD <path/to/fid>..." to unstage)##      added  Points#      added  Lines#      added  Points/Points.2# 8 total.#
# On branch master# Changes to be committed:#   (use "geogig reset HEAD <path/to/fid>..." to unstage)##      added  Points#      added  Lines#      added  Points/Points.2# 8 total.#
[main] INFO org.locationtech.geogig.cli.test.functional.DefaultStepDefinitions - 'Try to get the status of a repository with staged and unstaged changes using a limit': Using URIBuilder DefaultTestRepoURIBuilder

  Scenario: Try to get the status of a repository with staged changes using a limit # Status.feature:118
    Given I have a repository                                                       # DefaultStepDefinitions.I_have_a_repository()
    And I have staged "points1"                                                     # DefaultStepDefinitions.I_have_staged(String)
    And I have staged "points2"                                                     # DefaultStepDefinitions.I_have_staged(String)
    And I have staged "points3"                                                     # DefaultStepDefinitions.I_have_staged(String)
    And I have staged "lines1"                                                      # DefaultStepDefinitions.I_have_staged(String)
    And I have staged "lines2"                                                      # DefaultStepDefinitions.I_have_staged(String)
    And I have staged "lines3"                                                      # DefaultStepDefinitions.I_have_staged(String)
    When I run the command "status --limit 3"                                       # DefaultStepDefinitions.I_run_the_command_X(String)
    Then the response should contain "Changes to be committed"                      # DefaultStepDefinitions.the_response_should_contain(String)
    And the response should contain "8 total."                                      # DefaultStepDefinitions.the_response_should_contain(String)
    And the response should contain 9 lines                                         # DefaultStepDefinitions.the_response_should_contain_x_lines(int)
# On branch master# Changes to be committed:#   (use "geogig reset HEAD <path/to/fid>..." to unstage)## 8 total.## Changes not staged for commit:#   (use "geogig add <path/to/fid>..." to update what will be committed#   (use "geogig checkout -- <path/to/fid>..." to discard changes in working directory## 2 total.
# On branch master# Changes to be committed:#   (use "geogig reset HEAD <path/to/fid>..." to unstage)## 8 total.## Changes not staged for commit:#   (use "geogig add <path/to/fid>..." to update what will be committed#   (use "geogig checkout -- <path/to/fid>..." to discard changes in working directory## 2 total.
# On branch master# Changes to be committed:#   (use "geogig reset HEAD <path/to/fid>..." to unstage)## 8 total.## Changes not staged for commit:#   (use "geogig add <path/to/fid>..." to update what will be committed#   (use "geogig checkout -- <path/to/fid>..." to discard changes in working directory## 2 total.
# On branch master# Changes to be committed:#   (use "geogig reset HEAD <path/to/fid>..." to unstage)## 8 total.## Changes not staged for commit:#   (use "geogig add <path/to/fid>..." to update what will be committed#   (use "geogig checkout -- <path/to/fid>..." to discard changes in working directory## 2 total.
[main] INFO org.locationtech.geogig.cli.test.functional.DefaultStepDefinitions - 'Try to get the status of a repository with a negative limit': Using URIBuilder DefaultTestRepoURIBuilder

  Scenario: Try to get the status of a repository with staged and unstaged changes using a limit # Status.feature:131
    Given I have a repository                                                                    # DefaultStepDefinitions.I_have_a_repository()
    And I have staged "points1"                                                                  # DefaultStepDefinitions.I_have_staged(String)
    And I have staged "points2"                                                                  # DefaultStepDefinitions.I_have_staged(String)
    And I have staged "points3"                                                                  # DefaultStepDefinitions.I_have_staged(String)
    And I have staged "lines1"                                                                   # DefaultStepDefinitions.I_have_staged(String)
    And I have staged "lines2"                                                                   # DefaultStepDefinitions.I_have_staged(String)
    And I have staged "lines3"                                                                   # DefaultStepDefinitions.I_have_staged(String)
    And I modify a feature                                                                       # DefaultStepDefinitions.I_modify_a_feature()
    When I run the command "status --limit 0"                                                    # DefaultStepDefinitions.I_run_the_command_X(String)
    Then the response should contain "Changes to be committed"                                   # DefaultStepDefinitions.the_response_should_contain(String)
    And the response should contain "8 total."                                                   # DefaultStepDefinitions.the_response_should_contain(String)
    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 -> 45eea4e68202efd3753bbc682ad30b81a48f3b2c
[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 -> a978ee2281fb47483d55e44f6a76dd95bca8bb98
[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 : October 18, 2018 at 11:56:57 UTC         Build User Name : Boundless DevOps        Build User Email : devops@xxxxxxxxxxxxxxxx              Git Branch : origin/master           Git Commit ID : 5cdac15cf117b0b4400d22b0e1b3b7ab08cb8737         Git Commit Time : October 15, 2018 at 00:54:53 UTC  Git Commit Author Name : Gabriel Roldan Git Commit Author Email : groldan@xxxxxxxxxxxxxxxx      Git Commit Message : Dependency upgrade: geotools 20-SNAPSHOT -> 20.0Signed-off-by: Gabriel Roldan <groldan@xxxxxxxxxxxxxxxx>
         Project Version : 1.4-SNAPSHOT              Build Time : October 18, 2018 at 11:56:57 UTC         Build User Name : Boundless DevOps        Build User Email : devops@xxxxxxxxxxxxxxxx              Git Branch : origin/master           Git Commit ID : 5cdac15cf117b0b4400d22b0e1b3b7ab08cb8737         Git Commit Time : October 15, 2018 at 00:54:53 UTC  Git Commit Author Name : Gabriel Roldan Git Commit Author Email : groldan@xxxxxxxxxxxxxxxx      Git Commit Message : Dependency upgrade: geotools 20-SNAPSHOT -> 20.0Signed-off-by: Gabriel Roldan <groldan@xxxxxxxxxxxxxxxx>
         Project Version : 1.4-SNAPSHOT              Build Time : October 18, 2018 at 11:56:57 UTC         Build User Name : Boundless DevOps        Build User Email : devops@xxxxxxxxxxxxxxxx              Git Branch : origin/master           Git Commit ID : 5cdac15cf117b0b4400d22b0e1b3b7ab08cb8737         Git Commit Time : October 15, 2018 at 00:54:53 UTC  Git Commit Author Name : Gabriel Roldan Git Commit Author Email : groldan@xxxxxxxxxxxxxxxx      Git Commit Message : Dependency upgrade: geotools 20-SNAPSHOT -> 20.0Signed-off-by: Gabriel Roldan <groldan@xxxxxxxxxxxxxxxx>

  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:
Show.feature:6 # Scenario: Try to show the description of a feature using only its path

263 Scenarios (1 failed, 262 passed)
1765 Steps (1 failed, 9 skipped, 1755 passed)
8m39.682s

java.lang.NullPointerException
	at org.locationtech.geogig.cli.test.functional.CLIContext.insert(CLIContext.java:238)
	at org.locationtech.geogig.cli.test.functional.CLIContext.insert(CLIContext.java:218)
	at org.locationtech.geogig.cli.test.functional.CLIContext.insertAndAdd(CLIContext.java:208)
	at org.locationtech.geogig.cli.test.functional.CLIContext.insertAndAddFeatures(CLIContext.java:178)
	at org.locationtech.geogig.cli.test.functional.DefaultStepDefinitions.I_stage_6_features(DefaultStepDefinitions.java:586)
	at ✽.And I stage 6 features(Show.feature:8)

Tests run: 2028, Failures: 0, Errors: 2, Skipped: 9, Time elapsed: 528.536 sec <<< FAILURE! - in org.locationtech.geogig.cli.test.functional.RunPorcelainFunctionalTest
And I stage 6 features(Scenario: Try to show the description of a feature using only its path)  Time elapsed: 0.01 sec  <<< ERROR!
java.lang.NullPointerException: null
	at org.locationtech.geogig.cli.test.functional.CLIContext.insert(CLIContext.java:238)
	at org.locationtech.geogig.cli.test.functional.CLIContext.insert(CLIContext.java:218)
	at org.locationtech.geogig.cli.test.functional.CLIContext.insertAndAdd(CLIContext.java:208)
	at org.locationtech.geogig.cli.test.functional.CLIContext.insertAndAddFeatures(CLIContext.java:178)
	at org.locationtech.geogig.cli.test.functional.DefaultStepDefinitions.I_stage_6_features(DefaultStepDefinitions.java:586)
	at ✽.And I stage 6 features(Show.feature:8)

Scenario: Try to show the description of a feature using only its path  Time elapsed: 0.011 sec  <<< ERROR!
java.lang.NullPointerException: null
	at org.locationtech.geogig.cli.test.functional.CLIContext.insert(CLIContext.java:238)
	at org.locationtech.geogig.cli.test.functional.CLIContext.insert(CLIContext.java:218)
	at org.locationtech.geogig.cli.test.functional.CLIContext.insertAndAdd(CLIContext.java:208)
	at org.locationtech.geogig.cli.test.functional.CLIContext.insertAndAddFeatures(CLIContext.java:178)
	at org.locationtech.geogig.cli.test.functional.DefaultStepDefinitions.I_stage_6_features(DefaultStepDefinitions.java:586)
	at ✽.And I stage 6 features(Show.feature:8)


Results :

Tests in error: 
  null
  null

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

[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO] 
[INFO] GeoGig ............................................. SUCCESS [ 15.508 s]
[INFO] GeoGig Core API .................................... SUCCESS [ 29.323 s]
[INFO] GeoGig Core ........................................ SUCCESS [03:39 min]
[INFO] Replication and synchronization .................... SUCCESS [03:24 min]
[INFO] GeoGig DataStore Implementation .................... SUCCESS [02:38 min]
[INFO] Storage backends ................................... SUCCESS [  3.629 s]
[INFO] RocksDB storage backend ............................ SUCCESS [01:11 min]
[INFO] GeoGig Command Line Interface ...................... SUCCESS [  6.486 s]
[INFO] GeoGig Command Line Interface Core ................. FAILURE [08:59 min]
[INFO] geogig-cli-remoting ................................ SKIPPED
[INFO] PostgreSQL Storage Backend ......................... SKIPPED
[INFO] GeoTools Extension ................................. SKIPPED
[INFO] GeoGig Pull Requests Support Commands .............. 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: 20:49 min
[INFO] Finished at: 2018-10-18T12:05:55+00:00
[INFO] Final Memory: 92M/1470M
[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


Back to the top