SuccessConsole Output

Started calculate disk usage of build
Finished Calculation of disk usage of build in 0 seconds
Started calculate disk usage of workspace
Finished Calculation of disk usage of workspace in 0 seconds
[INFO] 
[INFO] --------------< org.locationtech.geogig:geogig-datastore >--------------
[INFO] Building GeoGig DataStore Implementation 1.4-SNAPSHOT             [5/21]
[INFO] --------------------------------[ jar ]---------------------------------
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ geogig-datastore ---
[INFO] Deleting /home/hudson/genie.geogig/.jenkins/jobs/geogig-master/workspace/src/datastore/target
[INFO] 
[INFO] --- git-commit-id-plugin:2.2.2:revision (default) @ geogig-datastore ---
[INFO] 
[INFO] --- maven-resources-plugin:3.0.1:resources (default-resources) @ geogig-datastore ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 4 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.7.0:compile (default-compile) @ geogig-datastore ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 25 source files to /home/hudson/genie.geogig/.jenkins/jobs/geogig-master/workspace/src/datastore/target/classes
[INFO] /home/hudson/genie.geogig/.jenkins/jobs/geogig-master/workspace/src/datastore/src/main/java/org/locationtech/geogig/geotools/data/reader/ExtraDataPropertyAccessorFactory.java: /home/hudson/genie.geogig/.jenkins/jobs/geogig-master/workspace/src/datastore/src/main/java/org/locationtech/geogig/geotools/data/reader/ExtraDataPropertyAccessorFactory.java uses unchecked or unsafe operations.
[INFO] /home/hudson/genie.geogig/.jenkins/jobs/geogig-master/workspace/src/datastore/src/main/java/org/locationtech/geogig/geotools/data/reader/ExtraDataPropertyAccessorFactory.java: Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-resources-plugin:3.0.1:testResources (default-testResources) @ geogig-datastore ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.7.0:testCompile (default-testCompile) @ geogig-datastore ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 16 source files to /home/hudson/genie.geogig/.jenkins/jobs/geogig-master/workspace/src/datastore/target/test-classes
[INFO] /home/hudson/genie.geogig/.jenkins/jobs/geogig-master/workspace/src/datastore/src/test/java/org/locationtech/geogig/geotools/data/reader/FeatureReaderBuilderTest.java: /home/hudson/genie.geogig/.jenkins/jobs/geogig-master/workspace/src/datastore/src/test/java/org/locationtech/geogig/geotools/data/reader/FeatureReaderBuilderTest.java uses unchecked or unsafe operations.
[INFO] /home/hudson/genie.geogig/.jenkins/jobs/geogig-master/workspace/src/datastore/src/test/java/org/locationtech/geogig/geotools/data/reader/FeatureReaderBuilderTest.java: Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-surefire-plugin:2.17:test (default-test) @ geogig-datastore ---
[INFO] Surefire report directory: /home/hudson/genie.geogig/.jenkins/jobs/geogig-master/workspace/src/datastore/target/surefire-reports

-------------------------------------------------------
 T E S T S
-------------------------------------------------------

-------------------------------------------------------
 T E S T S
-------------------------------------------------------
Picked up JAVA_TOOL_OPTIONS: -Xmx2G -Djava.io.tmpdir=/tmp/genie.geogig
Picked up JAVA_TOOL_OPTIONS: -Xmx2G -Djava.io.tmpdir=/tmp/genie.geogig
Picked up JAVA_TOOL_OPTIONS: -Xmx2G -Djava.io.tmpdir=/tmp/genie.geogig
Picked up JAVA_TOOL_OPTIONS: -Xmx2G -Djava.io.tmpdir=/tmp/genie.geogig
Picked up JAVA_TOOL_OPTIONS: -Xmx2G -Djava.io.tmpdir=/tmp/genie.geogig
Picked up JAVA_TOOL_OPTIONS: -Xmx2G -Djava.io.tmpdir=/tmp/genie.geogig
Picked up JAVA_TOOL_OPTIONS: -Xmx2G -Djava.io.tmpdir=/tmp/genie.geogig
Picked up JAVA_TOOL_OPTIONS: -Xmx2G -Djava.io.tmpdir=/tmp/genie.geogig
Picked up JAVA_TOOL_OPTIONS: -Xmx2G -Djava.io.tmpdir=/tmp/genie.geogig
Picked up JAVA_TOOL_OPTIONS: -Xmx2G -Djava.io.tmpdir=/tmp/genie.geogig
Picked up JAVA_TOOL_OPTIONS: -Xmx2G -Djava.io.tmpdir=/tmp/genie.geogig
Picked up JAVA_TOOL_OPTIONS: -Xmx2G -Djava.io.tmpdir=/tmp/genie.geogig
Picked up JAVA_TOOL_OPTIONS: -Xmx2G -Djava.io.tmpdir=/tmp/genie.geogig
Picked up JAVA_TOOL_OPTIONS: -Xmx2G -Djava.io.tmpdir=/tmp/genie.geogig
Running org.locationtech.geogig.geotools.data.reader.FeatureReaderBuilderTest
Running org.locationtech.geogig.geotools.data.reader.PreFilterTest
Running org.locationtech.geogig.geotools.data.reader.MaterializedIndexFeatureIteratorTest
Running org.locationtech.geogig.geotools.data.reader.ExtraDataPropertyAccessorFactoryTest
Running org.locationtech.geogig.geotools.data.reader.PrePostFilterSplitterTest
Running org.locationtech.geogig.geotools.data.GeoGigDataStoreFactoryTest
Running org.locationtech.geogig.geotools.data.GeoGigFeatureStoreIndexedTest
Running org.locationtech.geogig.geotools.data.GeoGigDataStoreTest
Running org.locationtech.geogig.geotools.data.stresstest.DataStoreConcurrencyTest
Running org.locationtech.geogig.geotools.data.GeoGigFeatureStoreTest
Running org.locationtech.geogig.geotools.data.functional.RunDataStoreFunctionalTest
Running org.locationtech.geogig.geotools.data.functional.RunDataStoreDimensionTest
Running org.locationtech.geogig.geotools.data.GeoGigDiffFeatureSourceTest
Running org.locationtech.geogig.geotools.data.GeoGigFeatureSourceTest
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.975 sec - in org.locationtech.geogig.geotools.data.reader.ExtraDataPropertyAccessorFactoryTest
Feature: GeoGig DataStore Feature read/write validation
  The GeoGig DataStore is the integration point between GeoServer/OGC services
  and GeoGig repositories. These scenarios are meant to ensure data/feature
  integrity via interactions with the DataStore.
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: 30, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.423 sec - in org.locationtech.geogig.geotools.data.reader.PreFilterTest
Tests run: 38, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.806 sec - in org.locationtech.geogig.geotools.data.reader.PrePostFilterSplitterTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.422 sec - in org.locationtech.geogig.geotools.data.reader.MaterializedIndexFeatureIteratorTest
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.997 sec - in org.locationtech.geogig.geotools.data.GeoGigDataStoreFactoryTest
2018-09-11T14:54:44.261-0400  WARNING  Feature Collection contains a heterogeneous mix of features
2018-09-11T14:54:45.252-0400  WARNING  Feature Collection contains a heterogeneous mix of features

  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: 14, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 7.27 sec - in org.locationtech.geogig.geotools.data.GeoGigDataStoreTest
2018-09-11T14:54:45.832-0400  WARNING  Feature Collection contains a heterogeneous mix of features
Tests run: 16, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 7.904 sec - in org.locationtech.geogig.geotools.data.reader.FeatureReaderBuilderTest
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 7.93 sec - in org.locationtech.geogig.geotools.data.GeoGigDiffFeatureSourceTest

  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 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: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 9.131 sec - in org.locationtech.geogig.geotools.data.GeoGigFeatureStoreTest

  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)
0m8.389s

Tests run: 21, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 9.629 sec - in org.locationtech.geogig.geotools.data.functional.RunDataStoreDimensionTest
2018-09-11T14:54:48.183-0400  WARNING  Feature Collection contains a heterogeneous mix of features
2018-09-11T14:54:48.733-0400  WARNING  Feature Collection contains a heterogeneous mix of features
2018-09-11T14:54:48.845-0400  WARNING  Feature Collection contains a heterogeneous mix of features

  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)
Tests run: 25, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 11.045 sec - in org.locationtech.geogig.geotools.data.GeoGigFeatureSourceTest
Tests run: 17, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 11.427 sec - in org.locationtech.geogig.geotools.data.GeoGigFeatureStoreIndexedTest

  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)
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 17.965 sec - in org.locationtech.geogig.geotools.data.stresstest.DataStoreConcurrencyTest

  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)
2m0.141s

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

Results :

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

[JENKINS] Recording test results
[INFO] 
[INFO] --- maven-jar-plugin:3.0.2:jar (default-jar) @ geogig-datastore ---
[INFO] Building jar: /home/hudson/genie.geogig/.jenkins/jobs/geogig-master/workspace/src/datastore/target/geogig-datastore-1.4-SNAPSHOT.jar
[INFO] 
[INFO] --- maven-jar-plugin:3.0.2:test-jar (default) @ geogig-datastore ---
[INFO] Building jar: /home/hudson/genie.geogig/.jenkins/jobs/geogig-master/workspace/src/datastore/target/geogig-datastore-1.4-SNAPSHOT-tests.jar
[INFO] 
[INFO] >>> maven-source-plugin:3.0.1:jar (attach-sources) > generate-sources @ geogig-datastore >>>
[INFO] 
[INFO] --- git-commit-id-plugin:2.2.2:revision (default) @ geogig-datastore ---
[WARNING] Failed to getClass for org.apache.maven.plugins.source.SourceJarMojo
[INFO] 
[INFO] <<< maven-source-plugin:3.0.1:jar (attach-sources) < generate-sources @ geogig-datastore <<<
[INFO] 
[INFO] 
[INFO] --- maven-source-plugin:3.0.1:jar (attach-sources) @ geogig-datastore ---
[INFO] Building jar: /home/hudson/genie.geogig/.jenkins/jobs/geogig-master/workspace/src/datastore/target/geogig-datastore-1.4-SNAPSHOT-sources.jar
[INFO] 
[INFO] >>> maven-source-plugin:3.0.1:test-jar (attach-sources) > generate-sources @ geogig-datastore >>>
[INFO] 
[INFO] --- git-commit-id-plugin:2.2.2:revision (default) @ geogig-datastore ---
[WARNING] Failed to getClass for org.apache.maven.plugins.source.TestSourceJarMojo
[INFO] 
[INFO] <<< maven-source-plugin:3.0.1:test-jar (attach-sources) < generate-sources @ geogig-datastore <<<
[INFO] 
[INFO] 
[INFO] --- maven-source-plugin:3.0.1:test-jar (attach-sources) @ geogig-datastore ---
[INFO] Building jar: /home/hudson/genie.geogig/.jenkins/jobs/geogig-master/workspace/src/datastore/target/geogig-datastore-1.4-SNAPSHOT-test-sources.jar
[INFO] 
[INFO] --- maven-install-plugin:2.4:install (default-install) @ geogig-datastore ---
[INFO] Installing /home/hudson/genie.geogig/.jenkins/jobs/geogig-master/workspace/src/datastore/target/geogig-datastore-1.4-SNAPSHOT.jar to /home/hudson/genie.geogig/.jenkins/jobs/geogig-master/workspace/.repository/org/locationtech/geogig/geogig-datastore/1.4-SNAPSHOT/geogig-datastore-1.4-SNAPSHOT.jar
[INFO] Installing /home/hudson/genie.geogig/.jenkins/jobs/geogig-master/workspace/src/datastore/pom.xml to /home/hudson/genie.geogig/.jenkins/jobs/geogig-master/workspace/.repository/org/locationtech/geogig/geogig-datastore/1.4-SNAPSHOT/geogig-datastore-1.4-SNAPSHOT.pom
[INFO] Installing /home/hudson/genie.geogig/.jenkins/jobs/geogig-master/workspace/src/datastore/target/geogig-datastore-1.4-SNAPSHOT-tests.jar to /home/hudson/genie.geogig/.jenkins/jobs/geogig-master/workspace/.repository/org/locationtech/geogig/geogig-datastore/1.4-SNAPSHOT/geogig-datastore-1.4-SNAPSHOT-tests.jar
[INFO] Installing /home/hudson/genie.geogig/.jenkins/jobs/geogig-master/workspace/src/datastore/target/geogig-datastore-1.4-SNAPSHOT-sources.jar to /home/hudson/genie.geogig/.jenkins/jobs/geogig-master/workspace/.repository/org/locationtech/geogig/geogig-datastore/1.4-SNAPSHOT/geogig-datastore-1.4-SNAPSHOT-sources.jar
[INFO] Installing /home/hudson/genie.geogig/.jenkins/jobs/geogig-master/workspace/src/datastore/target/geogig-datastore-1.4-SNAPSHOT-test-sources.jar to /home/hudson/genie.geogig/.jenkins/jobs/geogig-master/workspace/.repository/org/locationtech/geogig/geogig-datastore/1.4-SNAPSHOT/geogig-datastore-1.4-SNAPSHOT-test-sources.jar
[JENKINS] Archiving disabled