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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[geogig-dev] Build failed in Jenkins: geogig-master-nightly #191
From: monitor@xxxxxxxxxxxxxxxx
Date: Sun, 28 Jan 2018 11:58:02 +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/191/display/redirect?page=changes>

Changes:

[Gabriel Roldan] Allow DataStore to receive Context instead of Repository

------------------------------------------
[...truncated 801.89 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 21 lines                                                      # DefaultStepDefinitions.the_response_should_contain_x_lines(int)
[main] INFO org.locationtech.geogig.cli.test.functional.DefaultStepDefinitions - 'Try to get the status of a repository with staged changes using a limit': Using URIBuilder DefaultTestRepoURIBuilder

  Scenario: Try to get the status of a repository with unstaged changes using a limit # Status.feature:105
    Given I have a repository                                                         # DefaultStepDefinitions.I_have_a_repository()
    And I have unstaged "points1"                                                     # DefaultStepDefinitions.I_have_unstaged(String)
    And I have unstaged "points2"                                                     # DefaultStepDefinitions.I_have_unstaged(String)
    And I have unstaged "points3"                                                     # DefaultStepDefinitions.I_have_unstaged(String)
    And I have unstaged "lines1"                                                      # DefaultStepDefinitions.I_have_unstaged(String)
    And I have unstaged "lines2"                                                      # DefaultStepDefinitions.I_have_unstaged(String)
    And I have unstaged "lines3"                                                      # DefaultStepDefinitions.I_have_unstaged(String)
    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)
[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)
[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)
[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()

  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
[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)
[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)
[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)
[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)
[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()
[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()
[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()
[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()

  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

  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:
Branch.feature:41 # Scenario: Try to checkout a branch as soon as it is created

277 Scenarios (1 failed, 276 passed)
1832 Steps (1 failed, 3 skipped, 1828 passed)
5m16.431s

org.locationtech.geogig.cli.InvalidParameterException: Not in a geogig repository: /mnt/memtmp/geogig-geoserver/junit7183320443404367161/data
	at org.locationtech.geogig.cli.GeogigCLI.executeInternal(GeogigCLI.java:527)
	at org.locationtech.geogig.cli.GeogigCLI.execute(GeogigCLI.java:368)
	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.DefaultStepDefinitions.I_have_several_commits(DefaultStepDefinitions.java:592)
	at ✽.And I have several commits(Branch.feature:43)

Tests run: 2109, Failures: 0, Errors: 2, Skipped: 3, Time elapsed: 323.184 sec <<< FAILURE! - in org.locationtech.geogig.cli.test.functional.RunPorcelainFunctionalTest
And I have several commits(Scenario: Try to checkout a branch as soon as it is created)  Time elapsed: 0.008 sec  <<< ERROR!
org.locationtech.geogig.cli.InvalidParameterException: Not in a geogig repository: /mnt/memtmp/geogig-geoserver/junit7183320443404367161/data
	at org.locationtech.geogig.cli.GeogigCLI.executeInternal(GeogigCLI.java:527)
	at org.locationtech.geogig.cli.GeogigCLI.execute(GeogigCLI.java:368)
	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.DefaultStepDefinitions.I_have_several_commits(DefaultStepDefinitions.java:592)
	at ✽.And I have several commits(Branch.feature:43)

Scenario: Try to checkout a branch as soon as it is created  Time elapsed: 0.012 sec  <<< ERROR!
org.locationtech.geogig.cli.InvalidParameterException: Not in a geogig repository: /mnt/memtmp/geogig-geoserver/junit7183320443404367161/data
	at org.locationtech.geogig.cli.GeogigCLI.executeInternal(GeogigCLI.java:527)
	at org.locationtech.geogig.cli.GeogigCLI.execute(GeogigCLI.java:368)
	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.DefaultStepDefinitions.I_have_several_commits(DefaultStepDefinitions.java:592)
	at ✽.And I have several commits(Branch.feature:43)


Results :

Tests in error: 
  org.rocksdb.RocksDBException: Can't access /000057.sst: IO error: while stat a file for size: /mnt/memtmp/geogig-geoserver/junit2219596279051961857/data/localrepo/.geogig/objects.rocksdb/000057.sst: No such file or directory
Can't access /000053.sst: IO error: while stat a file for size: /mnt/memtmp/geogig-geoserver/junit2219596279051961857/data/localrepo/.geogig/objects.rocksdb/000053.sst: No such file or directory
Can't access /000010.sst: IO error: while stat a file for size: /mnt/memtmp/geogig-geoserver/junit2219596279051961857/data/localrepo/.geogig/objects.rocksdb/000010.sst: No such file or directory

  org.rocksdb.RocksDBException: Can't access /000057.sst: IO error: while stat a file for size: /mnt/memtmp/geogig-geoserver/junit2219596279051961857/data/localrepo/.geogig/objects.rocksdb/000057.sst: No such file or directory
Can't access /000053.sst: IO error: while stat a file for size: /mnt/memtmp/geogig-geoserver/junit2219596279051961857/data/localrepo/.geogig/objects.rocksdb/000053.sst: No such file or directory
Can't access /000010.sst: IO error: while stat a file for size: /mnt/memtmp/geogig-geoserver/junit2219596279051961857/data/localrepo/.geogig/objects.rocksdb/000010.sst: No such file or directory

  Not in a geogig repository: /mnt/memtmp/geogig-geoserver/junit7183320443404367161/data
  Not in a geogig repository: /mnt/memtmp/geogig-geoserver/junit7183320443404367161/data
  org.rocksdb.RocksDBException: Can't access /000013.sst: IO error: while stat a file for size: /mnt/memtmp/geogig-geoserver/junit3483123815198004618/data/remoterepo/.geogig/index.rocksdb/000013.sst: No such file or directory

  org.rocksdb.RocksDBException: Can't access /000013.sst: IO error: while stat a file for size: /mnt/memtmp/geogig-geoserver/junit3483123815198004618/data/remoterepo/.geogig/index.rocksdb/000013.sst: No such file or directory


Tests run: 3414, Failures: 0, Errors: 6, Skipped: 30

[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO] 
[INFO] GeoGig ............................................. SUCCESS [ 10.719 s]
[INFO] GeoGig Core API .................................... SUCCESS [ 17.952 s]
[INFO] GeoGig Core ........................................ SUCCESS [02:02 min]
[INFO] Replication and synchronization .................... SUCCESS [ 49.453 s]
[INFO] GeoGig DataStore Implementation .................... SUCCESS [03:07 min]
[INFO] Storage backends ................................... SUCCESS [  4.036 s]
[INFO] RocksDB storage backend ............................ SUCCESS [ 51.412 s]
[INFO] GeoGig Command Line Interface ...................... FAILURE [05:29 min]
[INFO] PostgreSQL Storage Backend ......................... SKIPPED
[INFO] GeoTools Extension ................................. SKIPPED
[INFO] Web modules ........................................ SKIPPED
[INFO] GeoGig Web API ..................................... SKIPPED
[INFO] GeoGig WebApp ...................................... SKIPPED
[INFO] GeoGig Web API Automated Functional Tests .......... SKIPPED
[INFO] GeoGig CLI App ..................................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 12:55 min
[INFO] Finished at: 2018-01-28T11:58:01+00:00
[INFO] Final Memory: 99M/979M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.17:test (default-test) on project geogig-cli: There are test failures.
[ERROR] 
[ERROR] Please refer to <https://build.geoserver.org/job/geogig-master-nightly/ws/src/cli/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
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 #192
  - From: monitor
Prev by Date: [geogig-dev] Jenkins build is back to normal : geogig-master-nightly #184
Next by Date: [geogig-dev] Jenkins build is back to normal : geogig-master-nightly #192
Previous by thread: [geogig-dev] Build failed in Jenkins: geogig-master-nightly #182
Next by thread: [geogig-dev] Jenkins build is back to normal : geogig-master-nightly #192
Index(es):
- Date
- Thread
Breadcrumbs
