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 #396

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

------------------------------------------
[...truncated 235.68 KB...]
	at org.geotools.geometry.jts.GeometryBuilder.lineString(GeometryBuilder.java:157)
	at org.locationtech.geogig.geotools.data.GeoGigDataStoreTest.testFeatureWriterAppend(GeoGigDataStoreTest.java:364)

Running org.locationtech.geogig.geotools.data.functional.RunDataStoreDimensionTest
Feature: GeoGig DataStore Layer Dimension validation
  The GeoGig DataStore is the integration point between GeoServer/OGC services
  and GeoGig repositories. These scenarios are meant to ensure data/feature
  integrity when layers utilize time/elevation dimensions.
Tests run: 17, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 26.33 sec - in org.locationtech.geogig.geotools.data.GeoGigFeatureStoreIndexedTest
Running org.locationtech.geogig.geotools.data.reader.ExtraDataPropertyAccessorFactoryTest
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.062 sec - in org.locationtech.geogig.geotools.data.reader.ExtraDataPropertyAccessorFactoryTest
Running org.locationtech.geogig.geotools.data.reader.PrePostFilterSplitterTest

  Scenario: Ensure Point Features with Time dimensions can be retrieved from a DataStore            # features/dimension/Dimesnion.feature:6
    Given I am working with the "pointTime" layer                                                   # FunctionalStepDefinitions.i_am_working_with_the_layer(String)
    And I have a datastore named "dataStore1" backed by a GeoGig repo                               # FunctionalStepDefinitions.i_have_a_datastore_backed_by_a_GeoGig_repo(String)
    And datastore "dataStore1" has 200 features per thread inserted using 4 threads                 # FunctionalStepDefinitions.datastore_has_features_inserted(String,int,int)
    Then I should be able to retrieve data from "dataStore1" using 1 threads and 1 reads per thread # FunctionalStepDefinitions.datastore_should_have_some_data(String,int,int)
    And features in "dataStore1" should contain a Time attribute                                    # FunctionalStepDefinitions.features_should_contain_time_attribute(String)
Tests run: 38, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.062 sec - in org.locationtech.geogig.geotools.data.reader.PrePostFilterSplitterTest
Running org.locationtech.geogig.geotools.data.reader.MaterializedIndexFeatureIteratorTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.282 sec - in org.locationtech.geogig.geotools.data.reader.MaterializedIndexFeatureIteratorTest
Running org.locationtech.geogig.geotools.data.reader.PreFilterTest
Tests run: 30, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.35 sec - in org.locationtech.geogig.geotools.data.reader.PreFilterTest
Running org.locationtech.geogig.geotools.data.reader.FeatureReaderBuilderTest

  Scenario: Ensure Point Features with Time dimensions can be retrieved from a DataStore with indexes # features/dimension/Dimesnion.feature:13
    Given I am working with the "pointTime" layer                                                     # FunctionalStepDefinitions.i_am_working_with_the_layer(String)
    And I have a datastore named "dataStore1" backed by a GeoGig repo                                 # FunctionalStepDefinitions.i_have_a_datastore_backed_by_a_GeoGig_repo(String)
    And datastore "dataStore1" has 200 features per thread inserted using 4 threads                   # FunctionalStepDefinitions.datastore_has_features_inserted(String,int,int)
    When I create a spatial index on "dataStore1" with extra attributes "dp"                          # FunctionalStepDefinitions.i_create_a_spatial_index_with_extra_Attributes(String,String)
    Then I should be able to retrieve data from "dataStore1" using 1 threads and 1 reads per thread   # FunctionalStepDefinitions.datastore_should_have_some_data(String,int,int)
    And features in "dataStore1" should contain a Time attribute                                      # FunctionalStepDefinitions.features_should_contain_time_attribute(String)

  Scenario: Ensure Point Features with NULL Time dimension values can be retrieved from a DataStore with indexes # features/dimension/Dimesnion.feature:21
    Given I am working with the "pointTime" layer                                                                # FunctionalStepDefinitions.i_am_working_with_the_layer(String)
    And I have a datastore named "dataStore1" backed by a GeoGig repo                                            # FunctionalStepDefinitions.i_have_a_datastore_backed_by_a_GeoGig_repo(String)
    And datastore "dataStore1" has 200 features per thread inserted using 4 threads                              # FunctionalStepDefinitions.datastore_has_features_inserted(String,int,int)
    When I create a spatial index on "dataStore1" with extra attributes "dp"                                     # FunctionalStepDefinitions.i_create_a_spatial_index_with_extra_Attributes(String,String)
    And I edit a time dimension attribute value in "dataStore1" to be NULL                                       # FunctionalStepDefinitions.i_edit_a_time_dimension_attribute_value_to_be_null(String)
    Then I should be able to retrieve data from "dataStore1" using 1 threads and 1 reads per thread              # FunctionalStepDefinitions.datastore_should_have_some_data(String,int,int)
    And the edited feature in "dataStore1" should contain a NULL Time attribute                                  # FunctionalStepDefinitions.edited_feature_should_contain_null_time_attribute(String)

3 Scenarios (3 passed)
18 Steps (18 passed)
0m4.703s

Tests run: 21, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.685 sec - in org.locationtech.geogig.geotools.data.functional.RunDataStoreDimensionTest

  Scenario: Ensure Point Features can be retrieved from a DataStore                                  # features/index/FeatureReader.feature:6
    Given I am working with the "point" layer                                                        # FunctionalStepDefinitions.i_am_working_with_the_layer(String)
    And I have a datastore named "dataStore1" backed by a GeoGig repo                                # FunctionalStepDefinitions.i_have_a_datastore_backed_by_a_GeoGig_repo(String)
    And datastore "dataStore1" has 200 features per thread inserted using 4 threads                  # FunctionalStepDefinitions.datastore_has_features_inserted(String,int,int)
    Then I should be able to retrieve data from "dataStore1" using 4 threads and 40 reads per thread # FunctionalStepDefinitions.datastore_should_have_some_data(String,int,int)
Tests run: 16, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.335 sec - in org.locationtech.geogig.geotools.data.reader.FeatureReaderBuilderTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 34.229 sec - in org.locationtech.geogig.geotools.data.stresstest.DataStoreConcurrencyTest

  Scenario: Ensure Polygon Features can be retrieved from a DataStore                                # features/index/FeatureReader.feature:12
    Given I am working with the "polygon" layer                                                      # FunctionalStepDefinitions.i_am_working_with_the_layer(String)
    And I have a datastore named "dataStore1" backed by a GeoGig repo                                # FunctionalStepDefinitions.i_have_a_datastore_backed_by_a_GeoGig_repo(String)
    And datastore "dataStore1" has 200 features per thread inserted using 4 threads                  # FunctionalStepDefinitions.datastore_has_features_inserted(String,int,int)
    Then I should be able to retrieve data from "dataStore1" using 4 threads and 40 reads per thread # FunctionalStepDefinitions.datastore_should_have_some_data(String,int,int)

  Scenario: Ensure Point Features can be retrieved from a DataStore with an indexed repo             # features/index/FeatureReader.feature:18
    Given I am working with the "point" layer                                                        # FunctionalStepDefinitions.i_am_working_with_the_layer(String)
    And I have a datastore named "dataStore1" backed by a GeoGig repo                                # FunctionalStepDefinitions.i_have_a_datastore_backed_by_a_GeoGig_repo(String)
    And datastore "dataStore1" has 200 features per thread inserted using 4 threads                  # FunctionalStepDefinitions.datastore_has_features_inserted(String,int,int)
    Then I should be able to retrieve data from "dataStore1" using 4 threads and 40 reads per thread # FunctionalStepDefinitions.datastore_should_have_some_data(String,int,int)
    When I create a spatial index on "dataStore1"                                                    # FunctionalStepDefinitions.i_create_a_spatial_index_on(String)
    Then I should be able to retrieve data from "dataStore1" using 4 threads and 40 reads per thread # FunctionalStepDefinitions.datastore_should_have_some_data(String,int,int)

  Scenario: Ensure Polygon Features can be retrieved from a DataStore with an indexed repo           # features/index/FeatureReader.feature:26
    Given I am working with the "polygon" layer                                                      # FunctionalStepDefinitions.i_am_working_with_the_layer(String)
    And I have a datastore named "dataStore1" backed by a GeoGig repo                                # FunctionalStepDefinitions.i_have_a_datastore_backed_by_a_GeoGig_repo(String)
    And datastore "dataStore1" has 200 features per thread inserted using 4 threads                  # FunctionalStepDefinitions.datastore_has_features_inserted(String,int,int)
    Then I should be able to retrieve data from "dataStore1" using 4 threads and 40 reads per thread # FunctionalStepDefinitions.datastore_should_have_some_data(String,int,int)
    When I create a spatial index on "dataStore1"                                                    # FunctionalStepDefinitions.i_create_a_spatial_index_on(String)
    Then I should be able to retrieve data from "dataStore1" using 4 threads and 40 reads per thread # FunctionalStepDefinitions.datastore_should_have_some_data(String,int,int)

  Scenario: Ensure indexed Point Features match non-indexed Features                                 # features/index/FeatureReader.feature:34
    Given I am working with the "point" layer                                                        # FunctionalStepDefinitions.i_am_working_with_the_layer(String)
    And I have a datastore named "dataStore1" backed by a GeoGig repo                                # FunctionalStepDefinitions.i_have_a_datastore_backed_by_a_GeoGig_repo(String)
    And datastore "dataStore1" has 200 features per thread inserted using 4 threads                  # FunctionalStepDefinitions.datastore_has_features_inserted(String,int,int)
    And I have a datastore named "dataStore2" backed by a GeoGig repo                                # FunctionalStepDefinitions.i_have_a_datastore_backed_by_a_GeoGig_repo(String)
    And datastore "dataStore2" has the same data as "dataStore1"                                     # FunctionalStepDefinitions.datastore_has_same_data(String,String)
    When I create a spatial index on "dataStore1"                                                    # FunctionalStepDefinitions.i_create_a_spatial_index_on(String)
    Then I should be able to retrieve data from "dataStore1" using 4 threads and 40 reads per thread # FunctionalStepDefinitions.datastore_should_have_some_data(String,int,int)
    And datastore "dataStore1" and datastore "dataStore2" both have the same features                # FunctionalStepDefinitions.datastores_have_the_same_features(String,String)

  Scenario: Ensure indexed Polygon Features match non-indexed Features                               # features/index/FeatureReader.feature:44
    Given I am working with the "polygon" layer                                                      # FunctionalStepDefinitions.i_am_working_with_the_layer(String)
    And I have a datastore named "dataStore1" backed by a GeoGig repo                                # FunctionalStepDefinitions.i_have_a_datastore_backed_by_a_GeoGig_repo(String)
    And datastore "dataStore1" has 200 features per thread inserted using 4 threads                  # FunctionalStepDefinitions.datastore_has_features_inserted(String,int,int)
    And I have a datastore named "dataStore2" backed by a GeoGig repo                                # FunctionalStepDefinitions.i_have_a_datastore_backed_by_a_GeoGig_repo(String)
    And datastore "dataStore2" has the same data as "dataStore1"                                     # FunctionalStepDefinitions.datastore_has_same_data(String,String)
    When I create a spatial index on "dataStore1"                                                    # FunctionalStepDefinitions.i_create_a_spatial_index_on(String)
    Then I should be able to retrieve data from "dataStore1" using 4 threads and 40 reads per thread # FunctionalStepDefinitions.datastore_should_have_some_data(String,int,int)
    And datastore "dataStore1" and datastore "dataStore2" both have the same features                # FunctionalStepDefinitions.datastores_have_the_same_features(String,String)

  Scenario: Ensure Point Features can be retrieved from a DataStore after editing   # features/index/FeatureReader.feature:54
    Given I am working with the "point" layer                                       # FunctionalStepDefinitions.i_am_working_with_the_layer(String)
    And I have a datastore named "dataStore1" backed by a GeoGig repo               # FunctionalStepDefinitions.i_have_a_datastore_backed_by_a_GeoGig_repo(String)
    And datastore "dataStore1" has 200 features per thread inserted using 4 threads # FunctionalStepDefinitions.datastore_has_features_inserted(String,int,int)
    When I make an edit to "dataStore1"                                             # FunctionalStepDefinitions.i_make_an_edit_to(String)
    Then datastore "dataStore1" has the edited feature                              # FunctionalStepDefinitions.datastore_has_the_edited_feature(String)

  Scenario: Ensure Polygon Features can be retrieved from a DataStore after editing # features/index/FeatureReader.feature:61
    Given I am working with the "polygon" layer                                     # FunctionalStepDefinitions.i_am_working_with_the_layer(String)
    And I have a datastore named "dataStore1" backed by a GeoGig repo               # FunctionalStepDefinitions.i_have_a_datastore_backed_by_a_GeoGig_repo(String)
    And datastore "dataStore1" has 200 features per thread inserted using 4 threads # FunctionalStepDefinitions.datastore_has_features_inserted(String,int,int)
    When I make an edit to "dataStore1"                                             # FunctionalStepDefinitions.i_make_an_edit_to(String)
    Then datastore "dataStore1" has the edited feature                              # FunctionalStepDefinitions.datastore_has_the_edited_feature(String)

  Scenario: Ensure Point Features can be retrieved from a DataStore after editing with index         # features/index/FeatureReader.feature:68
    Given I am working with the "point" layer                                                        # FunctionalStepDefinitions.i_am_working_with_the_layer(String)
    And I have a datastore named "dataStore1" backed by a GeoGig repo                                # FunctionalStepDefinitions.i_have_a_datastore_backed_by_a_GeoGig_repo(String)
    And datastore "dataStore1" has 200 features per thread inserted using 4 threads                  # FunctionalStepDefinitions.datastore_has_features_inserted(String,int,int)
    When I create a spatial index on "dataStore1"                                                    # FunctionalStepDefinitions.i_create_a_spatial_index_on(String)
    Then I should be able to retrieve data from "dataStore1" using 4 threads and 40 reads per thread # FunctionalStepDefinitions.datastore_should_have_some_data(String,int,int)
    When I make an edit to "dataStore1"                                                              # FunctionalStepDefinitions.i_make_an_edit_to(String)
    Then datastore "dataStore1" has the edited feature                                               # FunctionalStepDefinitions.datastore_has_the_edited_feature(String)

  Scenario: Ensure Polygon Features can be retrieved from a DataStore after editing with index       # features/index/FeatureReader.feature:77
    Given I am working with the "polygon" layer                                                      # FunctionalStepDefinitions.i_am_working_with_the_layer(String)
    And I have a datastore named "dataStore1" backed by a GeoGig repo                                # FunctionalStepDefinitions.i_have_a_datastore_backed_by_a_GeoGig_repo(String)
    And datastore "dataStore1" has 200 features per thread inserted using 4 threads                  # FunctionalStepDefinitions.datastore_has_features_inserted(String,int,int)
    When I create a spatial index on "dataStore1"                                                    # FunctionalStepDefinitions.i_create_a_spatial_index_on(String)
    Then I should be able to retrieve data from "dataStore1" using 4 threads and 40 reads per thread # FunctionalStepDefinitions.datastore_should_have_some_data(String,int,int)
    When I make an edit to "dataStore1"                                                              # FunctionalStepDefinitions.i_make_an_edit_to(String)
    Then datastore "dataStore1" has the edited feature                                               # FunctionalStepDefinitions.datastore_has_the_edited_feature(String)

  Scenario: Ensure edited indexed Point Features match edited non-indexed Features     # features/index/FeatureReader.feature:86
    Given I am working with the "point" layer                                          # FunctionalStepDefinitions.i_am_working_with_the_layer(String)
    And I have a datastore named "dataStore1" backed by a GeoGig repo                  # FunctionalStepDefinitions.i_have_a_datastore_backed_by_a_GeoGig_repo(String)
    And datastore "dataStore1" has 200 features per thread inserted using 4 threads    # FunctionalStepDefinitions.datastore_has_features_inserted(String,int,int)
    And I have a datastore named "dataStore2" backed by a GeoGig repo                  # FunctionalStepDefinitions.i_have_a_datastore_backed_by_a_GeoGig_repo(String)
    And datastore "dataStore2" has the same data as "dataStore1"                       # FunctionalStepDefinitions.datastore_has_same_data(String,String)
    When I create a spatial index on "dataStore1"                                      # FunctionalStepDefinitions.i_create_a_spatial_index_on(String)
    And I make an edit to "dataStore1"                                                 # FunctionalStepDefinitions.i_make_an_edit_to(String)
    And I make the same edit to "dataStore2"                                           # FunctionalStepDefinitions.i_make_the_same_edit(String)
    Then datastore "dataStore1" and datastore "dataStore2" both have the same features # FunctionalStepDefinitions.datastores_have_the_same_features(String,String)

  Scenario: Ensure edited indexed Polygon Features match edited non-indexed Features   # features/index/FeatureReader.feature:97
    Given I am working with the "polygon" layer                                        # FunctionalStepDefinitions.i_am_working_with_the_layer(String)
    And I have a datastore named "dataStore1" backed by a GeoGig repo                  # FunctionalStepDefinitions.i_have_a_datastore_backed_by_a_GeoGig_repo(String)
    And datastore "dataStore1" has 200 features per thread inserted using 4 threads    # FunctionalStepDefinitions.datastore_has_features_inserted(String,int,int)
    And I have a datastore named "dataStore2" backed by a GeoGig repo                  # FunctionalStepDefinitions.i_have_a_datastore_backed_by_a_GeoGig_repo(String)
    And datastore "dataStore2" has the same data as "dataStore1"                       # FunctionalStepDefinitions.datastore_has_same_data(String,String)
    When I create a spatial index on "dataStore1"                                      # FunctionalStepDefinitions.i_create_a_spatial_index_on(String)
    And I make an edit to "dataStore1"                                                 # FunctionalStepDefinitions.i_make_an_edit_to(String)
    And I make the same edit to "dataStore2"                                           # FunctionalStepDefinitions.i_make_the_same_edit(String)
    Then datastore "dataStore1" and datastore "dataStore2" both have the same features # FunctionalStepDefinitions.datastores_have_the_same_features(String,String)

  Scenario: Ensure Point Features can be edited concurrently                                         # features/index/FeatureReader.feature:108
    Given I am working with the "point" layer                                                        # FunctionalStepDefinitions.i_am_working_with_the_layer(String)
    And I have a datastore named "dataStore1" backed by a GeoGig repo                                # FunctionalStepDefinitions.i_have_a_datastore_backed_by_a_GeoGig_repo(String)
    And datastore "dataStore1" has 200 features per thread inserted using 4 threads                  # FunctionalStepDefinitions.datastore_has_features_inserted(String,int,int)
    When I create a spatial index on "dataStore1"                                                    # FunctionalStepDefinitions.i_create_a_spatial_index_on(String)
    Then I should be able to retrieve data from "dataStore1" using 4 threads and 40 reads per thread # FunctionalStepDefinitions.datastore_should_have_some_data(String,int,int)
    When I make 20 edits to "dataStore1" using 4 edit threads                                        # FunctionalStepDefinitions.i_make_concurrent_edits(int,String,int)
    Then datastore "dataStore1" has the edited features                                              # FunctionalStepDefinitions.datastore_has_the_edited_features(String)

  Scenario: Ensure Polygon Features can be edited concurrently                                       # features/index/FeatureReader.feature:117
    Given I am working with the "polygon" layer                                                      # FunctionalStepDefinitions.i_am_working_with_the_layer(String)
    And I have a datastore named "dataStore1" backed by a GeoGig repo                                # FunctionalStepDefinitions.i_have_a_datastore_backed_by_a_GeoGig_repo(String)
    And datastore "dataStore1" has 200 features per thread inserted using 4 threads                  # FunctionalStepDefinitions.datastore_has_features_inserted(String,int,int)
    When I create a spatial index on "dataStore1"                                                    # FunctionalStepDefinitions.i_create_a_spatial_index_on(String)
    Then I should be able to retrieve data from "dataStore1" using 4 threads and 40 reads per thread # FunctionalStepDefinitions.datastore_should_have_some_data(String,int,int)
    When I make 20 edits to "dataStore1" using 4 edit threads                                        # FunctionalStepDefinitions.i_make_concurrent_edits(int,String,int)
    Then datastore "dataStore1" has the edited features                                              # FunctionalStepDefinitions.datastore_has_the_edited_features(String)

  Scenario: Ensure Point Features can be edited concurrently with concurrent reads                              # features/index/FeatureReader.feature:126
    Given I am working with the "point" layer                                                                   # FunctionalStepDefinitions.i_am_working_with_the_layer(String)
    And I have a datastore named "dataStore1" backed by a GeoGig repo                                           # FunctionalStepDefinitions.i_have_a_datastore_backed_by_a_GeoGig_repo(String)
    And datastore "dataStore1" has 200 features per thread inserted using 4 threads                             # FunctionalStepDefinitions.datastore_has_features_inserted(String,int,int)
    When I create a spatial index on "dataStore1"                                                               # FunctionalStepDefinitions.i_create_a_spatial_index_on(String)
    And I make 20 edits to "dataStore1" using 4 edit threads while using 20 read threads and 8 reads per thread # FunctionalStepDefinitions.i_make_concurrent_edits_and_reads(int,String,int,int,int)
    Then datastore "dataStore1" has the edited features                                                         # FunctionalStepDefinitions.datastore_has_the_edited_features(String)

  Scenario: Ensure Polygon Features can be edited concurrently with concurrent reads                            # features/index/FeatureReader.feature:134
    Given I am working with the "polygon" layer                                                                 # FunctionalStepDefinitions.i_am_working_with_the_layer(String)
    And I have a datastore named "dataStore1" backed by a GeoGig repo                                           # FunctionalStepDefinitions.i_have_a_datastore_backed_by_a_GeoGig_repo(String)
    And datastore "dataStore1" has 200 features per thread inserted using 4 threads                             # FunctionalStepDefinitions.datastore_has_features_inserted(String,int,int)
    When I create a spatial index on "dataStore1"                                                               # FunctionalStepDefinitions.i_create_a_spatial_index_on(String)
    And I make 20 edits to "dataStore1" using 4 edit threads while using 20 read threads and 8 reads per thread # FunctionalStepDefinitions.i_make_concurrent_edits_and_reads(int,String,int,int,int)
    Then datastore "dataStore1" has the edited features                                                         # FunctionalStepDefinitions.datastore_has_the_edited_features(String)

16 Scenarios (16 passed)
104 Steps (104 passed)
2m25.716s

Tests run: 120, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 147.438 sec - in org.locationtech.geogig.geotools.data.functional.RunDataStoreFunctionalTest

Results :

Tests in error: 
  GeoGigFeatureSourceTest.testGetCount:287 » NoSuchMethod org.locationtech.jts.g...
  GeoGigFeatureSourceTest.testGetFeaturesFilter:366->toList:522 » NoSuchMethod o...
  GeoGigFeatureSourceTest.testGetBoundsQuery:212 » NoSuchMethod org.locationtech...
  GeoGigFeatureSourceTest.testGetBoundsQueryWithSpatialIndex:250 » NoSuchMethod ...
  GeoGigDataStoreTest.testFeatureWriterAppend:364 » NoSuchMethod org.locationtec...

Tests run: 321, Failures: 0, Errors: 5, Skipped: 0

[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO] 
[INFO] GeoGig ............................................. SUCCESS [  5.572 s]
[INFO] GeoGig Core API .................................... SUCCESS [ 12.721 s]
[INFO] GeoGig Core ........................................ SUCCESS [01:46 min]
[INFO] Replication and synchronization .................... SUCCESS [ 41.855 s]
[INFO] GeoGig DataStore Implementation .................... FAILURE [02:53 min]
[INFO] Storage backends ................................... SKIPPED
[INFO] RocksDB storage backend ............................ SKIPPED
[INFO] GeoGig Command Line Interface ...................... SKIPPED
[INFO] GeoGig Command Line Interface Core ................. SKIPPED
[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: 05:40 min
[INFO] Finished at: 2018-08-21T11:50:44+00:00
[INFO] Final Memory: 93M/1329M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.17:test (default-test) on project geogig-datastore: There are test failures.
[ERROR] 
[ERROR] Please refer to <https://build.geoserver.org/job/geogig-master-nightly/ws/src/datastore/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-datastore
Build step 'Invoke top-level Maven targets' marked build as failure
[Cucumber Tests] Parsing results.
[Cucumber Tests] parsing cucumber.json


Back to the top