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-cli-geotools >-------------
[INFO] Building GeoGig CLI GeoTools 1.4-SNAPSHOT                        [17/21]
[INFO] --------------------------------[ jar ]---------------------------------
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ geogig-cli-geotools ---
[INFO] Deleting /home/hudson/genie.geogig/.jenkins/jobs/geogig-master/workspace/src/cli/geotools/target
[INFO] 
[INFO] --- git-commit-id-plugin:2.2.2:revision (default) @ geogig-cli-geotools ---
[INFO] 
[INFO] --- maven-resources-plugin:3.0.1:resources (default-resources) @ geogig-cli-geotools ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.7.0:compile (default-compile) @ geogig-cli-geotools ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 30 source files to /home/hudson/genie.geogig/.jenkins/jobs/geogig-master/workspace/src/cli/geotools/target/classes
[INFO] 
[INFO] --- maven-resources-plugin:3.0.1:testResources (default-testResources) @ geogig-cli-geotools ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 14 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.7.0:testCompile (default-testCompile) @ geogig-cli-geotools ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 21 source files to /home/hudson/genie.geogig/.jenkins/jobs/geogig-master/workspace/src/cli/geotools/target/test-classes
[INFO] 
[INFO] --- maven-surefire-plugin:2.17:test (default-test) @ geogig-cli-geotools ---
[INFO] Surefire report directory: /home/hudson/genie.geogig/.jenkins/jobs/geogig-master/workspace/src/cli/geotools/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
Picked up JAVA_TOOL_OPTIONS: -Xmx2G -Djava.io.tmpdir=/tmp/genie.geogig
Running org.locationtech.geogig.geotools.cli.geojson.GeoJsonExportTest
Running org.locationtech.geogig.geotools.cli.geojson.GeoJsonImportTest
Running org.locationtech.geogig.geotools.cli.shp.ShpExportTest
Running org.locationtech.geogig.geotools.cli.shp.RunShpFunctionalTest
Running org.locationtech.geogig.geotools.cli.shp.ShpImportTest
Running org.locationtech.geogig.geotools.cli.postgis.PGListTest
Running org.locationtech.geogig.geotools.cli.postgis.PGDescribeTest
Running org.locationtech.geogig.geotools.cli.postgis.PGImportTest
Running org.locationtech.geogig.geotools.cli.postgis.PGExportTest
Running org.locationtech.geogig.geotools.cli.geopkg.GeoPkgDescribeTest
Running org.locationtech.geogig.geotools.cli.geopkg.GeoPkgListTest
Running org.locationtech.geogig.geotools.cli.geopkg.GeoPkgPullTest
Running org.locationtech.geogig.geotools.cli.geopkg.GeoPkgExportTest
Running org.locationtech.geogig.geotools.cli.geopkg.GeoPkgImportTest
Running org.locationtech.geogig.geotools.cli.geopkg.RunGeoPkgFunctionalTest
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
Feature: "shp export" command
    In order to export data to Geogig
    As a Geogig User
    I want to export from the repository to a shapefile
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
Feature: "geopkg describe" command
    In order to understand the structure of a table in a GeoPackage file
    As a Geogig User
    I want Geogig to describe the table
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
Usage: geogig describe [options]
  Options:
    --database, -D
       The database to connect to.  Default: database.gpkg
       Default: /opt/public/hipp/ramdisk/geogig/geogig_geopackage_test4098792874504969952.gpkg
  * --table, -t
       Table to describe.
       Default: <empty string>
    --user, -U
       User name.  Default: user
       Default: user

SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
Usage: geogig describe [options]
  Options:
    --database, -D
       The database to connect to.  Default: database
       Default: database
    --host, -H
       Machine name or IP address to connect to. Default: localhost
       Default: localhost
    --password, -W
       Password.  Default: <no password>
       Default: <empty string>
    --port, -P
       Port number to connect to.  Default: 5432
       Default: 5432
    --schema, -S
       The database schema to access.  Default: public
       Default: public
  * --table, -t
       Table to describe.
       Default: <empty string>
    --user, -U
       User name.  Default: postgres
       Default: postgres

The GeoJSON file 'file://nonexistent.geojson' could not be found, skipping...
Importing from database database
The shapefile '/home/hudson/genie.geogig/.jenkins/jobs/geogig-master/workspace/src/cli/geotools/target/test-classes/org/locationtech/geogig/geotools/cli/shp/shape.shp' could not be found, skipping...
Usage: geogig import [options] <geojson> [<geojson>]...
  Options:
    --add
       Do not replace or delete features on the destination path, but just add
       new ones
       Default: false
    --alter
       Set the path default feature type to the the feature type of imported
       features, and modify existing features to match it
       Default: false
    -d, --dest
       Path to import to
    --fid-attrib
       Use the specified attribute to create the feature Id
    --force-featuretype
       Use origin feature type even if it does not match the default destination
       featuretype
       Default: false
    --geom-name
       Name to use for geometry attribute, replacing the default one
       ('geometry')
    --geom-name-auto
       Uses the name of the geometry descriptor in the destination feature type
       Default: false

2018-12-17T21:57:50.127-0500  SEVERE  Connection error: 
org.postgresql.util.PSQLException: The connection attempt failed.
	at org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:275)
	at org.postgresql.core.ConnectionFactory.openConnection(ConnectionFactory.java:49)
	at org.postgresql.jdbc.PgConnection.<init>(PgConnection.java:194)
	at org.postgresql.Driver.makeConnection(Driver.java:450)
	at org.postgresql.Driver.connect(Driver.java:252)
	at org.apache.commons.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:38)
	at org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:582)
	at org.apache.commons.dbcp.BasicDataSource.validateConnectionFactory(BasicDataSource.java:1556)
	at org.apache.commons.dbcp.BasicDataSource.createPoolableConnectionFactory(BasicDataSource.java:1545)
	at org.apache.commons.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1388)
	at org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:1044)
	at org.geotools.data.jdbc.datasource.AbstractManageableDataSource.getConnection(AbstractManageableDataSource.java:42)
	at org.locationtech.geogig.geotools.cli.postgis.PGSupport.getDataStore(PGSupport.java:74)
	at org.locationtech.geogig.geotools.cli.postgis.PGDescribe.getDataStore(PGDescribe.java:40)
	at org.locationtech.geogig.geotools.cli.DataStoreDescribe.runInternal(DataStoreDescribe.java:51)
	at org.locationtech.geogig.cli.AbstractCommand.run(AbstractCommand.java:67)
	at org.locationtech.geogig.geotools.cli.postgis.PGDescribeTest.testInvalidDatabaseParams(PGDescribeTest.java:76)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
	at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
	at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
	at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
	at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
	at org.junit.rules.ExpectedException$ExpectedExceptionStatement.evaluate(ExpectedException.java:239)
	at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
	at org.junit.rules.RunRules.evaluate(RunRules.java:20)
	at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
	at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124)
	at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
Caused by: java.net.UnknownHostException: nonexistent
	at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:184)
	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
	at java.net.Socket.connect(Socket.java:589)
	at org.postgresql.core.PGStream.<init>(PGStream.java:68)
	at org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:144)
	... 44 more

Importing from database database
Importing from shapefile /home/hudson/genie.geogig/.jenkins/jobs/geogig-master/workspace/src/cli/geotools/target/test-classes/org/locationtech/geogig/geotools/cli/shp/shape.shp

0%
Importing table2           (1/2)... 
Importing from database database
Importing from GeoJSON /home/hudson/genie.geogig/.jenkins/jobs/geogig-master/workspace/src/cli/geotools/target/test-classes/org/locationtech/geogig/geotools/cli/geojson/sample.geojson

Importing feature          (1/1)... 
Usage: geogig export [options] <path> <geojson>
  Options:
    --alter
       Export all features if several types are found, altering them to adapt to
       the output feature type
       Default: false
    --defaulttype
       Export only features with the tree default feature type if several types
       are found
       Default: false
    --featuretype
       Export only features with the specified feature type if several types are
       found
    --overwrite, -o
       Overwrite output file
       Default: false


1 features inserted in 12.54 ms

Building final tree table2...

1 features tree built in 860.7 μs

Importing table1           (2/2)... 

1%
2 features inserted in 543.7 ms

Building final tree importedTable...

2 features tree built in 12.40 ms

100%/home/hudson/genie.geogig/.jenkins/jobs/geogig-master/workspace/src/cli/geotools/target/test-classes/org/locationtech/geogig/geotools/cli/geojson/sample.geojson imported successfully.
Fetching table...
2018-12-17T21:57:52.356-0500  SEVERE  Connection error: 
org.postgresql.util.PSQLException: The connection attempt failed.
	at org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:275)
	at org.postgresql.core.ConnectionFactory.openConnection(ConnectionFactory.java:49)
	at org.postgresql.jdbc.PgConnection.<init>(PgConnection.java:194)
	at org.postgresql.Driver.makeConnection(Driver.java:450)
	at org.postgresql.Driver.connect(Driver.java:252)
	at org.apache.commons.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:38)
	at org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:582)
	at org.apache.commons.dbcp.BasicDataSource.validateConnectionFactory(BasicDataSource.java:1556)
	at org.apache.commons.dbcp.BasicDataSource.createPoolableConnectionFactory(BasicDataSource.java:1545)
	at org.apache.commons.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1388)
	at org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:1044)
	at org.geotools.data.jdbc.datasource.AbstractManageableDataSource.getConnection(AbstractManageableDataSource.java:42)
	at org.locationtech.geogig.geotools.cli.postgis.PGSupport.getDataStore(PGSupport.java:74)
	at org.locationtech.geogig.geotools.cli.postgis.PGList.getDataStore(PGList.java:42)
	at org.locationtech.geogig.geotools.cli.DataStoreList.runInternal(DataStoreList.java:41)
	at org.locationtech.geogig.cli.AbstractCommand.run(AbstractCommand.java:67)
	at org.locationtech.geogig.geotools.cli.postgis.PGListTest.testInvalidDatabaseParams(PGListTest.java:69)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
	at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
	at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
	at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
	at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
	at org.junit.rules.ExpectedException$ExpectedExceptionStatement.evaluate(ExpectedException.java:239)
	at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
	at org.junit.rules.RunRules.evaluate(RunRules.java:20)
	at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
	at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124)
	at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
Caused by: java.net.UnknownHostException: nonexistent
	at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:184)
	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
	at java.net.Socket.connect(Socket.java:589)
	at org.postgresql.core.PGStream.<init>(PGStream.java:68)
	at org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:144)
	... 44 more


Exporting from WORK_HEAD:Points to Points... 
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 8.058 sec - in org.locationtech.geogig.geotools.cli.geojson.GeoJsonImportTest

100%WORK_HEAD:Points exported successfully to /opt/public/hipp/ramdisk/geogig/junit6192568280530235539/repo-403927158/TestPoints.geojson
Fetching table...
2018-12-17T21:57:52.722-0500  SEVERE  Connection error: 
org.postgresql.util.PSQLException: The connection attempt failed.
	at org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:275)
	at org.postgresql.core.ConnectionFactory.openConnection(ConnectionFactory.java:49)
	at org.postgresql.jdbc.PgConnection.<init>(PgConnection.java:194)
	at org.postgresql.Driver.makeConnection(Driver.java:450)
	at org.postgresql.Driver.connect(Driver.java:252)
	at org.apache.commons.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:38)
	at org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:582)
	at org.apache.commons.dbcp.BasicDataSource.validateConnectionFactory(BasicDataSource.java:1556)
	at org.apache.commons.dbcp.BasicDataSource.createPoolableConnectionFactory(BasicDataSource.java:1545)
	at org.apache.commons.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1388)
	at org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:1044)
	at org.geotools.data.jdbc.datasource.AbstractManageableDataSource.getConnection(AbstractManageableDataSource.java:42)
	at org.locationtech.geogig.geotools.cli.postgis.PGSupport.getDataStore(PGSupport.java:74)
	at org.locationtech.geogig.geotools.cli.postgis.PGImport.getDataStore(PGImport.java:39)
	at org.locationtech.geogig.geotools.cli.DataStoreImport.runInternal(DataStoreImport.java:95)
	at org.locationtech.geogig.cli.AbstractCommand.run(AbstractCommand.java:67)
	at org.locationtech.geogig.geotools.cli.postgis.PGImportTest.testInvalidDatabaseParams(PGImportTest.java:100)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
	at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
	at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
	at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
	at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
	at org.junit.rules.ExpectedException$ExpectedExceptionStatement.evaluate(ExpectedException.java:239)
	at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
	at org.junit.rules.RunRules.evaluate(RunRules.java:20)
	at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
	at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124)
	at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
Caused by: java.net.UnknownHostException: nonexistent
	at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:184)
	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
	at java.net.Socket.connect(Socket.java:589)
	at org.postgresql.core.PGStream.<init>(PGStream.java:68)
	at org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:144)
	... 44 more

Fetching feature types...
 - GeoJsonLikeTable
 - GeoJsonLikeTable2
 - shpLikeTable
 - shpLikeTable2
 - table1
 - table2
 - table3
 - table4
Usage: geogig export [options] <path> <shapefile>
  Options:
    --alter
       Export all features if several types are found, altering them to adapt to
       the output feature type
       Default: false
    --charset
       Use the specified charset to encode attributes. Default is ISO-8859-1.
       Default: ISO-8859-1
    --defaulttype
       Export only features with the tree default feature type if several types
       are found
       Default: false
    --featuretype
       Export only features with the specified feature type if several types are
       found
    --overwrite, -o
       Overwrite output file
       Default: false

Fetching table...
Table : table1
----------------------------------------
	Property  : label
	Type      : String
----------------------------------------
	Property  : geom
	Type      : Point
----------------------------------------
The shapefile 'file://nonexistent.shp' could not be found, skipping...
Fetching feature types...
Importing from database database

Importing table2           (1/2)... 
Fetching table...
Fetching feature types...
Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 9.301 sec - in org.locationtech.geogig.geotools.cli.postgis.PGDescribeTest

Exporting from Points to Points... 

100%Points exported successfully to /opt/public/hipp/ramdisk/geogig/junit5261274891973785615/repo255253591/TestPoints.geojson

0%
1 features inserted in 9.171 ms

Building final tree table2...

1 features tree built in 822.8 μs

Importing table1           (2/2)... 
Importing from shapefile /home/hudson/genie.geogig/.jenkins/jobs/geogig-master/workspace/src/cli/geotools/target/test-classes/org/locationtech/geogig/geotools/cli/shp/shape.shp

0%Usage: geogig list [options]
  Options:
    --database, -D
       The database to connect to.  Default: database
       Default: database
    --host, -H
       Machine name or IP address to connect to. Default: localhost
       Default: localhost
    --password, -W
       Password.  Default: <no password>
       Default: <empty string>
    --port, -P
       Port number to connect to.  Default: 5432
       Default: 5432
    --schema, -S
       The database schema to access.  Default: public
       Default: public
    --user, -U
       User name.  Default: postgres
       Default: postgres

Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 10.052 sec - in org.locationtech.geogig.geotools.cli.postgis.PGListTest
Importing from database database

Exporting from Points to Points... 

100%Points exported successfully to /opt/public/hipp/ramdisk/geogig/junit1368479274179710165/repo-1590280295/TestPoints.geojson

Exporting from Lines to Lines... 
Lines exported successfully to /opt/public/hipp/ramdisk/geogig/junit1368479274179710165/repo-1590280295/TestPoints.geojson
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 10.764 sec - in org.locationtech.geogig.geotools.cli.geojson.GeoJsonExportTest
Importing from database database

Importing table1           (1/1)... 

2 features inserted in 2.448 ms

Building final tree table1...

2 features tree built in 637.6 μs
Usage: geogig import [options] <shapefile> [<shapefile>]...
  Options:
    --add
       Do not replace or delete features on the destination path, but just add
       new ones
       Default: false
    --alter
       Set the path default feature type to the the feature type of imported
       features, and modify existing features to match it
       Default: false
    --charset
       Use the specified charset to decode attributes. Default is ISO-8859-1.
       Default: ISO-8859-1
    -f, --cql-filter
       GetoTools ECQL filter
    --create, -c
       Only create the schema, do not actually import its features
       Default: false
    -d, --dest
       Path to import to
    --fid-attrib
       Use the specified attribute to create the feature Id
    --force-featuretype
       Use origin feature type even if it does not match the default destination
       featuretype
       Default: false


100%Import successful.
Importing from database database
Importing from shapefile /home/hudson/genie.geogig/.jenkins/jobs/geogig-master/workspace/src/cli/geotools/target/test-classes/org/locationtech/geogig/geotools/cli/shp/shape.shp

0%
Importing table4           (1/8)... 

Importing table3           (2/8)... 

1 features inserted in 2.787 ms

Building final tree table3...

1 features tree built in 860.2 μs

Importing table2           (3/8)... 

1 features inserted in 1.482 ms

Building final tree table2...

1 features tree built in 573.8 μs

Importing table1           (4/8)... 

2 features inserted in 1.900 ms

Building final tree table1...

2 features tree built in 654.2 μs

Importing shpLikeTable2    (5/8)... 

1 features inserted in 1.747 ms

Building final tree shpLikeTable2...

1 features tree built in 632.2 μs

Importing shpLikeTable     (6/8)... 

1 features inserted in 1.680 ms

Building final tree shpLikeTable...

1 features tree built in 426.8 μs

Importing GeoJsonLikeTa... (7/8)... 

1 features inserted in 1.395 ms

Building final tree GeoJsonLikeTable2...

1 features tree built in 379.7 μs

Importing GeoJsonLikeTable (8/8)... 

1 features inserted in 1.181 ms

Building final tree GeoJsonLikeTable...

1 features tree built in 428.0 μs

100%/home/hudson/genie.geogig/.jenkins/jobs/geogig-master/workspace/src/cli/geotools/target/test-classes/org/locationtech/geogig/geotools/cli/shp/shape.shp imported successfully.
Usage: geogig import [options]
  Options:
    --add
       Do not replace or delete features on the destination path, but just add
       new ones
       Default: false
    --all
       Import all tables.
       Default: false
    --alter
       Set the path default feature type to the the feature type of imported
       features, and modify existing features to match it
       Default: false
    -f, --cql-filter
       GetoTools ECQL filter
    --database, -D
       The database to connect to.  Default: database
       Default: database
    -d, --dest
       Path to import to
    --fid-attrib
       Use the specified attribute to create the feature Id
    --force-featuretype
       Use origin feature type even if it does not match the default destination
       featuretype
       Default: false
    --host, -H
       Machine name or IP address to connect to. Default: localhost
       Default: localhost
    --password, -W
       Password.  Default: <no password>
       Default: <empty string>
    --port, -P
       Port number to connect to.  Default: 5432
       Default: 5432
    --schema, -S
       The database schema to access.  Default: public
       Default: public
    --table, -t
       Table to import.
       Default: <empty string>
    --user, -U
       User name.  Default: postgres
       Default: postgres

Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 11.656 sec - in org.locationtech.geogig.geotools.cli.shp.ShpImportTest
Usage: geogig export [options] <path> <shapefile>
  Options:
    --alter
       Export all features if several types are found, altering them to adapt to
       the output feature type
       Default: false
    --charset
       Use the specified charset to encode attributes. Default is ISO-8859-1.
       Default: ISO-8859-1
    --defaulttype
       Export only features with the tree default feature type if several types
       are found
       Default: false
    --featuretype
       Export only features with the specified feature type if several types are
       found
    --overwrite, -o
       Overwrite output file
       Default: false

Importing from database database

Importing table4           (1/8)... 

Importing table3           (2/8)... 

1 features inserted in 2.193 ms

Building final tree table3...

1 features tree built in 468.8 μs

Importing table2           (3/8)... 

1 features inserted in 1.336 ms

Building final tree table2...

1 features tree built in 434.5 μs

Importing table1           (4/8)... 

2 features inserted in 1.599 ms

Building final tree table1...

2 features tree built in 569.1 μs

Importing shpLikeTable2    (5/8)... 
2018-12-17T21:57:56.338-0500  SEVERE  There's code using JDBC based datastore and not disposing them. This may lead to temporary loss of database connections. Please make sure all data access code calls DataStore.dispose() before freeing all references to it

1 features inserted in 1.965 ms

Building final tree shpLikeTable2...

1 features tree built in 340.6 μs

Importing shpLikeTable     (6/8)... 

1 features inserted in 958.3 μs

Building final tree shpLikeTable...

1 features tree built in 282.6 μs

Importing GeoJsonLikeTa... (7/8)... 

1 features inserted in 2.062 ms

Building final tree GeoJsonLikeTable2...

1 features tree built in 593.4 μs

Importing GeoJsonLikeTable (8/8)... 

1 features inserted in 1.250 ms

Building final tree GeoJsonLikeTable...

1 features tree built in 639.3 μs

100%Import successful.

Exporting from WORK_HEAD:Points to testTable... 

100%WORK_HEAD:Points exported successfully to testTable

Exporting from Lines to testTable... 
Lines exported successfully to testTable
Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 12.629 sec - in org.locationtech.geogig.geotools.cli.postgis.PGImportTest

Exporting from Points to Points... 

100%Points exported successfully to Points
Usage: geogig export [options] [<commit-ish>:]<path> <table> (define source feature type tree and target table name)
  Options:
    --alter
       Export all features if several types are found, altering them to adapt to
       the output feature type
       Default: false
    --database, -D
       The database to connect to.  Default: database
       Default: database
    --defaulttype
       Export only features with the tree default feature type if several types
       are found
       Default: false
    --featuretype
       Export only features with the specified feature type if several types are
       found
    --host, -H
       Machine name or IP address to connect to. Default: localhost
       Default: localhost
    --overwrite, -o
       Overwrite output table
       Default: false
    --password, -W
       Password.  Default: <no password>
       Default: <empty string>
    --port, -P
       Port number to connect to.  Default: 5432
       Default: 5432
    --schema, -S
       The database schema to access.  Default: public
       Default: public
    --user, -U
       User name.  Default: postgres
       Default: postgres

Tests run: 11, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 13.115 sec - in org.locationtech.geogig.geotools.cli.postgis.PGExportTest

Exporting from WORK_HEAD:Points to TestPoints... 

67%
100%WORK_HEAD:Points exported successfully to /opt/public/hipp/ramdisk/geogig/junit5981470878443675848/repo-1384080268/TestPoints.shp

Exporting from Points to Points... 

Exporting from Points to Points... 

100%Points exported successfully to Points

67%
100%Points exported successfully to Points

Exporting repository metadata from 'HEAD:Points' (commit cd79d032b261c64a7f4750219078b3b320474707)...

Exporting repository metadata from 'HEAD:Points' (commit 83f4902222a66493fcee47386733a6fa7d4af727)...

Creating audit metadata for table 'Points'

Creating audit metadata for table 'Points'

Exporting from Points to TestPoints... 
Importing from database /opt/public/hipp/ramdisk/geogig/geogig_geopackage_test3855068702225207306.gpkg

67%
Importing Points           (1/2)... 

Importing changes to table Points onto feature tree Points...
Usage: geogig export [options] <path> <shapefile>
  Options:
    --alter
       Export all features if several types are found, altering them to adapt to
       the output feature type
       Default: false
    --charset
       Use the specified charset to encode attributes. Default is ISO-8859-1.
       Default: ISO-8859-1
    --defaulttype
       Export only features with the tree default feature type if several types
       are found
       Default: false
    --featuretype
       Export only features with the specified feature type if several types are
       found
    --overwrite, -o
       Overwrite output file
       Default: false


0%Fetching feature types...
 - GeoJsonLikeTable
 - GeoJsonLikeTable2
 - shpLikeTable
 - shpLikeTable2
 - table1
 - table2
 - table3
 - table4
Fetching table...
Table : table1
----------------------------------------
	Property  : label
	Type      : String
----------------------------------------
	Property  : geom
	Type      : Point
----------------------------------------
Fetching feature types...

0%
3 features inserted in 19.62 ms

Building final tree Points...

3 features tree built in 1.286 ms

Importing Lines            (2/2)... 
Import successful.
Changes committed and merge at 2042f23544d938c77ce0d67dfa3d0333a7316a00

  Scenario: Try exporting from an empty directory                    # ShpExport.feature:6
    Given I am in an empty directory                                 # DefaultStepDefinitions.I_am_in_an_empty_directory()
    When I run the command "shp export Points Points.shp"            # DefaultStepDefinitions.I_run_the_command_X(String)
    Then the response should start with "Not in a geogig repository" # DefaultStepDefinitions.the_response_should_start_with(String)

Exporting from Points to TestPoints... 
Fetching feature types...

1%
100%Points exported successfully to /opt/public/hipp/ramdisk/geogig/junit4119537241504404117/repo-234474771/TestPoints.shp

3 features inserted in 5.165 ms

Building final tree Lines...

3 features tree built in 909.3 μs

100%Import successful.
Usage: geogig list [options]
  Options:
    --database, -D
       The database to connect to.  Default: database.gpkg
       Default: database.gpkg
    --user, -U
       User name.  Default: user
       Default: user

Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 17.956 sec - in org.locationtech.geogig.geotools.cli.geopkg.GeoPkgListTest

Exporting from Points to TestPoints... 

100%Points exported successfully to /opt/public/hipp/ramdisk/geogig/junit943469106964632860/repo1454944598/TestPoints.shp

Exporting from Lines to TestPoints... 
Usage: geogig export [options] [<commit-ish>:]<path> <table> (define source feature type tree and target table name)
  Options:
    --alter
       Export all features if several types are found, altering them to adapt to
       the output feature type
       Default: false
    --database, -D
       The database to connect to.  Default: database.gpkg
       Default: database.gpkg
    --defaulttype
       Export only features with the tree default feature type if several types
       are found
       Default: false
    --featuretype
       Export only features with the specified feature type if several types are
       found
    -i, --interchange
       Export as geogig mobile interchange format
       Default: false
    --overwrite, -o
       Overwrite output table
       Default: false
    --user, -U
       User name.  Default: user
       Default: user

Lines exported successfully to /opt/public/hipp/ramdisk/geogig/junit943469106964632860/repo1454944598/TestPoints.shp
Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 18.381 sec - in org.locationtech.geogig.geotools.cli.shp.ShpExportTest
Fetching table...Could not find the specified table.

Exporting from Points to Points... 

100%Points exported successfully to Points

Exporting repository metadata from 'HEAD:Points' (commit 49a4a8033ae16e43f9d2410f2aa5ef4747d4c1df)...

Creating audit metadata for table 'Points'
Fetching table...
Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 18.457 sec - in org.locationtech.geogig.geotools.cli.geopkg.GeoPkgDescribeTest

Importing changes to table Points onto feature tree Points...
Import successful.
Changes committed and merge at b76a1772f2ff03df2924db27980720b627e9ceca
Importing from database /opt/public/hipp/ramdisk/geogig/geogig_geopackage_test8173605138957970465.gpkg

Importing Points           (1/1)... 

3 features inserted in 4.027 ms

Building final tree Points...

3 features tree built in 931.2 μs

100%Import successful.

Exporting from WORK_HEAD:Points to Points... 
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 20.06 sec - in org.locationtech.geogig.geotools.cli.geopkg.GeoPkgImportTest

100%WORK_HEAD:Points exported successfully to Points

  Scenario: Try describing a GeoPackage table from an empty directory                    # GeoPkgDescribe.feature:6
    Given I am in an empty directory                                                     # DefaultStepDefinitions.I_am_in_an_empty_directory()
    When I run the command "geopkg describe --table test" on an existing GeoPackage file # GeoPkgStepDefinitions.I_run_the_command_on_an_existing_GeoPackage_file(String)
    Then the response should contain "Could not find the specified table."               # DefaultStepDefinitions.the_response_should_contain(String)

Exporting from WORK_HEAD:Lines to Lines... 

Exporting from Points to Points... 
WORK_HEAD:Lines exported successfully to Lines

100%Points exported successfully to Points

Exporting repository metadata from 'HEAD:Points' (commit e3518d387249d7e8e947c3e145325b031f3cd511)...

Creating audit metadata for table 'Points'
Exporting from Points to Points... 
66.666664
100.0Points exported successfully to Points.shp

Importing changes to table Points onto feature tree Points...
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 22.148 sec - in org.locationtech.geogig.geotools.cli.geopkg.GeoPkgPullTest

  Scenario: Try exporting a feature type                                          # ShpExport.feature:11
    Given I have a repository                                                     # DefaultStepDefinitions.I_have_a_repository()
    And I stage 6 features                                                        # DefaultStepDefinitions.I_stage_6_features()
    When I run the command "shp export -o Points Points.shp"                      # DefaultStepDefinitions.I_run_the_command_X(String)
    Then the response should contain "Points exported successfully to Points.shp" # DefaultStepDefinitions.the_response_should_contain(String)

Exporting from Points to Points... 

100%Points exported successfully to Points
Fetching table...Table : Points----------------------------------------	Property  : pp	Type      : Point----------------------------------------	Property  : ip	Type      : Integer----------------------------------------	Property  : sp	Type      : String----------------------------------------

Exporting from Points to Points... 
pathspec 'WRONGTABLE' did not match any valid path

100%Points exported successfully to Points

  Scenario: Try describing a GeoPackage table                                              # GeoPkgDescribe.feature:11
    Given I have a repository                                                              # DefaultStepDefinitions.I_have_a_repository()
    When I run the command "geopkg describe --table Points" on an existing GeoPackage file # GeoPkgStepDefinitions.I_run_the_command_on_an_existing_GeoPackage_file(String)
    Then the response should contain "Table : Points"                                      # DefaultStepDefinitions.the_response_should_contain(String)

Exporting from Lines to Points... 

67%
100%Lines exported successfully to Points
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 28.28 sec - in org.locationtech.geogig.geotools.cli.geopkg.GeoPkgExportTest

  Scenario: Try exporting an inexistent feature type                                      # ShpExport.feature:17
    Given I have a repository                                                             # DefaultStepDefinitions.I_have_a_repository()
    And I stage 6 features                                                                # DefaultStepDefinitions.I_stage_6_features()
    When I run the command "shp export WRONGTABLE Points.shp"                             # DefaultStepDefinitions.I_run_the_command_X(String)
    Then the response should contain "pathspec 'WRONGTABLE' did not match any valid path" # DefaultStepDefinitions.the_response_should_contain(String)
Fetching table...Could not find the specified table.

  Scenario: Try to describe a GeoPackage table that doesn't exit in the database                      # GeoPkgDescribe.feature:16
    Given I have a repository                                                                         # DefaultStepDefinitions.I_have_a_repository()
    When I run the command "geopkg describe --table nonexistant_table" on an existing GeoPackage file # GeoPkgStepDefinitions.I_run_the_command_on_an_existing_GeoPackage_file(String)
    Then the response should contain "Could not find the specified table."                            # DefaultStepDefinitions.the_response_should_contain(String)
Feature: "geopkg export" command
    In order to export data to Geogig
    As a Geogig User
    I want to export from the repository into a GeoPackage file

  Scenario: Try exporting from an empty directory                                 # GeoPkgExport.feature:6
    Given I am in an empty directory                                              # DefaultStepDefinitions.I_am_in_an_empty_directory()
    When I run the command "geopkg export Points Points" on a new GeoPackage file # GeoPkgStepDefinitions.I_run_the_command_on_a_new_GeoPackage_file(String)
    Then the response should start with "Not in a geogig repository:"             # DefaultStepDefinitions.the_response_should_start_with(String)
Exporting from Points to Points... Error: The selected tree contains mixed feature types. Use --defaulttype or --featuretype <feature_type_ref> to export.
Exporting from Points to Points... Error: The selected tree contains mixed feature types. Use --defaulttype or --featuretype <feature_type_ref> to export.

  Scenario: Try exporting with mixed feature types                                                    # ShpExport.feature:23
    Given I have a repository                                                                         # DefaultStepDefinitions.I_have_a_repository()
    And I have several feature types in a path                                                        # GeoToolsStepDefinitions.I_have_several_feature_types_in_a_path()
    When I run the command "shp export -o Points Points.shp"                                          # DefaultStepDefinitions.I_run_the_command_X(String)
    Then the response should contain "The selected tree contains mixed feature types"                 # DefaultStepDefinitions.the_response_should_contain(String)
    And the response should contain "Use --defaulttype or --featuretype <feature_type_ref> to export" # DefaultStepDefinitions.the_response_should_contain(String)
Exporting from Points to MyPoints... 
100.0Points exported successfully to MyPoints

  Scenario: Try exporting a feature type                                               # GeoPkgExport.feature:11
    Given I have a repository                                                          # DefaultStepDefinitions.I_have_a_repository()
    And I stage 6 features                                                             # DefaultStepDefinitions.I_stage_6_features()
    When I run the command "geopkg export -o Points MyPoints" on a new GeoPackage file # GeoPkgStepDefinitions.I_run_the_command_on_a_new_GeoPackage_file(String)
    Then the response should contain "Points exported successfully to MyPoints"        # DefaultStepDefinitions.the_response_should_contain(String)
Exporting from Points to Points... Points exported successfully to Points.shp

  Scenario: Try exporting with mixed feature types using the default feature type # ShpExport.feature:30
    Given I have a repository                                                     # DefaultStepDefinitions.I_have_a_repository()
    And I have several feature types in a path                                    # GeoToolsStepDefinitions.I_have_several_feature_types_in_a_path()
    When I run the command "shp export -o --defaulttype Points Points.shp"        # DefaultStepDefinitions.I_run_the_command_X(String)
    Then the response should contain "Points exported successfully to Points.shp" # DefaultStepDefinitions.the_response_should_contain(String)
pathspec 'WRONGTABLE' did not match any valid path

  Scenario: Try exporting an inexistent feature type                                      # GeoPkgExport.feature:17
    Given I have a repository                                                             # DefaultStepDefinitions.I_have_a_repository()
    And I stage 6 features                                                                # DefaultStepDefinitions.I_stage_6_features()
    When I run the command "geopkg export WRONGTABLE Points" on a new GeoPackage file     # GeoPkgStepDefinitions.I_run_the_command_on_a_new_GeoPackage_file(String)
    Then the response should contain "pathspec 'WRONGTABLE' did not match any valid path" # DefaultStepDefinitions.the_response_should_contain(String)
Exporting from Points to Points... Points exported successfully to Points.shp

  Scenario: Try exporting with mixed feature types using --alter                  # ShpExport.feature:36
    Given I have a repository                                                     # DefaultStepDefinitions.I_have_a_repository()
    And I have several feature types in a path                                    # GeoToolsStepDefinitions.I_have_several_feature_types_in_a_path()
    When I run the command "shp export -o --defaulttype Points Points.shp"        # DefaultStepDefinitions.I_run_the_command_X(String)
    Then the response should contain "Points exported successfully to Points.shp" # DefaultStepDefinitions.the_response_should_contain(String)
The selected table already exists. Use -o to overwrite

  Scenario: Try exporting to a table that already exists                                      # GeoPkgExport.feature:23
    Given I have a repository                                                                 # DefaultStepDefinitions.I_have_a_repository()
    And I stage 6 features                                                                    # DefaultStepDefinitions.I_stage_6_features()
    When I run the command "geopkg export Points Points" on an existing GeoPackage file       # GeoPkgStepDefinitions.I_run_the_command_on_an_existing_GeoPackage_file(String)
    Then the response should contain "The selected table already exists. Use -o to overwrite" # DefaultStepDefinitions.the_response_should_contain(String)
Exporting from HEAD:Points to CommitedPoints... HEAD:Points exported successfully to CommitedPoints.shp

  Scenario: Try exporting a table from HEAD                                               # ShpExport.feature:42
    Given I have a repository                                                             # DefaultStepDefinitions.I_have_a_repository()
    And I stage 6 features                                                                # DefaultStepDefinitions.I_stage_6_features()
    When I run the command "commit -m TestCommit"                                         # DefaultStepDefinitions.I_run_the_command_X(String)
    When I run the command "shp export -o HEAD:Points CommitedPoints.shp"                 # DefaultStepDefinitions.I_run_the_command_X(String)
    Then the response should contain "Points exported successfully to CommitedPoints.shp" # DefaultStepDefinitions.the_response_should_contain(String)

7 Scenarios (7 passed)
29 Steps (29 passed)
0m39.033s

Tests run: 36, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 40.37 sec - in org.locationtech.geogig.geotools.cli.shp.RunShpFunctionalTest
Exporting from HEAD:Points to CommitedPoints... HEAD:Points exported successfully to CommitedPoints

  Scenario: Try exporting a table from HEAD                                                       # GeoPkgExport.feature:29
    Given I have a repository                                                                     # DefaultStepDefinitions.I_have_a_repository()
    And I stage 6 features                                                                        # DefaultStepDefinitions.I_stage_6_features()
    When I run the command "commit -m TestCommit"                                                 # DefaultStepDefinitions.I_run_the_command_X(String)
    When I run the command "geopkg export -o HEAD:Points CommitedPoints" on a new GeoPackage file # GeoPkgStepDefinitions.I_run_the_command_on_a_new_GeoPackage_file(String)
    Then the response should contain "Points exported successfully to CommitedPoints"             # DefaultStepDefinitions.the_response_should_contain(String)
Feature: "geopkg import" command
    In order to import data to Geogig
    As a Geogig User
    I want to import one or more tables from a GeoPackage file

  Scenario: Try importing into an empty directory                                        # GeoPkgImport.feature:6
    Given I am in an empty directory                                                     # DefaultStepDefinitions.I_am_in_an_empty_directory()
    When I run the command "geopkg import --table Points" on an existing GeoPackage file # GeoPkgStepDefinitions.I_run_the_command_on_an_existing_GeoPackage_file(String)
    Then the response should start with "Not in a geogig repository"                     # DefaultStepDefinitions.the_response_should_start_with(String)
Importing from database /opt/public/hipp/ramdisk/geogig/geogig_geopackage_test7257215075604327433.gpkgImporting Points           (1/1)... 3 features inserted in 12.69 msBuilding final tree Points...3 features tree built in 1.120 ms
100%Import successful.

  Scenario: Try to import a GeoPackage table                                             # GeoPkgImport.feature:11
    Given I have a repository                                                            # DefaultStepDefinitions.I_have_a_repository()
    When I run the command "geopkg import --table Points" on an existing GeoPackage file # GeoPkgStepDefinitions.I_run_the_command_on_an_existing_GeoPackage_file(String)
    Then the response should contain "Import successful."                                # DefaultStepDefinitions.the_response_should_contain(String)
Importing from database /opt/public/hipp/ramdisk/geogig/geogig_geopackage_test5747649684887449676.gpkgImporting Points           (1/2)... 
0%3 features inserted in 3.081 msBuilding final tree Points...3 features tree built in 883.3 μsImporting Lines            (2/2)... 3 features inserted in 3.991 msBuilding final tree Lines...3 features tree built in 1.136 ms
100%Import successful.

  Scenario: Try to import a full GeoPackage file                                # GeoPkgImport.feature:16
    Given I have a repository                                                   # DefaultStepDefinitions.I_have_a_repository()
    When I run the command "geopkg import --all" on an existing GeoPackage file # GeoPkgStepDefinitions.I_run_the_command_on_an_existing_GeoPackage_file(String)
    Then the response should contain "Import successful."                       # DefaultStepDefinitions.the_response_should_contain(String)
Importing from database /opt/public/hipp/ramdisk/geogig/geogig_geopackage_test2196655848390207346.gpkgCould not find the specified table.

  Scenario: Try to import a GeoPackage table that doesn't exit in the file                          # GeoPkgImport.feature:21
    Given I have a repository                                                                       # DefaultStepDefinitions.I_have_a_repository()
    When I run the command "geopkg import --table nonexistant_table" on an existing GeoPackage file # GeoPkgStepDefinitions.I_run_the_command_on_an_existing_GeoPackage_file(String)
    Then the response should contain "Could not find the specified table."                          # DefaultStepDefinitions.the_response_should_contain(String)
Importing from database /opt/public/hipp/ramdisk/geogig/geogig_geopackage_test1196787698825696276.gpkgNo tables specified for import. Specify --all or --table <table>.

  Scenario: Try to import without specifying table or -all                                               # GeoPkgImport.feature:26
    Given I have a repository                                                                            # DefaultStepDefinitions.I_have_a_repository()
    When I run the command "geopkg import" on an existing GeoPackage file                                # GeoPkgStepDefinitions.I_run_the_command_on_an_existing_GeoPackage_file(String)
    Then the response should contain "No tables specified for import. Specify --all or --table <table>." # DefaultStepDefinitions.the_response_should_contain(String)
Importing from database /opt/public/hipp/ramdisk/geogig/geogig_geopackage_test7414265998926665058.gpkgSpecify --all or --table <table>, both cannot be set.

  Scenario: Try to import with table and -all                                                  # GeoPkgImport.feature:31
    Given I have a repository                                                                  # DefaultStepDefinitions.I_have_a_repository()
    When I run the command "geopkg import --table Points --all" on an existing GeoPackage file # GeoPkgStepDefinitions.I_run_the_command_on_an_existing_GeoPackage_file(String)
    Then the response should contain "Specify --all or --table <table>, both cannot be set."   # DefaultStepDefinitions.the_response_should_contain(String)
Feature: "geopkg list" command
    In order to know all of the features available in a GeoPackage file
    As a Geogig User
    I want to list all of the features

  Scenario: Try listing from an empty directory                         # GeoPkgList.feature:6
    Given I am in an empty directory                                    # DefaultStepDefinitions.I_am_in_an_empty_directory()
    When I run the command "geopkg list" on an existing GeoPackage file # GeoPkgStepDefinitions.I_run_the_command_on_an_existing_GeoPackage_file(String)
    Then the response should start with "Not in a geogig repository"    # DefaultStepDefinitions.the_response_should_start_with(String)
Fetching feature types... - Lines - Points

  Scenario: Try listing from a valid directory                          # GeoPkgList.feature:11
    Given I have a repository                                           # DefaultStepDefinitions.I_have_a_repository()
    When I run the command "geopkg list" on an existing GeoPackage file # GeoPkgStepDefinitions.I_run_the_command_on_an_existing_GeoPackage_file(String)
    Then the response should contain "Points"                           # DefaultStepDefinitions.the_response_should_contain(String)
Feature: "geopkg pull" command
    In order to import data to Geogig
    As a Geogig User
    I want to import one or more tables from a GeoPackage file with the interchange format

  Scenario: Try pulling into an empty directory                                        # GeoPkgPull.feature:6
    Given I am in an empty directory                                                   # DefaultStepDefinitions.I_am_in_an_empty_directory()
    When I run the command "geopkg pull --table Points" on an existing GeoPackage file # GeoPkgStepDefinitions.I_run_the_command_on_an_existing_GeoPackage_file(String)
    Then the response should start with "Not in a geogig repository"                   # DefaultStepDefinitions.the_response_should_start_with(String)
Commit message not provided

  Scenario: Try to pull a GeoPackage table without commit message                                  # GeoPkgPull.feature:11
    Given I have a repository                                                                      # DefaultStepDefinitions.I_have_a_repository()
    When I run the command "geopkg pull --table Points" on an existing interchange GeoPackage file # GeoPkgStepDefinitions.I_run_the_command_on_an_existing_interchange_GeoPackage_file(String)
    Then the response should contain "Commit message not provided"                                 # DefaultStepDefinitions.the_response_should_contain(String)
Importing changes to table Points onto feature tree Points...Import successful.Changes committed and merge at 4c155a2aecefa2b01dc784adba9f813d63cd247b

  Scenario: Try to pull a GeoPackage table                                                                            # GeoPkgPull.feature:16
    Given I have a repository                                                                                         # DefaultStepDefinitions.I_have_a_repository()
    When I run the command "geopkg pull --table Points --message imported" on an existing interchange GeoPackage file # GeoPkgStepDefinitions.I_run_the_command_on_an_existing_interchange_GeoPackage_file(String)
    Then the response should contain "Import successful."                                                             # DefaultStepDefinitions.the_response_should_contain(String)
Unable to import: No table to import.

  Scenario: Try to pull a GeoPackage table that doesn't exit in the file                                                         # GeoPkgPull.feature:21
    Given I have a repository                                                                                                    # DefaultStepDefinitions.I_have_a_repository()
    When I run the command "geopkg pull --table nonexistant_table --message imported" on an existing interchange GeoPackage file # GeoPkgStepDefinitions.I_run_the_command_on_an_existing_interchange_GeoPackage_file(String)
    Then the response should contain "Unable to import: No table to import."                                                     # DefaultStepDefinitions.the_response_should_contain(String)
Importing changes to table Points onto feature tree Points...Import successful.Changes committed and merge at b893835aac3bec5ed8a8e2bef0af5adf08153b65

  Scenario: Try to pull without specifying table                                                       # GeoPkgPull.feature:26
    Given I have a repository                                                                          # DefaultStepDefinitions.I_have_a_repository()
    When I run the command "geopkg pull --message imported" on an existing interchange GeoPackage file # GeoPkgStepDefinitions.I_run_the_command_on_an_existing_interchange_GeoPackage_file(String)
    Then the response should contain "Import successful."                                              # DefaultStepDefinitions.the_response_should_contain(String)
Importing changes to table Points onto feature tree Points...CONFLICT: Merge conflict in Points/Points.1Automatic merge failed. Fix conflicts and then commit the result.

  Scenario: Try to pull a GeoPackage table with a conflict                                                                            # GeoPkgPull.feature:31
    Given I have a repository                                                                                                         # DefaultStepDefinitions.I_have_a_repository()
    When I run the command "geopkg pull --table Points --message imported" on an existing interchange GeoPackage file with a conflict # GeoPkgStepDefinitions.I_run_the_command_on_an_existing_interchange_GeoPackage_file_with_conflict(String)
    Then the response should contain "CONFLICT: Merge conflict in"                                                                    # DefaultStepDefinitions.the_response_should_contain(String)

22 Scenarios (22 passed)
71 Steps (71 passed)
1m3.029s

Tests run: 93, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 64.529 sec - in org.locationtech.geogig.geotools.cli.geopkg.RunGeoPkgFunctionalTest

Results :

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

[JENKINS] Recording test results
[INFO] 
[INFO] --- maven-jar-plugin:3.0.2:jar (default-jar) @ geogig-cli-geotools ---
[INFO] Building jar: /home/hudson/genie.geogig/.jenkins/jobs/geogig-master/workspace/src/cli/geotools/target/geogig-cli-geotools-1.4-SNAPSHOT.jar
[INFO] 
[INFO] --- maven-jar-plugin:3.0.2:test-jar (default) @ geogig-cli-geotools ---
[INFO] Building jar: /home/hudson/genie.geogig/.jenkins/jobs/geogig-master/workspace/src/cli/geotools/target/geogig-cli-geotools-1.4-SNAPSHOT-tests.jar
[INFO] 
[INFO] >>> maven-source-plugin:3.0.1:jar (attach-sources) > generate-sources @ geogig-cli-geotools >>>
[INFO] 
[INFO] --- git-commit-id-plugin:2.2.2:revision (default) @ geogig-cli-geotools ---
[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-cli-geotools <<<
[INFO] 
[INFO] 
[INFO] --- maven-source-plugin:3.0.1:jar (attach-sources) @ geogig-cli-geotools ---
[INFO] Building jar: /home/hudson/genie.geogig/.jenkins/jobs/geogig-master/workspace/src/cli/geotools/target/geogig-cli-geotools-1.4-SNAPSHOT-sources.jar
[INFO] 
[INFO] >>> maven-source-plugin:3.0.1:test-jar (attach-sources) > generate-sources @ geogig-cli-geotools >>>
[INFO] 
[INFO] --- git-commit-id-plugin:2.2.2:revision (default) @ geogig-cli-geotools ---
[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-cli-geotools <<<
[INFO] 
[INFO] 
[INFO] --- maven-source-plugin:3.0.1:test-jar (attach-sources) @ geogig-cli-geotools ---
[INFO] Building jar: /home/hudson/genie.geogig/.jenkins/jobs/geogig-master/workspace/src/cli/geotools/target/geogig-cli-geotools-1.4-SNAPSHOT-test-sources.jar
[INFO] 
[INFO] --- maven-install-plugin:2.4:install (default-install) @ geogig-cli-geotools ---
[INFO] Installing /home/hudson/genie.geogig/.jenkins/jobs/geogig-master/workspace/src/cli/geotools/target/geogig-cli-geotools-1.4-SNAPSHOT.jar to /home/hudson/genie.geogig/.jenkins/jobs/geogig-master/workspace/.repository/org/locationtech/geogig/geogig-cli-geotools/1.4-SNAPSHOT/geogig-cli-geotools-1.4-SNAPSHOT.jar
[INFO] Installing /home/hudson/genie.geogig/.jenkins/jobs/geogig-master/workspace/src/cli/geotools/pom.xml to /home/hudson/genie.geogig/.jenkins/jobs/geogig-master/workspace/.repository/org/locationtech/geogig/geogig-cli-geotools/1.4-SNAPSHOT/geogig-cli-geotools-1.4-SNAPSHOT.pom
[INFO] Installing /home/hudson/genie.geogig/.jenkins/jobs/geogig-master/workspace/src/cli/geotools/target/geogig-cli-geotools-1.4-SNAPSHOT-tests.jar to /home/hudson/genie.geogig/.jenkins/jobs/geogig-master/workspace/.repository/org/locationtech/geogig/geogig-cli-geotools/1.4-SNAPSHOT/geogig-cli-geotools-1.4-SNAPSHOT-tests.jar
[INFO] Installing /home/hudson/genie.geogig/.jenkins/jobs/geogig-master/workspace/src/cli/geotools/target/geogig-cli-geotools-1.4-SNAPSHOT-sources.jar to /home/hudson/genie.geogig/.jenkins/jobs/geogig-master/workspace/.repository/org/locationtech/geogig/geogig-cli-geotools/1.4-SNAPSHOT/geogig-cli-geotools-1.4-SNAPSHOT-sources.jar
[INFO] Installing /home/hudson/genie.geogig/.jenkins/jobs/geogig-master/workspace/src/cli/geotools/target/geogig-cli-geotools-1.4-SNAPSHOT-test-sources.jar to /home/hudson/genie.geogig/.jenkins/jobs/geogig-master/workspace/.repository/org/locationtech/geogig/geogig-cli-geotools/1.4-SNAPSHOT/geogig-cli-geotools-1.4-SNAPSHOT-test-sources.jar
[JENKINS] Archiving disabled