Started by GitHub push by kingudk
Building remotely on Local activeMQ in workspace /home/cibuild01/workspace/Bitrepository-reference-test
Cloning the remote Git repository
Cloning repository https://github.com/bitrepository/reference.git
> git init /home/cibuild01/workspace/Bitrepository-reference-test # timeout=10
Fetching upstream changes from https://github.com/bitrepository/reference.git
> git --version # timeout=10
> git -c core.askpass=true fetch --tags --progress https://github.com/bitrepository/reference.git +refs/heads/*:refs/remotes/origin/*
> git config remote.origin.url https://github.com/bitrepository/reference.git # timeout=10
> git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
> git config remote.origin.url https://github.com/bitrepository/reference.git # timeout=10
Fetching upstream changes from https://github.com/bitrepository/reference.git
> git -c core.askpass=true fetch --tags --progress https://github.com/bitrepository/reference.git +refs/heads/master:refs/remotes/origin/master
> git rev-parse refs/remotes/origin/master^{commit} # timeout=10
> git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision 7ce7b6fbce5c63601abacb274ca80128cec638cc (refs/remotes/origin/master)
> git config core.sparsecheckout # timeout=10
> git checkout -f 7ce7b6fbce5c63601abacb274ca80128cec638cc
> git rev-list 958663501d36a22e9723e000658267445fb2ed4e # timeout=10
> git tag -a -f -m Jenkins Build #5929 jenkins-Bitrepository-reference-test-5929 # timeout=10
Parsing POMs
Established TCP socket on 41352
maven32-agent.jar already up to date
maven32-interceptor.jar already up to date
maven3-interceptor-commons.jar already up to date
[Bitrepository-reference-test] $ /home/cibuild01/tools/hudson.model.JDK/Java8/bin/java -Xmx512m -XX:MaxPermSize=128m -cp /home/cibuild01/maven32-agent.jar:/home/cibuild01/tools/hudson.tasks.Maven_MavenInstallation/Maven3.2/boot/plexus-classworlds-2.5.2.jar:/home/cibuild01/tools/hudson.tasks.Maven_MavenInstallation/Maven3.2/conf/logging jenkins.maven3.agent.Maven32Main /home/cibuild01/tools/hudson.tasks.Maven_MavenInstallation/Maven3.2 /home/cibuild01/slave.jar /home/cibuild01/maven32-interceptor.jar /home/cibuild01/maven3-interceptor-commons.jar 41352
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=128m; support was removed in 8.0
<===[JENKINS REMOTING CAPACITY]===> channel started
Executing Maven: -B -f /home/cibuild01/workspace/Bitrepository-reference-test/pom.xml clean deploy
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO]
[INFO] Bitrepository
[INFO] Bitrepository Reference Settings
[INFO] Bitrepository Core
[INFO] Bitrepository Client
[INFO] Bitrepository Service
[INFO] Bitrepository Integrity Service
[INFO] Bitrepository Alarm Service
[INFO] Bitrepository Audit Trail Service
[INFO] Bitrepository Reference Pillar
[INFO] Bitrepository Monitoring Service
[INFO] Bitrepository Webclient
[INFO] Bitrepository Integration
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository 1.10-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:3.1.0:clean (default-clean) @ bitrepository-parent ---
[INFO]
[INFO] --- maven-enforcer-plugin:3.0.0-M3:enforce (enforce-maven) @ bitrepository-parent ---
[INFO]
[INFO] --- jacoco-maven-plugin:0.8.5:prepare-agent (default) @ bitrepository-parent ---
[INFO] argLine set to -javaagent:/home/cibuild01/.m2/repository/org/jacoco/org.jacoco.agent/0.8.5/org.jacoco.agent-0.8.5-runtime.jar=destfile=/home/cibuild01/workspace/Bitrepository-reference-test/target/jacoco.exec
[INFO]
[INFO] --- forbiddenapis:2.7:check (default) @ bitrepository-parent ---
[INFO] Skipping execution for packaging "pom"
[INFO]
[INFO] --- forbiddenapis:2.7:testCheck (default) @ bitrepository-parent ---
[INFO] Skipping execution for packaging "pom"
[INFO]
[INFO] --- jacoco-maven-plugin:0.8.5:report (report) @ bitrepository-parent ---
[INFO] Skipping JaCoCo execution due to missing execution data file.
[INFO]
[INFO] --- maven-jar-plugin:3.2.0:test-jar (default) @ bitrepository-parent ---
[WARNING] JAR will be empty - no content was marked for inclusion!
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-reference-test/target/bitrepository-parent-1.10-SNAPSHOT-tests.jar
[INFO]
[INFO] --- maven-source-plugin:3.2.1:jar-no-fork (attach-sources-no-fork) @ bitrepository-parent ---
[INFO]
[INFO] --- maven-install-plugin:3.0.0-M1:install (default-install) @ bitrepository-parent ---
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-parent/1.10-SNAPSHOT/bitrepository-parent-1.10-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/target/bitrepository-parent-1.10-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-parent/1.10-SNAPSHOT/bitrepository-parent-1.10-SNAPSHOT-tests.jar
[INFO]
[INFO] --- maven-deploy-plugin:3.0.0-M1:deploy (default-deploy) @ bitrepository-parent ---
[INFO] Downloading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-parent/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-parent/1.10-SNAPSHOT/maven-metadata.xml (836 B at 2.3 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-parent/1.10-SNAPSHOT/bitrepository-parent-1.10-20220215.124316-69.pom
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-parent/1.10-SNAPSHOT/bitrepository-parent-1.10-20220215.124316-69.pom (15 KB at 77.1 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-parent/1.10-SNAPSHOT/bitrepository-parent-1.10-20220215.124316-69-tests.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-parent/1.10-SNAPSHOT/bitrepository-parent-1.10-20220215.124316-69-tests.jar (5 KB at 76.8 KB/sec)
[INFO] Downloading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-parent/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-parent/maven-metadata.xml (526 B at 32.1 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-parent/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-parent/1.10-SNAPSHOT/maven-metadata.xml (836 B at 30.2 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-parent/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-parent/maven-metadata.xml (526 B at 18.3 KB/sec)
[JENKINS] Archiving disabled
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Reference Settings 1.10-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:3.1.0:clean (default-clean) @ bitrepository-reference-settings ---
[INFO]
[INFO] --- maven-enforcer-plugin:3.0.0-M3:enforce (enforce-maven) @ bitrepository-reference-settings ---
[INFO]
[INFO] --- jacoco-maven-plugin:0.8.5:prepare-agent (default) @ bitrepository-reference-settings ---
[INFO] argLine set to -javaagent:/home/cibuild01/.m2/repository/org/jacoco/org.jacoco.agent/0.8.5/org.jacoco.agent-0.8.5-runtime.jar=destfile=/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-settings/target/jacoco.exec
[INFO]
[INFO] --- maven-resources-plugin:3.1.0:copy-resources (copy-resources) @ bitrepository-reference-settings ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO]
[INFO] --- maven-jaxb2-plugin:0.14.0:generate (generate-classes-from-xsds) @ bitrepository-reference-settings ---
[INFO] Sources are not up-to-date, XJC will be executed.
[INFO] Episode file [/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-settings/target/generated-sources/jaxb/META-INF/sun-jaxb.episode] was augmented with if-exists="true" attributes.
[INFO]
[INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ bitrepository-reference-settings ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO] Copying 1 resource
[INFO] Copying 1 resource
[INFO]
[INFO] --- maven-compiler-plugin:3.8.1:compile (default-compile) @ bitrepository-reference-settings ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 38 source files to /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-settings/target/classes
[WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-settings/target/generated-sources/jaxb/org/bitrepository/settings/referencesettings/DatabaseSpecifics.java:[67,8] serializable class org.bitrepository.settings.referencesettings.DatabaseSpecifics has no definition of serialVersionUID
[WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-settings/target/generated-sources/jaxb/org/bitrepository/settings/referencesettings/WorkflowSettings.java:[56,8] serializable class org.bitrepository.settings.referencesettings.WorkflowSettings has no definition of serialVersionUID
[WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-settings/target/generated-sources/jaxb/org/bitrepository/settings/referencesettings/WorkflowConfiguration.java:[56,8] serializable class org.bitrepository.settings.referencesettings.WorkflowConfiguration has no definition of serialVersionUID
[WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-settings/target/generated-sources/jaxb/org/bitrepository/settings/referencesettings/Schedules.java:[58,8] serializable class org.bitrepository.settings.referencesettings.Schedules has no definition of serialVersionUID
[WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-settings/target/generated-sources/jaxb/org/bitrepository/settings/referencesettings/Schedule.java:[58,8] serializable class org.bitrepository.settings.referencesettings.Schedule has no definition of serialVersionUID
[WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-settings/target/generated-sources/jaxb/org/bitrepository/settings/referencesettings/Collections.java:[58,8] serializable class org.bitrepository.settings.referencesettings.Collections has no definition of serialVersionUID
[WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-settings/target/generated-sources/jaxb/org/bitrepository/settings/referencesettings/GetAuditTrailSettings.java:[51,8] serializable class org.bitrepository.settings.referencesettings.GetAuditTrailSettings has no definition of serialVersionUID
[WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-settings/target/generated-sources/jaxb/org/bitrepository/settings/referencesettings/AuditTrailServiceSettings.java:[70,8] serializable class org.bitrepository.settings.referencesettings.AuditTrailServiceSettings has no definition of serialVersionUID
[WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-settings/target/generated-sources/jaxb/org/bitrepository/settings/referencesettings/AuditTrailPreservation.java:[56,8] serializable class org.bitrepository.settings.referencesettings.AuditTrailPreservation has no definition of serialVersionUID
[WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-settings/target/generated-sources/jaxb/org/bitrepository/settings/referencesettings/GeneralSettings.java:[58,8] serializable class org.bitrepository.settings.referencesettings.GeneralSettings has no definition of serialVersionUID
[WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-settings/target/generated-sources/jaxb/org/bitrepository/settings/referencesettings/MessageThreadPools.java:[67,8] serializable class org.bitrepository.settings.referencesettings.MessageThreadPools has no definition of serialVersionUID
[WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-settings/target/generated-sources/jaxb/org/bitrepository/settings/referencesettings/MessageThreadPool.java:[67,8] serializable class org.bitrepository.settings.referencesettings.MessageThreadPool has no definition of serialVersionUID
[WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-settings/target/generated-sources/jaxb/org/bitrepository/settings/referencesettings/MaxChecksumAgeForPillar.java:[56,8] serializable class org.bitrepository.settings.referencesettings.MaxChecksumAgeForPillar has no definition of serialVersionUID
[WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-settings/target/generated-sources/jaxb/org/bitrepository/settings/referencesettings/AlarmServiceSettings.java:[62,8] serializable class org.bitrepository.settings.referencesettings.AlarmServiceSettings has no definition of serialVersionUID
[WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-settings/target/generated-sources/jaxb/org/bitrepository/settings/referencesettings/MailingConfiguration.java:[58,8] serializable class org.bitrepository.settings.referencesettings.MailingConfiguration has no definition of serialVersionUID
[WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-settings/target/generated-sources/jaxb/org/bitrepository/settings/referencesettings/PillarSettings.java:[86,8] serializable class org.bitrepository.settings.referencesettings.PillarSettings has no definition of serialVersionUID
[WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-settings/target/generated-sources/jaxb/org/bitrepository/settings/referencesettings/CollectionDirs.java:[58,8] serializable class org.bitrepository.settings.referencesettings.CollectionDirs has no definition of serialVersionUID
[WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-settings/target/generated-sources/jaxb/org/bitrepository/settings/referencesettings/GetChecksumsSettings.java:[51,8] serializable class org.bitrepository.settings.referencesettings.GetChecksumsSettings has no definition of serialVersionUID
[WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-settings/target/generated-sources/jaxb/org/bitrepository/settings/referencesettings/ReferenceSettings.java:[84,8] serializable class org.bitrepository.settings.referencesettings.ReferenceSettings has no definition of serialVersionUID
[WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-settings/target/generated-sources/jaxb/org/bitrepository/settings/referencesettings/ClientSettings.java:[66,8] serializable class org.bitrepository.settings.referencesettings.ClientSettings has no definition of serialVersionUID
[WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-settings/target/generated-sources/jaxb/org/bitrepository/settings/referencesettings/DeleteFileSettings.java:[51,8] serializable class org.bitrepository.settings.referencesettings.DeleteFileSettings has no definition of serialVersionUID
[WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-settings/target/generated-sources/jaxb/org/bitrepository/settings/referencesettings/GetFileSettings.java:[51,8] serializable class org.bitrepository.settings.referencesettings.GetFileSettings has no definition of serialVersionUID
[WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-settings/target/generated-sources/jaxb/org/bitrepository/settings/referencesettings/GetFileIDsSettings.java:[51,8] serializable class org.bitrepository.settings.referencesettings.GetFileIDsSettings has no definition of serialVersionUID
[WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-settings/target/generated-sources/jaxb/org/bitrepository/settings/referencesettings/GetStatusSettings.java:[51,8] serializable class org.bitrepository.settings.referencesettings.GetStatusSettings has no definition of serialVersionUID
[WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-settings/target/generated-sources/jaxb/org/bitrepository/settings/referencesettings/PutFileSettings.java:[58,8] serializable class org.bitrepository.settings.referencesettings.PutFileSettings has no definition of serialVersionUID
[WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-settings/target/generated-sources/jaxb/org/bitrepository/settings/referencesettings/ReplaceFileSettings.java:[51,8] serializable class org.bitrepository.settings.referencesettings.ReplaceFileSettings has no definition of serialVersionUID
[WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-settings/target/generated-sources/jaxb/org/bitrepository/settings/referencesettings/IntegrityServiceSettings.java:[76,8] serializable class org.bitrepository.settings.referencesettings.IntegrityServiceSettings has no definition of serialVersionUID
[WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-settings/target/generated-sources/jaxb/org/bitrepository/settings/referencesettings/ObsoleteChecksumSettings.java:[62,8] serializable class org.bitrepository.settings.referencesettings.ObsoleteChecksumSettings has no definition of serialVersionUID
[WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-settings/target/generated-sources/jaxb/org/bitrepository/settings/referencesettings/MonitoringServiceSettings.java:[64,8] serializable class org.bitrepository.settings.referencesettings.MonitoringServiceSettings has no definition of serialVersionUID
[WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-settings/target/generated-sources/jaxb/org/bitrepository/settings/referencesettings/FileExchangeSettings.java:[66,8] serializable class org.bitrepository.settings.referencesettings.FileExchangeSettings has no definition of serialVersionUID
[INFO]
[INFO] --- forbiddenapis:2.7:check (default) @ bitrepository-reference-settings ---
[INFO] Scanning for classes to check...
[INFO] Reading bundled API signatures: jdk-unsafe-1.8
[INFO] Reading bundled API signatures: jdk-deprecated-1.8
[INFO] Reading bundled API signatures: jdk-non-portable
[INFO] Reading bundled API signatures: jdk-reflection
[INFO] Loading classes to check...
[INFO] Scanning classes for violations...
[INFO] Scanned 38 class file(s) for forbidden API invocations (in 0.36s), 0 error(s).
[INFO]
[INFO] --- forbiddenapis:2.7:testCheck (default) @ bitrepository-reference-settings ---
[INFO] Scanning for classes to check...
[WARNING] Classes directory does not exist, forbiddenapis check skipped: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-settings/target/test-classes
[INFO]
[INFO] --- maven-resources-plugin:3.1.0:testResources (default-testResources) @ bitrepository-reference-settings ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-settings/src/test/resources
[INFO]
[INFO] --- maven-compiler-plugin:3.8.1:testCompile (default-testCompile) @ bitrepository-reference-settings ---
[INFO] No sources to compile
[INFO]
[INFO] --- maven-surefire-plugin:3.0.0-M4:test (default-test) @ bitrepository-reference-settings ---
[INFO] No tests to run.
[JENKINS] Recording test results
[INFO]
[INFO] --- jacoco-maven-plugin:0.8.5:report (report) @ bitrepository-reference-settings ---
[INFO] Skipping JaCoCo execution due to missing execution data file.
[INFO]
[INFO] --- maven-jar-plugin:3.2.0:jar (default-jar) @ bitrepository-reference-settings ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-settings/target/bitrepository-reference-settings-1.10-SNAPSHOT.jar
[INFO]
[INFO] --- maven-jar-plugin:3.2.0:test-jar (default) @ bitrepository-reference-settings ---
[WARNING] JAR will be empty - no content was marked for inclusion!
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-settings/target/bitrepository-reference-settings-1.10-SNAPSHOT-tests.jar
[INFO]
[INFO] --- maven-source-plugin:3.2.1:jar-no-fork (attach-sources-no-fork) @ bitrepository-reference-settings ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-settings/target/bitrepository-reference-settings-1.10-SNAPSHOT-sources.jar
[INFO]
[INFO] --- maven-install-plugin:3.0.0-M1:install (default-install) @ bitrepository-reference-settings ---
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-settings/target/bitrepository-reference-settings-1.10-SNAPSHOT.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-settings/1.10-SNAPSHOT/bitrepository-reference-settings-1.10-SNAPSHOT.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-settings/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-settings/1.10-SNAPSHOT/bitrepository-reference-settings-1.10-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-settings/target/bitrepository-reference-settings-1.10-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-settings/1.10-SNAPSHOT/bitrepository-reference-settings-1.10-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-settings/target/bitrepository-reference-settings-1.10-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-settings/1.10-SNAPSHOT/bitrepository-reference-settings-1.10-SNAPSHOT-sources.jar
[INFO]
[INFO] --- maven-deploy-plugin:3.0.0-M1:deploy (default-deploy) @ bitrepository-reference-settings ---
[INFO] Downloading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-settings/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-settings/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 100.5 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-settings/1.10-SNAPSHOT/bitrepository-reference-settings-1.10-20220215.124325-68.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-settings/1.10-SNAPSHOT/bitrepository-reference-settings-1.10-20220215.124325-68.jar (97 KB at 2603.8 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-settings/1.10-SNAPSHOT/bitrepository-reference-settings-1.10-20220215.124325-68.pom
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-settings/1.10-SNAPSHOT/bitrepository-reference-settings-1.10-20220215.124325-68.pom (4 KB at 153.0 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-settings/1.10-SNAPSHOT/bitrepository-reference-settings-1.10-20220215.124325-68-tests.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-settings/1.10-SNAPSHOT/bitrepository-reference-settings-1.10-20220215.124325-68-tests.jar (3 KB at 77.5 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-settings/1.10-SNAPSHOT/bitrepository-reference-settings-1.10-20220215.124325-68-sources.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-settings/1.10-SNAPSHOT/bitrepository-reference-settings-1.10-20220215.124325-68-sources.jar (87 KB at 3442.3 KB/sec)
[INFO] Downloading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-settings/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-settings/maven-metadata.xml (456 B at 34.3 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-settings/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-settings/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 63.5 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-settings/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-settings/maven-metadata.xml (456 B at 10.6 KB/sec)
[JENKINS] Archiving disabled
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Core 1.10-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] Downloading: https://sbforge.org/nexus/content/groups/public/org/bitrepository/bitrepository-message-xml-xsd/31-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/groups/public/org/bitrepository/bitrepository-message-xml-xsd/31-SNAPSHOT/maven-metadata.xml (1002 B at 36.2 KB/sec)
[INFO] Downloading: https://sbforge.org/nexus/content/groups/public/org/bitrepository/bitrepository-message-xml/31-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/groups/public/org/bitrepository/bitrepository-message-xml/31-SNAPSHOT/maven-metadata.xml (615 B at 33.4 KB/sec)
[INFO] Downloading: https://sbforge.org/nexus/content/groups/public/org/bitrepository/bitrepository-message-xml-java/31-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/groups/public/org/bitrepository/bitrepository-message-xml-java/31-SNAPSHOT/maven-metadata.xml (1003 B at 54.4 KB/sec)
[INFO]
[INFO] --- maven-clean-plugin:3.1.0:clean (default-clean) @ bitrepository-core ---
[INFO]
[INFO] --- maven-enforcer-plugin:3.0.0-M3:enforce (enforce-maven) @ bitrepository-core ---
[INFO]
[INFO] --- jacoco-maven-plugin:0.8.5:prepare-agent (default) @ bitrepository-core ---
[INFO] argLine set to -javaagent:/home/cibuild01/.m2/repository/org/jacoco/org.jacoco.agent/0.8.5/org.jacoco.agent-0.8.5-runtime.jar=destfile=/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-core/target/jacoco.exec
[INFO]
[INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ bitrepository-core ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.8.1:compile (default-compile) @ bitrepository-core ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 91 source files to /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-core/target/classes
[WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-core/src/main/java/org/bitrepository/protocol/security/BasicSecurityManager.java:[196,40] redundant cast to org.bouncycastle.cms.SignerInformation
[WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-core/src/main/java/org/bitrepository/protocol/security/BasicSecurityManager.java:[224,40] redundant cast to org.bouncycastle.cms.SignerInformation
[WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-core/src/main/java/org/bitrepository/protocol/security/BasicMessageAuthenticator.java:[59,40] redundant cast to org.bouncycastle.cms.SignerInformation
[WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-core/src/main/java/org/bitrepository/common/settings/XMLFileSettingsLoader.java:[97,24] redundant cast to T
[INFO]
[INFO] --- forbiddenapis:2.7:check (default) @ bitrepository-core ---
[INFO] Scanning for classes to check...
[INFO] Reading bundled API signatures: jdk-unsafe-1.8
[INFO] Reading bundled API signatures: jdk-deprecated-1.8
[INFO] Reading bundled API signatures: jdk-non-portable
[INFO] Reading bundled API signatures: jdk-reflection
[INFO] Loading classes to check...
[INFO] Scanning classes for violations...
[INFO] Scanned 101 class file(s) for forbidden API invocations (in 0.46s), 0 error(s).
[INFO]
[INFO] --- forbiddenapis:2.7:testCheck (default) @ bitrepository-core ---
[INFO] Scanning for classes to check...
[WARNING] Classes directory does not exist, forbiddenapis check skipped: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-core/target/test-classes
[INFO]
[INFO] --- maven-resources-plugin:3.1.0:testResources (default-testResources) @ bitrepository-core ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 11 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.8.1:testCompile (default-testCompile) @ bitrepository-core ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 66 source files to /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-core/target/test-classes
[WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-core/src/test/java/org/bitrepository/common/DefaultThreadFactoryTest.java:[33,58] unchecked conversion
required: ch.qos.logback.core.Appender<ch.qos.logback.classic.spi.ILoggingEvent>
found: ch.qos.logback.core.Appender
[WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-core/src/test/java/org/bitrepository/protocol/fileexchange/LocalFileExchangeTest.java:[131,37] toString(java.io.InputStream) in org.apache.commons.io.IOUtils has been deprecated
[WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-core/src/test/java/org/bitrepository/protocol/security/CertificateIDTest.java:[60,36] redundant cast to org.bouncycastle.cms.SignerInformation
[WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-core/src/test/java/org/bitrepository/protocol/security/CertificateIDTest.java:[85,36] redundant cast to org.bouncycastle.cms.SignerInformation
[WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-core/src/test/java/org/bitrepository/protocol/message/ExampleMessageFactory.java:[60,23] toString(java.io.InputStream) in org.apache.commons.io.IOUtils has been deprecated
[WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-core/src/test/java/org/bitrepository/protocol/MessageCreationTest.java:[76,33] toString(java.io.InputStream) in org.apache.commons.io.IOUtils has been deprecated
[WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-core/src/test/java/org/bitrepository/protocol/security/PermissionStoreTest.java:[60,36] redundant cast to org.bouncycastle.cms.SignerInformation
[WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-core/src/test/java/org/bitrepository/protocol/security/PermissionStoreTest.java:[78,36] redundant cast to org.bouncycastle.cms.SignerInformation
[WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-core/src/test/java/org/bitrepository/protocol/security/PermissionStoreTest.java:[110,36] redundant cast to org.bouncycastle.cms.SignerInformation
[INFO]
[INFO] --- maven-surefire-plugin:3.0.0-M4:test (default-test) @ bitrepository-core ---
[INFO]
[INFO] -------------------------------------------------------
[INFO] T E S T S
[INFO] -------------------------------------------------------
[INFO] Running TestSuite
Starting test project Core module test
Suite: Surefire suite
Starting testcase ArgumentValidatorTest
Test starting: testArgumentValidatorArrays
Description: Test the argument validator for arguments for arrays
Step: Check against null or empty arrays
Test success: testArgumentValidatorArrays
Test starting: testArgumentValidatorBoolean
Description: Test the argument validator for arguments for booleans
Step: validate checkTrue
Test success: testArgumentValidatorBoolean
Test starting: testArgumentValidatorCollection
Description: Test the argument validator for arguments for collections
Step: Check against null or empty collection
Test success: testArgumentValidatorCollection
Test starting: testArgumentValidatorInteger
Description: Test the argument validator for arguments for integers
Step: Test not negative
Step: Test positive
Test success: testArgumentValidatorInteger
Test starting: testArgumentValidatorLong
Description: Test the argument validator for arguments for longs
Step: Test not negative
Step: Test positive
Test success: testArgumentValidatorLong
Test starting: testArgumentValidatorObject
Description: Test the argument validator for arguments not null
Step: Test not null
Test success: testArgumentValidatorObject
Test starting: testArgumentValidatorString
Description: Test the argument validator for arguments for strings
Step: Test empty string
Test success: testArgumentValidatorString
Test starting: utilityTester
Description: Test that the utility class is a proper utility class.
Test success: utilityTester
Starting testcase CalendarUtilsTest
Test starting: calendarTester
Description: Test the calendar utility class
Step: Test the convertion of a date
Step: Test that a 'null' date is equivalent to epoch
Step: Test epoch
Step: Test that a given time in millis is extractable in millis
Step: Test the 'getNow' function
Step: Test the reverse conversion, from XMLCalendar to Date
Test success: calendarTester
Test starting: endDateRolloverTest
Description: Test that the end date is correctly rolls over a year and month change.
Test success: endDateRolloverTest
Test starting: endDateTest
Description: Test that the end date is considered as localtime and converted into UTC.
Test success: endDateTest
Test starting: startDateTest
Description: Test that the start date is considered as localtime and converted into UTC.
Test success: startDateTest
Test starting: testBeginningOfDay
Description: Tests that the time is converted to the beginning of the day localtime, not UTC
expectedSTartofDayInUTC parsed: 1454281200000
Test success: testBeginningOfDay
Test starting: testEndOfDay
Description: Tests that the time is converted to the beginning of the day localtime, not UTC
Test success: testEndOfDay
Test starting: testSummerWinterTimeChange
Description: Test that the interval between start and end date on a summertime to wintertime change is 25 hours (-1 millisecond).
Test success: testSummerWinterTimeChange
Test starting: testWinterSummerTimeChange
Description: Test that the interval between start and end date on a wintertime to summertime change is 23 hours (-1 millisecond).
Test success: testWinterSummerTimeChange
Starting testcase CertificateUseExceptionTest
Test starting: testCertificateUseException
Description: Test the instantiation of the exception
Step: Setup
Step: Try to throw such an exception
Step: Throw the exception with an embedded exception
Test success: testCertificateUseException
Starting testcase FileUtilsTest
Test starting: cleanupEmptyDirectoriesTester
Description: Test the cleanup of empty directories.
Step: Cleanup non-empty folder
Step: Cleanup when dir and root are the same
Step: Test succes case, when the directory is empty
Step: Test with a file.
Test success: cleanupEmptyDirectoriesTester
Test starting: createDeleteDirectoryTester
Description: Test the ability to delete directories.
Step: Test deleting a directory with file and subdirectory
Test success: createDeleteDirectoryTester
Test starting: createDirectoryTester
Description: Test the ability to create directories.
Step: Test the ability to create a directory
Step: Test error scenarios, when the directory path is a file
Test success: createDirectoryTester
Test starting: createSubDirectoryTester
Description: Test the ability to create sub directories.
Step: Test the ability to create sub-directories
Step: Test that it fails if the 'directory' is actually a file
Step: Test that it fails, if the parent directory does not allow writing
Test success: createSubDirectoryTester
Test starting: deprecateFileTester
Description: Test the deprecation of a file.
Step: Setup
Step: Deprecate the file
Test success: deprecateFileTester
Test starting: moveFileTester
Description: Test the moving of a file.
Step: Setup
Step: Move the file
Test success: moveFileTester
Test starting: unzipFileTester
Description: Test unzipping a file.
Step: Setup
Step: Unzip the zipfile to the directory
Test success: unzipFileTester
Test starting: utilityTester
Description: Test that the utility class is a proper utility class.
Test success: utilityTester
Test starting: writeInputstreamTester
Description: Test writing an inputstream to a file.
Step: Setup
Step: Write the input stream to the file
Test success: writeInputstreamTester
Starting testcase GeneralMessageBusTest
Test starting: busActivityTest
Description: Tests whether it is possible to create a message listener, and then set it to listen to the topic. Then puts a messageon the topic for the message listener to find, andtests whether it finds the correct message.
Step: Send a message to the topic
Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@2213854b[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>(default), version=31, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@6c2be147[origDateTime=2011-05-03T11:18:00Z, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>(default)]]
Step: Make sure both listeners received the message
Test success: busActivityTest
Test starting: twoListenersForTopicTest
Description: Verifies that two listeners on the same topic both receive the message
Step: Make a connection to the message bus and add two listeners
Step: Send a message to the topic
Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@43201f84[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>(default), version=31, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@2c51c756[origDateTime=2011-05-03T11:18:00Z, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>(default)]]
Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@43201f84[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>(default), version=31, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@2c51c756[origDateTime=2011-05-03T11:18:00Z, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>(default)]]
Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@43201f84[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>(default), version=31, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@2c51c756[origDateTime=2011-05-03T11:18:00Z, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>(default)]]
Step: Make sure both listeners received the message
Test success: twoListenersForTopicTest
Result: The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.AlarmMessage@43201f84[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>(default), version=31, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@2c51c756[origDateTime=2011-05-03T11:18:00Z, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>(default)]]
13:43:36.717 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.AlarmMessage@43201f84[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>(default), version=31, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@2c51c756[origDateTime=2011-05-03T11:18:00Z, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>(default)]]
Test starting: utilityTester
Description: Test that the utility class is a proper utility class.
Test success: utilityTester
Starting testcase HttpFileExchangeTest
Test starting: checkUrlEncodingOfFilenamesTest
Description: Tests that the filename is url-encoded correctly for a configured webdav server
Step: Check plain filename (a filename that does not see any changes due to urlencoding
Step: Check that + is encoded as expected
Test success: checkUrlEncodingOfFilenamesTest
Starting testcase MessageCreationTest
Test starting: badDateMessageTest
Description: Test to ensure that messages carrying dates must provide offset.
Test success: badDateMessageTest
Test starting: messageCreationTest
Description: Tests if we are able to create message objects from xml. The input XML is the example code defined in the message-xml, thereby also testing whether this is valid.
Step: Creating IdentifyPillarsForGetFileRequest message
Step: Creating IdentifyPillarsForGetFileResponse message
Step: Creating GetFileRequest message
Step: Creating GetFileProgressResponse message
Step: Creating GetFileFinalResponse message
Step: Creating IdentifyPillarsForPutFileRequest message
Step: Creating IdentifyPillarsForPutFileResponse message
Step: Creating PutFileRequest message
Step: Creating PutFileProgressResponse message
Step: Creating PutFileFinalResponse message
Step: Creating IdentifyPillarsForDeleteFileRequest message
Step: Creating IdentifyPillarsForDeleteFileResponse message
Step: Creating DeleteFileRequest message
Step: Creating DeleteFileProgressResponse message
Step: Creating DeleteFileFinalResponse message
Step: Creating IdentifyPillarsForReplaceFileRequest message
Step: Creating IdentifyPillarsForReplaceFileResponse message
Step: Creating ReplaceFileRequest message
Step: Creating ReplaceFileProgressResponse message
Step: Creating ReplaceFileFinalResponse message
Step: Creating IdentifyPillarsForGetChecksumsRequest message
Step: Creating IdentifyPillarsForGetChecksumsResponse message
Step: Creating GetChecksumsRequest message
Step: Creating GetChecksumsProgressResponse message
Step: Creating GetChecksumsFinalResponse message
Step: Creating IdentifyPillarsForGetFileIDsRequest message
Step: Creating IdentifyPillarsForGetFileIDsResponse message
Step: Creating GetFileIDsRequest message
Step: Creating GetFileIDsProgressResponse message
Step: Creating GetFileIDsFinalResponse message
Step: Creating IdentifyContributorsForGetStatusRequest message
Step: Creating IdentifyContributorsForGetStatusResponse message
Step: Creating GetStatusRequest message
Step: Creating GetStatusProgressResponse message
Step: Creating GetStatusFinalResponse message
Step: Creating IdentifyContributorsForGetAuditTrailsRequest message
Step: Creating IdentifyContributorsForGetAuditTrailsResponse message
Step: Creating GetAuditTrailsRequest message
Step: Creating GetAuditTrailsProgressResponse message
Step: Creating GetAuditTrailsFinalResponse message
Step: Creating AlarmMessage message
Test success: messageCreationTest
Starting testcase MessageUtilsTest
Test starting: testIdentificationResponse
Description: Tests isIdentifyResponse method in the message utility class.
Step: validate that it can see a identify response
Test success: testIdentificationResponse
Test starting: testPositiveIdentification
Description: Tests isPositiveIdentifyResponse method in the message utility class.
Step: validate that it can see a positive identify response
Test success: testPositiveIdentification
Test starting: testProgressResponse
Description: Tests isPositiveProgressResponse method in the message utility class.
Step: validate progress response
Test success: testProgressResponse
Test starting: validateUtilityClass
Description: Validating that the utility class is actually an utility class.
Test success: validateUtilityClass
Starting testcase PermissionStoreExceptionTest
Test starting: testPermissionStoreException
Description: Test the instantiation of the exception
Step: Setup
Step: Try to throw such an exception
Step: Throw the exception with an embedded exception
Test success: testPermissionStoreException
Starting testcase PermissionStoreTest
Test starting: certificateFingerprintTest
Description: Tests that a certificate fingerprint can correctly be retrived for a signer.
Added fixture: Create signer to lookup fingerprint
Step: Lookup fingerprint based on signerId
Test success: certificateFingerprintTest
Test starting: negativeCertificateRetrievalTest
Description: Tests that a certificate cannot be retrieved based on the wrong signerId.
Step: Create signer and modify its ID so lookup will fail
Step: Lookup certificate based on signerId
Test success: negativeCertificateRetrievalTest
Test starting: positiveCertificateRetrievalTest
Description: Tests that a certificate can be retrieved based on the correct signerId.
Step: Create signer to lookup certificate
Step: Lookup certificate based on signerId
Test success: positiveCertificateRetrievalTest
Starting testcase UnableToFinishExceptionTest
Test starting: testUnableToFinish
Description: Test the instantiation of the exception
Step: Setup
Step: Try to throw such an exception
Step: Throw the exception with an embedded exception
Test success: testUnableToFinish
Starting testcase ActiveMQMessageBusTest
13:43:44.614 WARN o.a.activemq.broker.BrokerService - Memory Usage for the Broker (1024mb) is more than the maximum available for the JVM: 444 mb - resetting to 70% of maximum available: 311 mb
13:43:45.098 WARN o.a.activemq.broker.BrokerService - Temporary Store limit is 51200 mb (current store usage is 0 mb). The data directory: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-core/target only has 1609 mb of usable space. - resetting to maximum available disk space: 1609 mb
Test starting: collectionFilterTest
Description: Test that message bus filters identify requests to other collection, eg. ignores these.
Step: Send an identify request with a undefined 'Collection' header property, eg. this identify requests should be handled by everybody.
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@59c92f61[correlationID=12345, collectionID=MyCollection, destination=topic://collectionTopic, replyTo=topic://clientTopic, from=ClientPillar, to=<null>(default), version=31, minVersion=24, auditTrailInformation=User: Name, Institution: Place, fileID=MyDataID]
Step: Send an identify request with the 'Collection' header property set to my collection
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@570eca28[correlationID=12345, collectionID=MyCollection, destination=topic://collectionTopic, replyTo=topic://clientTopic, from=ClientPillar, to=<null>(default), version=31, minVersion=24, auditTrailInformation=User: Name, Institution: Place, fileID=MyDataID]
Step: Send an invalid message with the 'Receiver' header property set to another specific component
Test success: collectionFilterTest
Test starting: sendMessageToSpecificComponentTest
Description: Test that message bus correct uses the 'to' header property to indicated that the message is meant for a specific component
Step: Send a message with the 'Recipient' parameter set to at specific component
Stimuli: Sending message: org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@6ec6adcc[correlationID=12345, collectionID=MySla, destination=TEST-TOPIC-cibuild01, replyTo=topic://clientTopic, from=ClientPillar, to=specificReceiver, version=31, minVersion=24, auditTrailInformation=User: Name, Institution: Place, fileID=MyDataID]
Test success: sendMessageToSpecificComponentTest
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@53314411[correlationID=12345, collectionID=MySla, destination=TEST-TOPIC-cibuild01, replyTo=topic://clientTopic, from=ClientPillar, to=specificReceiver, version=31, minVersion=24, auditTrailInformation=User: Name, Institution: Place, fileID=MyDataID]
Result: The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@53314411[correlationID=12345, collectionID=MySla, destination=TEST-TOPIC-cibuild01, replyTo=topic://clientTopic, from=ClientPillar, to=specificReceiver, version=31, minVersion=24, auditTrailInformation=User: Name, Institution: Place, fileID=MyDataID]
13:43:48.307 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@53314411[correlationID=12345, collectionID=MySla, destination=TEST-TOPIC-cibuild01, replyTo=topic://clientTopic, from=ClientPillar, to=specificReceiver, version=31, minVersion=24, auditTrailInformation=User: Name, Institution: Place, fileID=MyDataID]
Test starting: toFilterTest
Description: Test that message bus filters identify requests to other components, eg. ignores these.
Step: Send an identify request with a undefined 'To' header property, eg. this identify requests should be handled by all components.
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@1633c013[correlationID=12345, collectionID=MySla, destination=TEST-TOPIC-cibuild01, replyTo=topic://clientTopic, from=ClientPillar, to=<null>(default), version=31, minVersion=24, auditTrailInformation=User: Name, Institution: Place, fileID=MyDataID]
Step: Send an identify request with the 'To' header property set to this component
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@6115793[correlationID=12345, collectionID=MySla, destination=TEST-TOPIC-cibuild01, replyTo=topic://clientTopic, from=ClientPillar, to=<null>(default), version=31, minVersion=24, auditTrailInformation=User: Name, Institution: Place, fileID=MyDataID]
Step: Send an invalid identify request with the 'To' header property set to another specific component
Step: Send an identify response with the 'To' header property set to another component
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileResponse@276f92f3[correlationID=12345, collectionID=MySla, destination=topic://clientTopic, replyTo=queue://pillarQueue, from=MyPillar, to=<null>(default), version=31, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@7ea75bc3[responseCode=IDENTIFICATION_POSITIVE, responseText=Ready to delete file 'MyDataID'.], fileID=MyDataID, pillarID=MyPillar, pillarChecksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@761c3f5c[checksumType=MD5, checksumSalt={-85,-51}, otherChecksumType=<null>(default)], timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@7abd43c3[timeMeasureUnit=MILLISECONDS, timeMeasureValue=1000]]
Step: Send an non-identify request with the 'To' header property set to another component
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.DeleteFileRequest@219eae6d[correlationID=12345, collectionID=MySla, destination=TEST-TOPIC-cibuild01, replyTo=topic://clientTopic, from=ClientPillar, to=<null>(default), version=31, minVersion=24, auditTrailInformation=User: Name, Institution: Place, pillarID=MyPillar, fileID=MyDataID, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@56c056c0[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2ec09ad4[checksumType=MD5, checksumSalt={-85,-85}, otherChecksumType=<null>(default)], checksumValue={19,95,33,86}, calculationTimestamp=2011-02-17T09:47:00.000+01:00], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2c8da091[checksumType=MD5, checksumSalt={-85,-51}, otherChecksumType=<null>(default)]]
Test success: toFilterTest
Starting testcase ChecksumUtilsTest
Test starting: calculateDigestChecksums
Description: Tests whether the utility class for calculating checksums with MessageDigest is able to correctly calculate the checksums.
Step: Setup variables.
Step: Test with no text and no key for MD5, SHA1, and SHA256
Step: Test with text
Step: add a salt to the checksum
Test success: calculateDigestChecksums
Test starting: calculateHmacChecksums
Description: Tests whether the utility class for calculating checksums with HMAC is able to correctly calculate predefined examples from : http://en.wikipedia.org/wiki/HMAC#Examples_of_HMAC_.28MD5.2C_SHA1.2C_SHA256_.29
Step: Setup variables.
Step: Test with no text and no key for HMAC_MD5, HMAC_SHA1, and HMAC_SHA256
Step: Test with the text 'The quick brown fox jumps over the lazy dog' and key 'key' for MD5, SHA1, and SHA256
Step: Try calculating HMAC with a null salt
Test success: calculateHmacChecksums
Test starting: testChecksumAlgorithmValidation
Description: Test the algorithm validation for every single possible checksum algorithm.
Step: Test 'MD5'
Step: Test 'SHA1'
Step: Test 'SHA256'
Step: Test 'SHA384'
Step: Test 'SHA512'
Step: Test 'HMAC_MD5'
Step: Test 'HMAC_SHA1'
Step: Test 'HMAC_SHA256'
Step: Test 'HMAC_SHA384'
Step: Test 'HMAC_SHA512'
Step: Test 'OTHER'
Test success: testChecksumAlgorithmValidation
Test starting: testChecksumOnFile
Description: Test the checksum calculation on a file
Step: Setup
Step: Calculate the checksum of the file with the different ways of defining the MD5 without salt
Test success: testChecksumOnFile
Test starting: testDefaultChecksum
Description: Test the extraction of the default checksum from settings.
Step: Setup the settings
Step: Use utils to extract default checksum spec
Test success: testDefaultChecksum
Test starting: utilityTester
Description: Test that the utility class is a proper utility class.
Test success: utilityTester
Starting testcase ConfigLoaderTest
Test starting: testLoadingConfig
Description: Test the loading of a configuration file for the config loader.
Step: Setup variables
Step: Test with a invalid file path
Step: Test when the file is unreadable
Step: success case
Test success: testLoadingConfig
Test starting: busActivityTest
Description: Tests whether it is possible to create a message listener, and then set it to listen to the topic. Then puts a messageon the topic for the message listener to find, andtests whether it finds the correct message.
Step: Send a message to the topic
Stimuli: Sending message: org.bitrepository.bitrepositorymessages.AlarmMessage@3fd2dbe2[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>(default), version=31, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@55f2a26d[origDateTime=2011-05-03T11:18:00Z, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>(default)]]
Step: Make sure both listeners received the message
Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@65a390de[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>(default), version=31, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@2f1f3101[origDateTime=2011-05-03T11:18:00Z, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>(default)]]
Test success: busActivityTest
Test starting: twoListenersForTopicTest
Description: Verifies that two listeners on the same topic both receive the message
Step: Make a connection to the message bus and add two listeners
Step: Send a message to the topic
Stimuli: Sending message: org.bitrepository.bitrepositorymessages.AlarmMessage@578a1c1a[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>(default), version=31, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@526388ee[origDateTime=2011-05-03T11:18:00Z, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>(default)]]
Step: Make sure both listeners received the message
Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@7252a5e9[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>(default), version=31, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@38ed34bc[origDateTime=2011-05-03T11:18:00Z, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>(default)]]
Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@62e1533b[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>(default), version=31, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@268cea3c[origDateTime=2011-05-03T11:18:00Z, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>(default)]]
Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@36d874cc[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>(default), version=31, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@154fd912[origDateTime=2011-05-03T11:18:00Z, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>(default)]]
Test success: twoListenersForTopicTest
Result: The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.AlarmMessage@7252a5e9[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>(default), version=31, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@38ed34bc[origDateTime=2011-05-03T11:18:00Z, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>(default)]]
13:43:52.909 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.AlarmMessage@7252a5e9[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>(default), version=31, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@38ed34bc[origDateTime=2011-05-03T11:18:00Z, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>(default)]]
Test starting: utilityTester
Description: Test that the utility class is a proper utility class.
Test success: utilityTester
Starting testcase MessageAuthenticationExceptionTest
Test starting: testMessageAuthenticationException
Description: Test the instantiation of the exception
Step: Setup
Step: Try to throw such an exception
Step: Throw the exception with an embedded exception
Test success: testMessageAuthenticationException
Starting testcase MessageSignerExceptionTest
Test starting: testMessageSigningException
Description: Test the instantiation of the exception
Step: Setup
Step: Try to throw such an exception
Step: Throw the exception with an embedded exception
Test success: testMessageSigningException
Starting testcase ReceivedMessageHandlerTest
Test starting: manyMessageDispatch
Description: Tests that many (50) messages can be handled in parallel in the default pool configuration.
Added fixture: Create a ReceivedMessageHandler with a null configuration. This should create a ReceivedMessageHandler with a single CachedThreadPool.
Step: Dispatch messages to 49 listeners, where the first 49 are blocking.
Step: Unblock the blocked listeners
Test success: manyMessageDispatch
Test starting: parallelMessageDispatch
Description: Tests that two messages can be handled in parallel in the default pool configuration.
Added fixture: Create a ReceivedMessageHandler with a null configuration. This should create a ReceivedMessageHandler with a single CachedThreadPool.
Step: Dispatch messages to two listeners, the first blocking.
Step: Unblock the first listener
Test success: parallelMessageDispatch
Test starting: singleMessageDispatch
Description: Tests that a single message is dispatched correctly
Test success: singleMessageDispatch
Test starting: singleThreadMessageDispatch
Description: Tests that two messages will be handled in sequence if a singleThreaded pool is configured.
Added fixture: Create a ReceivedMessageHandler with a single pool of size 1.
Step: Dispatch messages to two listeners, the first blocking.
Step: Unblock the first listener
Test success: singleThreadMessageDispatch
Test starting: specificCollectionPoolAndDefaultPool
Description: Tests it is possible to specify a pool for a specific collection, with a default pool for the remainder.
Added fixture: Create a ReceivedMessageHandler with a one specific pool for Collection1. The Collection1 pool should be limited to 1 thread.
Step: Dispatch two messages for collection1, blocking on the processing of the first message.
Step: Dispatch a message for the other collection.
Step: Dispatch a message with no collectionID.
Step: Unblock the blocked collection1 listener
Test success: specificCollectionPoolAndDefaultPool
Test starting: specificCollectionPoolWithSpecificMessageTypePool
Description: Tests it is possible to specify a pool for a specific collection for only a specificmessage type.
Added fixture: Create a ReceivedMessageHandler with a one specific pool for Collection1 and PutFileRequests. The pool should be limited to 1 thread.
Step: Dispatch two putFileRequests for collection1, blocking on the processing of the first message.
Step: Dispatch a putFile request for the other collection.
Step: Dispatch a status request for collection1.
Step: Unblock the blocked collection1 listener
Test success: specificCollectionPoolWithSpecificMessageTypePool
Test starting: specificMessageCategoryPoolAndDefaultPool
Description: Tests it is possible to specify a pool for a specific message category, with a default pool for the remainder.
Added fixture: Create a ReceivedMessageHandler with a one specific pool for slow requests. The put file pool should be limited to 1 thread.
Step: Dispatch two put messages, blocking on the processing of the first message.
Step: Dispatch a status request message.
Step: Unblock the blocked put listener
Test success: specificMessageCategoryPoolAndDefaultPool
Test starting: specificMessageNamePoolAndDefaultPool
Description: Tests it is possible to specify a pool for a specific message type, with a default pool for the remainder.
Added fixture: Create a ReceivedMessageHandler with a one specific pool for put requests. The put file pool should be limited to 1 thread.
Step: Dispatch two put messages, blocking on the processing of the first message.
Step: Dispatch a status request message.
Step: Unblock the blocked put listener
Test success: specificMessageNamePoolAndDefaultPool
Test starting: specificMessagePools
Description: Tests that different message types can be handled by different executors.
Added fixture: Create a ReceivedMessageHandler with a two pools, one for status requests and one for put requests. The put file pool should be limited to 1 thread.
Step: Dispatch two put messages, blocking on the processing of the first message.
Step: Dispatch a status request message.
Step: Unblock the blocked put listener
Test success: specificMessagePools
Starting testcase StreamUtilsTest
Test starting: streamTester
Description: Tests the SteamUtils class.
Step: Setup variables
Step: Test with null arguments
Step: Test copying the input stream to the output stream.
Test success: streamTester
Test starting: utilityTester
Description: Test that the utility class is a proper utility class.
Test success: utilityTester
Starting testcase UnregisteredPermissionTest
Test starting: testUnregisteredPermissionException
Description: Test the instantiation of the exception
Step: Setup
Step: Try to throw such an exception
Step: Throw the exception with an embedded exception
Test success: testUnregisteredPermissionException
Starting testcase Base16UtilsTest
Test starting: badArgumentTest
Description: Test bad arguments
Step: Test with a odd number of characters.
Test success: badArgumentTest
Test starting: decodeChecksum
Description: Validating the decoding of the checksums.
Step: Decode the checksum and validate.
Test success: decodeChecksum
Test starting: encodeChecksum
Description: Validating the encoding of the checksums.
Step: Encode the checksum and validate
Test success: encodeChecksum
Test starting: utilityTester
Description: Test that the utility class is a proper utility class.
Test success: utilityTester
Starting testcase SecurityManagerTest
Test starting: certificateAuthorizationBehaviourTest
Description: Tests that a certificate is only allowed by registered users (component).
Step: Check that the registered component is allowed.
Step: Check that an unregistered component is not allowed.
Test success: certificateAuthorizationBehaviourTest
Test starting: negativeSigningAuthenticationRoundtripBadDataTest
Description: Tests that a roundtrip of signing a request and afterwards authenticating it fails due to bad data
Description: Tests that a roundtrip of signing a request and afterwards authenticating is succedes.
Step: Sign a chunck of data.
Step: Check signature matches the data
Test success: negativeSigningAuthenticationRoundtripBadDataTest
Test starting: negativeSigningAuthenticationRoundtripUnkonwnCertificateTest
Description: Tests that a roundtrip of signing a request and afterwards authenticating it fails due to a unknown certificate.
Step: Sign a chunck of data.
Step: Check signature matches the data
Test success: negativeSigningAuthenticationRoundtripUnkonwnCertificateTest
Test starting: operationAuthorizationBehaviourTest
Description: Tests that a signature only allows the correct requests.
Step: Check that PUT_FILE is allowed for both collections.
Step: Check that GET_FILE is only allowed for the first collection.
Test success: operationAuthorizationBehaviourTest
Test starting: positiveSigningAuthenticationRoundtripTest
Description: Tests that a roundtrip of signing a request and afterwards authenticating is succedes.
Step: Sign a chunck of data.
Step: Check signature matches the data
Test success: positiveSigningAuthenticationRoundtripTest
Starting testcase TimeMeasurementUtilsTest
Test starting: testCompareMilliSeconds
Description: Test the comparison between TimeMeasure units.
Test success: testCompareMilliSeconds
Test starting: testCompareMilliSecondsToHours
Description: Test the comparison between milliseconds and hours.
Test success: testCompareMilliSecondsToHours
Test starting: testMaxValue
Description: Test the Maximum value
Test success: testMaxValue
Test starting: utilityTester
Description: Test that the utility class is a proper utility class.
Test success: utilityTester
Starting testcase TimeUtilsTest
Test starting: shortDateTest
Test success: shortDateTest
Test starting: timeTester
Description: Tests the TimeUtils. Pi days = 271433605 milliseconds
Step: Test that milliseconds can be converted into human readable seconds
Step: Test that milliseconds can be converted into human readable minutes.
Step: Test that milliseconds can be converted into human readable hours.
Step: Test that milliseconds can be converted into human readable minutes.
Step: Test the human readable output.
Test success: timeTester
Test starting: utilityTester
Description: Test that the utility class is a proper utility class.
Test success: utilityTester
Test starting: zeroIntervalTest
Description: Verifies that a 0 ms interval is represented correctly
Step: Call the millisecondsToHuman with 0 ms
Test success: zeroIntervalTest
Test starting: testUncaughtExceptionHandler
13:43:58.690 ERROR o.b.common.DefaultThreadFactoryTest - UncaughtExceptionHandler caught Exception:
java.lang.RuntimeException: Hey this is the message I want to see
at org.bitrepository.common.DefaultThreadFactoryTest.lambda$testUncaughtExceptionHandler$0(DefaultThreadFactoryTest.java:50)
at java.lang.Thread.run(Thread.java:745)
Test success: testUncaughtExceptionHandler
Starting testcase OperationAuthorizationExceptionTest
Test starting: testOperationAuthorizationException
Description: Test the instantiation of the exception
Step: Setup
Step: Try to throw such an exception
Step: Throw the exception with an embedded exception
Test success: testOperationAuthorizationException
Starting testcase CertificateIDTest
Test starting: equalTest
Description: Tests the equality of CertificateIDs
Step: Setup
Step: Validate the content of the certificateID
Step: Test whether it equals it self
Step: Test with a null as argument
Step: Test with another class
Step: Test with same issuer but no serial
Step: Test with same serial but no issuer
Step: Test the positive case, with both the issuer and serial
Step: Setup an empty certificate
Step: Test empty certificate against issuer but no serial
Step: Test empty certificate against serial but no issuer
Step: Test empty certificate against serial and issuer
Step: Test the positive case, with neither issuer nor serial
Step: Check the hash codes for the two certificate
Test success: equalTest
Test starting: negativeCertificateIdentificationTest
Description: Tests that a certificate is not identified based on a incorrect signature.
Step: Create CertificateID object based on a certificate not used for signing the data
Step: Create CertificateID object based on signature
Step: Assert that the two CertificateID objects are equal
Test success: negativeCertificateIdentificationTest
Test starting: positiveCertificateIdentificationTest
Description: Tests that a certificate can be identified based on the correct signature.
Step: Create CertificateID object based on the certificate used to sign the data
Step: Create CertificateID object based on signature
Step: Assert that the two CertificateID objects are equal
Test success: positiveCertificateIdentificationTest
Test starting: componentIDTest
Test success: componentIDTest
Test starting: reloadTest
Test success: reloadTest
Starting testcase ResponseInfoUtilsTest
Test starting: responseInfoTester
Description: Test the response info.
Step: Validate the positive identification response
Step: Validate the Progress response
Test success: responseInfoTester
Test starting: utilityTester
Description: Test that the utility class is a proper utility class.
Test success: utilityTester
Starting testcase SecurityExceptionTest
Test starting: testSecurityException
Description: Test the instantiation of the exception
Step: Setup
Step: Try to throw such an exception
Step: Throw the exception with an embedded exception
Test success: testSecurityException
Starting testcase FileIDUtilsTest
Test starting: fileIDsTest
Description: Test the utility class for generating FileIDs
Step: Test 'all file ids'
Step: Test a specific file id
Test success: fileIDsTest
Test starting: utilityTester
Description: Test that the utility class is a proper utility class.
Test success: utilityTester
Starting testcase MultiThreadedMessageBusTest
Test starting: manyTheadsBeforeFinish
Description: Tests whether it is possible to start the handling of many threads simultaneously.
Step: Send one message for each listener
Stimuli: Sending message: org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileRequest@3d64f938[correlationID=12345, collectionID=MySla, destination=BusActivityTest, replyTo=topic://clientTopic, from=ClientPillar, to=<null>(default), version=31, minVersion=24, auditTrailInformation=User: Name, Institution: Place, fileID=MyDataID]
Stimuli: Sending message: org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileRequest@3d64f938[correlationID=12345, collectionID=MySla, destination=BusActivityTest, replyTo=topic://clientTopic, from=ClientPillar, to=<null>(default), version=31, minVersion=24, auditTrailInformation=User: Name, Institution: Place, fileID=MyDataID]
Stimuli: Sending message: org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileRequest@3d64f938[correlationID=12345, collectionID=MySla, destination=BusActivityTest, replyTo=topic://clientTopic, from=ClientPillar, to=<null>(default), version=31, minVersion=24, auditTrailInformation=User: Name, Institution: Place, fileID=MyDataID]
Test success: manyTheadsBeforeFinish
Starting testcase FileIDValidatorTest
Test starting: badRegexTest
Description: Tests the FileIDValidator handling of bad file id pattern.
Step: Give the validator a 'null' as allowed file id pattern
Step: Give the validator an empty string as allowed file id pattern
Test success: badRegexTest
Test starting: validatorDefaultTest
Description: Tests the FileIDValidator class default restrictions. Only the length should fail.
Step: Setup the validator, where all file ids are allowed at default.
Step: Test a null as argument
Step: Test a valid fileID
Step: Test odd characters
Step: Test invalid length
Step: Test too short
Test success: validatorDefaultTest
Test starting: validatorTest
Description: Tests the FileIDValidator class for the input handling based on a given regex.
Step: Setup the validator
Step: Test a null as argument
Step: Test a valid fileID
Step: Test invalid characters
Step: Test invalid length
Step: Test too short
Test success: validatorTest
Starting testcase XMLFileSettingsLoaderTest
Test starting: testCollectionSettingsLoading
Test success: testCollectionSettingsLoading
Starting testcase SettingsLoaderTest
Test starting: testDevelopmentCollectionSettingsLoading
Test success: testDevelopmentCollectionSettingsLoading
Test starting: testExampleSettingsLoading
Test success: testExampleSettingsLoading
Finished testcase
13:44:00.688 ERROR o.b.protocol.bus.RawMessagebus - JMSException caught:
javax.jms.JMSException: java.io.EOFException
at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:54)
at org.apache.activemq.ActiveMQConnection.onAsyncException(ActiveMQConnection.java:1960)
at org.apache.activemq.ActiveMQConnection.onException(ActiveMQConnection.java:1979)
at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:114)
at org.apache.activemq.transport.ResponseCorrelator.onException(ResponseCorrelator.java:126)
at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:114)
at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:114)
at org.apache.activemq.transport.WireFormatNegotiator.onException(WireFormatNegotiator.java:173)
at org.apache.activemq.transport.AbstractInactivityMonitor.onException(AbstractInactivityMonitor.java:345)
at org.apache.activemq.transport.TransportSupport.onException(TransportSupport.java:96)
at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:219)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.io.EOFException: null
at java.io.DataInputStream.readInt(DataInputStream.java:392)
at org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:268)
at org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:240)
at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:232)
at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:215)
... 1 common frames omitted
13:44:00.702 ERROR o.b.protocol.bus.RawMessagebus - JMSException caught:
javax.jms.JMSException: java.io.EOFException
at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:54)
at org.apache.activemq.ActiveMQConnection.onAsyncException(ActiveMQConnection.java:1960)
at org.apache.activemq.ActiveMQConnection.onException(ActiveMQConnection.java:1979)
at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:114)
at org.apache.activemq.transport.ResponseCorrelator.onException(ResponseCorrelator.java:126)
at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:114)
at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:114)
at org.apache.activemq.transport.WireFormatNegotiator.onException(WireFormatNegotiator.java:173)
at org.apache.activemq.transport.AbstractInactivityMonitor.onException(AbstractInactivityMonitor.java:345)
at org.apache.activemq.transport.TransportSupport.onException(TransportSupport.java:96)
at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:219)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.io.EOFException: null
at java.io.DataInputStream.readInt(DataInputStream.java:392)
at org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:268)
at org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:240)
at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:232)
at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:215)
... 1 common frames omitted
13:44:00.721 ERROR o.b.protocol.bus.RawMessagebus - JMSException caught:
javax.jms.JMSException: java.io.EOFException
at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:54)
at org.apache.activemq.ActiveMQConnection.onAsyncException(ActiveMQConnection.java:1960)
at org.apache.activemq.ActiveMQConnection.onException(ActiveMQConnection.java:1979)
at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:114)
at org.apache.activemq.transport.ResponseCorrelator.onException(ResponseCorrelator.java:126)
at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:114)
at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:114)
at org.apache.activemq.transport.WireFormatNegotiator.onException(WireFormatNegotiator.java:173)
at org.apache.activemq.transport.AbstractInactivityMonitor.onException(AbstractInactivityMonitor.java:345)
at org.apache.activemq.transport.TransportSupport.onException(TransportSupport.java:96)
at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:219)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.io.EOFException: null
at java.io.DataInputStream.readInt(DataInputStream.java:392)
at org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:268)
at org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:240)
at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:232)
at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:215)
... 1 common frames omitted
Finished suite
Finished project
[INFO] Tests run: 104, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 29.846 s - in TestSuite
[INFO]
[INFO] Results:
[INFO]
[INFO] Tests run: 104, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[JENKINS] Recording test results
log4j:WARN No appenders could be found for logger (org.apache.commons.beanutils.converters.BooleanConverter).
log4j:WARN Please initialize the log4j system properly.
[INFO]
[INFO] --- jacoco-maven-plugin:0.8.5:report (report) @ bitrepository-core ---
[INFO] Loading execution data file /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-core/target/jacoco.exec
[INFO] Analyzed bundle 'Bitrepository Core' with 86 classes
[INFO]
[INFO] --- maven-jar-plugin:3.2.0:jar (default-jar) @ bitrepository-core ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-core/target/bitrepository-core-1.10-SNAPSHOT.jar
[INFO]
[INFO] --- maven-jar-plugin:3.2.0:test-jar (default) @ bitrepository-core ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-core/target/bitrepository-core-1.10-SNAPSHOT-tests.jar
[INFO]
[INFO] --- maven-source-plugin:3.2.1:jar-no-fork (attach-sources-no-fork) @ bitrepository-core ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-core/target/bitrepository-core-1.10-SNAPSHOT-sources.jar
[INFO]
[INFO] --- maven-install-plugin:3.0.0-M1:install (default-install) @ bitrepository-core ---
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-core/target/bitrepository-core-1.10-SNAPSHOT.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-core/1.10-SNAPSHOT/bitrepository-core-1.10-SNAPSHOT.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-core/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-core/1.10-SNAPSHOT/bitrepository-core-1.10-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-core/target/bitrepository-core-1.10-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-core/1.10-SNAPSHOT/bitrepository-core-1.10-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-core/target/bitrepository-core-1.10-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-core/1.10-SNAPSHOT/bitrepository-core-1.10-SNAPSHOT-sources.jar
[INFO]
[INFO] --- maven-deploy-plugin:3.0.0-M1:deploy (default-deploy) @ bitrepository-core ---
[INFO] Downloading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-core/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-core/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 49.7 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-core/1.10-SNAPSHOT/bitrepository-core-1.10-20220215.124405-64.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-core/1.10-SNAPSHOT/bitrepository-core-1.10-20220215.124405-64.jar (146 KB at 3169.2 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-core/1.10-SNAPSHOT/bitrepository-core-1.10-20220215.124405-64.pom
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-core/1.10-SNAPSHOT/bitrepository-core-1.10-20220215.124405-64.pom (4 KB at 109.9 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-core/1.10-SNAPSHOT/bitrepository-core-1.10-20220215.124405-64-tests.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-core/1.10-SNAPSHOT/bitrepository-core-1.10-20220215.124405-64-tests.jar (169 KB at 4203.6 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-core/1.10-SNAPSHOT/bitrepository-core-1.10-20220215.124405-64-sources.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-core/1.10-SNAPSHOT/bitrepository-core-1.10-20220215.124405-64-sources.jar (142 KB at 4053.5 KB/sec)
[INFO] Downloading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-core/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-core/maven-metadata.xml (482 B at 47.1 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-core/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-core/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 31.4 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-core/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-core/maven-metadata.xml (482 B at 15.7 KB/sec)
[JENKINS] Archiving disabled
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Client 1.10-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:3.1.0:clean (default-clean) @ bitrepository-client ---
[INFO]
[INFO] --- maven-enforcer-plugin:3.0.0-M3:enforce (enforce-maven) @ bitrepository-client ---
[INFO]
[INFO] --- jacoco-maven-plugin:0.8.5:prepare-agent (default) @ bitrepository-client ---
[INFO] argLine set to -javaagent:/home/cibuild01/.m2/repository/org/jacoco/org.jacoco.agent/0.8.5/org.jacoco.agent-0.8.5-runtime.jar=destfile=/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-client/target/jacoco.exec
[INFO]
[INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ bitrepository-client ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 4 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.8.1:compile (default-compile) @ bitrepository-client ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 130 source files to /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-client/target/classes
[WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-client/src/main/java/org/bitrepository/commandline/utils/CommandLineArgumentsHandler.java:[130,29] redundant cast to java.util.Collection<org.apache.commons.cli.Option>
[INFO]
[INFO] --- forbiddenapis:2.7:check (default) @ bitrepository-client ---
[INFO] Scanning for classes to check...
[INFO] Reading bundled API signatures: jdk-unsafe-1.8
[INFO] Reading bundled API signatures: jdk-deprecated-1.8
[INFO] Reading bundled API signatures: jdk-non-portable
[INFO] Reading bundled API signatures: jdk-reflection
[INFO] Loading classes to check...
[INFO] Scanning classes for violations...
[INFO] Scanned 137 class file(s) for forbidden API invocations (in 0.20s), 0 error(s).
[INFO]
[INFO] --- forbiddenapis:2.7:testCheck (default) @ bitrepository-client ---
[INFO] Scanning for classes to check...
[WARNING] Classes directory does not exist, forbiddenapis check skipped: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-client/target/test-classes
[INFO]
[INFO] --- maven-resources-plugin:3.1.0:testResources (default-testResources) @ bitrepository-client ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-client/src/test/resources
[INFO]
[INFO] --- maven-compiler-plugin:3.8.1:testCompile (default-testCompile) @ bitrepository-client ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 41 source files to /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-client/target/test-classes
[INFO]
[INFO] --- maven-surefire-plugin:3.0.0-M4:test (default-test) @ bitrepository-client ---
[INFO]
[INFO] -------------------------------------------------------
[INFO] T E S T S
[INFO] -------------------------------------------------------
[INFO] Running TestSuite
Starting test project Core module test
Suite: Surefire suite
Starting testcase AuditTrailClientComponentTest
Test starting: getAllAuditTrailsTest
Description: Tests the simplest case of getting all audit trail event for all contributers.
Step: Create a AuditTrailClient.
Step: Retrieve all audit trails from the collection by calling with a null componentQueries array
Stimuli: Calling getAuditTrails(null, default-test-file.txt, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@1d1deb11[correlationID=89abf3d8-202e-414f-b9c4-e05c3227a536, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=getAllAuditTrailsTest, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default)]
Result: Received event: 89abf3d8: GET_AUDIT_TRAILS for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
Step: Send a identifyResponse from each pillar
Result: Received event: 89abf3d8: GET_AUDIT_TRAILS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 89abf3d8: GET_AUDIT_TRAILS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 89abf3d8: GET_AUDIT_TRAILS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2]
Result: Received event: 89abf3d8: GET_AUDIT_TRAILS for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for audit trails
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@6839d03b[correlationID=89abf3d8-202e-414f-b9c4-e05c3227a536, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=getAllAuditTrailsTest, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), contributor=Pillar1, fileID=default-test-file.txt, minSequenceNumber=<null>(default), maxSequenceNumber=<null>(default), minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), resultAddress=<null>(default)]
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@703e5614[correlationID=89abf3d8-202e-414f-b9c4-e05c3227a536, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=getAllAuditTrailsTest, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), contributor=Pillar2, fileID=default-test-file.txt, minSequenceNumber=<null>(default), maxSequenceNumber=<null>(default), minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), resultAddress=<null>(default)]
Step: Send a final response from pillar 1
Result: Received event: 89abf3d8: GET_AUDIT_TRAILS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, NumberOfAuditTrailEvents=2, PartialResult=false
Step: Send a final response from pillar 2
Result: Received event: 89abf3d8: GET_AUDIT_TRAILS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2, NumberOfAuditTrailEvents=2, PartialResult=false
Result: Received event: 89abf3d8: GET_AUDIT_TRAILS for file default-test-file.txt: COMPLETE:
Test success: getAllAuditTrailsTest
Test starting: getSomeAuditTrailsTest
Description: Tests the client maps a AuditTrail query correctly to a GetAuditTrail request.
Step: Request audit trails from pillar 1 with both min and max sequence number set.
Stimuli: Calling getAuditTrails([AuditTrailQuery{componentID='Pillar1, minTimestamp=null, maxTimestamp=null, maxNumberOfResults=10000}minSequenceNumber=1, maxSequenceNumber=3}], null, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@57806346[correlationID=6a82ee75-953a-4061-86c0-3e95df4d3f7d, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=getSomeAuditTrailsTest, to=Pillar1, version=31, minVersion=24, auditTrailInformation=<null>(default)]
Result: Received event: 6a82ee75: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
Step: Send a identifyResponse from pillar1
Result: Received event: 6a82ee75: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 6a82ee75: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 6a82ee75: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1], Sending request for audit trails
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@3ab70d34[correlationID=6a82ee75-953a-4061-86c0-3e95df4d3f7d, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=getSomeAuditTrailsTest, to=Pillar1, version=31, minVersion=24, auditTrailInformation=<null>(default), contributor=Pillar1, fileID=<null>(default), minSequenceNumber=1, maxSequenceNumber=3, minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=10000, resultAddress=<null>(default)]
Step: Verify no request is sent to pillar2
Step: Send a final response from pillar 1
Result: Received event: 6a82ee75: GET_AUDIT_TRAILS: COMPONENT_COMPLETE: ContributorID Pillar1, NumberOfAuditTrailEvents=2, PartialResult=false
Result: Received event: 6a82ee75: GET_AUDIT_TRAILS: COMPLETE:
Test success: getSomeAuditTrailsTest
Test starting: incompleteSetOfFinalResponsesTest
Description: Verify that the GetAuditTrail client works correct without receiving responses from all contributers.
Step: Configure 500 ms second timeout for the operation itself. The default 2 contributers collection is used
Stimuli: Calling getAuditTrails(null, null, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@632d1b1b[correlationID=92f78b02-b31c-423e-a0a2-846f77816e48, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=incompleteSetOfFinalResponsesTest, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default)]
Result: Received event: 92f78b02: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
Step: Send a identifyResponse from each of the two pillars
Result: Received event: 92f78b02: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 92f78b02: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 92f78b02: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2]
Result: Received event: 92f78b02: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for audit trails
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@48cd8e71[correlationID=92f78b02-b31c-423e-a0a2-846f77816e48, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=incompleteSetOfFinalResponsesTest, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), contributor=Pillar1, fileID=<null>(default), minSequenceNumber=<null>(default), maxSequenceNumber=<null>(default), minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), resultAddress=<null>(default)]
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@43b3b1b0[correlationID=92f78b02-b31c-423e-a0a2-846f77816e48, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=incompleteSetOfFinalResponsesTest, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), contributor=Pillar2, fileID=<null>(default), minSequenceNumber=<null>(default), maxSequenceNumber=<null>(default), minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), resultAddress=<null>(default)]
Test success: incompleteSetOfFinalResponsesTest
Result: The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@43b3b1b0[correlationID=92f78b02-b31c-423e-a0a2-846f77816e48, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=incompleteSetOfFinalResponsesTest, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), contributor=Pillar2, fileID=<null>(default), minSequenceNumber=<null>(default), maxSequenceNumber=<null>(default), minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), resultAddress=<null>(default)]
13:44:15.067 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@43b3b1b0[correlationID=92f78b02-b31c-423e-a0a2-846f77816e48, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=incompleteSetOfFinalResponsesTest, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), contributor=Pillar2, fileID=<null>(default), minSequenceNumber=<null>(default), maxSequenceNumber=<null>(default), minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), resultAddress=<null>(default)]
Test starting: negativeGetAuditTrailsResponseTest
Description: Verify that the GetAuditTrail client works correct when receiving a negative GetAuditTrails response from one contributers.
Step: Create a AuditTrailClient.
Step: Retrieve all audit trails from the collection by calling with a null componentQueries array
Stimuli: Calling getAuditTrails(null, null, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@669469c9[correlationID=48c2a566-239b-47c3-831e-7126d81da6b6, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=negativeGetAuditTrailsResponseTest, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default)]
Result: Received event: 48c2a566: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
Step: Send a identifyResponse from each of the two pillars
Result: Received event: 48c2a566: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 48c2a566: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 48c2a566: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2]
Result: Received event: 48c2a566: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for audit trails
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@7612f385[correlationID=48c2a566-239b-47c3-831e-7126d81da6b6, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=negativeGetAuditTrailsResponseTest, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), contributor=Pillar1, fileID=<null>(default), minSequenceNumber=<null>(default), maxSequenceNumber=<null>(default), minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), resultAddress=<null>(default)]
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@330d16af[correlationID=48c2a566-239b-47c3-831e-7126d81da6b6, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=negativeGetAuditTrailsResponseTest, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), contributor=Pillar2, fileID=<null>(default), minSequenceNumber=<null>(default), maxSequenceNumber=<null>(default), minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), resultAddress=<null>(default)]
Step: Send a failed response from pillar 1
Result: Received event: 48c2a566: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE, GetAuditTrails failed
Step: Send a final response from pillar 2
Result: Received event: 48c2a566: GET_AUDIT_TRAILS: COMPONENT_COMPLETE: ContributorID Pillar2, NumberOfAuditTrailEvents=2, PartialResult=false
Result: Received event: 48c2a566: GET_AUDIT_TRAILS: FAILED: , Failed operation. Cause(s):
[48c2a566: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE, GetAuditTrails failed]
Test success: negativeGetAuditTrailsResponseTest
Result: Received event: 92f78b02: GET_AUDIT_TRAILS: FAILED: , Failed to receive responses from all contributors before timeout(500ms). Missing contributors [Pillar1, Pillar2]
13:44:15.563 ERROR o.b.a.g.client.GettingAuditTrails - Failing conversation 'AuditTrailConversationContext{collectionID='TwoPillarCollection', conversationID='92f78b02-b31c-423e-a0a2-846f77816e48', clientID='incompleteSetOfFinalResponsesTest', fileID='null', contributors=[Pillar1, Pillar2], monitor=ConversationEventMonitor{, collectionID='TwoPillarCollection', conversationID='92f78b02', operationType=GET_AUDIT_TRAILS, fileID='null', eventHandler=org.bitrepository.client.TestEventHandler@7c57ee60, contributorCompleteEvents=[], contributorFailedEvents=[], failOnComponentFailure=true}, auditTrailInformation='null', state=org.bitrepository.client.conversation.FinishedState@68f9e7e7, checksumPillars=[]}' with exception
org.bitrepository.common.exceptions.UnableToFinishException: Failed to receive responses from all contributors before timeout(500ms). Missing contributors [Pillar1, Pillar2]
at org.bitrepository.client.conversation.PerformingOperationState.logStateTimeout(PerformingOperationState.java:82)
at org.bitrepository.client.conversation.GeneralConversationState$TimeoutHandler.run(GeneralConversationState.java:133)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Test starting: noFinalResponsesTest
Description: Tests the the AuditTrailClient handles lack of Final Responses gracefully
Step: Set a 100 ms timeout for the operation.
Step: Make the client ask for all audit trails.
Stimuli: Calling getAuditTrails(null, null, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@3e0e3048[correlationID=abfb81a0-99af-464c-a22c-350070822b02, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noFinalResponsesTest, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default)]
Result: Received event: abfb81a0: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
Step: Send a identifyResponse from each of the two pillars
Result: Received event: abfb81a0: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: abfb81a0: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: abfb81a0: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2, Pillar1]
Result: Received event: abfb81a0: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for audit trails
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@16e5c19f[correlationID=abfb81a0-99af-464c-a22c-350070822b02, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noFinalResponsesTest, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), contributor=Pillar1, fileID=<null>(default), minSequenceNumber=<null>(default), maxSequenceNumber=<null>(default), minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), resultAddress=<null>(default)]
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@59263f7b[correlationID=abfb81a0-99af-464c-a22c-350070822b02, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noFinalResponsesTest, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), contributor=Pillar2, fileID=<null>(default), minSequenceNumber=<null>(default), maxSequenceNumber=<null>(default), minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), resultAddress=<null>(default)]
Step: Wait for 1 second
Result: Received event: abfb81a0: GET_AUDIT_TRAILS: FAILED: , Failed to receive responses from all contributors before timeout(100ms). Missing contributors [Pillar1, Pillar2]
13:44:15.747 ERROR o.b.a.g.client.GettingAuditTrails - Failing conversation 'AuditTrailConversationContext{collectionID='TwoPillarCollection', conversationID='abfb81a0-99af-464c-a22c-350070822b02', clientID='noFinalResponsesTest', fileID='null', contributors=[Pillar1, Pillar2], monitor=ConversationEventMonitor{, collectionID='TwoPillarCollection', conversationID='abfb81a0', operationType=GET_AUDIT_TRAILS, fileID='null', eventHandler=org.bitrepository.client.TestEventHandler@78c8f4e0, contributorCompleteEvents=[], contributorFailedEvents=[], failOnComponentFailure=true}, auditTrailInformation='null', state=org.bitrepository.client.conversation.FinishedState@5fa9f2c1, checksumPillars=[]}' with exception
org.bitrepository.common.exceptions.UnableToFinishException: Failed to receive responses from all contributors before timeout(100ms). Missing contributors [Pillar1, Pillar2]
at org.bitrepository.client.conversation.PerformingOperationState.logStateTimeout(PerformingOperationState.java:82)
at org.bitrepository.client.conversation.GeneralConversationState$TimeoutHandler.run(GeneralConversationState.java:133)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Test success: noFinalResponsesTest
Result: The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@16e5c19f[correlationID=abfb81a0-99af-464c-a22c-350070822b02, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noFinalResponsesTest, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), contributor=Pillar1, fileID=<null>(default), minSequenceNumber=<null>(default), maxSequenceNumber=<null>(default), minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), resultAddress=<null>(default)]
13:44:15.748 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@16e5c19f[correlationID=abfb81a0-99af-464c-a22c-350070822b02, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noFinalResponsesTest, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), contributor=Pillar1, fileID=<null>(default), minSequenceNumber=<null>(default), maxSequenceNumber=<null>(default), minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), resultAddress=<null>(default)]
Result: The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@59263f7b[correlationID=abfb81a0-99af-464c-a22c-350070822b02, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noFinalResponsesTest, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), contributor=Pillar2, fileID=<null>(default), minSequenceNumber=<null>(default), maxSequenceNumber=<null>(default), minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), resultAddress=<null>(default)]
13:44:15.750 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@59263f7b[correlationID=abfb81a0-99af-464c-a22c-350070822b02, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noFinalResponsesTest, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), contributor=Pillar2, fileID=<null>(default), minSequenceNumber=<null>(default), maxSequenceNumber=<null>(default), minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), resultAddress=<null>(default)]
Test starting: progressEventsTest
Description: Tests that progress events are handled correctly.
Step: Create a AuditTrailClient.
Step: Retrieve all audit trails from the collection by calling with a null componentQueries array
Stimuli: Calling getAuditTrails(null, null, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@4c89c98a[correlationID=dbdb9748-1875-4180-af9d-2bbd55c50fd7, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=progressEventsTest, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default)]
Result: Received event: dbdb9748: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
Step: Send a identifyResponse from each of the two pillars
Result: Received event: dbdb9748: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: dbdb9748: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: dbdb9748: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2]
Result: Received event: dbdb9748: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for audit trails
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@38318d67[correlationID=dbdb9748-1875-4180-af9d-2bbd55c50fd7, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=progressEventsTest, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), contributor=Pillar1, fileID=<null>(default), minSequenceNumber=<null>(default), maxSequenceNumber=<null>(default), minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), resultAddress=<null>(default)]
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@3af6c672[correlationID=dbdb9748-1875-4180-af9d-2bbd55c50fd7, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=progressEventsTest, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), contributor=Pillar2, fileID=<null>(default), minSequenceNumber=<null>(default), maxSequenceNumber=<null>(default), minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), resultAddress=<null>(default)]
Step: Send a progress accepted response from pillar 1
Result: Received event: dbdb9748: GET_AUDIT_TRAILS: PROGRESS: ContributorID Pillar1, GetAuditTrails request accepted
Step: Send a general progress response from pillar 2
Result: Received event: dbdb9748: GET_AUDIT_TRAILS: PROGRESS: ContributorID Pillar2, Still progressing
Test success: progressEventsTest
Test starting: verifyAuditTrailClientFromFactory
Test success: verifyAuditTrailClientFromFactory
Starting testcase CommandLineTest
Test starting: argumentsTesterUnknownArgument
Description: Test the handling of arguments by the CommandLineArgumentHandler.
Step: Validate arguments without any options.
Test success: argumentsTesterUnknownArgument
Test starting: argumentsTesterWrongArgument
Description: Test the handling of arguments by the CommandLineArgumentHandler.
Step: Validate the default options
Test success: argumentsTesterWrongArgument
Test starting: newArgumentTester
Description: Test the handling of a new argument.
Step: Test the option
Test success: newArgumentTester
Test starting: collectionIDIncludedInEventsTest
Description: Tests the the client provides collectionID in events.
Step: Set a 0.5 second operation timeout.
Step: Start the operation
Stimuli: Calling getAuditTrails(null, null, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@14f254f[correlationID=1d561db5-e6b3-42bb-9ac3-c978d77a3914, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=collectionIDIncludedInEventsTest, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default)]
Result: Received event: 1d561db5: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
Step: Send positive responses from the pillar1 and a negative response from pillar2
Result: Received event: 1d561db5: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 1d561db5: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE
Result: Received event: 1d561db5: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 1d561db5: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1], Sending request for audit trails
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@4df54c1[correlationID=1d561db5-e6b3-42bb-9ac3-c978d77a3914, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=collectionIDIncludedInEventsTest, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), contributor=Pillar1, fileID=<null>(default), minSequenceNumber=<null>(default), maxSequenceNumber=<null>(default), minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), resultAddress=<null>(default)]
Step: Wait for 1 second
Result: Received event: 1d561db5: GET_AUDIT_TRAILS: FAILED: , Failed to receive responses from all contributors before timeout(500ms). Missing contributors [Pillar1]
13:44:17.071 ERROR o.b.a.g.client.GettingAuditTrails - Failing conversation 'AuditTrailConversationContext{collectionID='TwoPillarCollection', conversationID='1d561db5-e6b3-42bb-9ac3-c978d77a3914', clientID='collectionIDIncludedInEventsTest', fileID='null', contributors=[Pillar1, Pillar2], monitor=ConversationEventMonitor{, collectionID='TwoPillarCollection', conversationID='1d561db5', operationType=GET_AUDIT_TRAILS, fileID='null', eventHandler=org.bitrepository.client.TestEventHandler@182acad1, contributorCompleteEvents=[], contributorFailedEvents=[1d561db5: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE], failOnComponentFailure=true}, auditTrailInformation='null', state=org.bitrepository.client.conversation.FinishedState@5a0fdf3e, checksumPillars=[]}' with exception
org.bitrepository.common.exceptions.UnableToFinishException: Failed to receive responses from all contributors before timeout(500ms). Missing contributors [Pillar1]
at org.bitrepository.client.conversation.PerformingOperationState.logStateTimeout(PerformingOperationState.java:82)
at org.bitrepository.client.conversation.GeneralConversationState$TimeoutHandler.run(GeneralConversationState.java:133)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Test success: collectionIDIncludedInEventsTest
Starting testcase GetChecksumsClientComponentTest
Test starting: collectionIDIncludedInEventsTest
Description: Tests the the client provides collectionID in events.
Step: Set a 0.5 second operation timeout.
Step: Start the operation
Stimuli: Calling getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@7f82a71f, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@6037748a[correlationID=c56dbc11-bbfb-4649-8355-96e9c7946003, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=collectionIDIncludedInEventsTest, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@4d87e7f3[fileID=<null>(default), allFileIDs=true], checksumRequestForExistingFile=<null>(default)]
Result: Received event: c56dbc11: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums
Step: Send positive responses from the pillar1 and a negative response from pillar2
Result: Received event: c56dbc11: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: c56dbc11: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE
Result: Received event: c56dbc11: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: c56dbc11: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar1], Sending GetChecksumsRequest's
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@5620470a[correlationID=c56dbc11-bbfb-4649-8355-96e9c7946003, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=collectionIDIncludedInEventsTest, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@29682244[fileID=<null>(default), allFileIDs=true], minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), checksumRequestForExistingFile=<null>(default), resultAddress=<null>(default)]
Step: Wait for 1 second
Result: Received event: c56dbc11: GET_CHECKSUMS: FAILED: , Failed to receive responses from all contributors before timeout(500ms). Missing contributors [Pillar1]
13:44:17.842 ERROR o.b.a.g.c.GettingChecksums - Failing conversation 'GetChecksumsConversationContext{collectionID='TwoPillarCollection', conversationID='c56dbc11-bbfb-4649-8355-96e9c7946003', clientID='collectionIDIncludedInEventsTest', fileID='null', contributors=[Pillar1, Pillar2], monitor=ConversationEventMonitor{, collectionID='TwoPillarCollection', conversationID='c56dbc11', operationType=GET_CHECKSUMS, fileID='null', eventHandler=org.bitrepository.client.TestEventHandler@7f82a71f, contributorCompleteEvents=[], contributorFailedEvents=[c56dbc11: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE], failOnComponentFailure=true}, auditTrailInformation='null', state=org.bitrepository.client.conversation.FinishedState@65df5f6b, checksumPillars=[]}' with exception
org.bitrepository.common.exceptions.UnableToFinishException: Failed to receive responses from all contributors before timeout(500ms). Missing contributors [Pillar1]
at org.bitrepository.client.conversation.PerformingOperationState.logStateTimeout(PerformingOperationState.java:82)
at org.bitrepository.client.conversation.GeneralConversationState$TimeoutHandler.run(GeneralConversationState.java:133)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Test success: collectionIDIncludedInEventsTest
Starting testcase GetFileIDsClientComponentTest
Test starting: collectionIDIncludedInEventsTest
Description: Tests the the client provides collectionID in events.
Step: Set a 0.5 second operation timeout.
Step: Start the operation
Stimuli: Calling getFileIDs(null, null, null, org.bitrepository.client.TestEventHandler@449f9628)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@5dd5422f[correlationID=bc9b5c21-59d1-49b8-8f5a-2335de4fe6a4, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=collectionIDIncludedInEventsTest, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@158b8d10[fileID=<null>(default), allFileIDs=true]]
Result: Received event: bc9b5c21: GET_FILE_IDS: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs
Step: Send positive responses from the pillar1 and a negative response from pillar2
Result: Received event: bc9b5c21: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: bc9b5c21: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE
Result: Received event: bc9b5c21: GET_FILE_IDS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: bc9b5c21: GET_FILE_IDS: REQUEST_SENT: ContributorID [Pillar1], Sending request for get fileIDs
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@104e6540[correlationID=bc9b5c21-59d1-49b8-8f5a-2335de4fe6a4, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=collectionIDIncludedInEventsTest, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@3f9ee527[fileID=<null>(default), allFileIDs=true], minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), resultAddress=<null>(default)]
Step: Wait for 1 second
Result: Received event: bc9b5c21: GET_FILE_IDS: FAILED: , Failed to receive responses from all contributors before timeout(500ms). Missing contributors [Pillar1]
13:44:18.607 ERROR o.b.a.g.conversation.GettingFileIDs - Failing conversation 'GetFileIDsConversationContext{collectionID='TwoPillarCollection', conversationID='bc9b5c21-59d1-49b8-8f5a-2335de4fe6a4', clientID='collectionIDIncludedInEventsTest', fileID='null', contributors=[Pillar1, Pillar2], monitor=ConversationEventMonitor{, collectionID='TwoPillarCollection', conversationID='bc9b5c21', operationType=GET_FILE_IDS, fileID='null', eventHandler=org.bitrepository.client.TestEventHandler@449f9628, contributorCompleteEvents=[], contributorFailedEvents=[bc9b5c21: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE], failOnComponentFailure=true}, auditTrailInformation='null', state=org.bitrepository.client.conversation.FinishedState@75f096eb, checksumPillars=[]}' with exception
org.bitrepository.common.exceptions.UnableToFinishException: Failed to receive responses from all contributors before timeout(500ms). Missing contributors [Pillar1]
at org.bitrepository.client.conversation.PerformingOperationState.logStateTimeout(PerformingOperationState.java:82)
at org.bitrepository.client.conversation.GeneralConversationState$TimeoutHandler.run(GeneralConversationState.java:133)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Test success: collectionIDIncludedInEventsTest
Test starting: conversationTimeoutTest
Description: Tests the the client handles lack of IdentifyPillarResponses gracefully
Step: Set a 100 ms ConversationTimeout.
Step: Start the operation
Stimuli: Calling getAuditTrails(null, null, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@58f8ce0f[correlationID=ea40c85b-bf3d-4cee-9dbe-16da1fcd6f48, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=conversationTimeoutTest, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default)]
Result: Received event: ea40c85b: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
13:44:19.850 WARN o.b.c.c.m.CollectionBasedConversationMediator - Failing timed out conversation ea40c85b-bf3d-4cee-9dbe-16da1fcd6f48 (Age 1000ms)
Result: Received event: ea40c85b: GET_AUDIT_TRAILS: FAILED: , Failing timed out conversation ea40c85b-bf3d-4cee-9dbe-16da1fcd6f48
Test success: conversationTimeoutTest
Test starting: conversationTimeoutTest
Description: Tests the the client handles lack of IdentifyPillarResponses gracefully
Step: Set a 100 ms ConversationTimeout.
Step: Start the operation
Stimuli: Calling getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@7f82a71f, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@46bbcb82[correlationID=bbdf4e9b-ef85-48d3-8c6b-a3949a156851, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=conversationTimeoutTest, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@b91e024[fileID=<null>(default), allFileIDs=true], checksumRequestForExistingFile=<null>(default)]
Result: Received event: bbdf4e9b: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums
13:44:21.099 WARN o.b.c.c.m.CollectionBasedConversationMediator - Failing timed out conversation bbdf4e9b-ef85-48d3-8c6b-a3949a156851 (Age 997ms)
Result: Received event: bbdf4e9b: GET_CHECKSUMS: FAILED: , Failing timed out conversation bbdf4e9b-ef85-48d3-8c6b-a3949a156851
Test success: conversationTimeoutTest
Test starting: conversationTimeoutTest
Description: Tests the the client handles lack of IdentifyPillarResponses gracefully
Step: Set a 100 ms ConversationTimeout.
Step: Start the operation
Stimuli: Calling getFileIDs(null, null, null, org.bitrepository.client.TestEventHandler@449f9628)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@6fb3d3bb[correlationID=1268e2af-fa8c-440e-8f66-08b32646a06d, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=conversationTimeoutTest, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@38a3c078[fileID=<null>(default), allFileIDs=true]]
Result: Received event: 1268e2af: GET_FILE_IDS: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs
13:44:22.376 WARN o.b.c.c.m.CollectionBasedConversationMediator - Failing timed out conversation 1268e2af-fa8c-440e-8f66-08b32646a06d (Age 999ms)
Result: Received event: 1268e2af: GET_FILE_IDS: FAILED: , Failing timed out conversation 1268e2af-fa8c-440e-8f66-08b32646a06d
Test success: conversationTimeoutTest
Test starting: identificationFailureTest
Description: Verify that the client works correctly when a contributor sends a failure response.
Step: Start the operation.
Stimuli: Calling getAuditTrails(null, null, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@7c1e5d14[correlationID=06007d72-ece3-4eea-9859-14b74f57914f, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=identificationFailureTest, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default)]
Result: Received event: 06007d72: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
Step: Send a identification response from contributor1 with a FAILURE response code.
Result: Received event: 06007d72: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE
Step: Send a identification response from contributor2 with a IDENTIFICATION_POSITIVE response code .
Result: Received event: 06007d72: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 06007d72: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: 06007d72: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar2], Sending request for audit trails
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@479f738a[correlationID=06007d72-ece3-4eea-9859-14b74f57914f, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=identificationFailureTest, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), contributor=Pillar2, fileID=<null>(default), minSequenceNumber=<null>(default), maxSequenceNumber=<null>(default), minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), resultAddress=<null>(default)]
Step: Verify that the client continues to the performing phase.
Step: Send a final response message from contributor2
Result: Received event: 06007d72: GET_AUDIT_TRAILS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false
Result: Received event: 06007d72: GET_AUDIT_TRAILS: FAILED: , Failed operation. Cause(s):
[06007d72: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE]
Test success: identificationFailureTest
Test starting: identificationFailureTest
Description: Verify that the client works correctly when a contributor sends a failure response.
Step: Start the operation.
Stimuli: Calling getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@7f82a71f, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@72557e0d[correlationID=c4e55fa2-5464-4b29-a17b-92984db4b7bb, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=identificationFailureTest, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@14b4caba[fileID=<null>(default), allFileIDs=true], checksumRequestForExistingFile=<null>(default)]
Result: Received event: c4e55fa2: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums
Step: Send a identification response from contributor1 with a FAILURE response code.
Result: Received event: c4e55fa2: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE
Step: Send a identification response from contributor2 with a IDENTIFICATION_POSITIVE response code .
Result: Received event: c4e55fa2: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: c4e55fa2: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: c4e55fa2: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar2], Sending GetChecksumsRequest's
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@6e157f48[correlationID=c4e55fa2-5464-4b29-a17b-92984db4b7bb, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=identificationFailureTest, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@37e9d191[fileID=<null>(default), allFileIDs=true], minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), checksumRequestForExistingFile=<null>(default), resultAddress=<null>(default)]
Step: Verify that the client continues to the performing phase.
Step: Send a final response message from contributor2
Result: Received event: c4e55fa2: GET_CHECKSUMS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false
Result: Received event: c4e55fa2: GET_CHECKSUMS: FAILED: , Failed operation. Cause(s):
[c4e55fa2: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE]
Test success: identificationFailureTest
Test starting: identificationFailureTest
Description: Verify that the client works correctly when a contributor sends a failure response.
Step: Start the operation.
Stimuli: Calling getFileIDs(null, null, null, org.bitrepository.client.TestEventHandler@449f9628)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@664c411d[correlationID=e2e85450-8689-4ab5-8861-a8475db3b32a, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=identificationFailureTest, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@7641d70[fileID=<null>(default), allFileIDs=true]]
Result: Received event: e2e85450: GET_FILE_IDS: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs
Step: Send a identification response from contributor1 with a FAILURE response code.
Result: Received event: e2e85450: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE
Step: Send a identification response from contributor2 with a IDENTIFICATION_POSITIVE response code .
Result: Received event: e2e85450: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: e2e85450: GET_FILE_IDS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: e2e85450: GET_FILE_IDS: REQUEST_SENT: ContributorID [Pillar2], Sending request for get fileIDs
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@3726fc3b[correlationID=e2e85450-8689-4ab5-8861-a8475db3b32a, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=identificationFailureTest, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@33e6176b[fileID=<null>(default), allFileIDs=true], minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), resultAddress=<null>(default)]
Step: Verify that the client continues to the performing phase.
Step: Send a final response message from contributor2
Result: Received event: e2e85450: GET_FILE_IDS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false
Result: Received event: e2e85450: GET_FILE_IDS: FAILED: , Failed operation. Cause(s):
[e2e85450: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE]
Test success: identificationFailureTest
Test starting: identificationNegativeTest
Description: Verify that the client works correctly when a contributor sends a negative response.
Step: Start the operation.
Stimuli: Calling getAuditTrails(null, null, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@17179a7e[correlationID=5b6fe5e7-eb90-40ff-a3ba-e98238bcf954, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=identificationNegativeTest, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default)]
Result: Received event: 5b6fe5e7: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
Step: Send a identification response from contributor1 with a IDENTIFICATION_NEGATIVE response code .
Result: Received event: 5b6fe5e7: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: IDENTIFICATION_NEGATIVE
Step: Send a identification response from contributor2 with a IDENTIFICATION_POSITIVE response code .
Result: Received event: 5b6fe5e7: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 5b6fe5e7: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: 5b6fe5e7: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar2], Sending request for audit trails
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@5ce593bc[correlationID=5b6fe5e7-eb90-40ff-a3ba-e98238bcf954, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=identificationNegativeTest, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), contributor=Pillar2, fileID=<null>(default), minSequenceNumber=<null>(default), maxSequenceNumber=<null>(default), minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), resultAddress=<null>(default)]
Step: Verify that the client continues to the performing phase.
Step: Send a final response message from contributor2
Result: Received event: 5b6fe5e7: GET_AUDIT_TRAILS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false
Result: Received event: 5b6fe5e7: GET_AUDIT_TRAILS: FAILED: , Failed operation. Cause(s):
[5b6fe5e7: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: IDENTIFICATION_NEGATIVE]
Test success: identificationNegativeTest
Test starting: identificationNegativeTest
Description: Verify that the client works correctly when a contributor sends a negative response.
Step: Start the operation.
Stimuli: Calling getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@7f82a71f, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@10522dfd[correlationID=0af5605c-a416-4f0e-9831-28128585f04d, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=identificationNegativeTest, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@17d6b6e[fileID=<null>(default), allFileIDs=true], checksumRequestForExistingFile=<null>(default)]
Result: Received event: 0af5605c: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums
Step: Send a identification response from contributor1 with a IDENTIFICATION_NEGATIVE response code .
Result: Received event: 0af5605c: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: IDENTIFICATION_NEGATIVE
Step: Send a identification response from contributor2 with a IDENTIFICATION_POSITIVE response code .
Result: Received event: 0af5605c: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 0af5605c: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: 0af5605c: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar2], Sending GetChecksumsRequest's
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@5c519681[correlationID=0af5605c-a416-4f0e-9831-28128585f04d, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=identificationNegativeTest, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@5d6d6533[fileID=<null>(default), allFileIDs=true], minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), checksumRequestForExistingFile=<null>(default), resultAddress=<null>(default)]
Step: Verify that the client continues to the performing phase.
Step: Send a final response message from contributor2
Result: Received event: 0af5605c: GET_CHECKSUMS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false
Result: Received event: 0af5605c: GET_CHECKSUMS: FAILED: , Failed operation. Cause(s):
[0af5605c: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: IDENTIFICATION_NEGATIVE]
Test success: identificationNegativeTest
Test starting: identificationNegativeTest
Description: Verify that the client works correctly when a contributor sends a negative response.
Step: Start the operation.
Stimuli: Calling getFileIDs(null, null, null, org.bitrepository.client.TestEventHandler@449f9628)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@2d2c794d[correlationID=90bd15bd-c5c3-4ba0-9302-f9735881d2dc, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=identificationNegativeTest, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@53f67af6[fileID=<null>(default), allFileIDs=true]]
Result: Received event: 90bd15bd: GET_FILE_IDS: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs
Step: Send a identification response from contributor1 with a IDENTIFICATION_NEGATIVE response code .
Result: Received event: 90bd15bd: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: IDENTIFICATION_NEGATIVE
Step: Send a identification response from contributor2 with a IDENTIFICATION_POSITIVE response code .
Result: Received event: 90bd15bd: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 90bd15bd: GET_FILE_IDS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: 90bd15bd: GET_FILE_IDS: REQUEST_SENT: ContributorID [Pillar2], Sending request for get fileIDs
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@35abfeba[correlationID=90bd15bd-c5c3-4ba0-9302-f9735881d2dc, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=identificationNegativeTest, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@7b031f53[fileID=<null>(default), allFileIDs=true], minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), resultAddress=<null>(default)]
Step: Verify that the client continues to the performing phase.
Step: Send a final response message from contributor2
Result: Received event: 90bd15bd: GET_FILE_IDS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false
Result: Received event: 90bd15bd: GET_FILE_IDS: FAILED: , Failed operation. Cause(s):
[90bd15bd: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: IDENTIFICATION_NEGATIVE]
Test success: identificationNegativeTest
Test starting: noContributorsRespondingTest
Description: Tests the the client handles lack of a IdentifyResponse gracefully. More concrete this means that the occurrence of a identification timeout should be handled correctly
Step: Set a 100 ms timeout for identifying contributors.
Step: Start the operation.
Stimuli: Calling getAuditTrails(null, null, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@29ae939c[correlationID=abe43406-f6a5-4764-a422-a858ed254051, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noContributorsRespondingTest, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default)]
Result: Received event: abe43406: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
Step: Wait for 1 second
Result: Received event: abe43406: GET_AUDIT_TRAILS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar1, Pillar2]
Result: Received event: abe43406: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor
Result: Received event: abe43406: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
Result: Received event: abe43406: GET_AUDIT_TRAILS: FAILED: , Unable to continue operation, contributors unavailable.
13:44:30.195 ERROR o.b.a.g.c.IdentifyingAuditTrailContributors - Failing conversation 'AuditTrailConversationContext{collectionID='TwoPillarCollection', conversationID='abe43406-f6a5-4764-a422-a858ed254051', clientID='noContributorsRespondingTest', fileID='null', contributors=[Pillar1, Pillar2], monitor=ConversationEventMonitor{, collectionID='TwoPillarCollection', conversationID='abe43406', operationType=GET_AUDIT_TRAILS, fileID='null', eventHandler=org.bitrepository.client.TestEventHandler@182acad1, contributorCompleteEvents=[], contributorFailedEvents=[abe43406: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor, abe43406: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor], failOnComponentFailure=true}, auditTrailInformation='null', state=org.bitrepository.client.conversation.FinishedState@3bc2a6c6, checksumPillars=[]}' with exception
org.bitrepository.common.exceptions.UnableToFinishException: Unable to continue operation, contributors unavailable.
at org.bitrepository.client.conversation.IdentifyingState.completeState(IdentifyingState.java:76)
at org.bitrepository.client.conversation.GeneralConversationState.changeState(GeneralConversationState.java:147)
at org.bitrepository.client.conversation.GeneralConversationState.access$100(GeneralConversationState.java:48)
at org.bitrepository.client.conversation.GeneralConversationState$TimeoutHandler.run(GeneralConversationState.java:134)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Test success: noContributorsRespondingTest
Result: The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@29ae939c[correlationID=abe43406-f6a5-4764-a422-a858ed254051, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noContributorsRespondingTest, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default)]
13:44:30.206 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@29ae939c[correlationID=abe43406-f6a5-4764-a422-a858ed254051, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noContributorsRespondingTest, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default)]
Test starting: noContributorsRespondingTest
Description: Tests the the client handles lack of a IdentifyResponse gracefully. More concrete this means that the occurrence of a identification timeout should be handled correctly
Step: Set a 100 ms timeout for identifying contributors.
Step: Start the operation.
Stimuli: Calling getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@7f82a71f, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@3c2956a6[correlationID=9681aa9b-a098-4806-a23a-c15d0e3d0f76, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=noContributorsRespondingTest, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@7172525e[fileID=<null>(default), allFileIDs=true], checksumRequestForExistingFile=<null>(default)]
Result: Received event: 9681aa9b: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums
Step: Wait for 1 second
Result: Received event: 9681aa9b: GET_CHECKSUMS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar1, Pillar2]
Result: Received event: 9681aa9b: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor
Result: Received event: 9681aa9b: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
Result: Received event: 9681aa9b: GET_CHECKSUMS: FAILED: , Unable to continue operation, contributors unavailable.
13:44:30.571 ERROR o.b.a.g.c.IdentifyPillarsForGetChecksums - Failing conversation 'GetChecksumsConversationContext{collectionID='TwoPillarCollection', conversationID='9681aa9b-a098-4806-a23a-c15d0e3d0f76', clientID='noContributorsRespondingTest', fileID='null', contributors=[Pillar1, Pillar2], monitor=ConversationEventMonitor{, collectionID='TwoPillarCollection', conversationID='9681aa9b', operationType=GET_CHECKSUMS, fileID='null', eventHandler=org.bitrepository.client.TestEventHandler@7f82a71f, contributorCompleteEvents=[], contributorFailedEvents=[9681aa9b: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor, 9681aa9b: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor], failOnComponentFailure=true}, auditTrailInformation='null', state=org.bitrepository.client.conversation.FinishedState@1f9078af, checksumPillars=[]}' with exception
org.bitrepository.common.exceptions.UnableToFinishException: Unable to continue operation, contributors unavailable.
at org.bitrepository.client.conversation.IdentifyingState.completeState(IdentifyingState.java:76)
at org.bitrepository.client.conversation.GeneralConversationState.changeState(GeneralConversationState.java:147)
at org.bitrepository.client.conversation.GeneralConversationState.access$100(GeneralConversationState.java:48)
at org.bitrepository.client.conversation.GeneralConversationState$TimeoutHandler.run(GeneralConversationState.java:134)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Test success: noContributorsRespondingTest
Result: The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@3c2956a6[correlationID=9681aa9b-a098-4806-a23a-c15d0e3d0f76, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=noContributorsRespondingTest, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@7172525e[fileID=<null>(default), allFileIDs=true], checksumRequestForExistingFile=<null>(default)]
13:44:30.572 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@3c2956a6[correlationID=9681aa9b-a098-4806-a23a-c15d0e3d0f76, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=noContributorsRespondingTest, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@7172525e[fileID=<null>(default), allFileIDs=true], checksumRequestForExistingFile=<null>(default)]
Test starting: noContributorsRespondingTest
Description: Tests the the client handles lack of a IdentifyResponse gracefully. More concrete this means that the occurrence of a identification timeout should be handled correctly
Step: Set a 100 ms timeout for identifying contributors.
Step: Start the operation.
Stimuli: Calling getFileIDs(null, null, null, org.bitrepository.client.TestEventHandler@449f9628)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@4a6c3720[correlationID=d034ba47-23a4-490f-a160-d36f0fbe7061, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=noContributorsRespondingTest, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@2a8e93db[fileID=<null>(default), allFileIDs=true]]
Result: Received event: d034ba47: GET_FILE_IDS: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs
Step: Wait for 1 second
Result: Received event: d034ba47: GET_FILE_IDS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar1, Pillar2]
Result: Received event: d034ba47: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor
Result: Received event: d034ba47: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
Result: Received event: d034ba47: GET_FILE_IDS: FAILED: , Unable to continue operation, contributors unavailable.
13:44:30.851 ERROR o.b.a.g.c.IdentifyPillarsForGetFileIDs - Failing conversation 'GetFileIDsConversationContext{collectionID='TwoPillarCollection', conversationID='d034ba47-23a4-490f-a160-d36f0fbe7061', clientID='noContributorsRespondingTest', fileID='null', contributors=[Pillar1, Pillar2], monitor=ConversationEventMonitor{, collectionID='TwoPillarCollection', conversationID='d034ba47', operationType=GET_FILE_IDS, fileID='null', eventHandler=org.bitrepository.client.TestEventHandler@449f9628, contributorCompleteEvents=[], contributorFailedEvents=[d034ba47: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor, d034ba47: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor], failOnComponentFailure=true}, auditTrailInformation='null', state=org.bitrepository.client.conversation.FinishedState@2b4831, checksumPillars=[]}' with exception
org.bitrepository.common.exceptions.UnableToFinishException: Unable to continue operation, contributors unavailable.
at org.bitrepository.client.conversation.IdentifyingState.completeState(IdentifyingState.java:76)
at org.bitrepository.client.conversation.GeneralConversationState.changeState(GeneralConversationState.java:147)
at org.bitrepository.client.conversation.GeneralConversationState.access$100(GeneralConversationState.java:48)
at org.bitrepository.client.conversation.GeneralConversationState$TimeoutHandler.run(GeneralConversationState.java:134)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Test success: noContributorsRespondingTest
Result: The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@4a6c3720[correlationID=d034ba47-23a4-490f-a160-d36f0fbe7061, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=noContributorsRespondingTest, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@2a8e93db[fileID=<null>(default), allFileIDs=true]]
13:44:30.855 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@4a6c3720[correlationID=d034ba47-23a4-490f-a160-d36f0fbe7061, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=noContributorsRespondingTest, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@2a8e93db[fileID=<null>(default), allFileIDs=true]]
Test starting: oneContributorNotRespondingTest
Description: Verify that the client works correct without receiving identification responses from all contributors.
Added fixture: Set the a identification timeout to 100 ms.
Step: Start the operation.
Stimuli: Calling getAuditTrails(null, null, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@18c8a027[correlationID=9cf9862f-deea-476a-9026-54f086023a60, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=oneContributorNotRespondingTest, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default)]
Result: Received event: 9cf9862f: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
Step: Send a identification response from contributor1.
Result: Received event: 9cf9862f: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Step: Wait 1 second.
Result: Received event: 9cf9862f: GET_AUDIT_TRAILS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar2]
Result: Received event: 9cf9862f: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
Result: Received event: 9cf9862f: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 9cf9862f: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1], Sending request for audit trails
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@719dc111[correlationID=9cf9862f-deea-476a-9026-54f086023a60, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=oneContributorNotRespondingTest, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), contributor=Pillar1, fileID=<null>(default), minSequenceNumber=<null>(default), maxSequenceNumber=<null>(default), minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), resultAddress=<null>(default)]
Step: Verify that the client continues to the performing phase.
Step: Send a final response upload message
Result: Received event: 9cf9862f: GET_AUDIT_TRAILS: COMPONENT_COMPLETE: ContributorID Pillar1, PartialResult=false
Result: Received event: 9cf9862f: GET_AUDIT_TRAILS: FAILED: , Failed operation. Cause(s):
[9cf9862f: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor]
Test success: oneContributorNotRespondingTest
Test starting: oneContributorNotRespondingTest
Description: Verify that the client works correct without receiving identification responses from all contributors.
Added fixture: Set the a identification timeout to 100 ms.
Step: Start the operation.
Stimuli: Calling getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@7f82a71f, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@71e740c6[correlationID=d8e51b3d-c07c-405f-90e1-0b884f37dd47, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=oneContributorNotRespondingTest, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@50aa5826[fileID=<null>(default), allFileIDs=true], checksumRequestForExistingFile=<null>(default)]
Result: Received event: d8e51b3d: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums
Step: Send a identification response from contributor1.
Result: Received event: d8e51b3d: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Step: Wait 1 second.
Result: Received event: d8e51b3d: GET_CHECKSUMS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar2]
Result: Received event: d8e51b3d: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
Result: Received event: d8e51b3d: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: d8e51b3d: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar1], Sending GetChecksumsRequest's
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@5f47bd72[correlationID=d8e51b3d-c07c-405f-90e1-0b884f37dd47, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=oneContributorNotRespondingTest, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@430ef335[fileID=<null>(default), allFileIDs=true], minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), checksumRequestForExistingFile=<null>(default), resultAddress=<null>(default)]
Step: Verify that the client continues to the performing phase.
Step: Send a final response upload message
Result: Received event: d8e51b3d: GET_CHECKSUMS: COMPONENT_COMPLETE: ContributorID Pillar1, PartialResult=false
Result: Received event: d8e51b3d: GET_CHECKSUMS: FAILED: , Failed operation. Cause(s):
[d8e51b3d: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor]
Test success: oneContributorNotRespondingTest
Test starting: oneContributorNotRespondingTest
Description: Verify that the client works correct without receiving identification responses from all contributors.
Added fixture: Set the a identification timeout to 100 ms.
Step: Start the operation.
Stimuli: Calling getFileIDs(null, null, null, org.bitrepository.client.TestEventHandler@449f9628)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@6f05d5f2[correlationID=3ee73890-a465-43b6-a446-c1227cef53a3, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=oneContributorNotRespondingTest, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@3acae925[fileID=<null>(default), allFileIDs=true]]
Result: Received event: 3ee73890: GET_FILE_IDS: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs
Step: Send a identification response from contributor1.
Result: Received event: 3ee73890: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Step: Wait 1 second.
Result: Received event: 3ee73890: GET_FILE_IDS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar2]
Result: Received event: 3ee73890: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
Result: Received event: 3ee73890: GET_FILE_IDS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 3ee73890: GET_FILE_IDS: REQUEST_SENT: ContributorID [Pillar1], Sending request for get fileIDs
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@193e41a5[correlationID=3ee73890-a465-43b6-a446-c1227cef53a3, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=oneContributorNotRespondingTest, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@6b48eda[fileID=<null>(default), allFileIDs=true], minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), resultAddress=<null>(default)]
Step: Verify that the client continues to the performing phase.
Step: Send a final response upload message
Result: Received event: 3ee73890: GET_FILE_IDS: COMPONENT_COMPLETE: ContributorID Pillar1, PartialResult=false
Result: Received event: 3ee73890: GET_FILE_IDS: FAILED: , Failed operation. Cause(s):
[3ee73890: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor]
Test success: oneContributorNotRespondingTest
Test starting: operationTimeoutTest
Description: Tests the the client handles lack of final responses gracefully.
Step: Set a 100 ms operation timeout.
Step: Start the operation
Stimuli: Calling getAuditTrails(null, null, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@ca72afb[correlationID=0e6138bc-27ca-464f-851a-2bd1cb4c1207, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=operationTimeoutTest, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default)]
Result: Received event: 0e6138bc: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
Step: Send positive responses from the pillar1 and a negative response from pillar2
Result: Received event: 0e6138bc: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 0e6138bc: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE
Result: Received event: 0e6138bc: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 0e6138bc: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1], Sending request for audit trails
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@2b24fcba[correlationID=0e6138bc-27ca-464f-851a-2bd1cb4c1207, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=operationTimeoutTest, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), contributor=Pillar1, fileID=<null>(default), minSequenceNumber=<null>(default), maxSequenceNumber=<null>(default), minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), resultAddress=<null>(default)]
Step: Wait for 1 second
Result: Received event: 0e6138bc: GET_AUDIT_TRAILS: FAILED: , Failed to receive responses from all contributors before timeout(100ms). Missing contributors [Pillar1]
13:44:32.138 ERROR o.b.a.g.client.GettingAuditTrails - Failing conversation 'AuditTrailConversationContext{collectionID='TwoPillarCollection', conversationID='0e6138bc-27ca-464f-851a-2bd1cb4c1207', clientID='operationTimeoutTest', fileID='null', contributors=[Pillar1, Pillar2], monitor=ConversationEventMonitor{, collectionID='TwoPillarCollection', conversationID='0e6138bc', operationType=GET_AUDIT_TRAILS, fileID='null', eventHandler=org.bitrepository.client.TestEventHandler@182acad1, contributorCompleteEvents=[], contributorFailedEvents=[0e6138bc: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE], failOnComponentFailure=true}, auditTrailInformation='null', state=org.bitrepository.client.conversation.FinishedState@64fa1f53, checksumPillars=[]}' with exception
org.bitrepository.common.exceptions.UnableToFinishException: Failed to receive responses from all contributors before timeout(100ms). Missing contributors [Pillar1]
at org.bitrepository.client.conversation.PerformingOperationState.logStateTimeout(PerformingOperationState.java:82)
at org.bitrepository.client.conversation.GeneralConversationState$TimeoutHandler.run(GeneralConversationState.java:133)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Test success: operationTimeoutTest
Test starting: operationTimeoutTest
Description: Tests the the client handles lack of final responses gracefully.
Step: Set a 100 ms operation timeout.
Step: Start the operation
Stimuli: Calling getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@7f82a71f, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@5be17e53[correlationID=03925caa-dad1-43bc-b5a7-50402a326511, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=operationTimeoutTest, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@79a68d4e[fileID=<null>(default), allFileIDs=true], checksumRequestForExistingFile=<null>(default)]
Result: Received event: 03925caa: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums
Step: Send positive responses from the pillar1 and a negative response from pillar2
Result: Received event: 03925caa: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 03925caa: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE
Result: Received event: 03925caa: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 03925caa: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar1], Sending GetChecksumsRequest's
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@60483dcf[correlationID=03925caa-dad1-43bc-b5a7-50402a326511, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=operationTimeoutTest, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@308bd473[fileID=<null>(default), allFileIDs=true], minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), checksumRequestForExistingFile=<null>(default), resultAddress=<null>(default)]
Step: Wait for 1 second
Result: Received event: 03925caa: GET_CHECKSUMS: FAILED: , Failed to receive responses from all contributors before timeout(100ms). Missing contributors [Pillar1]
13:44:32.450 ERROR o.b.a.g.c.GettingChecksums - Failing conversation 'GetChecksumsConversationContext{collectionID='TwoPillarCollection', conversationID='03925caa-dad1-43bc-b5a7-50402a326511', clientID='operationTimeoutTest', fileID='null', contributors=[Pillar1, Pillar2], monitor=ConversationEventMonitor{, collectionID='TwoPillarCollection', conversationID='03925caa', operationType=GET_CHECKSUMS, fileID='null', eventHandler=org.bitrepository.client.TestEventHandler@7f82a71f, contributorCompleteEvents=[], contributorFailedEvents=[03925caa: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE], failOnComponentFailure=true}, auditTrailInformation='null', state=org.bitrepository.client.conversation.FinishedState@50d9dfa2, checksumPillars=[]}' with exception
org.bitrepository.common.exceptions.UnableToFinishException: Failed to receive responses from all contributors before timeout(100ms). Missing contributors [Pillar1]
at org.bitrepository.client.conversation.PerformingOperationState.logStateTimeout(PerformingOperationState.java:82)
at org.bitrepository.client.conversation.GeneralConversationState$TimeoutHandler.run(GeneralConversationState.java:133)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Test success: operationTimeoutTest
Test starting: operationTimeoutTest
Description: Tests the the client handles lack of final responses gracefully.
Step: Set a 100 ms operation timeout.
Step: Start the operation
Stimuli: Calling getFileIDs(null, null, null, org.bitrepository.client.TestEventHandler@449f9628)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@1f3b8bfe[correlationID=f06ff193-6e7d-432f-8a65-d29e3c852f11, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=operationTimeoutTest, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@1b596e21[fileID=<null>(default), allFileIDs=true]]
Result: Received event: f06ff193: GET_FILE_IDS: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs
Step: Send positive responses from the pillar1 and a negative response from pillar2
Result: Received event: f06ff193: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: f06ff193: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE
Result: Received event: f06ff193: GET_FILE_IDS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: f06ff193: GET_FILE_IDS: REQUEST_SENT: ContributorID [Pillar1], Sending request for get fileIDs
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@61b83fef[correlationID=f06ff193-6e7d-432f-8a65-d29e3c852f11, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=operationTimeoutTest, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@229f3c5d[fileID=<null>(default), allFileIDs=true], minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), resultAddress=<null>(default)]
Step: Wait for 1 second
Result: Received event: f06ff193: GET_FILE_IDS: FAILED: , Failed to receive responses from all contributors before timeout(100ms). Missing contributors [Pillar1]
13:44:32.753 ERROR o.b.a.g.conversation.GettingFileIDs - Failing conversation 'GetFileIDsConversationContext{collectionID='TwoPillarCollection', conversationID='f06ff193-6e7d-432f-8a65-d29e3c852f11', clientID='operationTimeoutTest', fileID='null', contributors=[Pillar1, Pillar2], monitor=ConversationEventMonitor{, collectionID='TwoPillarCollection', conversationID='f06ff193', operationType=GET_FILE_IDS, fileID='null', eventHandler=org.bitrepository.client.TestEventHandler@449f9628, contributorCompleteEvents=[], contributorFailedEvents=[f06ff193: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE], failOnComponentFailure=true}, auditTrailInformation='null', state=org.bitrepository.client.conversation.FinishedState@3b819f75, checksumPillars=[]}' with exception
org.bitrepository.common.exceptions.UnableToFinishException: Failed to receive responses from all contributors before timeout(100ms). Missing contributors [Pillar1]
at org.bitrepository.client.conversation.PerformingOperationState.logStateTimeout(PerformingOperationState.java:82)
at org.bitrepository.client.conversation.GeneralConversationState$TimeoutHandler.run(GeneralConversationState.java:133)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Test success: operationTimeoutTest
Starting testcase DeleteFileClientComponentTest
Test starting: deleteClientIdentificationTimeout
Description: Tests the handling of a failed identification for the DeleteClient
Step: Initialise the number of pillars and the DeleteClient. Sets the identification timeout to 1 sec.
Step: Request a file to be deleted on the default pillar.
Stimuli: Calling deleteFile(default-test-file.txt, Pillar1, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@28908c04[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2b9132ad[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7adc8212[checksumType=SHA1, checksumSalt=<null>(default), otherChecksumType=<null>(default)], eventHandler, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@4ea4e0f3[correlationID=85271936-6803-4222-b5bb-33e899db2ee2, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientIdentificationTimeout, to=Pillar1, version=31, minVersion=24, auditTrailInformation=<null>(default), fileID=default-test-file.txt]
Result: Received event: 85271936: DELETE_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for delete file
Step: Do not respond. Just await the timeout.
Result: Received event: 85271936: DELETE_FILE for file default-test-file.txt: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar1]
Result: Received event: 85271936: DELETE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor
Result: Received event: 85271936: DELETE_FILE for file default-test-file.txt: FAILED: , Unable to continue operation, contributors unavailable.
13:44:33.961 ERROR o.b.m.d.c.IdentifyPillarsForDeleteFile - Failing conversation 'DeleteFileConversationContext{collectionID='TwoPillarCollection', conversationID='85271936-6803-4222-b5bb-33e899db2ee2', clientID='deleteClientIdentificationTimeout', fileID='default-test-file.txt', contributors=[Pillar1], monitor=ConversationEventMonitor{, collectionID='TwoPillarCollection', conversationID='85271936', operationType=DELETE_FILE, fileID='default-test-file.txt', eventHandler=org.bitrepository.client.TestEventHandler@19611481, contributorCompleteEvents=[], contributorFailedEvents=[85271936: DELETE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor], failOnComponentFailure=true}, auditTrailInformation='null', state=org.bitrepository.client.conversation.FinishedState@2dd58079, checksumPillars=[]}' with exception
org.bitrepository.common.exceptions.UnableToFinishException: Unable to continue operation, contributors unavailable.
at org.bitrepository.client.conversation.IdentifyingState.completeState(IdentifyingState.java:76)
at org.bitrepository.client.conversation.GeneralConversationState.changeState(GeneralConversationState.java:147)
at org.bitrepository.client.conversation.GeneralConversationState.access$100(GeneralConversationState.java:48)
at org.bitrepository.client.conversation.GeneralConversationState$TimeoutHandler.run(GeneralConversationState.java:134)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Test success: deleteClientIdentificationTimeout
Test starting: deleteClientOperationTimeout
Description: Tests the handling of a failed operation for the DeleteClient
Step: Initialise the number of pillars and the DeleteClient. Sets the operation timeout to 100 ms.
Step: Request a file to be deleted on the default pillar.
Stimuli: Calling deleteFile(default-test-file.txt, Pillar1, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@15200332[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1d123972[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@4567dcbc[checksumType=SHA1, checksumSalt=<null>(default), otherChecksumType=<null>(default)], eventHandler, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@7b3d759f[correlationID=cfe15b85-9a20-4248-9be5-b65f2738511f, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientOperationTimeout, to=Pillar1, version=31, minVersion=24, auditTrailInformation=<null>(default), fileID=default-test-file.txt]
Result: Received event: cfe15b85: DELETE_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for delete file
Step: Make response for the pillar.
Result: Received event: cfe15b85: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: cfe15b85: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: cfe15b85: DELETE_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for deleting file
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.DeleteFileRequest@62c4ad40[correlationID=cfe15b85-9a20-4248-9be5-b65f2738511f, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientOperationTimeout, to=Pillar1, version=31, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@15200332[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1d123972[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@4567dcbc[checksumType=SHA1, checksumSalt=<null>(default), otherChecksumType=<null>(default)]]
Step: Validate the steps of the DeleteClient by going through the events.
Step: Do not respond. Just await the timeout.
Result: Received event: cfe15b85: DELETE_FILE for file default-test-file.txt: FAILED: , Failed to receive responses from all contributors before timeout(100ms). Missing contributors [Pillar1]
13:44:34.258 ERROR o.b.m.d.conversation.DeletingFile - Failing conversation 'DeleteFileConversationContext{collectionID='TwoPillarCollection', conversationID='cfe15b85-9a20-4248-9be5-b65f2738511f', clientID='deleteClientOperationTimeout', fileID='default-test-file.txt', contributors=[Pillar1], monitor=ConversationEventMonitor{, collectionID='TwoPillarCollection', conversationID='cfe15b85', operationType=DELETE_FILE, fileID='default-test-file.txt', eventHandler=org.bitrepository.client.TestEventHandler@33ef6eae, contributorCompleteEvents=[], contributorFailedEvents=[], failOnComponentFailure=true}, auditTrailInformation='null', state=org.bitrepository.client.conversation.FinishedState@4222591, checksumPillars=[]}' with exception
org.bitrepository.common.exceptions.UnableToFinishException: Failed to receive responses from all contributors before timeout(100ms). Missing contributors [Pillar1]
at org.bitrepository.client.conversation.PerformingOperationState.logStateTimeout(PerformingOperationState.java:82)
at org.bitrepository.client.conversation.GeneralConversationState$TimeoutHandler.run(GeneralConversationState.java:133)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Test success: deleteClientOperationTimeout
Test starting: deleteClientOtherPillarFailedDuringIdentification
Description: Tests the handling of a identification failure for a pillar for the DeleteClient.
Step: Request a file to be deleted on the pillar1.
Stimuli: Calling deleteFile(default-test-file.txt, Pillar1, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@25c4d2a0[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@43a304ee[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2022-02-15T13:44:34.487+01:00], null, eventHandler, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@7fb57b7c[correlationID=ab07be3a-050a-4b88-b0bf-5997a9e290fb, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientOtherPillarFailedDuringIdentification, to=Pillar1, version=31, minVersion=24, auditTrailInformation=<null>(default), fileID=default-test-file.txt]
Result: Received event: ab07be3a: DELETE_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for delete file
Step: Send a failed response from pillar2.
Step: Send a ok response from pillar1.
Result: Received event: ab07be3a: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: ab07be3a: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: ab07be3a: DELETE_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for deleting file
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.DeleteFileRequest@35cf5d9[correlationID=ab07be3a-050a-4b88-b0bf-5997a9e290fb, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientOtherPillarFailedDuringIdentification, to=Pillar1, version=31, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@25c4d2a0[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@43a304ee[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2022-02-15T13:44:34.487+01:00], checksumRequestForExistingFile=<null>(default)]
Step: Send a final response message from pillar 1 to the DeleteClient.
Result: Received event: ab07be3a: DELETE_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, DeleteFileResult=null
Result: Received event: ab07be3a: DELETE_FILE for file default-test-file.txt: COMPLETE:
Test success: deleteClientOtherPillarFailedDuringIdentification
Test starting: deleteClientPillarFailedDuringPerform
Description: Tests the handling of a operation failure for the DeleteClient.
Step: Initialise the number of pillars to one
Step: Request a file to be deleted on the default pillar.
Stimuli: Calling deleteFile(default-test-file.txt, Pillar1, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@3d872a12[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7efaa137[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@e08853d[checksumType=SHA1, checksumSalt=<null>(default), otherChecksumType=<null>(default)], eventHandler, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@3828f303[correlationID=bcb4cb5d-2e00-4a53-a516-c45c8a9f8f62, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientPillarFailedDuringPerform, to=Pillar1, version=31, minVersion=24, auditTrailInformation=<null>(default), fileID=default-test-file.txt]
Result: Received event: bcb4cb5d: DELETE_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for delete file
Step: Make response for the pillar.
Result: Received event: bcb4cb5d: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: bcb4cb5d: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: bcb4cb5d: DELETE_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for deleting file
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.DeleteFileRequest@1723640f[correlationID=bcb4cb5d-2e00-4a53-a516-c45c8a9f8f62, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientPillarFailedDuringPerform, to=Pillar1, version=31, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@3d872a12[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7efaa137[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@e08853d[checksumType=SHA1, checksumSalt=<null>(default), otherChecksumType=<null>(default)]]
Step: Validate the steps of the DeleteClient by going through the events.
Step: Send a failed response message to the DeleteClient.
Result: Received event: bcb4cb5d: DELETE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE, Verifying that a failure can be understood!
Result: Received event: bcb4cb5d: DELETE_FILE for file default-test-file.txt: FAILED: , Failed operation. Cause(s):
[bcb4cb5d: DELETE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE, Verifying that a failure can be understood!]
Test success: deleteClientPillarFailedDuringPerform
Test starting: deleteClientSpecifiedPillarFailedDuringIdentification
Description: Tests the handling of a identification failure for a pillar for the DeleteClient.
Step: Request a file to be deleted on the pillar1.
Stimuli: Calling deleteFile(default-test-file.txt, Pillar1, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@7200ac94[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@5cf4023d[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2022-02-15T13:44:35.907+01:00], null, eventHandler, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@4306191[correlationID=75131b42-ae7b-47d8-9bac-a3e699844bba, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientSpecifiedPillarFailedDuringIdentification, to=Pillar1, version=31, minVersion=24, auditTrailInformation=<null>(default), fileID=default-test-file.txt]
Result: Received event: 75131b42: DELETE_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for delete file
Step: Send a failed response from pillar1.
Result: Received event: 75131b42: DELETE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: IDENTIFICATION_NEGATIVE
Result: Received event: 75131b42: DELETE_FILE for file default-test-file.txt: FAILED: , Can not continue with delete operation, as Pillar1 is unable to perform the deletion.
13:44:35.910 ERROR o.b.m.d.c.IdentifyPillarsForDeleteFile - Failing conversation 'DeleteFileConversationContext{collectionID='TwoPillarCollection', conversationID='75131b42-ae7b-47d8-9bac-a3e699844bba', clientID='deleteClientSpecifiedPillarFailedDuringIdentification', fileID='default-test-file.txt', contributors=[Pillar1], monitor=ConversationEventMonitor{, collectionID='TwoPillarCollection', conversationID='75131b42', operationType=DELETE_FILE, fileID='default-test-file.txt', eventHandler=org.bitrepository.client.TestEventHandler@649573d0, contributorCompleteEvents=[], contributorFailedEvents=[75131b42: DELETE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: IDENTIFICATION_NEGATIVE], failOnComponentFailure=true}, auditTrailInformation='null', state=org.bitrepository.client.conversation.FinishedState@138617da, checksumPillars=[]}' with exception
org.bitrepository.common.exceptions.UnableToFinishException: Can not continue with delete operation, as Pillar1 is unable to perform the deletion.
at org.bitrepository.modify.deletefile.conversation.IdentifyPillarsForDeleteFile.handleFailureResponse(IdentifyPillarsForDeleteFile.java:71)
at org.bitrepository.client.conversation.IdentifyingState.processMessage(IdentifyingState.java:60)
at org.bitrepository.client.conversation.GeneralConversationState.handleMessage(GeneralConversationState.java:110)
at org.bitrepository.client.conversation.StateBasedConversation.onMessage(StateBasedConversation.java:53)
at org.bitrepository.client.conversation.mediator.CollectionBasedConversationMediator.onMessage(CollectionBasedConversationMediator.java:136)
at org.bitrepository.protocol.messagebus.SimpleMessageBus.lambda$sendMessage$0(SimpleMessageBus.java:73)
at java.lang.Iterable.forEach(Iterable.java:75)
at org.bitrepository.protocol.messagebus.SimpleMessageBus.sendMessage(SimpleMessageBus.java:73)
at org.bitrepository.modify.deletefile.DeleteFileClientComponentTest.deleteClientSpecifiedPillarFailedDuringIdentification(DeleteFileClientComponentTest.java:357)
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.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:134)
at org.testng.internal.TestInvoker.invokeMethod(TestInvoker.java:597)
at org.testng.internal.TestInvoker.invokeTestMethod(TestInvoker.java:173)
at org.testng.internal.MethodRunner.runInSequence(MethodRunner.java:46)
at org.testng.internal.TestInvoker$MethodInvocationAgent.invoke(TestInvoker.java:816)
at org.testng.internal.TestInvoker.invokeTestMethods(TestInvoker.java:146)
at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:146)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:128)
at java.util.ArrayList.forEach(ArrayList.java:1249)
at org.testng.TestRunner.privateRun(TestRunner.java:766)
at org.testng.TestRunner.run(TestRunner.java:587)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:384)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:378)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:337)
at org.testng.SuiteRunner.run(SuiteRunner.java:286)
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:53)
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:96)
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1187)
at org.testng.TestNG.runSuitesLocally(TestNG.java:1109)
at org.testng.TestNG.runSuites(TestNG.java:1039)
at org.testng.TestNG.run(TestNG.java:1007)
at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:135)
at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:193)
at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:94)
at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:146)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:377)
at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:138)
at org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:465)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:451)
Test success: deleteClientSpecifiedPillarFailedDuringIdentification
Test starting: deleteClientTester
Description: Tests the DeleteClient. Makes a whole conversation for the delete client for a 'good' scenario.
Step: Initialise the number of pillars to one
Step: Request a file to be deleted on all pillars (which means only the default pillar).
Stimuli: Calling deleteFile(default-test-file.txt, Pillar1, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@11c7756f[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@35798cd0[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2fc70622[checksumType=SHA1, checksumSalt=<null>(default), otherChecksumType=<null>(default)], eventHandler, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@1e2d4645[correlationID=53f50307-28f1-4caa-be51-eddfbe08c5d5, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientTester, to=Pillar1, version=31, minVersion=24, auditTrailInformation=<null>(default), fileID=default-test-file.txt]
Result: Received event: 53f50307: DELETE_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for delete file
Step: Make response for the pillar.
Result: Received event: 53f50307: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 53f50307: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 53f50307: DELETE_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for deleting file
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.DeleteFileRequest@4d8d21a3[correlationID=53f50307-28f1-4caa-be51-eddfbe08c5d5, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientTester, to=Pillar1, version=31, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@11c7756f[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@35798cd0[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2fc70622[checksumType=SHA1, checksumSalt=<null>(default), otherChecksumType=<null>(default)]]
Step: Validate the steps of the DeleteClient by going through the events.
Step: The pillar sends a progress response to the DeleteClient.
Result: Received event: 53f50307: DELETE_FILE for file default-test-file.txt: PROGRESS: ContributorID Pillar1, First test progress response message
Step: Send a final response message to the DeleteClient.
Result: Received event: 53f50307: DELETE_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, DeleteFileResult=null
Result: Received event: 53f50307: DELETE_FILE for file default-test-file.txt: COMPLETE:
Test success: deleteClientTester
Test starting: deleteOnChecksumPillar
Description: Verify that the DeleteClient works correctly when a checksum pillar is present.
Step: Request a file to be deleted on the pillar1.
Stimuli: Calling deleteFile(default-test-file.txt, Pillar1, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@4967d14c[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@38aa5ffe[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2022-02-15T13:44:36.321+01:00], null, eventHandler, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@551f38b1[correlationID=ad6a695a-2ac8-4108-816d-4f1475ecce5b, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteOnChecksumPillar, to=Pillar1, version=31, minVersion=24, auditTrailInformation=<null>(default), fileID=default-test-file.txt]
Result: Received event: ad6a695a: DELETE_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for delete file
Step: Send an identification response from pillar2.
Step: Send a response from pillar1 with PillarChecksumSpec element set, indicating that this is a checksum pillar.
Result: Received event: ad6a695a: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: ad6a695a: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: ad6a695a: DELETE_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for deleting file
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.DeleteFileRequest@283fe454[correlationID=ad6a695a-2ac8-4108-816d-4f1475ecce5b, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteOnChecksumPillar, to=Pillar1, version=31, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@4967d14c[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@38aa5ffe[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2022-02-15T13:44:36.321+01:00], checksumRequestForExistingFile=<null>(default)]
Test success: deleteOnChecksumPillar
Test starting: deleteOnChecksumPillarWithDefaultReturnChecksumType
Description: Verify that the DeleteClient works correctly when a return checksum of the default typeis requested.
Step: Request a file to be deleted on the pillar1. The call should include a request for a check sum of the default type
Stimuli: Calling deleteFile(default-test-file.txt, Pillar1, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@70e3f664[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@38b2a4e7[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2022-02-15T13:44:38.518+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@cc65ea1[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], eventHandler, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@5a2661dc[correlationID=c5a1ae16-2596-42b4-a4ab-e17bb5be281e, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteOnChecksumPillarWithDefaultReturnChecksumType, to=Pillar1, version=31, minVersion=24, auditTrailInformation=<null>(default), fileID=default-test-file.txt]
Result: Received event: c5a1ae16: DELETE_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for delete file
Step: Send a response from pillar1 with PillarChecksumSpec element set, indicating that this is a checksum pillar.
Result: Received event: c5a1ae16: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: c5a1ae16: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: c5a1ae16: DELETE_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for deleting file
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.DeleteFileRequest@26ac8501[correlationID=c5a1ae16-2596-42b4-a4ab-e17bb5be281e, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteOnChecksumPillarWithDefaultReturnChecksumType, to=Pillar1, version=31, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@70e3f664[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@38b2a4e7[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2022-02-15T13:44:38.518+01:00], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@cc65ea1[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)]]
Test success: deleteOnChecksumPillarWithDefaultReturnChecksumType
Test starting: deleteOnChecksumPillarWithSaltedReturnChecksumType
Description: Verify that the DeleteClient works correctly when a return checksum with a salt is requested.
Step: Request a file to be deleted on the pillar1. The call should include a request for a salted check sum
Stimuli: Calling deleteFile(default-test-file.txt, Pillar1, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@32002a21[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@b13c600[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2022-02-15T13:44:38.713+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7ae5231c[checksumType=MD5, checksumSalt={-86}, otherChecksumType=<null>(default)], eventHandler, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@642bfa5e[correlationID=01c4127c-744e-4abc-a8d3-454f43324ab7, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteOnChecksumPillarWithSaltedReturnChecksumType, to=Pillar1, version=31, minVersion=24, auditTrailInformation=<null>(default), fileID=default-test-file.txt]
Result: Received event: 01c4127c: DELETE_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for delete file
Step: Send a response from pillar1 with PillarChecksumSpec element set, indicating that this is a checksum pillar.
Result: Received event: 01c4127c: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 01c4127c: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 01c4127c: DELETE_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for deleting file
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.DeleteFileRequest@42ff6af7[correlationID=01c4127c-744e-4abc-a8d3-454f43324ab7, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteOnChecksumPillarWithSaltedReturnChecksumType, to=Pillar1, version=31, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@32002a21[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@b13c600[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2022-02-15T13:44:38.713+01:00], checksumRequestForExistingFile=<null>(default)]
Test success: deleteOnChecksumPillarWithSaltedReturnChecksumType
Test starting: fileAlreadyDeletedFromPillar
Description: Test that a delete on a pillar completes successfully when the file is missing (has already been deleted). This is a test of the Idempotent behaviour of the delete client
Step: Request a file to be deleted on pillar1.
Stimuli: Calling deleteFile(default-test-file.txt, Pillar1, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@5426c89f[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@4e8765dd[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2022-02-15T13:44:38.920+01:00], null, eventHandler, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@7eeb8139[correlationID=36ed5553-7bc3-48c9-af63-e1e5d2cf2008, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=fileAlreadyDeletedFromPillar, to=Pillar1, version=31, minVersion=24, auditTrailInformation=<null>(default), fileID=default-test-file.txt]
Result: Received event: 36ed5553: DELETE_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for delete file
Step: Send a identify response from Pillar1 with a missing file response.
Result: Received event: 36ed5553: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 36ed5553: DELETE_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, DeleteFileResult=null
Result: Received event: 36ed5553: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: []
Result: Received event: 36ed5553: DELETE_FILE for file default-test-file.txt: COMPLETE:
Step: The client should then continue to the performing phase and finish immediately as the pillar has already had the file removed apparently .
Step: Send a identify response from Pillar2
Test success: fileAlreadyDeletedFromPillar
Test starting: verifyDeleteClientFromFactory
Description: Testing the initialization through the ModifyComponentFactory.
Step: Use the ModifyComponentFactory to instantiate a PutFileClient.
Test success: verifyDeleteClientFromFactory
Starting testcase DeleteFileCmdTest
Test starting: checksumArgumentNonSaltAlgorithmWitoutSaltTest
Description: Test MD5 checksum without salt -> no failure
Test success: checksumArgumentNonSaltAlgorithmWitoutSaltTest
Test starting: checksumArgumentSaltAlgorithmWithSaltTest
Description: Test HMAC_SHA256 checksum with salt -> No failure
Test success: checksumArgumentSaltAlgorithmWithSaltTest
Test starting: defaultSuccessScenarioTest
Description: Tests simplest arguments for running the CmdLineClient
Test success: defaultSuccessScenarioTest
Test starting: missingCollectionArgumentTest
Description: Tests the scenario, where the collection arguments is missing.
Takes the following arguments:
-s The path to the directory with the settings files for the client
-k The path to the file containing the private key.
-v Makes the client more verbose
-c The id for the collection to perform the operation on.
-i The id for the file to perform the operation on.
-p [OPTIONAL] The id of the pillar where the operation should be performed. If undefined the operation is performed on all pillars.
-C [OPTIONAL] The checksum of the file to be deleted.
-R [OPTIONAL] The algorithm of checksum to request in the response from the pillars.
-S [OPTIONAL] The salt of checksum to request in the response. Requires the ChecksumType argument.
Missing argument: Missing required option: c
Test success: missingCollectionArgumentTest
Test starting: missingFileIDArgumentTest
Description: Tests the scenario, where no arguments for file id argument is given.
Takes the following arguments:
-s The path to the directory with the settings files for the client
-k The path to the file containing the private key.
-v Makes the client more verbose
-c The id for the collection to perform the operation on.
-i The id for the file to perform the operation on.
-p [OPTIONAL] The id of the pillar where the operation should be performed. If undefined the operation is performed on all pillars.
-C [OPTIONAL] The checksum of the file to be deleted.
-R [OPTIONAL] The algorithm of checksum to request in the response from the pillars.
-S [OPTIONAL] The salt of checksum to request in the response. Requires the ChecksumType argument.
Missing argument: Missing required option: i
Test success: missingFileIDArgumentTest
Test starting: missingPillarArgumentTest
Description: Tests the different scenarios, with the pillar argument.
Invalid argument: The pillar argument -p must defined for the delete operation, only single pillar deletes are allowed
Test success: missingPillarArgumentTest
Test starting: unknownPillarArgumentTest
Step: Testing against a non-existing pillar id
Invalid argument: Random1644929083040pillar is not a valid pillar for collection TwoPillarCollection
The collection contains the following pillars: [Pillar1, Pillar2]
Test success: unknownPillarArgumentTest
Test starting: getChecksumsDeliveredAtUrl
Description: Tests the delivery of checksums from all pillars at a given URL.
Step: Ensure the delivery file isn't already present on the http server
Step: Request the delivery of the checksum of a file from all pillars.
Stimuli: Calling getChecksums(null, default-test-file.txt, null, file:../bitrepository-core/src/test/resources/test-files//TEST-CHECKSUM-DELIVERY.xml, org.bitrepository.client.TestEventHandler@7c060680, TEST-AUDIT)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@4e80ba38[correlationID=3f30f805-372a-42a2-9ab8-9e6bd6d8679c, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=getChecksumsDeliveredAtUrl, to=<null>(default), version=31, minVersion=24, auditTrailInformation=TEST-AUDIT, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@8d92b1e[fileID=default-test-file.txt, allFileIDs=<null>(default)], checksumRequestForExistingFile=<null>(default)]
Result: Received event: 3f30f805: GET_CHECKSUMS for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums
Step: The pillar sends a response to the identify message.
Result: Received event: 3f30f805: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 3f30f805: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 3f30f805: GET_CHECKSUMS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2, Pillar1]
Result: Received event: 3f30f805: GET_CHECKSUMS for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending GetChecksumsRequest's
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@749bbb99[correlationID=3f30f805-372a-42a2-9ab8-9e6bd6d8679c, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=getChecksumsDeliveredAtUrl, to=<null>(default), version=31, minVersion=24, auditTrailInformation=TEST-AUDIT, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@355bffcf[fileID=default-test-file.txt, allFileIDs=<null>(default)], minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), checksumRequestForExistingFile=<null>(default), resultAddress=file:../bitrepository-core/src/test/resources/test-files//TEST-CHECKSUM-DELIVERY.xml-Pillar1]
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@3b44d50b[correlationID=3f30f805-372a-42a2-9ab8-9e6bd6d8679c, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=getChecksumsDeliveredAtUrl, to=<null>(default), version=31, minVersion=24, auditTrailInformation=TEST-AUDIT, pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@84fb597[fileID=default-test-file.txt, allFileIDs=<null>(default)], minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), checksumRequestForExistingFile=<null>(default), resultAddress=file:../bitrepository-core/src/test/resources/test-files//TEST-CHECKSUM-DELIVERY.xml-Pillar2]
Step: Sends a final response from each pillar
Result: Received event: 3f30f805: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, NumberOfChecksums=0, PartialResult=false
Result: Received event: 3f30f805: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2, NumberOfChecksums=0, PartialResult=false
Result: Received event: 3f30f805: GET_CHECKSUMS for file default-test-file.txt: COMPLETE:
Test success: getChecksumsDeliveredAtUrl
Result: The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.GetChecksumsRequest@3b44d50b[correlationID=3f30f805-372a-42a2-9ab8-9e6bd6d8679c, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=getChecksumsDeliveredAtUrl, to=<null>(default), version=31, minVersion=24, auditTrailInformation=TEST-AUDIT, pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@84fb597[fileID=default-test-file.txt, allFileIDs=<null>(default)], minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), checksumRequestForExistingFile=<null>(default), resultAddress=file:../bitrepository-core/src/test/resources/test-files//TEST-CHECKSUM-DELIVERY.xml-Pillar2]
13:44:43.379 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.GetChecksumsRequest@3b44d50b[correlationID=3f30f805-372a-42a2-9ab8-9e6bd6d8679c, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=getChecksumsDeliveredAtUrl, to=<null>(default), version=31, minVersion=24, auditTrailInformation=TEST-AUDIT, pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@84fb597[fileID=default-test-file.txt, allFileIDs=<null>(default)], minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), checksumRequestForExistingFile=<null>(default), resultAddress=file:../bitrepository-core/src/test/resources/test-files//TEST-CHECKSUM-DELIVERY.xml-Pillar2]
Test starting: getChecksumsFromOtherCollection
Description: Tests the getChecksums client will correctly try to get from a second collection if required
Added fixture: Configure collection1 to contain both pillars and collection 2 to only contain pillar2
Step: Request the putting of a file through the PutClient for collection2
Stimuli: Calling getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@5cfbbefb, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@25cff0[correlationID=fcfe36ee-93b1-4146-9826-ba9488d05ca2, collectionID=SinglePillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=getChecksumsFromOtherCollection, to=Pillar2, version=31, minVersion=24, auditTrailInformation=<null>(default), fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@61e1ecd5[fileID=<null>(default), allFileIDs=true], checksumRequestForExistingFile=<null>(default)]
Result: Received event: fcfe36ee: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums
Step: Send an identification response from pillar2.
Result: Received event: fcfe36ee: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: fcfe36ee: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: fcfe36ee: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar2], Sending GetChecksumsRequest's
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@45adac0e[correlationID=fcfe36ee-93b1-4146-9826-ba9488d05ca2, collectionID=SinglePillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=getChecksumsFromOtherCollection, to=Pillar2, version=31, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@6bd9a104[fileID=<null>(default), allFileIDs=true], minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), checksumRequestForExistingFile=<null>(default), resultAddress=<null>(default)]
Step: Send a complete event from the pillar
Result: Received event: fcfe36ee: GET_CHECKSUMS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false
Result: Received event: fcfe36ee: GET_CHECKSUMS: COMPLETE:
Test success: getChecksumsFromOtherCollection
Test starting: getChecksumsFromSinglePillar
Description: Tests that the client can retrieve checksums from a single pillar.
Step: Request the delivery of the checksum of a file from pillar1.
Stimuli: Calling getChecksums([ContributorQuery{componentID='Pillar1, minTimestamp=null, maxTimestamp=null, maxNumberOfResults=null}], default-test-file.txt, org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@5dd5142[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], null, org.bitrepository.client.TestEventHandler@3c401155, TEST-AUDIT)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@80f1151[correlationID=7f4256f7-292a-41a5-92cc-cbfbf5f011cd, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=getChecksumsFromSinglePillar, to=Pillar1, version=31, minVersion=24, auditTrailInformation=TEST-AUDIT, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@30f139f[fileID=default-test-file.txt, allFileIDs=<null>(default)], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@5dd5142[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)]]
Result: Received event: 7f4256f7: GET_CHECKSUMS for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums
Step: Sends a response from pillar2.
Step: Sends a response from pillar1.
Result: Received event: 7f4256f7: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 7f4256f7: GET_CHECKSUMS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 7f4256f7: GET_CHECKSUMS for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending GetChecksumsRequest's
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@50416b87[correlationID=7f4256f7-292a-41a5-92cc-cbfbf5f011cd, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=getChecksumsFromSinglePillar, to=Pillar1, version=31, minVersion=24, auditTrailInformation=TEST-AUDIT, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@20347d47[fileID=default-test-file.txt, allFileIDs=<null>(default)], minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@5dd5142[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultAddress=<null>(default)]
Step: Send a GetChecksumsFinalResponse to the client from pillar1
Result: Received event: 7f4256f7: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, NumberOfChecksums=0, PartialResult=false
Result: Received event: 7f4256f7: GET_CHECKSUMS for file default-test-file.txt: COMPLETE:
Test success: getChecksumsFromSinglePillar
Test starting: testNoSuchFile
Description: Testing how a request for a non-existing file is handled.
Step: Setting up variables and such.
Step: Request the delivery of the checksum of a file from the pillar(s). A callback listener should be supplied.
Stimuli: Calling getChecksums(null, default-test-file.txt, null, null, org.bitrepository.client.TestEventHandler@104d07a8, TEST-AUDIT)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@6fa53b0d[correlationID=6dee6928-183d-4afa-b8ca-1d81632fbcb4, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=testNoSuchFile, to=Pillar1, version=31, minVersion=24, auditTrailInformation=TEST-AUDIT, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@4b16145[fileID=default-test-file.txt, allFileIDs=<null>(default)], checksumRequestForExistingFile=<null>(default)]
Result: Received event: 6dee6928: GET_CHECKSUMS for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums
Step: The pillar sends a response to the identify message.
Result: Received event: 6dee6928: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 6dee6928: GET_CHECKSUMS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 6dee6928: GET_CHECKSUMS for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending GetChecksumsRequest's
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@3b1bf4bf[correlationID=6dee6928-183d-4afa-b8ca-1d81632fbcb4, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=testNoSuchFile, to=Pillar1, version=31, minVersion=24, auditTrailInformation=TEST-AUDIT, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@7d20cd82[fileID=default-test-file.txt, allFileIDs=<null>(default)], minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), checksumRequestForExistingFile=<null>(default), resultAddress=<null>(default)]
Step: Send a error that the file cannot be found.
Result: Received event: 6dee6928: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FILE_NOT_FOUND_FAILURE, No such file.
Result: Received event: 6dee6928: GET_CHECKSUMS for file default-test-file.txt: FAILED: , Failed operation. Cause(s):
[6dee6928: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FILE_NOT_FOUND_FAILURE, No such file.]
Test success: testNoSuchFile
Test starting: testPaging
Description: Tests the GetChecksums client correctly handles functionality for limiting results, either by timestamp or result count.
Step: Request checksums from with MinTimestamp, MaxTimestamp, MaxNumberOfResults set for both pillars .
Stimuli: Calling getChecksums([ContributorQuery{componentID='Pillar1, minTimestamp=Tue Feb 15 13:44:44 CET 2022, maxTimestamp=Tue Feb 15 13:44:45 CET 2022, maxNumberOfResults=1}, ContributorQuery{componentID='Pillar2, minTimestamp=Tue Feb 15 13:44:45 CET 2022, maxTimestamp=Tue Feb 15 13:44:45 CET 2022, maxNumberOfResults=2}], null, null, null, org.bitrepository.client.TestEventHandler@7f82a71f, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@551a24f[correlationID=8b4eb8b0-192a-43d4-ae22-a40fc4ee7923, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=testPaging, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@730b8793[fileID=<null>(default), allFileIDs=true], checksumRequestForExistingFile=<null>(default)]
Result: Received event: 8b4eb8b0: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums
Step: Send a IdentifyPillarsForGetChecksumsResponse from both pillars.
Result: Received event: 8b4eb8b0: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 8b4eb8b0: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 8b4eb8b0: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2, Pillar1]
Result: Received event: 8b4eb8b0: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending GetChecksumsRequest's
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@6430c591[correlationID=8b4eb8b0-192a-43d4-ae22-a40fc4ee7923, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=testPaging, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@4b28e19b[fileID=<null>(default), allFileIDs=true], minTimestamp=2022-02-15T13:44:44.173+01:00, maxTimestamp=2022-02-15T13:44:45.073+01:00, maxNumberOfResults=1, checksumRequestForExistingFile=<null>(default), resultAddress=<null>(default)]
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@61ecfae6[correlationID=8b4eb8b0-192a-43d4-ae22-a40fc4ee7923, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=testPaging, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@57ad1859[fileID=<null>(default), allFileIDs=true], minTimestamp=2022-02-15T13:44:45.073+01:00, maxTimestamp=2022-02-15T13:44:45.173+01:00, maxNumberOfResults=2, checksumRequestForExistingFile=<null>(default), resultAddress=<null>(default)]
Test success: testPaging
Test starting: verifyGetChecksumsClientFromFactory
Test success: verifyGetChecksumsClientFromFactory
Test starting: getFileIDsDeliveredAtUrl
Description: Tests the delivery of fileIDs from a pillar at a given URL.
Step: Initialise the variables for this test.
Step: Request the delivery of the file ids of a file from the pillar(s). A callback listener should be supplied.
Stimuli: Calling getFileIDs(null, default-test-file.txt, file:../bitrepository-core/src/test/resources/test-files//TEST-FILE-IDS-DELIVERY.xml, org.bitrepository.client.TestEventHandler@449f9628)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@504081be[correlationID=e94f1a68-16ae-4de5-bce9-e671b7974a98, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=getFileIDsDeliveredAtUrl, to=Pillar1, version=31, minVersion=24, auditTrailInformation=<null>(default), fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@6433611f[fileID=default-test-file.txt, allFileIDs=<null>(default)]]
Result: Received event: e94f1a68: GET_FILE_IDS for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs
Step: The pillar sends a response to the identify message.
Result: Received event: e94f1a68: GET_FILE_IDS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: e94f1a68: GET_FILE_IDS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: e94f1a68: GET_FILE_IDS for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for get fileIDs
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@79a9a3a2[correlationID=e94f1a68-16ae-4de5-bce9-e671b7974a98, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=getFileIDsDeliveredAtUrl, to=Pillar1, version=31, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@2d309058[fileID=default-test-file.txt, allFileIDs=<null>(default)], minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), resultAddress=file:../bitrepository-core/src/test/resources/test-files//TEST-FILE-IDS-DELIVERY.xml-Pillar1]
Step: The pillar sends a getFileIDsProgressResponse to the GetFileIDsClient.
Result: Received event: e94f1a68: GET_FILE_IDS for file default-test-file.txt: PROGRESS: ContributorID Pillar1, First test progress response message
Step: The resulting file is uploaded to the indicated url and the pillar sends a final response upload message
Result: Received event: e94f1a68: GET_FILE_IDS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, PartialResult=false
Result: Received event: e94f1a68: GET_FILE_IDS for file default-test-file.txt: COMPLETE:
Step: Receive and validate event results for the pillar.
Test success: getFileIDsDeliveredAtUrl
Test starting: getFileIDsDeliveredThroughMessage
Description: Tests the delivery of fileIDs from a pillar at a given URL.
Step: Initialise the variables for this test.
Step: Ensure the delivery file isn't already present on the http server
Step: Request the delivery of the file ids of a file from the pillar(s). A callback listener should be supplied.
Stimuli: Calling getFileIDs(null, default-test-file.txt, null, org.bitrepository.client.TestEventHandler@449f9628)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@34ec4134[correlationID=447ca346-7ed9-445c-99c2-703f33120fe3, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=getFileIDsDeliveredThroughMessage, to=Pillar1, version=31, minVersion=24, auditTrailInformation=<null>(default), fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@47b541a3[fileID=default-test-file.txt, allFileIDs=<null>(default)]]
Result: Received event: 447ca346: GET_FILE_IDS for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs
Step: The pillar sends a response to the identify message.
Result: Received event: 447ca346: GET_FILE_IDS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 447ca346: GET_FILE_IDS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 447ca346: GET_FILE_IDS for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for get fileIDs
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@1916f999[correlationID=447ca346-7ed9-445c-99c2-703f33120fe3, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=getFileIDsDeliveredThroughMessage, to=Pillar1, version=31, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@4f25fe6e[fileID=default-test-file.txt, allFileIDs=<null>(default)], minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), resultAddress=<null>(default)]
Step: The pillar sends a getFileIDsProgressResponse to the GetFileIDsClient.
Result: Received event: 447ca346: GET_FILE_IDS for file default-test-file.txt: PROGRESS: ContributorID Pillar1, First test progress response message
Step: The resulting file is uploaded to the indicated url and the pillar sends a final response upload message
Result: Received event: 447ca346: GET_FILE_IDS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, NumberOfFileIDs=1, PartialResult=false
Result: Received event: 447ca346: GET_FILE_IDS for file default-test-file.txt: COMPLETE:
Step: Receive and validate event results for the pillar.
Test success: getFileIDsDeliveredThroughMessage
Test starting: getFileIDsFromOtherCollection
Description: Tests the getFileIDs client will correctly try to get from a second collection if required
Added fixture: Configure collection1 to contain both pillars and collection 2 to only contain pillar2
Step: Request the putting of a file through the PutClient for collection2
Stimuli: Calling getFileIDs(null, default-test-file.txt, null, org.bitrepository.client.TestEventHandler@779b12b)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@72dd302[correlationID=ee82c1f4-f723-4d9e-bbf7-8d471a25394d, collectionID=SinglePillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=getFileIDsFromOtherCollection, to=Pillar2, version=31, minVersion=24, auditTrailInformation=<null>(default), fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@4cf7e832[fileID=default-test-file.txt, allFileIDs=<null>(default)]]
Result: Received event: ee82c1f4: GET_FILE_IDS for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs
Step: Send an identification response from pillar2.
Result: Received event: ee82c1f4: GET_FILE_IDS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: ee82c1f4: GET_FILE_IDS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: ee82c1f4: GET_FILE_IDS for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar2], Sending request for get fileIDs
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@34b01423[correlationID=ee82c1f4-f723-4d9e-bbf7-8d471a25394d, collectionID=SinglePillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=getFileIDsFromOtherCollection, to=Pillar2, version=31, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@5d6c7474[fileID=default-test-file.txt, allFileIDs=<null>(default)], minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), resultAddress=<null>(default)]
Step: Send a complete event from the pillar
Result: Received event: ee82c1f4: GET_FILE_IDS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false
Result: Received event: ee82c1f4: GET_FILE_IDS for file default-test-file.txt: COMPLETE:
Test success: getFileIDsFromOtherCollection
Test starting: testNoSuchFile
Description: Testing how a request for a non-existing file is handled.
Step: Setting up variables and such.
Step: Request the delivery of the file id of a file from the pillar(s). A callback listener should be supplied.
Stimuli: Calling getFileIDs(null, default-test-file.txt, file:../bitrepository-core/src/test/resources/test-files//TEST-FILE-IDS-DELIVERY.xml, org.bitrepository.client.TestEventHandler@449f9628)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@2b953930[correlationID=8aa3300b-347c-4f30-acb9-4e77b21aa1c8, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=testNoSuchFile, to=Pillar1, version=31, minVersion=24, auditTrailInformation=<null>(default), fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@7606a261[fileID=default-test-file.txt, allFileIDs=<null>(default)]]
Result: Received event: 8aa3300b: GET_FILE_IDS for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs
Step: The pillar sends a response to the identify message.
Result: Received event: 8aa3300b: GET_FILE_IDS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 8aa3300b: GET_FILE_IDS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 8aa3300b: GET_FILE_IDS for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for get fileIDs
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@be96f52[correlationID=8aa3300b-347c-4f30-acb9-4e77b21aa1c8, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=testNoSuchFile, to=Pillar1, version=31, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@9379ba6[fileID=default-test-file.txt, allFileIDs=<null>(default)], minTimestamp=<null>(default), maxTimestamp=<null>(default), maxNumberOfResults=<null>(default), resultAddress=file:../bitrepository-core/src/test/resources/test-files//TEST-FILE-IDS-DELIVERY.xml-Pillar1]
Step: Send a error that the file cannot be found.
Result: Received event: 8aa3300b: GET_FILE_IDS for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FILE_NOT_FOUND_FAILURE, No such file.
Result: Received event: 8aa3300b: GET_FILE_IDS for file default-test-file.txt: FAILED: , Failed operation. Cause(s):
[8aa3300b: GET_FILE_IDS for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FILE_NOT_FOUND_FAILURE, No such file.]
Test success: testNoSuchFile
Test starting: testPaging
Description: Tests the GetFileIDs client correctly handles functionality for limiting results, either by timestamp or result count.
Step: Request fileIDs from with MinTimestamp, MaxTimestamp, MaxNumberOfResults set for both pillars .
Stimuli: Calling getFileIDs([ContributorQuery{componentID='Pillar1, minTimestamp=Tue Feb 15 13:44:45 CET 2022, maxTimestamp=Tue Feb 15 13:44:46 CET 2022, maxNumberOfResults=1}, ContributorQuery{componentID='Pillar2, minTimestamp=Tue Feb 15 13:44:46 CET 2022, maxTimestamp=Tue Feb 15 13:44:46 CET 2022, maxNumberOfResults=2}], null, null, org.bitrepository.client.TestEventHandler@449f9628)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@75e05153[correlationID=864f9b30-6434-4ba8-8434-b1830d87949e, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=testPaging, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@1d95743[fileID=<null>(default), allFileIDs=true]]
Result: Received event: 864f9b30: GET_FILE_IDS: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs
Step: Send a IdentifyPillarsForGetFileIDsResponse from both pillars.
Result: Received event: 864f9b30: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 864f9b30: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 864f9b30: GET_FILE_IDS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2, Pillar1]
Result: Received event: 864f9b30: GET_FILE_IDS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for get fileIDs
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@886a0f5[correlationID=864f9b30-6434-4ba8-8434-b1830d87949e, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=testPaging, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@432e9de9[fileID=<null>(default), allFileIDs=true], minTimestamp=2022-02-15T13:44:45.342+01:00, maxTimestamp=2022-02-15T13:44:46.242+01:00, maxNumberOfResults=1, resultAddress=<null>(default)]
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@5299c25d[correlationID=864f9b30-6434-4ba8-8434-b1830d87949e, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=testPaging, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@7541dbee[fileID=<null>(default), allFileIDs=true], minTimestamp=2022-02-15T13:44:46.242+01:00, maxTimestamp=2022-02-15T13:44:46.342+01:00, maxNumberOfResults=2, resultAddress=<null>(default)]
Test success: testPaging
Test starting: verifyGetFileIDsClientFromFactory
Test success: verifyGetFileIDsClientFromFactory
Starting testcase NegativeResponseExceptionTest
Test starting: testNegativeResponse
Description: Test the instantiation of the exception
Step: Setup
Step: Try to throw such an exception with the response code
Test success: testNegativeResponse
Starting testcase PutFileClientComponentTest
Test starting: defaultReturnChecksumsWithChecksumPillar
Description: Tests that PutClient handles the presence of a ChecksumPillar correctly, when a return checksum of default type is requested (which a checksum pillar can provide).
Step: Call putFile while requesting a salted checksum to be returned.
Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@58b709c9[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], org.bitrepository.client.TestEventHandler@3d8eae5d, TEST-AUDIT-TRAIL)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@332f6402[correlationID=cb8a9881-53e0-4a6a-80fa-699411da7e69, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=defaultReturnChecksumsWithChecksumPillar, to=<null>(default), version=31, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, fileID=default-test-file.txt, fileSize=0]
Result: Received event: cb8a9881: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file
Step: Send an identification response with a PillarChecksumSpec element set, indicating that this is a checksum pillar.
Result: Received event: cb8a9881: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Step: Send an normal identification response from pillar2.
Result: Received event: cb8a9881: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: cb8a9881: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2, Pillar1]
Result: Received event: cb8a9881: PUT_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for put file
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@3590ccd[correlationID=cb8a9881-53e0-4a6a-80fa-699411da7e69, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=defaultReturnChecksumsWithChecksumPillar, to=<null>(default), version=31, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>(default), checksumRequestForNewFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@58b709c9[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)]]
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@785bc970[correlationID=cb8a9881-53e0-4a6a-80fa-699411da7e69, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=defaultReturnChecksumsWithChecksumPillar, to=<null>(default), version=31, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, pillarID=Pillar2, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>(default), checksumRequestForNewFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@58b709c9[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)]]
Test success: defaultReturnChecksumsWithChecksumPillar
Test starting: fileExistsOnPillarChecksumFromPillarNoClientChecksum
Description: Tests that PutClient handles the presence of a file correctly, when the pillar returns a checksum but the putFile was called without a checksum.
Step: Call putFile.
Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, null, org.bitrepository.client.TestEventHandler@67cd2d0a, TEST-AUDIT-TRAIL)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@48d2adc2[correlationID=6d26ea20-0106-4986-b836-cc547211cdac, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=fileExistsOnPillarChecksumFromPillarNoClientChecksum, to=<null>(default), version=31, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, fileID=default-test-file.txt, fileSize=0]
Result: Received event: 6d26ea20: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file
Step: Send a DUPLICATE_FILE_FAILURE response with a random checksum.
Result: Received event: 6d26ea20: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: DUPLICATE_FILE_FAILURE, Received negative response from component Pillar1: org.bitrepository.bitrepositoryelements.ResponseInfo@1da5cb5a[responseCode=DUPLICATE_FILE_FAILURE, responseText=Testing the handling of 'DUPLICATE FILE' identification.] (existing file checksum does not match)
Result: Received event: 6d26ea20: PUT_FILE for file default-test-file.txt: FAILED: , Can not put file default-test-file.txt, as an different file already exists on pillar Pillar1
13:44:47.017 ERROR o.b.m.p.c.IdentifyPillarsForPutFile - Failing conversation 'PutFileConversationContext{collectionID='TwoPillarCollection', conversationID='6d26ea20-0106-4986-b836-cc547211cdac', clientID='fileExistsOnPillarChecksumFromPillarNoClientChecksum', fileID='default-test-file.txt', contributors=[Pillar1, Pillar2], monitor=ConversationEventMonitor{, collectionID='TwoPillarCollection', conversationID='6d26ea20', operationType=PUT_FILE, fileID='default-test-file.txt', eventHandler=org.bitrepository.client.TestEventHandler@67cd2d0a, contributorCompleteEvents=[], contributorFailedEvents=[6d26ea20: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: DUPLICATE_FILE_FAILURE, Received negative response from component Pillar1: org.bitrepository.bitrepositoryelements.ResponseInfo@1da5cb5a[responseCode=DUPLICATE_FILE_FAILURE, responseText=Testing the handling of 'DUPLICATE FILE' identification.] (existing file checksum does not match)], failOnComponentFailure=true}, auditTrailInformation='TEST-AUDIT-TRAIL', state=org.bitrepository.client.conversation.FinishedState@3fad2065, checksumPillars=[]}' with exception
org.bitrepository.common.exceptions.UnableToFinishException: Can not put file default-test-file.txt, as an different file already exists on pillar Pillar1
at org.bitrepository.modify.putfile.conversation.IdentifyPillarsForPutFile.handleFailureResponse(IdentifyPillarsForPutFile.java:76)
at org.bitrepository.client.conversation.IdentifyingState.processMessage(IdentifyingState.java:60)
at org.bitrepository.client.conversation.GeneralConversationState.handleMessage(GeneralConversationState.java:110)
at org.bitrepository.client.conversation.StateBasedConversation.onMessage(StateBasedConversation.java:53)
at org.bitrepository.client.conversation.mediator.CollectionBasedConversationMediator.onMessage(CollectionBasedConversationMediator.java:136)
at org.bitrepository.protocol.messagebus.SimpleMessageBus.lambda$sendMessage$0(SimpleMessageBus.java:73)
at java.lang.Iterable.forEach(Iterable.java:75)
at org.bitrepository.protocol.messagebus.SimpleMessageBus.sendMessage(SimpleMessageBus.java:73)
at org.bitrepository.modify.putfile.PutFileClientComponentTest.fileExistsOnPillarChecksumFromPillarNoClientChecksum(PutFileClientComponentTest.java:492)
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.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:134)
at org.testng.internal.TestInvoker.invokeMethod(TestInvoker.java:597)
at org.testng.internal.TestInvoker.invokeTestMethod(TestInvoker.java:173)
at org.testng.internal.MethodRunner.runInSequence(MethodRunner.java:46)
at org.testng.internal.TestInvoker$MethodInvocationAgent.invoke(TestInvoker.java:816)
at org.testng.internal.TestInvoker.invokeTestMethods(TestInvoker.java:146)
at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:146)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:128)
at java.util.ArrayList.forEach(ArrayList.java:1249)
at org.testng.TestRunner.privateRun(TestRunner.java:766)
at org.testng.TestRunner.run(TestRunner.java:587)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:384)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:378)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:337)
at org.testng.SuiteRunner.run(SuiteRunner.java:286)
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:53)
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:96)
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1187)
at org.testng.TestNG.runSuitesLocally(TestNG.java:1109)
at org.testng.TestNG.runSuites(TestNG.java:1039)
at org.testng.TestNG.run(TestNG.java:1007)
at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:135)
at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:193)
at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:94)
at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:146)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:377)
at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:138)
at org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:465)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:451)
Test success: fileExistsOnPillarChecksumFromPillarNoClientChecksum
Test starting: fileExistsOnPillarDifferentChecksumFromPillar
Description: Tests that PutClient handles the presence of a file correctly, when the pillar returns a checksum different from the file being put.
Step: Call putFile.
Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@76a34504[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@5a0d2ed8[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={-70}, calculationTimestamp=2022-02-15T13:44:47.192+01:00], null, org.bitrepository.client.TestEventHandler@6da63893, TEST-AUDIT-TRAIL)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@279b5232[correlationID=873c60b1-9645-4463-9603-9fd89ed8941a, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=fileExistsOnPillarDifferentChecksumFromPillar, to=<null>(default), version=31, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, fileID=default-test-file.txt, fileSize=0]
Result: Received event: 873c60b1: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file
Step: Send a DUPLICATE_FILE_FAILURE response with a random checksum.
Result: Received event: 873c60b1: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: DUPLICATE_FILE_FAILURE, Received negative response from component Pillar1: org.bitrepository.bitrepositoryelements.ResponseInfo@240af9dc[responseCode=DUPLICATE_FILE_FAILURE, responseText=Testing the handling of 'DUPLICATE FILE' identification.] (existing file checksum does not match)
Result: Received event: 873c60b1: PUT_FILE for file default-test-file.txt: FAILED: , Can not put file default-test-file.txt, as an different file already exists on pillar Pillar1
13:44:47.198 ERROR o.b.m.p.c.IdentifyPillarsForPutFile - Failing conversation 'PutFileConversationContext{collectionID='TwoPillarCollection', conversationID='873c60b1-9645-4463-9603-9fd89ed8941a', clientID='fileExistsOnPillarDifferentChecksumFromPillar', fileID='default-test-file.txt', contributors=[Pillar1, Pillar2], monitor=ConversationEventMonitor{, collectionID='TwoPillarCollection', conversationID='873c60b1', operationType=PUT_FILE, fileID='default-test-file.txt', eventHandler=org.bitrepository.client.TestEventHandler@6da63893, contributorCompleteEvents=[], contributorFailedEvents=[873c60b1: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: DUPLICATE_FILE_FAILURE, Received negative response from component Pillar1: org.bitrepository.bitrepositoryelements.ResponseInfo@240af9dc[responseCode=DUPLICATE_FILE_FAILURE, responseText=Testing the handling of 'DUPLICATE FILE' identification.] (existing file checksum does not match)], failOnComponentFailure=true}, auditTrailInformation='TEST-AUDIT-TRAIL', state=org.bitrepository.client.conversation.FinishedState@77ea2f8a, checksumPillars=[]}' with exception
org.bitrepository.common.exceptions.UnableToFinishException: Can not put file default-test-file.txt, as an different file already exists on pillar Pillar1
at org.bitrepository.modify.putfile.conversation.IdentifyPillarsForPutFile.handleFailureResponse(IdentifyPillarsForPutFile.java:76)
at org.bitrepository.client.conversation.IdentifyingState.processMessage(IdentifyingState.java:60)
at org.bitrepository.client.conversation.GeneralConversationState.handleMessage(GeneralConversationState.java:110)
at org.bitrepository.client.conversation.StateBasedConversation.onMessage(StateBasedConversation.java:53)
at org.bitrepository.client.conversation.mediator.CollectionBasedConversationMediator.onMessage(CollectionBasedConversationMediator.java:136)
at org.bitrepository.protocol.messagebus.SimpleMessageBus.lambda$sendMessage$0(SimpleMessageBus.java:73)
at java.lang.Iterable.forEach(Iterable.java:75)
at org.bitrepository.protocol.messagebus.SimpleMessageBus.sendMessage(SimpleMessageBus.java:73)
at org.bitrepository.modify.putfile.PutFileClientComponentTest.fileExistsOnPillarDifferentChecksumFromPillar(PutFileClientComponentTest.java:401)
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.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:134)
at org.testng.internal.TestInvoker.invokeMethod(TestInvoker.java:597)
at org.testng.internal.TestInvoker.invokeTestMethod(TestInvoker.java:173)
at org.testng.internal.MethodRunner.runInSequence(MethodRunner.java:46)
at org.testng.internal.TestInvoker$MethodInvocationAgent.invoke(TestInvoker.java:816)
at org.testng.internal.TestInvoker.invokeTestMethods(TestInvoker.java:146)
at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:146)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:128)
at java.util.ArrayList.forEach(ArrayList.java:1249)
at org.testng.TestRunner.privateRun(TestRunner.java:766)
at org.testng.TestRunner.run(TestRunner.java:587)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:384)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:378)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:337)
at org.testng.SuiteRunner.run(SuiteRunner.java:286)
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:53)
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:96)
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1187)
at org.testng.TestNG.runSuitesLocally(TestNG.java:1109)
at org.testng.TestNG.runSuites(TestNG.java:1039)
at org.testng.TestNG.run(TestNG.java:1007)
at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:135)
at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:193)
at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:94)
at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:146)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:377)
at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:138)
at org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:465)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:451)
Test success: fileExistsOnPillarDifferentChecksumFromPillar
Test starting: fileExistsOnPillarNoChecksumFromPillar
Description: Tests that PutClient handles the presence of a file correctly, when the pillar doesn't return a checksum in the identification response.
Step: Call putFile.
Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, null, org.bitrepository.client.TestEventHandler@61876e0e, TEST-AUDIT-TRAIL)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@53a6d5fc[correlationID=5fc45327-9b20-4633-ba85-7aa700caa7c0, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=fileExistsOnPillarNoChecksumFromPillar, to=<null>(default), version=31, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, fileID=default-test-file.txt, fileSize=0]
Result: Received event: 5fc45327: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file
Step: Send a DUPLICATE_FILE_FAILURE response without a checksum.
Result: Received event: 5fc45327: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: DUPLICATE_FILE_FAILURE, Received negative response from component Pillar1: org.bitrepository.bitrepositoryelements.ResponseInfo@3fa87583[responseCode=DUPLICATE_FILE_FAILURE, responseText=Testing the handling of 'DUPLICATE FILE' identification.]
Result: Received event: 5fc45327: PUT_FILE for file default-test-file.txt: FAILED: , Can not put file default-test-file.txt, as an file already exists on pillar Pillar1
13:44:47.371 ERROR o.b.m.p.c.IdentifyPillarsForPutFile - Failing conversation 'PutFileConversationContext{collectionID='TwoPillarCollection', conversationID='5fc45327-9b20-4633-ba85-7aa700caa7c0', clientID='fileExistsOnPillarNoChecksumFromPillar', fileID='default-test-file.txt', contributors=[Pillar1, Pillar2], monitor=ConversationEventMonitor{, collectionID='TwoPillarCollection', conversationID='5fc45327', operationType=PUT_FILE, fileID='default-test-file.txt', eventHandler=org.bitrepository.client.TestEventHandler@61876e0e, contributorCompleteEvents=[], contributorFailedEvents=[5fc45327: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: DUPLICATE_FILE_FAILURE, Received negative response from component Pillar1: org.bitrepository.bitrepositoryelements.ResponseInfo@3fa87583[responseCode=DUPLICATE_FILE_FAILURE, responseText=Testing the handling of 'DUPLICATE FILE' identification.]], failOnComponentFailure=true}, auditTrailInformation='TEST-AUDIT-TRAIL', state=org.bitrepository.client.conversation.FinishedState@552b5799, checksumPillars=[]}' with exception
org.bitrepository.common.exceptions.UnableToFinishException: Can not put file default-test-file.txt, as an file already exists on pillar Pillar1
at org.bitrepository.modify.putfile.conversation.IdentifyPillarsForPutFile.handleFailureResponse(IdentifyPillarsForPutFile.java:84)
at org.bitrepository.client.conversation.IdentifyingState.processMessage(IdentifyingState.java:60)
at org.bitrepository.client.conversation.GeneralConversationState.handleMessage(GeneralConversationState.java:110)
at org.bitrepository.client.conversation.StateBasedConversation.onMessage(StateBasedConversation.java:53)
at org.bitrepository.client.conversation.mediator.CollectionBasedConversationMediator.onMessage(CollectionBasedConversationMediator.java:136)
at org.bitrepository.protocol.messagebus.SimpleMessageBus.lambda$sendMessage$0(SimpleMessageBus.java:73)
at java.lang.Iterable.forEach(Iterable.java:75)
at org.bitrepository.protocol.messagebus.SimpleMessageBus.sendMessage(SimpleMessageBus.java:73)
at org.bitrepository.modify.putfile.PutFileClientComponentTest.fileExistsOnPillarNoChecksumFromPillar(PutFileClientComponentTest.java:363)
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.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:134)
at org.testng.internal.TestInvoker.invokeMethod(TestInvoker.java:597)
at org.testng.internal.TestInvoker.invokeTestMethod(TestInvoker.java:173)
at org.testng.internal.MethodRunner.runInSequence(MethodRunner.java:46)
at org.testng.internal.TestInvoker$MethodInvocationAgent.invoke(TestInvoker.java:816)
at org.testng.internal.TestInvoker.invokeTestMethods(TestInvoker.java:146)
at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:146)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:128)
at java.util.ArrayList.forEach(ArrayList.java:1249)
at org.testng.TestRunner.privateRun(TestRunner.java:766)
at org.testng.TestRunner.run(TestRunner.java:587)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:384)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:378)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:337)
at org.testng.SuiteRunner.run(SuiteRunner.java:286)
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:53)
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:96)
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1187)
at org.testng.TestNG.runSuitesLocally(TestNG.java:1109)
at org.testng.TestNG.runSuites(TestNG.java:1039)
at org.testng.TestNG.run(TestNG.java:1007)
at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:135)
at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:193)
at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:94)
at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:146)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:377)
at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:138)
at org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:465)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:451)
Test success: fileExistsOnPillarNoChecksumFromPillar
Test starting: noPillarsResponding
Description: Tests the handling of missing identification responses from all pillar
Added fixture: Sets the identification timeout to 100 ms.
Step: Request the putting of a file through the PutClient
Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, null, org.bitrepository.client.TestEventHandler@4c511912, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@1ef8f1ca[correlationID=bac235d0-5f04-48be-ad80-4d550e43d005, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=noPillarsResponding, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), fileID=default-test-file.txt, fileSize=0]
Result: Received event: bac235d0: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file
Step: Do not respond. Just await the timeout.
Result: Received event: bac235d0: PUT_FILE for file default-test-file.txt: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar1, Pillar2]
Result: Received event: bac235d0: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor
Result: Received event: bac235d0: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
Result: Received event: bac235d0: PUT_FILE for file default-test-file.txt: FAILED: , Unable to continue operation, contributors unavailable.
13:44:47.678 ERROR o.b.m.p.c.IdentifyPillarsForPutFile - Failing conversation 'PutFileConversationContext{collectionID='TwoPillarCollection', conversationID='bac235d0-5f04-48be-ad80-4d550e43d005', clientID='noPillarsResponding', fileID='default-test-file.txt', contributors=[Pillar1, Pillar2], monitor=ConversationEventMonitor{, collectionID='TwoPillarCollection', conversationID='bac235d0', operationType=PUT_FILE, fileID='default-test-file.txt', eventHandler=org.bitrepository.client.TestEventHandler@4c511912, contributorCompleteEvents=[], contributorFailedEvents=[bac235d0: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor, bac235d0: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor], failOnComponentFailure=true}, auditTrailInformation='null', state=org.bitrepository.client.conversation.FinishedState@1576ec88, checksumPillars=[]}' with exception
org.bitrepository.common.exceptions.UnableToFinishException: Unable to continue operation, contributors unavailable.
at org.bitrepository.client.conversation.IdentifyingState.completeState(IdentifyingState.java:76)
at org.bitrepository.client.conversation.GeneralConversationState.changeState(GeneralConversationState.java:147)
at org.bitrepository.client.conversation.GeneralConversationState.access$100(GeneralConversationState.java:48)
at org.bitrepository.client.conversation.GeneralConversationState$TimeoutHandler.run(GeneralConversationState.java:134)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Test success: noPillarsResponding
Test starting: noReturnChecksumsWithChecksumPillar
Description: Tests that PutClient handles the presence of a ChecksumPillar correctly, when no return checksum is requested.
Step: Call putFile while requesting a salted checksum to be returned.
Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, null, org.bitrepository.client.TestEventHandler@68b7a133, TEST-AUDIT-TRAIL)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@1942bc06[correlationID=a7e37642-763b-448c-aa56-75220c9ed824, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=noReturnChecksumsWithChecksumPillar, to=<null>(default), version=31, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, fileID=default-test-file.txt, fileSize=0]
Result: Received event: a7e37642: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file
Step: Send an identification response with a PillarChecksumSpec element set, indicating that this is a checksum pillar.
Result: Received event: a7e37642: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Step: Send an normal identification response from pillar2.
Result: Received event: a7e37642: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: a7e37642: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2, Pillar1]
Result: Received event: a7e37642: PUT_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for put file
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@6918300a[correlationID=a7e37642-763b-448c-aa56-75220c9ed824, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=noReturnChecksumsWithChecksumPillar, to=<null>(default), version=31, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>(default), checksumRequestForNewFile=<null>(default)]
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@65b603a3[correlationID=a7e37642-763b-448c-aa56-75220c9ed824, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=noReturnChecksumsWithChecksumPillar, to=<null>(default), version=31, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, pillarID=Pillar2, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>(default), checksumRequestForNewFile=<null>(default)]
Test success: noReturnChecksumsWithChecksumPillar
Test starting: normalPutFile
Description: Tests the PutClient. Makes a whole conversation for the put client for a 'good' scenario.
Added fixture: Initialise the number of pillars to one
Step: Ensure that the test-file is placed on the HTTP server.
Step: Request the delivery of a file from a specific pillar. A callback listener should be supplied.
Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, null, org.bitrepository.client.TestEventHandler@7f0e9c4c, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@34963943[correlationID=0ebcb856-2e9e-40d2-a9f3-247d4e67a488, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=normalPutFile, to=Pillar1, version=31, minVersion=24, auditTrailInformation=<null>(default), fileID=default-test-file.txt, fileSize=0]
Result: Received event: 0ebcb856: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file
Step: Make response for the pillar.
Result: Received event: 0ebcb856: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 0ebcb856: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 0ebcb856: PUT_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for put file
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@480b1693[correlationID=0ebcb856-2e9e-40d2-a9f3-247d4e67a488, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=normalPutFile, to=Pillar1, version=31, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>(default), checksumRequestForNewFile=<null>(default)]
Step: Validate the steps of the PutClient by going through the events.
Step: The pillar sends a progress response to the PutClient.
Result: Received event: 0ebcb856: PUT_FILE for file default-test-file.txt: PROGRESS: ContributorID Pillar1, First test progress response message
Step: Send a final response message to the PutClient.
Result: Received event: 0ebcb856: PUT_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, requestedChecksumResult=null
Result: Received event: 0ebcb856: PUT_FILE for file default-test-file.txt: COMPLETE:
Test success: normalPutFile
Test starting: onePillarPutRetryFailure
Reference: <a href=https://sbforge.org/jira/browse/BITMAG-810>BITMAG-810 Reference client should be able to retry failed file transfers</a>
Description: Tests that a putfile attempt failing due to FILE_TRANSFER_FAILURE is only attempted the maximum allowed attempts
Added fixture: Sets the identification timeout to 3 sec, allow two retries and only register one pillar.
Step: Request the putting of a file through the PutClient
Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, null, org.bitrepository.client.TestEventHandler@ff68deb, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@2eff4e88[correlationID=e67c6dab-2cfd-4317-91af-d489c95e0986, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarPutRetryFailure, to=Pillar1, version=31, minVersion=24, auditTrailInformation=<null>(default), fileID=default-test-file.txt, fileSize=0]
Result: Received event: e67c6dab: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file
Step: Send an identification response from the one pillar.
Result: Received event: e67c6dab: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: e67c6dab: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: e67c6dab: PUT_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for put file
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@1199a91[correlationID=e67c6dab-2cfd-4317-91af-d489c95e0986, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarPutRetryFailure, to=Pillar1, version=31, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>(default), checksumRequestForNewFile=<null>(default)]
Step: The client should proceed to send a putFileOperation request to the responding pillar.
Step: Send a PutFileFinalResponse indicating a FILE_TRANSFER_FAILURE
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@577017c6[correlationID=e67c6dab-2cfd-4317-91af-d489c95e0986, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarPutRetryFailure, to=Pillar1, version=31, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>(default), checksumRequestForNewFile=<null>(default)]
Result: Received event: e67c6dab: PUT_FILE for file default-test-file.txt: WARNING: ContributorID Pillar1, Retrying putfile (attempt number 2)
Step: Send a PutFileFinalResponse indicating a FILE_TRANSFER_FAILURE for the second put attempt
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@69d18bf0[correlationID=e67c6dab-2cfd-4317-91af-d489c95e0986, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarPutRetryFailure, to=Pillar1, version=31, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>(default), checksumRequestForNewFile=<null>(default)]
Result: Received event: e67c6dab: PUT_FILE for file default-test-file.txt: WARNING: ContributorID Pillar1, Retrying putfile (attempt number 3)
Step: Send a PutFileFinalResponse indicating a FILE_TRANSFER_FAILURE for the third put attempt
Result: Received event: e67c6dab: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FILE_TRANSFER_FAILURE
Result: Received event: e67c6dab: PUT_FILE for file default-test-file.txt: FAILED: , Failed operation. Cause(s):
[e67c6dab: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FILE_TRANSFER_FAILURE]
Test success: onePillarPutRetryFailure
Test starting: onePillarPutRetrySuccess
Reference: <a href=https://sbforge.org/jira/browse/BITMAG-810>BITMAG-810 Reference client should be able to retry failed file transfers</a>
Description: Tests the handling of a failed transmission when retry is allowed
Added fixture: Sets the identification timeout to 3 sec, allow two retries and only register one pillar.
Step: Request the putting of a file through the PutClient
Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, null, org.bitrepository.client.TestEventHandler@562c6d5c, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@5efd5ebd[correlationID=76be116d-0dd4-445e-9351-2e6c2692bfba, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarPutRetrySuccess, to=Pillar1, version=31, minVersion=24, auditTrailInformation=<null>(default), fileID=default-test-file.txt, fileSize=0]
Result: Received event: 76be116d: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file
Step: Send an identification response from the one pillar.
Result: Received event: 76be116d: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 76be116d: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 76be116d: PUT_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for put file
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@54b64ebf[correlationID=76be116d-0dd4-445e-9351-2e6c2692bfba, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarPutRetrySuccess, to=Pillar1, version=31, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>(default), checksumRequestForNewFile=<null>(default)]
Step: The client should proceed to send a putFileOperation request to the responding pillar.
Step: Send a PutFileFinalResponse indicating a FILE_TRANSFER_FAILURE
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@61458ff8[correlationID=76be116d-0dd4-445e-9351-2e6c2692bfba, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarPutRetrySuccess, to=Pillar1, version=31, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>(default), checksumRequestForNewFile=<null>(default)]
Result: Received event: 76be116d: PUT_FILE for file default-test-file.txt: WARNING: ContributorID Pillar1, Retrying putfile (attempt number 2)
Step: A new PutFileRequest is send, pillar responds with success
Result: Received event: 76be116d: PUT_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, requestedChecksumResult=null
Result: Received event: 76be116d: PUT_FILE for file default-test-file.txt: COMPLETE:
Test success: onePillarPutRetrySuccess
Test starting: onePillarRespondingWithPartialPutAllowed
Reference: <a href=https://sbforge.org/jira/browse/BITMAG-598>BITMAG-598 It should be possible to putFiles, even though only a subset of the pillars are available</a>
Description: Tests the handling of missing identification responses from one pillar, when partial put are allowed
Added fixture: Sets the identification timeout to 100 ms and allow partial puts.
Step: Request the putting of a file through the PutClient
Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, null, org.bitrepository.client.TestEventHandler@7bbaf6fc, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@381eb99[correlationID=89c84ba7-314f-4154-a130-bafd8a614d26, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarRespondingWithPartialPutAllowed, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), fileID=default-test-file.txt, fileSize=0]
Result: Received event: 89c84ba7: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file
Step: Only send an identification response from one pillar.
Result: Received event: 89c84ba7: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Step: Await the timeout.
Result: Received event: 89c84ba7: PUT_FILE for file default-test-file.txt: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar2]
Result: Received event: 89c84ba7: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
Result: Received event: 89c84ba7: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 89c84ba7: PUT_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for put file
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@14217017[correlationID=89c84ba7-314f-4154-a130-bafd8a614d26, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarRespondingWithPartialPutAllowed, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>(default), checksumRequestForNewFile=<null>(default)]
Step: The client should proceed to send a putFileOperation request to the responding pillar.
Step: Send a pillar complete event
Result: Received event: 89c84ba7: PUT_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, requestedChecksumResult=null
Result: Received event: 89c84ba7: PUT_FILE for file default-test-file.txt: FAILED: , Failed operation. Cause(s):
[89c84ba7: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor]
Test success: onePillarRespondingWithPartialPutAllowed
Test starting: onePillarRespondingWithPartialPutDisallowed
Description: Tests the handling of missing identification responses from one pillar, when partial put are allowed
Added fixture: Sets the identification timeout to 100 ms and disallow partial puts.
Step: Request the putting of a file through the PutClient
Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, null, org.bitrepository.client.TestEventHandler@4f7e0ea7, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@62fe5aca[correlationID=ffdfd343-aa9c-4732-aae0-d40171c7c5f1, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarRespondingWithPartialPutDisallowed, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), fileID=default-test-file.txt, fileSize=0]
Result: Received event: ffdfd343: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file
Step: Only send an identification response from one pillar.
Result: Received event: ffdfd343: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Step: Await the timeout.
Result: Received event: ffdfd343: PUT_FILE for file default-test-file.txt: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar2]
Result: Received event: ffdfd343: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
Result: Received event: ffdfd343: PUT_FILE for file default-test-file.txt: FAILED: , Unable to continue operation, contributors unavailable.
13:44:49.114 ERROR o.b.m.p.c.IdentifyPillarsForPutFile - Failing conversation 'PutFileConversationContext{collectionID='TwoPillarCollection', conversationID='ffdfd343-aa9c-4732-aae0-d40171c7c5f1', clientID='onePillarRespondingWithPartialPutDisallowed', fileID='default-test-file.txt', contributors=[Pillar1, Pillar2], monitor=ConversationEventMonitor{, collectionID='TwoPillarCollection', conversationID='ffdfd343', operationType=PUT_FILE, fileID='default-test-file.txt', eventHandler=org.bitrepository.client.TestEventHandler@4f7e0ea7, contributorCompleteEvents=[], contributorFailedEvents=[ffdfd343: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor], failOnComponentFailure=true}, auditTrailInformation='null', state=org.bitrepository.client.conversation.FinishedState@5cf3e623, checksumPillars=[]}' with exception
org.bitrepository.common.exceptions.UnableToFinishException: Unable to continue operation, contributors unavailable.
at org.bitrepository.client.conversation.IdentifyingState.completeState(IdentifyingState.java:76)
at org.bitrepository.client.conversation.GeneralConversationState.changeState(GeneralConversationState.java:147)
at org.bitrepository.client.conversation.GeneralConversationState.access$100(GeneralConversationState.java:48)
at org.bitrepository.client.conversation.GeneralConversationState$TimeoutHandler.run(GeneralConversationState.java:134)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Test success: onePillarRespondingWithPartialPutDisallowed
Test starting: putClientOperationTimeout
Description: Tests the handling of a failed operation for the PutClient
Step: Initialise the number of pillars and the PutClient. Sets the operation timeout to 100 ms.
Step: Request the putting of a file through the PutClient
Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, null, org.bitrepository.client.TestEventHandler@1005364f, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@55455a81[correlationID=976808ee-454b-4172-9160-e3b85f39b72a, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=putClientOperationTimeout, to=Pillar1, version=31, minVersion=24, auditTrailInformation=<null>(default), fileID=default-test-file.txt, fileSize=0]
Result: Received event: 976808ee: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file
Step: Make response for the pillar.
Result: Received event: 976808ee: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 976808ee: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 976808ee: PUT_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for put file
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@1574cb5[correlationID=976808ee-454b-4172-9160-e3b85f39b72a, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=putClientOperationTimeout, to=Pillar1, version=31, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>(default), checksumRequestForNewFile=<null>(default)]
Step: Validate the steps of the PutClient by going through the events.
Step: Do not respond. Just await the timeout.
Result: Received event: 976808ee: PUT_FILE for file default-test-file.txt: FAILED: , Failed to receive responses from all contributors before timeout(100ms). Missing contributors [Pillar1]
13:44:49.355 ERROR o.b.m.p.conversation.PuttingFile - Failing conversation 'PutFileConversationContext{collectionID='TwoPillarCollection', conversationID='976808ee-454b-4172-9160-e3b85f39b72a', clientID='putClientOperationTimeout', fileID='default-test-file.txt', contributors=[Pillar1], monitor=ConversationEventMonitor{, collectionID='TwoPillarCollection', conversationID='976808ee', operationType=PUT_FILE, fileID='default-test-file.txt', eventHandler=org.bitrepository.client.TestEventHandler@1005364f, contributorCompleteEvents=[], contributorFailedEvents=[], failOnComponentFailure=true}, auditTrailInformation='null', state=org.bitrepository.client.conversation.FinishedState@49685e81, checksumPillars=[]}' with exception
org.bitrepository.common.exceptions.UnableToFinishException: Failed to receive responses from all contributors before timeout(100ms). Missing contributors [Pillar1]
at org.bitrepository.client.conversation.PerformingOperationState.logStateTimeout(PerformingOperationState.java:82)
at org.bitrepository.client.conversation.GeneralConversationState$TimeoutHandler.run(GeneralConversationState.java:133)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Test success: putClientOperationTimeout
Test starting: putClientPillarOperationFailed
Description: Tests the handling of a operation failure for the PutClient.
Step: Initialise the number of pillars to one
Step: Ensure that the test-file is placed on the HTTP server.
Step: Request the delivery of a file from a specific pillar. A callback listener should be supplied.
Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, null, org.bitrepository.client.TestEventHandler@1029f5d2, TEST-AUDIT-TRAIL)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@7789af0b[correlationID=34416e5a-7008-4077-9528-581839b68687, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=putClientPillarOperationFailed, to=Pillar1, version=31, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, fileID=default-test-file.txt, fileSize=0]
Result: Received event: 34416e5a: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file
Step: Send pillar response.
Result: Received event: 34416e5a: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 34416e5a: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 34416e5a: PUT_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for put file
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@2b27b44d[correlationID=34416e5a-7008-4077-9528-581839b68687, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=putClientPillarOperationFailed, to=Pillar1, version=31, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>(default), checksumRequestForNewFile=<null>(default)]
Step: Validate the steps of the PutClient by going through the events.
Step: Send a failed response message to the PutClient.
Result: Received event: 34416e5a: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE, Verifying that a failure can be understood!
Result: Received event: 34416e5a: PUT_FILE for file default-test-file.txt: FAILED: , Failed operation. Cause(s):
[34416e5a: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE, Verifying that a failure can be understood!]
Test success: putClientPillarOperationFailed
Test starting: putToOtherCollection
Reference: <a href=https://sbforge.org/jira/browse/BITMAG-925>BITMAG-925 Client will always try to put to the pillars defined in the first collection</a>
Description: Tests the putFIle client will correctly try to put to a second collection if required
Added fixture: Sets the identification timeout to 3 sec, allow two retries and only register one pillar.
Added fixture: Configure collection1 to contain both pillars and collection 2 to only contain pillar2
Step: Request the putting of a file through the PutClient for collection2
Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, null, org.bitrepository.client.TestEventHandler@5e8e40e8, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@469603b[correlationID=92f2b360-180a-4435-b264-6461d419d29e, collectionID=SinglePillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=putToOtherCollection, to=Pillar2, version=31, minVersion=24, auditTrailInformation=<null>(default), fileID=default-test-file.txt, fileSize=0]
Result: Received event: 92f2b360: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file
Step: Send an identification response from pillar2.
Result: Received event: 92f2b360: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 92f2b360: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: 92f2b360: PUT_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar2], Sending request for put file
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@9608d1d[correlationID=92f2b360-180a-4435-b264-6461d419d29e, collectionID=SinglePillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=putToOtherCollection, to=Pillar2, version=31, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar2, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>(default), checksumRequestForNewFile=<null>(default)]
Step: Send a put complete event from the pillar
Result: Received event: 92f2b360: PUT_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2, requestedChecksumResult=null
Result: Received event: 92f2b360: PUT_FILE for file default-test-file.txt: COMPLETE:
Test success: putToOtherCollection
Test starting: saltedReturnChecksumsWithChecksumPillar
Description: Tests that PutClient handles the presence of a ChecksumPillar correctly, when a salted return checksum (which a checksum pillar can't provide) is requested.
Reference: <a href="https://sbforge.org/jira/browse/BITMAG-677">BITMAG-677put, replace and delete clients fails if return checksums are requested and a checksumpillar is involved</a>
Step: Call putFile while requesting a salted checksum to be returned.
Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@3feaa2b3[checksumType=HMAC_MD5, checksumSalt={-86}, otherChecksumType=<null>(default)], org.bitrepository.client.TestEventHandler@629f2844, TEST-AUDIT-TRAIL)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@4f453c84[correlationID=add16815-5ff2-4df1-8c58-7028b625c1d4, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=saltedReturnChecksumsWithChecksumPillar, to=<null>(default), version=31, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, fileID=default-test-file.txt, fileSize=0]
Result: Received event: add16815: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file
Step: Send an identification response with a PillarChecksumSpec element set, indicating that this is a checksum pillar.
Result: Received event: add16815: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Step: Send an normal identification response from pillar2.
Result: Received event: add16815: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: add16815: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2, Pillar1]
Result: Received event: add16815: PUT_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for put file
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@37936dac[correlationID=add16815-5ff2-4df1-8c58-7028b625c1d4, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=saltedReturnChecksumsWithChecksumPillar, to=<null>(default), version=31, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>(default), checksumRequestForNewFile=<null>(default)]
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@69e780ff[correlationID=add16815-5ff2-4df1-8c58-7028b625c1d4, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=saltedReturnChecksumsWithChecksumPillar, to=<null>(default), version=31, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, pillarID=Pillar2, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>(default), checksumRequestForNewFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@3feaa2b3[checksumType=HMAC_MD5, checksumSalt={-86}, otherChecksumType=<null>(default)]]
Test success: saltedReturnChecksumsWithChecksumPillar
Test starting: sameFileExistsOnOnePillar
Description: Tests that PutClient handles the presence of a file correctly, when the pillar returns a checksum equal the file being put (idempotent).
Step: Call putFile.
Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@14a7acd8[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@25e7a411[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2022-02-15T13:44:50.009+01:00], null, org.bitrepository.client.TestEventHandler@601d0bc8, TEST-AUDIT-TRAIL)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@4b378607[correlationID=d1dbc5c1-4919-42d1-9dfe-214e624033d6, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=sameFileExistsOnOnePillar, to=<null>(default), version=31, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, fileID=default-test-file.txt, fileSize=0]
Result: Received event: d1dbc5c1: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file
Step: Send a DUPLICATE_FILE_FAILURE response with a checksum equal to the one supplied to the client.
Result: Received event: d1dbc5c1: PUT_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, requestedChecksumResult=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@72cbd260[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@53b7580[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2022-02-15T13:44:50.012+01:00], File already existed on Pillar1
Step: Send an identification response from the second pillar.
Result: Received event: d1dbc5c1: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: d1dbc5c1: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: d1dbc5c1: PUT_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar2], Sending request for put file
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@6238d55b[correlationID=d1dbc5c1-4919-42d1-9dfe-214e624033d6, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=sameFileExistsOnOnePillar, to=<null>(default), version=31, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, pillarID=Pillar2, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@14a7acd8[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@25e7a411[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2022-02-15T13:44:50.009+01:00], checksumRequestForNewFile=<null>(default)]
Step: The client should proceed to send a putFileOperation request to the second pillar.
Step: Send a pillar complete event
Result: Received event: d1dbc5c1: PUT_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2, requestedChecksumResult=null
Result: Received event: d1dbc5c1: PUT_FILE for file default-test-file.txt: COMPLETE:
Test success: sameFileExistsOnOnePillar
Test starting: verifyPutClientFromFactory
Description: Testing the initialization through the ModifyComponentFactory.
Step: Use the ModifyComponentFactory to instantiate a PutFileClient.
Test success: verifyPutClientFromFactory
Starting testcase PutFileCmdTest
Test starting: checksumArgumentNonSaltAlgorithmWitoutSaltTest
Description: Test MD5 checksum without salt -> no failure
Test success: checksumArgumentNonSaltAlgorithmWitoutSaltTest
Test starting: checksumArgumentSaltAlgorithmWithSaltTest
Description: Test HMAC_SHA256 checksum with salt -> No failure
Test success: checksumArgumentSaltAlgorithmWithSaltTest
Test starting: defaultSuccessScenarioTest
Description: Tests simplest arguments for running the CmdLineClient
Test success: defaultSuccessScenarioTest
Test starting: missingChecksumWhenFileArgumentTest
Description: Tests the scenario, where no checksum argument is given, but a file is given.
Test success: missingChecksumWhenFileArgumentTest
Test starting: missingChecksumWhenURLArgumentTest
Description: Tests the scenario, where no checksum argument is given, but a URL is given.
Invalid argument: The URL argument requires also the checksum argument (-c).
Test success: missingChecksumWhenURLArgumentTest
Test starting: missingCollectionArgumentTest
Description: Tests the scenario, where the collection arguments is missing.
Takes the following arguments:
-s The path to the directory with the settings files for the client
-k The path to the file containing the private key.
-v Makes the client more verbose
-c The id for the collection to perform the operation on.
-i The id for the file to perform the operation on.
-p [OPTIONAL] The id of the pillar where the operation should be performed. If undefined the operation is performed on all pillars.
-f The path to the file, which needs to be uploaded. Is required, unless a URL is given.
-u The URL for the file to be put. Is required, unless the actual file is given.
-C The checksum for the file to be retrieved. Required if using an URL.
-R [OPTIONAL] The algorithm of checksum to request in the response from the pillars.
-S [OPTIONAL] The salt of checksum to request in the response. Requires the ChecksumType argument.
-d If this argument is present, then the file will be removed from the server, when the operation is complete.
Missing argument: Missing required option: c
Test success: missingCollectionArgumentTest
Test starting: missingFileIDWhenFileArgumentTest
Description: Tests the scenario, where no checksum argument is given, but a URL is given.
Test success: missingFileIDWhenFileArgumentTest
Test starting: missingFileIDWhenURLArgumentTest
Description: Tests the scenario, where no checksum argument is given, but a URL is given.
Invalid argument: The URL argument requires also the argument for the ID of the file (-i).
Test success: missingFileIDWhenURLArgumentTest
Test starting: missingFileOrURLArgumentTest
Description: Tests the scenario, where no arguments for file or url is given.
Invalid argument: Requires either the file argument (-f) or the URL argument (-u).
Test success: missingFileOrURLArgumentTest
Test starting: specificPillarArgumentTest
Description: Test argument for a specific pillar
Test success: specificPillarArgumentTest
Test starting: unknownPillarArgumentTest
Description: Testing against a non-existing pillar id -> Should fail
Invalid argument: Random1644929092823pillar is not a valid pillar for collection TwoPillarCollection
The collection contains the following pillars: [Pillar1, Pillar2]
Test success: unknownPillarArgumentTest
Test starting: urlSuccessScenarioTest
Description: Tests arguments for putting a file on a given URL
Test success: urlSuccessScenarioTest
Starting testcase ReplaceFileCmdTest
Test starting: URLSuccessScenarioTest
Description: Tests the scenario, where a URL instead of a file is used for the replacement file.
Test success: URLSuccessScenarioTest
Test starting: bothFileAndURLArgumentTest
Description: Tests the scenario, where both arguments for file or url is given.
Invalid argument: Cannot take both a file (-f) and an URL (-u) as argument.
Test success: bothFileAndURLArgumentTest
Test starting: checksumArgumentNonSaltAlgorithmWitoutSaltTest
Description: Test MD5 checksum without salt -> no failure
Test success: checksumArgumentNonSaltAlgorithmWitoutSaltTest
Test starting: checksumArgumentSaltAlgorithmWithSaltTest
Description: Test HMAC_SHA256 checksum with salt -> No failure
Test success: checksumArgumentSaltAlgorithmWithSaltTest
Test starting: defaultSuccessScenarioTest
Description: Tests simplest arguments for running the CmdLineClient
Test success: defaultSuccessScenarioTest
Test starting: missingChecksumForExistingFileWhenUsingFileArgumentTest
Description: Tests the scenario, where no checksum argument is given, but a File is given.
Invalid argument: Checksum argument (-C) are mandatory for Replace and replace operations as defined in RepositorySettings.
Test success: missingChecksumForExistingFileWhenUsingFileArgumentTest
Test starting: missingChecksumForExistingFileWhenUsingURLArgumentTest
Description: Tests the scenario, where no checksum argument is given, but a URL is given.
Invalid argument: Checksum argument (-C) are mandatory for Replace and replace operations as defined in RepositorySettings.
Test success: missingChecksumForExistingFileWhenUsingURLArgumentTest
Test starting: missingChecksumForNewFileWhenUsingFileArgumentTest
Description: Tests the scenario, where no checksum argument is given, but a File is given.
Test success: missingChecksumForNewFileWhenUsingFileArgumentTest
Test starting: missingChecksumForNewFileWhenUsingURLArgumentTest
Description: Tests the scenario, where no checksum argument is given, but a URL is given.
Invalid argument: The URL argument requires also the checksum argument for the file to replace with (-r).
Test success: missingChecksumForNewFileWhenUsingURLArgumentTest
Test starting: missingCollectionArgumentTest
Description: Tests the scenario, where the collection arguments is missing.
Takes the following arguments:
-s The path to the directory with the settings files for the client
-k The path to the file containing the private key.
-v Makes the client more verbose
-c The id for the collection to perform the operation on.
-i The id for the file to perform the operation on.
-p [OPTIONAL] The id of the pillar where the operation should be performed. If undefined the operation is performed on all pillars.
-C [OPTIONAL] The checksum of the file to be replaced.
-f The path to the new file for the replacement. Required unless using the URL argument.
-u The URL for the file to be retreived. Is required, unless the actual file is given.
-r The checksum for the file to replace with. Required when using the URL argument.
-R [OPTIONAL] The algorithm of checksum to request in the response from the pillars.
-S [OPTIONAL] The salt of checksum to request in the response. Requires the ChecksumType argument.
-d If this argument is present, then the file will be removed from the server, when the operation is complete.
Missing argument: Missing required option: c
Test success: missingCollectionArgumentTest
Test starting: missingFileIDWhenFileArgumentTest
Description: Tests the scenario, where no checksum argument is given, but a URL is given.
Test success: missingFileIDWhenFileArgumentTest
Test starting: missingFileIDWhenURLArgumentTest
Description: Tests the scenario, where no checksum argument is given, but a URL is given.
Invalid argument: The URL argument requires also the argument for the ID of the file (-i).
Test success: missingFileIDWhenURLArgumentTest
Test starting: missingFileOrURLArgumentTest
Description: Tests the scenario, where no arguments for file or url is given.
Invalid argument: Requires either the file argument (-f) or the URL argument (-u).
Test success: missingFileOrURLArgumentTest
Test starting: missingPillarArgumentTest
Description: Tests the different scenarios, with the pillar argument.
Invalid argument: The pillar argument (-p) must defined for the Replace operation, only single pillar Replaces are allowed
Test success: missingPillarArgumentTest
Test starting: unknownPillarArgumentTest
Step: Testing against a non-existing pillar id
Invalid argument: Random1644929095722pillar is not a valid pillar for collection TwoPillarCollection
The collection contains the following pillars: [Pillar1, Pillar2]
Test success: unknownPillarArgumentTest
Starting testcase ChecksumExtractionUtilsTest
Test starting: testDefaultChecksumSpec
Description: Test that the default checksum is retrieved when no arguments are given.
Test success: testDefaultChecksumSpec
Test starting: testDefaultChecksumSpecWithSaltArgument
Description: Test that the HMAC version of default checksum is retrieved when the salt arguments are given.
Test success: testDefaultChecksumSpecWithSaltArgument
Test starting: testNonSaltChecksumSpecWithSaltArgument
Description: Test that a salt checksum type is retrieved even though a non-salt checksum algorithm it is given as argument, but a salt argument also is given.
Test success: testNonSaltChecksumSpecWithSaltArgument
Test starting: testNonSaltChecksumSpecWithoutSaltArgument
Description: Test that a non-salt checksum type is retrieved when it is given as argument, and no salt arguments are given.
Test success: testNonSaltChecksumSpecWithoutSaltArgument
Test starting: testSaltChecksumSpecWithSaltArgument
Description: Test that a salt checksum type is retrieved when the salt checksum algorithm it is given as argument, and a salt argument also is given.
Test success: testSaltChecksumSpecWithSaltArgument
Test starting: testSaltChecksumSpecWithoutSaltArgument
Description: Test that a non-salt checksum type is retrieved even though a salt checksum algorithm it is given as argument, but no salt argument also is given.
Test success: testSaltChecksumSpecWithoutSaltArgument
Starting testcase GetFileIDsCmdTest
Test starting: defaultSuccessScenarioTest
Description: Tests simplest arguments for running the CmdLineClient
Test success: defaultSuccessScenarioTest
Test starting: fileArgumentTest
Description: Tests the argument for a specific file.
Test success: fileArgumentTest
Test starting: missingCollectionArgumentTest
Description: Tests the scenario, where the collection arguments is missing.
Takes the following arguments:
-s The path to the directory with the settings files for the client
-k The path to the file containing the private key.
-v Makes the client more verbose
-c The id for the collection to perform the operation on.
-i The id for the file to perform the operation on.
-p [OPTIONAL] The id of the pillar where the operation should be performed. If undefined the operation is performed on all pillars.
Missing argument: Missing required option: c
Test success: missingCollectionArgumentTest
Test starting: specificPillarArgumentTest
Description: Test argument for a specific pillar
Test success: specificPillarArgumentTest
Test starting: unknownPillarArgumentTest
Description: Testing against a non-existing pillar id -> Should fail
Invalid argument: Random1644929098665pillar is not a valid pillar for collection TwoPillarCollection
The collection contains the following pillars: [Pillar1, Pillar2]
Test success: unknownPillarArgumentTest
Starting testcase ReplaceFileClientComponentTest
Test starting: replaceClientIdentificationTimeout
Description: Tests the handling of a failed identification for the ReplaceClient
Step: Initialise the number of pillars and the DeleteClient. Sets the identification timeout to 100 ms.
Step: Request a file to be replaced on the default pillar.
Stimuli: replaceFile(default-test-file.txt, Pillar1, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@3e7628bc[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7bcc0392[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1106798e[checksumType=SHA1, checksumSalt=<null>(default), otherChecksumType=<null>(default)], file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, 10, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@46c421a1[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7bcc0392[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1106798e[checksumType=SHA1, checksumSalt=<null>(default), otherChecksumType=<null>(default)], org.bitrepository.client.TestEventHandler@49f8c20d, null
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileRequest@54e8465b[correlationID=34ef3349-f574-4788-87fd-6d83c285f411, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-ReplaceFileClientComponentTest-cibuild01, from=replaceClientIdentificationTimeout, to=Pillar1, version=31, minVersion=24, auditTrailInformation=<null>(default), fileID=default-test-file.txt, fileSize=<null>(default)]
Result: Received event: 34ef3349: REPLACE_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for replace file
Step: Do not respond. Just await the timeout.
Result: Received event: 34ef3349: REPLACE_FILE for file default-test-file.txt: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar1]
Result: Received event: 34ef3349: REPLACE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor
Result: Received event: 34ef3349: REPLACE_FILE for file default-test-file.txt: FAILED: , Unable to continue operation, contributors unavailable.
13:44:58.992 ERROR o.b.m.r.c.IdentifyPillarsForReplaceFile - Failing conversation 'ReplaceFileConversationContext{collectionID='TwoPillarCollection', conversationID='34ef3349-f574-4788-87fd-6d83c285f411', clientID='replaceClientIdentificationTimeout', fileID='default-test-file.txt', contributors=[Pillar1], monitor=ConversationEventMonitor{, collectionID='TwoPillarCollection', conversationID='34ef3349', operationType=REPLACE_FILE, fileID='default-test-file.txt', eventHandler=org.bitrepository.client.TestEventHandler@49f8c20d, contributorCompleteEvents=[], contributorFailedEvents=[34ef3349: REPLACE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor], failOnComponentFailure=true}, auditTrailInformation='null', state=org.bitrepository.client.conversation.FinishedState@6bd8e988, checksumPillars=[]}' with exception
org.bitrepository.common.exceptions.UnableToFinishException: Unable to continue operation, contributors unavailable.
at org.bitrepository.client.conversation.IdentifyingState.completeState(IdentifyingState.java:76)
at org.bitrepository.client.conversation.GeneralConversationState.changeState(GeneralConversationState.java:147)
at org.bitrepository.client.conversation.GeneralConversationState.access$100(GeneralConversationState.java:48)
at org.bitrepository.client.conversation.GeneralConversationState$TimeoutHandler.run(GeneralConversationState.java:134)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Test success: replaceClientIdentificationTimeout
Test starting: replaceClientOperationTimeout
Description: Tests the handling of a failed operation for the ReplaceClient
Step: Initialise the number of pillars and the DeleteClient. Sets the operation timeout to 100 ms.
Step: Request a file to be replaced on the default pillar.
Stimuli: replaceFile(default-test-file.txt, Pillar1, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@37eaad10[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@65fd262d[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@9a62f68[checksumType=SHA1, checksumSalt=<null>(default), otherChecksumType=<null>(default)], file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, 10, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@3e6a266f[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@65fd262d[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@9a62f68[checksumType=SHA1, checksumSalt=<null>(default), otherChecksumType=<null>(default)], org.bitrepository.client.TestEventHandler@5c8a9e9f, null
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileRequest@504a076d[correlationID=878aa5c3-68fb-4315-9ce6-97c64cf7fc29, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-ReplaceFileClientComponentTest-cibuild01, from=replaceClientOperationTimeout, to=Pillar1, version=31, minVersion=24, auditTrailInformation=<null>(default), fileID=default-test-file.txt, fileSize=<null>(default)]
Result: Received event: 878aa5c3: REPLACE_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for replace file
Step: Make response for the pillar.
Result: Received event: 878aa5c3: REPLACE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 878aa5c3: REPLACE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 878aa5c3: REPLACE_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for replace file
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.ReplaceFileRequest@f6fad5d[correlationID=878aa5c3-68fb-4315-9ce6-97c64cf7fc29, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-ReplaceFileClientComponentTest-cibuild01, from=replaceClientOperationTimeout, to=Pillar1, version=31, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@37eaad10[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@65fd262d[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@9a62f68[checksumType=SHA1, checksumSalt=<null>(default), otherChecksumType=<null>(default)], fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=10, checksumDataForNewFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@3e6a266f[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@65fd262d[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], checksumRequestForNewFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@9a62f68[checksumType=SHA1, checksumSalt=<null>(default), otherChecksumType=<null>(default)]]
Step: Validate the steps of the ReplaceClient by going through the events.
Step: Do not respond. Just await the timeout.
Result: Received event: 878aa5c3: REPLACE_FILE for file default-test-file.txt: FAILED: , Failed to receive responses from all contributors before timeout(100ms). Missing contributors [Pillar1]
13:44:59.205 ERROR o.b.m.r.conversation.ReplacingFile - Failing conversation 'ReplaceFileConversationContext{collectionID='TwoPillarCollection', conversationID='878aa5c3-68fb-4315-9ce6-97c64cf7fc29', clientID='replaceClientOperationTimeout', fileID='default-test-file.txt', contributors=[Pillar1], monitor=ConversationEventMonitor{, collectionID='TwoPillarCollection', conversationID='878aa5c3', operationType=REPLACE_FILE, fileID='default-test-file.txt', eventHandler=org.bitrepository.client.TestEventHandler@5c8a9e9f, contributorCompleteEvents=[], contributorFailedEvents=[], failOnComponentFailure=true}, auditTrailInformation='null', state=org.bitrepository.client.conversation.FinishedState@74e69d2c, checksumPillars=[]}' with exception
org.bitrepository.common.exceptions.UnableToFinishException: Failed to receive responses from all contributors before timeout(100ms). Missing contributors [Pillar1]
at org.bitrepository.client.conversation.PerformingOperationState.logStateTimeout(PerformingOperationState.java:82)
at org.bitrepository.client.conversation.GeneralConversationState$TimeoutHandler.run(GeneralConversationState.java:133)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Test success: replaceClientOperationTimeout
Test starting: replaceClientPillarFailed
Description: Tests the handling of a operation failure for the ReplaceClient.
Step: Initialise the number of pillars to one
Step: Request a file to be replaced on the default pillar.
Stimuli: replaceFile(default-test-file.txt, Pillar1, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@b868353[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1b37576[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@65c9d689[checksumType=SHA1, checksumSalt=<null>(default), otherChecksumType=<null>(default)], file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, 0, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@10e1ebd5[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1b37576[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@65c9d689[checksumType=SHA1, checksumSalt=<null>(default), otherChecksumType=<null>(default)], org.bitrepository.client.TestEventHandler@2f426e81, null
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileRequest@3540b6da[correlationID=5b7173c9-16d6-4d7d-b58d-e390569b48e3, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-ReplaceFileClientComponentTest-cibuild01, from=replaceClientPillarFailed, to=Pillar1, version=31, minVersion=24, auditTrailInformation=<null>(default), fileID=default-test-file.txt, fileSize=<null>(default)]
Result: Received event: 5b7173c9: REPLACE_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for replace file
Step: Make response for the pillar.
Result: Received event: 5b7173c9: REPLACE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 5b7173c9: REPLACE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 5b7173c9: REPLACE_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for replace file
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.ReplaceFileRequest@1b6ac31[correlationID=5b7173c9-16d6-4d7d-b58d-e390569b48e3, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-ReplaceFileClientComponentTest-cibuild01, from=replaceClientPillarFailed, to=Pillar1, version=31, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@b868353[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1b37576[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@65c9d689[checksumType=SHA1, checksumSalt=<null>(default), otherChecksumType=<null>(default)], fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@10e1ebd5[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1b37576[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], checksumRequestForNewFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@65c9d689[checksumType=SHA1, checksumSalt=<null>(default), otherChecksumType=<null>(default)]]
Step: Validate the steps of the ReplaceClient by going through the events.
Step: Send a failed response message to the ReplaceClient.
Result: Received event: 5b7173c9: REPLACE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE, Verifying that a failure can be understood!
Result: Received event: 5b7173c9: REPLACE_FILE for file default-test-file.txt: FAILED: , Failed operation. Cause(s):
[5b7173c9: REPLACE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE, Verifying that a failure can be understood!]
Test success: replaceClientPillarFailed
Test starting: replaceClientTester
Description: Tests the ReplaceFileClient. Makes a whole conversation for the replace client for a 'good' scenario.
Step: Initialise the number of pillars to one
Step: Request a file to be replaced on all pillars (which means only the default pillar).
Stimuli: replaceFile(default-test-file.txt, Pillar1, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@3dcd951b[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2b5bd83c[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@41ecb4f2[checksumType=SHA1, checksumSalt=<null>(default), otherChecksumType=<null>(default)], file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, 10, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@4a47c29a[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2b5bd83c[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@41ecb4f2[checksumType=SHA1, checksumSalt=<null>(default), otherChecksumType=<null>(default)], org.bitrepository.client.TestEventHandler@1b73e384, null
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileRequest@6e9c42ee[correlationID=4e4e6d9e-b80b-4329-8364-43add3c0e080, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-ReplaceFileClientComponentTest-cibuild01, from=replaceClientTester, to=Pillar1, version=31, minVersion=24, auditTrailInformation=<null>(default), fileID=default-test-file.txt, fileSize=<null>(default)]
Result: Received event: 4e4e6d9e: REPLACE_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for replace file
Step: Make response for the pillar.
Result: Received event: 4e4e6d9e: REPLACE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 4e4e6d9e: REPLACE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 4e4e6d9e: REPLACE_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for replace file
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.ReplaceFileRequest@3e54782d[correlationID=4e4e6d9e-b80b-4329-8364-43add3c0e080, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-ReplaceFileClientComponentTest-cibuild01, from=replaceClientTester, to=Pillar1, version=31, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@3dcd951b[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2b5bd83c[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@41ecb4f2[checksumType=SHA1, checksumSalt=<null>(default), otherChecksumType=<null>(default)], fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=10, checksumDataForNewFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@4a47c29a[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2b5bd83c[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], checksumRequestForNewFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@41ecb4f2[checksumType=SHA1, checksumSalt=<null>(default), otherChecksumType=<null>(default)]]
Step: Validate the steps of the ReplaceClient by going through the events.
Step: The pillar sends a progress response to the ReplaceClient.
Result: Received event: 4e4e6d9e: REPLACE_FILE for file default-test-file.txt: PROGRESS: ContributorID Pillar1, First test progress response message
Step: Send a final response message to the ReplaceClient.
Result: Received event: 4e4e6d9e: REPLACE_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, checksum for new file: 'org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@4a47c29a[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2b5bd83c[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00]',checksum for replaced file: 'null'
Result: Received event: 4e4e6d9e: REPLACE_FILE for file default-test-file.txt: COMPLETE:
Test success: replaceClientTester
Test starting: saltedReturnChecksumsForNewFileWithChecksumPillar
Description: Tests that the ReplaceClient handles the presence of a ChecksumPillar correctly, when a salted return checksum (which a checksum pillar can't provide) is requested for the new file.
Step: Call replaceFile while requesting a salted checksum to be returned.
Stimuli: replaceFile(default-test-file.txt, Pillar1, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@29739d16[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@54bf393c[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], null, file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, 0, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@348f0a0[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@54bf393c[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@46ea9b55[checksumType=MD5, checksumSalt={-86}, otherChecksumType=<null>(default)], org.bitrepository.client.TestEventHandler@734425b3, null
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileRequest@5e9f843e[correlationID=05850381-1a36-4599-921b-f3943a293f46, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-ReplaceFileClientComponentTest-cibuild01, from=saltedReturnChecksumsForNewFileWithChecksumPillar, to=Pillar1, version=31, minVersion=24, auditTrailInformation=<null>(default), fileID=default-test-file.txt, fileSize=<null>(default)]
Result: Received event: 05850381: REPLACE_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for replace file
Step: Send an identification response with a PillarChecksumSpec element set, indicating that this is a checksum pillar.
Result: Received event: 05850381: REPLACE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 05850381: REPLACE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 05850381: REPLACE_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for replace file
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.ReplaceFileRequest@8b4a289[correlationID=05850381-1a36-4599-921b-f3943a293f46, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-ReplaceFileClientComponentTest-cibuild01, from=saltedReturnChecksumsForNewFileWithChecksumPillar, to=Pillar1, version=31, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@29739d16[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@54bf393c[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], checksumRequestForExistingFile=<null>(default), fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@348f0a0[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@54bf393c[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], checksumRequestForNewFile=<null>(default)]
Test success: saltedReturnChecksumsForNewFileWithChecksumPillar
Test starting: verifyReplaceFileClientFromFactory
Description: Testing the initialization through the ModifyComponentFactory.
Step: Use the ModifyComponentFactory to instantiate a ReplaceFileClient.
Test success: verifyReplaceFileClientFromFactory
Starting testcase UnexpectedResponseExceptionTest
Test starting: testUnexpectedResponse
Description: Test the instantiation of the exception
Step: Setup
Step: Try to throw such an exception
Step: Throw the exception with an embedded exception
Test success: testUnexpectedResponse
Starting testcase GetChecksumsCmdTest
Test starting: checksumArgumentNonSaltAlgorithmWitoutSaltTest
Description: Test MD5 checksum without salt -> no failure
Test success: checksumArgumentNonSaltAlgorithmWitoutSaltTest
Test starting: checksumArgumentSaltAlgorithmWithSaltTest
Description: Test HMAC_SHA256 checksum with salt -> No failure
Test success: checksumArgumentSaltAlgorithmWithSaltTest
Test starting: defaultSuccessScenarioTest
Description: Tests simplest arguments for running the CmdLineClient
Test success: defaultSuccessScenarioTest
Test starting: fileArgumentTest
Description: Tests the argument for a specific file.
Test success: fileArgumentTest
Test starting: missingCollectionArgumentTest
Description: Tests the scenario, where the collection arguments is missing.
Takes the following arguments:
-s The path to the directory with the settings files for the client
-k The path to the file containing the private key.
-v Makes the client more verbose
-c The id for the collection to perform the operation on.
-i The id for the file to perform the operation on.
-p [OPTIONAL] The id of the pillar where the operation should be performed. If undefined the operation is performed on all pillars.
-R [OPTIONAL] The algorithm of checksum to request in the response from the pillars. If no such argument is given, then the default from settings is retrieved.
-S [OPTIONAL] The salt of checksum to request in the response. Requires the ChecksumType argument.
Missing argument: Missing required option: c
Test success: missingCollectionArgumentTest
Test starting: specificPillarArgumentTest
Description: Test argument for a specific pillar
Test success: specificPillarArgumentTest
Test starting: unknownPillarArgumentTest
Description: Testing against a non-existing pillar id -> Should fail
Invalid argument: Random1644929100952pillar is not a valid pillar for collection TwoPillarCollection
The collection contains the following pillars: [Pillar1, Pillar2]
Test success: unknownPillarArgumentTest
Starting testcase GetFileCmdTest
Test starting: defaultSuccessScenarioTest
Description: Tests simplest arguments for running the CmdLineClient
Test success: defaultSuccessScenarioTest
Test starting: missingCollectionArgumentTest
Description: Tests the scenario, where the collection arguments is missing.
Takes the following arguments:
-s The path to the directory with the settings files for the client
-k The path to the file containing the private key.
-v Makes the client more verbose
-c The id for the collection to perform the operation on.
-i The id for the file to perform the operation on.
-p [OPTIONAL] The id of the pillar where the operation should be performed. If undefined the operation is performed on all pillars.
-l [OPTIONAL] The location where the file should be placed (either total path or directory). If no argument, then the file is placed in the directory where the script is located.
Missing argument: Missing required option: c
Test success: missingCollectionArgumentTest
Test starting: missingFileIDArgumentTest
Description: Tests the scenario, where no arguments for file id argument is given.
Takes the following arguments:
-s The path to the directory with the settings files for the client
-k The path to the file containing the private key.
-v Makes the client more verbose
-c The id for the collection to perform the operation on.
-i The id for the file to perform the operation on.
-p [OPTIONAL] The id of the pillar where the operation should be performed. If undefined the operation is performed on all pillars.
-l [OPTIONAL] The location where the file should be placed (either total path or directory). If no argument, then the file is placed in the directory where the script is located.
Missing argument: Missing required option: i
Test success: missingFileIDArgumentTest
Test starting: specificPillarArgumentTest
Description: Test argument for a specific pillar
Test success: specificPillarArgumentTest
Test starting: unknownPillarArgumentTest
Description: Testing against a non-existing pillar id -> Should fail
Invalid argument: Random1644929101683pillar is not a valid pillar for collection TwoPillarCollection
The collection contains the following pillars: [Pillar1, Pillar2]
Test success: unknownPillarArgumentTest
Starting testcase AuditTrailQueryTest
Test starting: testBothSequenceNumberFailure
Description: Test the creation of a AuditTrailQuery with both SequenceNumber, where max is smalle than min.
Test success: testBothSequenceNumberFailure
Test starting: testBothSequenceNumberSuccess
Description: Test the creation of a AuditTrailQuery with both SequenceNumber, where max is larger than min.
Test success: testBothSequenceNumberSuccess
Test starting: testNoSequenceNumbers
Description: Test that a AuditTrailQuery can be created without any sequence numbers.
Test success: testNoSequenceNumbers
Test starting: testOnlyMinSequenceNumber
Description: Test the creation of a AuditTrailQuery with only the minSequenceNumber
Test success: testOnlyMinSequenceNumber
Starting testcase GetStatusClientComponentTest
Test starting: getAllStatuses
Description: Tests the simplest case of getting status for all contributers.
Step: Create a GetStatusClient.
Step: Retrieve from all contributors in the collection
Stimuli: Calling getAuditTrails()
Result: Received event: 02723610: GET_STATUS: IDENTIFY_REQUEST_SENT: , Identifying contributors for getting status
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetStatusRequest@370c1ea2[correlationID=02723610-440e-4d5c-97ed-bdb8b74fe3f6, collectionID=<null>(default), destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetStatusClientComponentTest-cibuild01, from=getAllStatuses, to=<null>(default), version=31, minVersion=24, auditTrailInformation=]
Step: Send a identifyResponse from each pillar
Result: Received event: 02723610: GET_STATUS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 02723610: GET_STATUS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 02723610: GET_STATUS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2, Pillar1]
Result: Received event: 02723610: GET_STATUS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending GetStatusRequest
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetStatusRequest@6e73382b[correlationID=02723610-440e-4d5c-97ed-bdb8b74fe3f6, collectionID=<null>(default), destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetStatusClientComponentTest-cibuild01, from=getAllStatuses, to=<null>(default), version=31, minVersion=24, auditTrailInformation=, contributor=Pillar1]
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetStatusRequest@5de8c041[correlationID=02723610-440e-4d5c-97ed-bdb8b74fe3f6, collectionID=<null>(default), destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetStatusClientComponentTest-cibuild01, from=getAllStatuses, to=<null>(default), version=31, minVersion=24, auditTrailInformation=, contributor=Pillar2]
Step: Send a final response from pillar 1
Result: Received event: 02723610: GET_STATUS: COMPONENT_COMPLETE: ContributorID Pillar1, resulting status: org.bitrepository.bitrepositoryelements.ResultingStatus@2be796b7[statusInfo=org.bitrepository.bitrepositoryelements.StatusInfo@19ab0aa6[statusCode=OK, statusText=Everythings fine..], statusTimestamp=2022-02-15T13:45:01.947+01:00]
Step: Send a final response from pillar 2
Result: Received event: 02723610: GET_STATUS: COMPONENT_COMPLETE: ContributorID Pillar2, resulting status: org.bitrepository.bitrepositoryelements.ResultingStatus@53beda24[statusInfo=org.bitrepository.bitrepositoryelements.StatusInfo@58e975e1[statusCode=OK, statusText=Everythings fine..], statusTimestamp=2022-02-15T13:45:01.949+01:00]
Result: Received event: 02723610: GET_STATUS: COMPLETE:
Test success: getAllStatuses
Test starting: incompleteSetOfIdendifyResponses
Description: Verify that the GetStatus client works correct without receiving responses from all contributers.
Step: Configure 1 second timeout for identifying contributers. The default 2 contributers collection is used
Stimuli: Calling getAuditTrails()
Result: Received event: 9f759afa: GET_STATUS: IDENTIFY_REQUEST_SENT: , Identifying contributors for getting status
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetStatusRequest@19008513[correlationID=9f759afa-e523-4028-8cb2-3db82bd5906e, collectionID=<null>(default), destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetStatusClientComponentTest-cibuild01, from=incompleteSetOfIdendifyResponses, to=<null>(default), version=31, minVersion=24, auditTrailInformation=]
Step: Send a identifyResponse from pillar 1
Result: Received event: 9f759afa: GET_STATUS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Step: Wait for timeout event
Result: Received event: 9f759afa: GET_STATUS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar2]
Result: Received event: 9f759afa: GET_STATUS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
Result: Received event: 9f759afa: GET_STATUS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 9f759afa: GET_STATUS: REQUEST_SENT: ContributorID [Pillar1], Sending GetStatusRequest
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetStatusRequest@3767af6d[correlationID=9f759afa-e523-4028-8cb2-3db82bd5906e, collectionID=<null>(default), destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetStatusClientComponentTest-cibuild01, from=incompleteSetOfIdendifyResponses, to=<null>(default), version=31, minVersion=24, auditTrailInformation=, contributor=Pillar1]
Test success: incompleteSetOfIdendifyResponses
Test starting: verifyGetStatusClientFromFactory
Test success: verifyGetStatusClientFromFactory
Starting testcase GetFileClientComponentTest
Test starting: chooseFastestPillarGetFileClient
Description: Set the GetClient to retrieve a file as fast as possible, where it has to choose between to pillars with different times. The messages should be delivered at the same time.
Step: Create a GetFileClient configured to use a fast and a slow pillar.
Step: Defining the variables for the GetFileClient and defining them in the configuration
Step: Make the GetClient ask for fastest pillar.
Stimuli: Calling getFileFromFastestPillar(default-test-file.txt, file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileRequest@78a20bb8[correlationID=1f974c4e-560d-4bb5-ae25-a2076818712e, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=chooseFastestPillarGetFileClient, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), fileID=default-test-file.txt]
Result: Received event: 1f974c4e: GET_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetFile
Step: Three pillars send responses. First an average timeToDeliver, then a fast timeToDeliver and last a slow timeToDeliver.
Result: Received event: 1f974c4e: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID THE-AVERAGE-PILLAR
Result: Received event: 1f974c4e: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID THE-FAST-PILLAR
Result: Received event: 1f974c4e: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID THE-SLOW-PILLAR
Result: Received event: 1f974c4e: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [THE-FAST-PILLAR]
Result: Received event: 1f974c4e: GET_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID SelectedComponentInfo: componentID=THE-FAST-PILLAR, componentTopic=Pillar1_topic-cibuild01, Sending GetFileRequest to
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileRequest@7a22dd94[correlationID=1f974c4e-560d-4bb5-ae25-a2076818712e, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=chooseFastestPillarGetFileClient, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), pillarID=THE-FAST-PILLAR, fileID=default-test-file.txt, filePart=<null>(default), fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt]
Test success: chooseFastestPillarGetFileClient
Test starting: conversationTimeout
Description: Tests the the GetFileClient handles lack of IdentifyPillarResponses gracefully
Step: Set the number of pillars to 100ms and a 300 ms timeout for the conversation.
Step: Request the delivery of a file from a specific pillar. A callback listener should be supplied.
Stimuli: Calling getFileFromSpecificPillar(default-test-file.txt, file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, Pillar1)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileRequest@2fb476dd[correlationID=ea6a7ebf-3e41-4c1d-9fc3-103954d1f5da, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=conversationTimeout, to=Pillar1, version=31, minVersion=24, auditTrailInformation=<null>(default), fileID=default-test-file.txt]
Result: Received event: ea6a7ebf: GET_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetFile
Step: The pillar sends a response to the identify message.
Result: Received event: ea6a7ebf: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: ea6a7ebf: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: ea6a7ebf: GET_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID SelectedComponentInfo: componentID=Pillar1, componentTopic=Pillar1_topic-cibuild01, Sending GetFileRequest to
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileRequest@4fa8e353[correlationID=ea6a7ebf-3e41-4c1d-9fc3-103954d1f5da, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=conversationTimeout, to=Pillar1, version=31, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileID=default-test-file.txt, filePart=<null>(default), fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt]
Step: Wait for 1 second
13:45:04.583 WARN o.b.c.c.m.CollectionBasedConversationMediator - Failing timed out conversation ea6a7ebf-3e41-4c1d-9fc3-103954d1f5da (Age 997ms)
Result: Received event: ea6a7ebf: GET_FILE for file default-test-file.txt: FAILED: , Failing timed out conversation ea6a7ebf-3e41-4c1d-9fc3-103954d1f5da
Test success: conversationTimeout
Test starting: failureDuringPerform
Description: Verify that the GetFile reports a failed operation, in case of a component failing during the performing phase.
Step: Request a getFile from the fastest pillar.
Stimuli: Calling getFileFromFastestPillar(default-test-file.txt, file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileRequest@44752276[correlationID=1aaaca75-3b42-4ae1-9e36-f185125cdf7d, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=failureDuringPerform, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), fileID=default-test-file.txt]
Result: Received event: 1aaaca75: GET_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetFile
Step: Send a identification response from pillar1 and pillar2 with pillar1 the fastest.
Result: Received event: 1aaaca75: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 1aaaca75: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 1aaaca75: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 1aaaca75: GET_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID SelectedComponentInfo: componentID=Pillar1, componentTopic=Pillar1_topic-cibuild01, Sending GetFileRequest to
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileRequest@677c98e1[correlationID=1aaaca75-3b42-4ae1-9e36-f185125cdf7d, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=failureDuringPerform, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileID=default-test-file.txt, filePart=<null>(default), fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt]
Step: Send a failure response from pillar1
Result: Received event: 1aaaca75: GET_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE
Result: Received event: 1aaaca75: GET_FILE for file default-test-file.txt: FAILED: , Failed to get file from Pillar1, org.bitrepository.bitrepositoryelements.ResponseInfo@34a33be8[responseCode=FAILURE, responseText=<null>(default)]
13:45:04.745 ERROR o.b.a.g.conversation.GettingFile - Failing conversation 'GetFileConversationContext{collectionID='TwoPillarCollection', conversationID='1aaaca75-3b42-4ae1-9e36-f185125cdf7d', clientID='failureDuringPerform', fileID='default-test-file.txt', contributors=[Pillar1, Pillar2], monitor=ConversationEventMonitor{, collectionID='TwoPillarCollection', conversationID='1aaaca75', operationType=GET_FILE, fileID='default-test-file.txt', eventHandler=org.bitrepository.client.TestEventHandler@5928c998, contributorCompleteEvents=[], contributorFailedEvents=[1aaaca75: GET_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE], failOnComponentFailure=false}, auditTrailInformation='null', state=org.bitrepository.client.conversation.FinishedState@566a052e, checksumPillars=[]}' with exception
org.bitrepository.common.exceptions.UnableToFinishException: Failed to get file from Pillar1, org.bitrepository.bitrepositoryelements.ResponseInfo@34a33be8[responseCode=FAILURE, responseText=<null>(default)]
at org.bitrepository.access.getfile.conversation.GettingFile.handleFailureResponse(GettingFile.java:78)
at org.bitrepository.client.conversation.PerformingOperationState.processMessage(PerformingOperationState.java:70)
at org.bitrepository.client.conversation.GeneralConversationState.handleMessage(GeneralConversationState.java:110)
at org.bitrepository.client.conversation.StateBasedConversation.onMessage(StateBasedConversation.java:53)
at org.bitrepository.client.conversation.mediator.CollectionBasedConversationMediator.onMessage(CollectionBasedConversationMediator.java:136)
at org.bitrepository.protocol.messagebus.SimpleMessageBus.lambda$sendMessage$0(SimpleMessageBus.java:73)
at java.lang.Iterable.forEach(Iterable.java:75)
at org.bitrepository.protocol.messagebus.SimpleMessageBus.sendMessage(SimpleMessageBus.java:73)
at org.bitrepository.access.getfile.GetFileClientComponentTest.failureDuringPerform(GetFileClientComponentTest.java:579)
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.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:134)
at org.testng.internal.TestInvoker.invokeMethod(TestInvoker.java:597)
at org.testng.internal.TestInvoker.invokeTestMethod(TestInvoker.java:173)
at org.testng.internal.MethodRunner.runInSequence(MethodRunner.java:46)
at org.testng.internal.TestInvoker$MethodInvocationAgent.invoke(TestInvoker.java:816)
at org.testng.internal.TestInvoker.invokeTestMethods(TestInvoker.java:146)
at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:146)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:128)
at java.util.ArrayList.forEach(ArrayList.java:1249)
at org.testng.TestRunner.privateRun(TestRunner.java:766)
at org.testng.TestRunner.run(TestRunner.java:587)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:384)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:378)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:337)
at org.testng.SuiteRunner.run(SuiteRunner.java:286)
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:53)
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:96)
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1187)
at org.testng.TestNG.runSuitesLocally(TestNG.java:1109)
at org.testng.TestNG.runSuites(TestNG.java:1039)
at org.testng.TestNG.run(TestNG.java:1007)
at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:135)
at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:193)
at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:94)
at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:146)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:377)
at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:138)
at org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:465)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:451)
Test success: failureDuringPerform
Test starting: getFileClientWithChecksumPillarInvolved
Description: Verify that the GetFile works correctly when a checksum pillar respond.
Step: Call getFile form fastest pillar.
Stimuli: Calling getFileFromFastestPillar(default-test-file.txt, file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileRequest@58763549[correlationID=b5264dd9-1e9b-4f89-97e8-fa1e22f5f022, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=getFileClientWithChecksumPillarInvolved, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), fileID=default-test-file.txt]
Result: Received event: b5264dd9: GET_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetFile
Step: Send a identification response from pillar1 with a REQUEST_NOT_SUPPORTED response code.
Step: Send a identification response from pillar2 with a IDENTIFICATION_POSITIVE response code .
Result: Received event: b5264dd9: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: b5264dd9: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: b5264dd9: GET_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID SelectedComponentInfo: componentID=Pillar2, componentTopic=Pillar2_topic-cibuild01, Sending GetFileRequest to
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileRequest@777d7ac1[correlationID=b5264dd9-1e9b-4f89-97e8-fa1e22f5f022, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=getFileClientWithChecksumPillarInvolved, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar2, fileID=default-test-file.txt, filePart=<null>(default), fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt]
Step: Verify that the client continues to the performing phase.
Step: Send a final response upload message
Result: Received event: b5264dd9: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2
Result: Received event: b5264dd9: GET_FILE for file default-test-file.txt: COMPLETE:
Test success: getFileClientWithChecksumPillarInvolved
Test starting: getFileClientWithIdentifyTimeout
Description: Verify that the GetFile works correct without receiving responses from all pillars.
Added fixture: Set the identification timeout to 500ms
Step: Call getFile form fastest pillar.
Stimuli: Calling getFileFromFastestPillar(default-test-file.txt, file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileRequest@8ac656c[correlationID=8a05058c-4fc4-4046-9f69-540a56925802, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=getFileClientWithIdentifyTimeout, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), fileID=default-test-file.txt]
Result: Received event: 8a05058c: GET_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetFile
Step: Send a identification response from pillar1.
Result: Received event: 8a05058c: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Step: Wait 1 second.
Result: Received event: 8a05058c: GET_FILE for file default-test-file.txt: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar2]
Result: Received event: 8a05058c: GET_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
Result: Received event: 8a05058c: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 8a05058c: GET_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID SelectedComponentInfo: componentID=Pillar1, componentTopic=Pillar1_topic-cibuild01, Sending GetFileRequest to
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileRequest@3cf06356[correlationID=8a05058c-4fc4-4046-9f69-540a56925802, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=getFileClientWithIdentifyTimeout, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileID=default-test-file.txt, filePart=<null>(default), fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt]
Step: Verify that the client continues to the performing phase.
Step: Send a final response upload message
Result: Received event: 8a05058c: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1
Result: Received event: 8a05058c: GET_FILE for file default-test-file.txt: COMPLETE:
Test success: getFileClientWithIdentifyTimeout
Test starting: getFileFromOtherCollection
Description: Tests the getFiles client will correctly try to get from a second collection if required
Added fixture: Configure collection1 to contain both pillars and collection 2 to only contain pillar2
Step: Request the getting of a file through the client for collection2
Stimuli: Calling getFileFromFastestPillar(default-test-file.txt, file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileRequest@2b8d1741[correlationID=8dd6fdff-fd50-4997-b3bc-998ce6799065, collectionID=SinglePillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=getFileFromOtherCollection, to=Pillar2, version=31, minVersion=24, auditTrailInformation=<null>(default), fileID=default-test-file.txt]
Result: Received event: 8dd6fdff: GET_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetFile
Step: Send an identification response from pillar2.
Result: Received event: 8dd6fdff: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 8dd6fdff: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: 8dd6fdff: GET_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID SelectedComponentInfo: componentID=Pillar2, componentTopic=Pillar2_topic-cibuild01, Sending GetFileRequest to
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileRequest@37e2e6a[correlationID=8dd6fdff-fd50-4997-b3bc-998ce6799065, collectionID=SinglePillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=getFileFromOtherCollection, to=Pillar2, version=31, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar2, fileID=default-test-file.txt, filePart=<null>(default), fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt]
Step: Send a complete event from the pillar
Result: Received event: 8dd6fdff: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2
Result: Received event: 8dd6fdff: GET_FILE for file default-test-file.txt: COMPLETE:
Test success: getFileFromOtherCollection
Test starting: getFileFromSpecificPillar
Description: Tests that the GetClient client works correctly when requesting a file from a specific pillar
Step: Request the delivery of a file from pillar2.
Stimuli: Calling getFileFromSpecificPillar(default-test-file.txt, file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, Pillar2)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileRequest@67ac21bc[correlationID=6dea2f2c-eff6-4a89-868e-fe603d0afc52, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=getFileFromSpecificPillar, to=Pillar2, version=31, minVersion=24, auditTrailInformation=AuditTrailInfo for getFileFromSpecificPillarTest, fileID=default-test-file.txt]
Result: Received event: 6dea2f2c: GET_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetFile
Step: Send a response from pillar1
Step: Send a response from pillar2
Result: Received event: 6dea2f2c: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 6dea2f2c: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: 6dea2f2c: GET_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID SelectedComponentInfo: componentID=Pillar2, componentTopic=Pillar2_topic-cibuild01, Sending GetFileRequest to
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileRequest@5121cd7f[correlationID=6dea2f2c-eff6-4a89-868e-fe603d0afc52, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=getFileFromSpecificPillar, to=Pillar2, version=31, minVersion=24, auditTrailInformation=AuditTrailInfo for getFileFromSpecificPillarTest, pillarID=Pillar2, fileID=default-test-file.txt, filePart=<null>(default), fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt]
Step: Send a GetFileProgressResponse.
Result: Received event: 6dea2f2c: GET_FILE for file default-test-file.txt: PROGRESS: ContributorID Pillar2, First test progress response message
Step: Send a GetFileFinalResponse.
Result: Received event: 6dea2f2c: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2
Result: Received event: 6dea2f2c: GET_FILE for file default-test-file.txt: COMPLETE:
Test success: getFileFromSpecificPillar
Test starting: getFileFromSpecificPillarWithFilePart
Description: Tests that the GetClient client works for a single pillar participates. Also validate, that the 'FilePart' can be used.
Step: Set the number of pillars to 1
Step: Request the delivery of a file from a specific pillar. A callback listener should be supplied.
Stimuli: Calling getFileFromSpecificPillar(default-test-file.txt, file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, Pillar1)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileRequest@4207c0f[correlationID=955fb78d-6f97-43f6-baa8-bc616b040dd0, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=getFileFromSpecificPillarWithFilePart, to=Pillar1, version=31, minVersion=24, auditTrailInformation=<null>(default), fileID=default-test-file.txt]
Result: Received event: 955fb78d: GET_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetFile
Step: The pillar sends a response to the identify message.
Result: Received event: 955fb78d: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 955fb78d: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 955fb78d: GET_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID SelectedComponentInfo: componentID=Pillar1, componentTopic=Pillar1_topic-cibuild01, Sending GetFileRequest to
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileRequest@171fea6f[correlationID=955fb78d-6f97-43f6-baa8-bc616b040dd0, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=getFileFromSpecificPillarWithFilePart, to=Pillar1, version=31, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar1, fileID=default-test-file.txt, filePart=org.bitrepository.bitrepositoryelements.FilePart@78fa7f84[partOffSet=1, partLength=10], fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt]
Step: The pillar sends a getFile response to the GetClient.
Result: Received event: 955fb78d: GET_FILE for file default-test-file.txt: PROGRESS: ContributorID Pillar1, First test progress response message
Step: The file is uploaded to the indicated url and the pillar sends a final response upload message
Result: Received event: 955fb78d: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1
Result: Received event: 955fb78d: GET_FILE for file default-test-file.txt: COMPLETE:
Test success: getFileFromSpecificPillarWithFilePart
Test starting: noIdentifyResponse
Description: Tests the the GetFileClient handles lack of IdentifyPillarResponses gracefully
Step: Set a 500 ms timeout for identifying pillar.
Step: Make the GetClient ask for fastest pillar.
Stimuli: Calling getFileFromFastestPillar(default-test-file.txt, file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileRequest@755af51e[correlationID=bcce214b-112f-4221-a21c-442fd0d30ad0, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=noIdentifyResponse, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), fileID=default-test-file.txt]
Result: Received event: bcce214b: GET_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetFile
Step: Wait for 1 seconds
Result: Received event: bcce214b: GET_FILE for file default-test-file.txt: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar1, Pillar2]
Result: Received event: bcce214b: GET_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor
Result: Received event: bcce214b: GET_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
Result: Received event: bcce214b: GET_FILE for file default-test-file.txt: FAILED: , Unable to continue operation, contributors unavailable.
13:45:07.439 ERROR o.b.a.g.c.IdentifyingPillarsForGetFile - Failing conversation 'GetFileConversationContext{collectionID='TwoPillarCollection', conversationID='bcce214b-112f-4221-a21c-442fd0d30ad0', clientID='noIdentifyResponse', fileID='default-test-file.txt', contributors=[Pillar1, Pillar2], monitor=ConversationEventMonitor{, collectionID='TwoPillarCollection', conversationID='bcce214b', operationType=GET_FILE, fileID='default-test-file.txt', eventHandler=org.bitrepository.client.TestEventHandler@104859e9, contributorCompleteEvents=[], contributorFailedEvents=[bcce214b: GET_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor, bcce214b: GET_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor], failOnComponentFailure=false}, auditTrailInformation='null', state=org.bitrepository.client.conversation.FinishedState@5007a931, checksumPillars=[]}' with exception
org.bitrepository.common.exceptions.UnableToFinishException: Unable to continue operation, contributors unavailable.
at org.bitrepository.client.conversation.IdentifyingState.completeState(IdentifyingState.java:76)
at org.bitrepository.client.conversation.GeneralConversationState.changeState(GeneralConversationState.java:147)
at org.bitrepository.client.conversation.GeneralConversationState.access$100(GeneralConversationState.java:48)
at org.bitrepository.client.conversation.GeneralConversationState$TimeoutHandler.run(GeneralConversationState.java:134)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Test success: noIdentifyResponse
Test starting: singleComponentFailureDuringIdentify
Description: Verify that the GetFile reports a complete (not failed), in case of a component failing during the identify phase.
Step: Call getFile from the fastest pillar.
Stimuli: Calling getFileFromFastestPillar(default-test-file.txt, file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileRequest@16241d1[correlationID=d0c63d7d-1246-4090-b8c5-06c697793d9e, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=singleComponentFailureDuringIdentify, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), fileID=default-test-file.txt]
Result: Received event: d0c63d7d: GET_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetFile
Step: Send a identification response from pillar1 with a IDENTIFICATION_NEGATIVE response code .
Result: Received event: d0c63d7d: GET_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: IDENTIFICATION_NEGATIVE
Step: Send a identification response from pillar2 with a IDENTIFICATION_POSITIVE response code .
Result: Received event: d0c63d7d: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: d0c63d7d: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: d0c63d7d: GET_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID SelectedComponentInfo: componentID=Pillar2, componentTopic=Pillar2_topic-cibuild01, Sending GetFileRequest to
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileRequest@4c76d705[correlationID=d0c63d7d-1246-4090-b8c5-06c697793d9e, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=singleComponentFailureDuringIdentify, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), pillarID=Pillar2, fileID=default-test-file.txt, filePart=<null>(default), fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt]
Step: Verify that the client continues to the performing phase.
Step: Send a final response upload message
Result: Received event: d0c63d7d: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2
Result: Received event: d0c63d7d: GET_FILE for file default-test-file.txt: COMPLETE:
Test success: singleComponentFailureDuringIdentify
Test starting: testNoSuchFileMultiplePillars
Description: Testing how a request for a non-existing file is handled when all pillars miss the file.
Step: Use the default 2 pillars.
Step: Call getFileFromFastestPillar.
Stimuli: Calling getFileFromFastestPillar(ERROR-NO-SUCH-FILE-ERROR, file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileRequest@33b33c3a[correlationID=241d1757-4ea4-45c7-a555-093c265eeda8, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=testNoSuchFileMultiplePillars, to=<null>(default), version=31, minVersion=24, auditTrailInformation=<null>(default), fileID=ERROR-NO-SUCH-FILE-ERROR]
Result: Received event: 241d1757: GET_FILE for file ERROR-NO-SUCH-FILE-ERROR: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetFile
Step: Both pillars sends a FILE_NOT_FOUND response
Result: Received event: 241d1757: GET_FILE for file ERROR-NO-SUCH-FILE-ERROR: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FILE_NOT_FOUND_FAILURE, File ERROR-NO-SUCH-FILE-ERROR not present on this pillar
Result: Received event: 241d1757: GET_FILE for file ERROR-NO-SUCH-FILE-ERROR: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: FILE_NOT_FOUND_FAILURE, File ERROR-NO-SUCH-FILE-ERRORnot present on this pillar
Result: Received event: 241d1757: GET_FILE for file ERROR-NO-SUCH-FILE-ERROR: FAILED: , Unable to continue operation, contributors unavailable.
13:45:07.675 ERROR o.b.a.g.c.IdentifyingPillarsForGetFile - Failing conversation 'GetFileConversationContext{collectionID='TwoPillarCollection', conversationID='241d1757-4ea4-45c7-a555-093c265eeda8', clientID='testNoSuchFileMultiplePillars', fileID='ERROR-NO-SUCH-FILE-ERROR', contributors=[Pillar1, Pillar2], monitor=ConversationEventMonitor{, collectionID='TwoPillarCollection', conversationID='241d1757', operationType=GET_FILE, fileID='ERROR-NO-SUCH-FILE-ERROR', eventHandler=org.bitrepository.client.TestEventHandler@2987ccc2, contributorCompleteEvents=[], contributorFailedEvents=[241d1757: GET_FILE for file ERROR-NO-SUCH-FILE-ERROR: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FILE_NOT_FOUND_FAILURE, File ERROR-NO-SUCH-FILE-ERROR not present on this pillar , 241d1757: GET_FILE for file ERROR-NO-SUCH-FILE-ERROR: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: FILE_NOT_FOUND_FAILURE, File ERROR-NO-SUCH-FILE-ERRORnot present on this pillar ], failOnComponentFailure=false}, auditTrailInformation='null', state=org.bitrepository.client.conversation.FinishedState@688cbf30, checksumPillars=[]}' with exception
org.bitrepository.common.exceptions.UnableToFinishException: Unable to continue operation, contributors unavailable.
at org.bitrepository.client.conversation.IdentifyingState.completeState(IdentifyingState.java:76)
at org.bitrepository.client.conversation.GeneralConversationState.changeState(GeneralConversationState.java:147)
at org.bitrepository.client.conversation.GeneralConversationState.handleMessage(GeneralConversationState.java:114)
at org.bitrepository.client.conversation.StateBasedConversation.onMessage(StateBasedConversation.java:53)
at org.bitrepository.client.conversation.mediator.CollectionBasedConversationMediator.onMessage(CollectionBasedConversationMediator.java:136)
at org.bitrepository.protocol.messagebus.SimpleMessageBus.lambda$sendMessage$0(SimpleMessageBus.java:73)
at java.lang.Iterable.forEach(Iterable.java:75)
at org.bitrepository.protocol.messagebus.SimpleMessageBus.sendMessage(SimpleMessageBus.java:73)
at org.bitrepository.access.getfile.GetFileClientComponentTest.testNoSuchFileMultiplePillars(GetFileClientComponentTest.java:444)
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.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:134)
at org.testng.internal.TestInvoker.invokeMethod(TestInvoker.java:597)
at org.testng.internal.TestInvoker.invokeTestMethod(TestInvoker.java:173)
at org.testng.internal.MethodRunner.runInSequence(MethodRunner.java:46)
at org.testng.internal.TestInvoker$MethodInvocationAgent.invoke(TestInvoker.java:816)
at org.testng.internal.TestInvoker.invokeTestMethods(TestInvoker.java:146)
at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:146)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:128)
at java.util.ArrayList.forEach(ArrayList.java:1249)
at org.testng.TestRunner.privateRun(TestRunner.java:766)
at org.testng.TestRunner.run(TestRunner.java:587)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:384)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:378)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:337)
at org.testng.SuiteRunner.run(SuiteRunner.java:286)
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:53)
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:96)
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1187)
at org.testng.TestNG.runSuitesLocally(TestNG.java:1109)
at org.testng.TestNG.runSuites(TestNG.java:1039)
at org.testng.TestNG.run(TestNG.java:1007)
at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:135)
at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:193)
at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:94)
at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:146)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:377)
at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:138)
at org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:465)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:451)
Test success: testNoSuchFileMultiplePillars
Test starting: testNoSuchFileSpecificPillar
Description: Testing how a request for a non-existing file is handled on a specific pillar request.
Step: Define 1 pillar.
Step: Call getFileFromSpecificPillar.
Stimuli: Calling getFileFromSpecificPillar(ERROR-NO-SUCH-FILE-ERROR, file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, Pillar1)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileRequest@7d06c68d[correlationID=b12ab0e9-153f-42ab-b952-035816b41d6a, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=testNoSuchFileSpecificPillar, to=Pillar1, version=31, minVersion=24, auditTrailInformation=<null>(default), fileID=ERROR-NO-SUCH-FILE-ERROR]
Result: Received event: b12ab0e9: GET_FILE for file ERROR-NO-SUCH-FILE-ERROR: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetFile
Step: The specified pillars sends a FILE_NOT_FOUND response
Result: Received event: b12ab0e9: GET_FILE for file ERROR-NO-SUCH-FILE-ERROR: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FILE_NOT_FOUND_FAILURE, File ERROR-NO-SUCH-FILE-ERROR not present on this pillar Pillar1
Result: Received event: b12ab0e9: GET_FILE for file ERROR-NO-SUCH-FILE-ERROR: FAILED: , Unable to continue operation, contributors unavailable.
13:45:07.776 ERROR o.b.a.g.c.IdentifyingPillarsForGetFile - Failing conversation 'GetFileConversationContext{collectionID='TwoPillarCollection', conversationID='b12ab0e9-153f-42ab-b952-035816b41d6a', clientID='testNoSuchFileSpecificPillar', fileID='ERROR-NO-SUCH-FILE-ERROR', contributors=[Pillar1], monitor=ConversationEventMonitor{, collectionID='TwoPillarCollection', conversationID='b12ab0e9', operationType=GET_FILE, fileID='ERROR-NO-SUCH-FILE-ERROR', eventHandler=org.bitrepository.client.TestEventHandler@2d4696a0, contributorCompleteEvents=[], contributorFailedEvents=[b12ab0e9: GET_FILE for file ERROR-NO-SUCH-FILE-ERROR: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FILE_NOT_FOUND_FAILURE, File ERROR-NO-SUCH-FILE-ERROR not present on this pillar Pillar1], failOnComponentFailure=false}, auditTrailInformation='null', state=org.bitrepository.client.conversation.FinishedState@5cb99a43, checksumPillars=[]}' with exception
org.bitrepository.common.exceptions.UnableToFinishException: Unable to continue operation, contributors unavailable.
at org.bitrepository.client.conversation.IdentifyingState.completeState(IdentifyingState.java:76)
at org.bitrepository.client.conversation.GeneralConversationState.changeState(GeneralConversationState.java:147)
at org.bitrepository.client.conversation.GeneralConversationState.handleMessage(GeneralConversationState.java:114)
at org.bitrepository.client.conversation.StateBasedConversation.onMessage(StateBasedConversation.java:53)
at org.bitrepository.client.conversation.mediator.CollectionBasedConversationMediator.onMessage(CollectionBasedConversationMediator.java:136)
at org.bitrepository.protocol.messagebus.SimpleMessageBus.lambda$sendMessage$0(SimpleMessageBus.java:73)
at java.lang.Iterable.forEach(Iterable.java:75)
at org.bitrepository.protocol.messagebus.SimpleMessageBus.sendMessage(SimpleMessageBus.java:73)
at org.bitrepository.access.getfile.GetFileClientComponentTest.testNoSuchFileSpecificPillar(GetFileClientComponentTest.java:405)
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.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:134)
at org.testng.internal.TestInvoker.invokeMethod(TestInvoker.java:597)
at org.testng.internal.TestInvoker.invokeTestMethod(TestInvoker.java:173)
at org.testng.internal.MethodRunner.runInSequence(MethodRunner.java:46)
at org.testng.internal.TestInvoker$MethodInvocationAgent.invoke(TestInvoker.java:816)
at org.testng.internal.TestInvoker.invokeTestMethods(TestInvoker.java:146)
at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:146)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:128)
at java.util.ArrayList.forEach(ArrayList.java:1249)
at org.testng.TestRunner.privateRun(TestRunner.java:766)
at org.testng.TestRunner.run(TestRunner.java:587)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:384)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:378)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:337)
at org.testng.SuiteRunner.run(SuiteRunner.java:286)
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:53)
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:96)
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1187)
at org.testng.TestNG.runSuitesLocally(TestNG.java:1109)
at org.testng.TestNG.runSuites(TestNG.java:1039)
at org.testng.TestNG.run(TestNG.java:1007)
at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:135)
at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:193)
at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:94)
at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:146)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:377)
at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:138)
at org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:465)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:451)
Test success: testNoSuchFileSpecificPillar
Test starting: verifyGetFileClientFromFactory
Test success: verifyGetFileClientFromFactory
Finished testcase
Finished suite
Finished project
[INFO] Tests run: 156, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 58.817 s - in TestSuite
[INFO]
[INFO] Results:
[INFO]
[INFO] Tests run: 156, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[JENKINS] Recording test results
[INFO]
[INFO] --- jacoco-maven-plugin:0.8.5:report (report) @ bitrepository-client ---
[INFO] Loading execution data file /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-client/target/jacoco.exec
[INFO] Analyzed bundle 'Bitrepository Client' with 114 classes
[INFO]
[INFO] --- maven-jar-plugin:3.2.0:jar (default-jar) @ bitrepository-client ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-client/target/bitrepository-client-1.10-SNAPSHOT.jar
[INFO]
[INFO] --- maven-jar-plugin:3.2.0:test-jar (default) @ bitrepository-client ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-client/target/bitrepository-client-1.10-SNAPSHOT-tests.jar
[INFO]
[INFO] --- maven-source-plugin:3.2.1:jar-no-fork (attach-sources-no-fork) @ bitrepository-client ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-client/target/bitrepository-client-1.10-SNAPSHOT-sources.jar
[INFO]
[INFO] --- maven-assembly-plugin:3.3.0:single (make-assembly) @ bitrepository-client ---
[INFO] Reading assembly descriptor: src/main/assembly/assembly.xml
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-client/target/bitrepository-client-1.10-SNAPSHOT-distribution.tar.gz
[INFO]
[INFO] --- maven-install-plugin:3.0.0-M1:install (default-install) @ bitrepository-client ---
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-client/target/bitrepository-client-1.10-SNAPSHOT.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-client/1.10-SNAPSHOT/bitrepository-client-1.10-SNAPSHOT.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-client/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-client/1.10-SNAPSHOT/bitrepository-client-1.10-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-client/target/bitrepository-client-1.10-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-client/1.10-SNAPSHOT/bitrepository-client-1.10-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-client/target/bitrepository-client-1.10-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-client/1.10-SNAPSHOT/bitrepository-client-1.10-SNAPSHOT-sources.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-client/target/bitrepository-client-1.10-SNAPSHOT-distribution.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-client/1.10-SNAPSHOT/bitrepository-client-1.10-SNAPSHOT-distribution.tar.gz
[INFO]
[INFO] --- maven-deploy-plugin:3.0.0-M1:deploy (default-deploy) @ bitrepository-client ---
[INFO] Downloading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-client/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-client/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 88.2 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-client/1.10-SNAPSHOT/bitrepository-client-1.10-20220215.124513-64.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-client/1.10-SNAPSHOT/bitrepository-client-1.10-20220215.124513-64.jar (191 KB at 4235.2 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-client/1.10-SNAPSHOT/bitrepository-client-1.10-20220215.124513-64.pom
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-client/1.10-SNAPSHOT/bitrepository-client-1.10-20220215.124513-64.pom (2 KB at 62.9 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-client/1.10-SNAPSHOT/bitrepository-client-1.10-20220215.124513-64-tests.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-client/1.10-SNAPSHOT/bitrepository-client-1.10-20220215.124513-64-tests.jar (114 KB at 3350.1 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-client/1.10-SNAPSHOT/bitrepository-client-1.10-20220215.124513-64-sources.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-client/1.10-SNAPSHOT/bitrepository-client-1.10-20220215.124513-64-sources.jar (198 KB at 6360.5 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-client/1.10-SNAPSHOT/bitrepository-client-1.10-20220215.124513-64-distribution.tar.gz
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-client/1.10-SNAPSHOT/bitrepository-client-1.10-20220215.124513-64-distribution.tar.gz (9036 KB at 26731.6 KB/sec)
[INFO] Downloading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-client/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-client/maven-metadata.xml (484 B at 29.5 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-client/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-client/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 64.1 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-client/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-client/maven-metadata.xml (484 B at 19.7 KB/sec)
[JENKINS] Archiving disabled
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Service 1.10-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:3.1.0:clean (default-clean) @ bitrepository-service ---
[INFO]
[INFO] --- maven-enforcer-plugin:3.0.0-M3:enforce (enforce-maven) @ bitrepository-service ---
[INFO]
[INFO] --- jacoco-maven-plugin:0.8.5:prepare-agent (default) @ bitrepository-service ---
[INFO] argLine set to -javaagent:/home/cibuild01/.m2/repository/org/jacoco/org.jacoco.agent/0.8.5/org.jacoco.agent-0.8.5-runtime.jar=destfile=/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-service/target/jacoco.exec
[INFO]
[INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ bitrepository-service ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 9 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.8.1:compile (default-compile) @ bitrepository-service ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 53 source files to /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-service/target/classes
[WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-service/src/main/java/org/bitrepository/service/exception/StepFailedException.java:[27,8] serializable class org.bitrepository.service.exception.StepFailedException has no definition of serialVersionUID
[WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-service/src/main/java/org/bitrepository/service/exception/WorkflowAbortedException.java:[27,8] serializable class org.bitrepository.service.exception.WorkflowAbortedException has no definition of serialVersionUID
[WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-service/src/main/java/org/bitrepository/service/audit/AuditTrailContributerDAO.java:[258,25] explicit call to close() on an auto-closeable resource
[INFO]
[INFO] --- forbiddenapis:2.7:check (default) @ bitrepository-service ---
[INFO] Scanning for classes to check...
[INFO] Reading bundled API signatures: jdk-unsafe-1.8
[INFO] Reading bundled API signatures: jdk-deprecated-1.8
[INFO] Reading bundled API signatures: jdk-non-portable
[INFO] Reading bundled API signatures: jdk-reflection
[INFO] Loading classes to check...
[INFO] Scanning classes for violations...
[INFO] Scanned 58 class file(s) for forbidden API invocations (in 0.15s), 0 error(s).
[INFO]
[INFO] --- forbiddenapis:2.7:testCheck (default) @ bitrepository-service ---
[INFO] Scanning for classes to check...
[WARNING] Classes directory does not exist, forbiddenapis check skipped: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-service/target/test-classes
[INFO]
[INFO] --- maven-resources-plugin:3.1.0:testResources (default-testResources) @ bitrepository-service ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 3 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.8.1:testCompile (default-testCompile) @ bitrepository-service ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 9 source files to /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-service/target/test-classes
[INFO]
[INFO] --- maven-surefire-plugin:3.0.0-M4:test (default-test) @ bitrepository-service ---
[INFO]
[INFO] -------------------------------------------------------
[INFO] T E S T S
[INFO] -------------------------------------------------------
[INFO] Running TestSuite
Starting test project Core module test
Suite: Surefire suite
Starting testcase AuditTrailContributorDatabaseMigrationTest
Test starting: testMigratingAuditContributorDatabase
Description: Tests that the database can be migrated to latest version with the provided scripts.
Step: Validate setup
Step: Ingest a entry to the database without the collection id
Step: Perform migration
13:45:22.274 WARN o.b.service.database.DatabaseUtils - Migrating AuditContributorDB from version 1 to 2.
13:45:22.515 WARN o.b.service.database.DatabaseUtils - Migrating AuditContributorDB from version 2 to 3.
13:45:22.869 WARN o.b.service.database.DatabaseUtils - Migrating AuditContributorDB from version 3 to 4.
13:45:22.921 WARN o.b.service.database.DatabaseUtils - Migrating AuditContributorDB from version 4 to 5.
Test success: testMigratingAuditContributorDatabase
Starting testcase IdentifyContributorExceptionTest
Test starting: testIdentifyContributor
Description: Test the instantiation of the exception
Step: Setup
Step: Try to throw such an exception
Step: Throw the exception with an embedded exception
Test success: testIdentifyContributor
Starting testcase InvalidMessageExceptionTest
Test starting: testIdentifyContributor
Description: Test the instantiation of the exception
Step: Setup
Step: Try to throw such an exception
Step: Throw the exception with an embedded exception
Step: Throw the exception with a ResponseInfo
Test success: testIdentifyContributor
Test starting: componentIDTest
Test success: componentIDTest
Starting testcase AuditTrailContributorDatabaseTest
Test starting: testAuditTrailDatabaseExtraction
Description: Testing the basic functions of the audit trail database interface.
Step: Setup varibles and the database connection.
Step: Populate the database.
Step: Test extracting all the events
Step: Test extracting the events for fileID1
Step: Test extracting the events for fileID2
Step: Test extracting the events with the sequence number at least equal to the largest sequence number.
Step: Test extracting the events for fileID1 with sequence number 2 or more
Step: Test extracting the events for fileID1 with at most sequence number 2
Step: Test extracting at most 3 events
Step: Test extracting at most 1000 events
Step: Test extracting from another collection
Test success: testAuditTrailDatabaseExtraction
Test starting: testAuditTrailDatabaseExtractionOrder
Description: Test the order of extraction
Step: Setup variables and database connection
Step: Populate the database.
Step: Extract 3 audit-trails
Step: Extract 3 audit-trails, with larger seq-number than the first
Test success: testAuditTrailDatabaseExtractionOrder
Test starting: testAuditTrailDatabaseIngest
Description: Testing the ingest of data.
Step: Setup varibles and the database connection.
Step: Test with all data.
Step: Test with no collection
Step: Test with with no file id.
Step: Test with with no actor.
Step: Test with with no info.
Step: Test with with no audittrail.
Step: Test with with no operationID.
Step: Test with with no certificateID.
Step: Test with with no action.
Step: Test with with very large file id.
Step: Test with with very large actor name.
Step: Test with with very large info.
Step: Test with with very large audittrail.
Test success: testAuditTrailDatabaseIngest
Starting testcase IllegalOperationExceptionTest
Test starting: testIdentifyContributor
Description: Test the instantiation of the exception
Step: Setup
Step: Try to throw such an exception
Step: Throw the exception with an embedded exception
Test success: testIdentifyContributor
Finished testcase
Finished suite
Finished project
[INFO] Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 12.434 s - in TestSuite
[INFO]
[INFO] Results:
[INFO]
[INFO] Tests run: 8, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[JENKINS] Recording test results
[INFO]
[INFO] --- jacoco-maven-plugin:0.8.5:report (report) @ bitrepository-service ---
[INFO] Loading execution data file /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-service/target/jacoco.exec
[INFO] Analyzed bundle 'Bitrepository Service' with 46 classes
[INFO]
[INFO] --- maven-jar-plugin:3.2.0:jar (default-jar) @ bitrepository-service ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-service/target/bitrepository-service-1.10-SNAPSHOT.jar
[INFO]
[INFO] --- maven-jar-plugin:3.2.0:test-jar (default) @ bitrepository-service ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-service/target/bitrepository-service-1.10-SNAPSHOT-tests.jar
[INFO]
[INFO] --- maven-source-plugin:3.2.1:jar-no-fork (attach-sources-no-fork) @ bitrepository-service ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-service/target/bitrepository-service-1.10-SNAPSHOT-sources.jar
[INFO]
[INFO] --- maven-install-plugin:3.0.0-M1:install (default-install) @ bitrepository-service ---
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-service/target/bitrepository-service-1.10-SNAPSHOT.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-service/1.10-SNAPSHOT/bitrepository-service-1.10-SNAPSHOT.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-service/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-service/1.10-SNAPSHOT/bitrepository-service-1.10-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-service/target/bitrepository-service-1.10-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-service/1.10-SNAPSHOT/bitrepository-service-1.10-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-service/target/bitrepository-service-1.10-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-service/1.10-SNAPSHOT/bitrepository-service-1.10-SNAPSHOT-sources.jar
[INFO]
[INFO] --- maven-deploy-plugin:3.0.0-M1:deploy (default-deploy) @ bitrepository-service ---
[INFO] Downloading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-service/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-service/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 59.8 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-service/1.10-SNAPSHOT/bitrepository-service-1.10-20220215.124530-64.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-service/1.10-SNAPSHOT/bitrepository-service-1.10-20220215.124530-64.jar (93 KB at 3197.2 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-service/1.10-SNAPSHOT/bitrepository-service-1.10-20220215.124530-64.pom
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-service/1.10-SNAPSHOT/bitrepository-service-1.10-20220215.124530-64.pom (3 KB at 60.0 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-service/1.10-SNAPSHOT/bitrepository-service-1.10-20220215.124530-64-tests.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-service/1.10-SNAPSHOT/bitrepository-service-1.10-20220215.124530-64-tests.jar (255 KB at 6364.6 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-service/1.10-SNAPSHOT/bitrepository-service-1.10-20220215.124530-64-sources.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-service/1.10-SNAPSHOT/bitrepository-service-1.10-20220215.124530-64-sources.jar (91 KB at 3611.3 KB/sec)
[INFO] Downloading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-service/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-service/maven-metadata.xml (485 B at 47.4 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-service/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-service/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 37.4 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-service/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-service/maven-metadata.xml (485 B at 17.5 KB/sec)
[JENKINS] Archiving disabled
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Integrity Service 1.10-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:3.1.0:clean (default-clean) @ bitrepository-integrity-service ---
[INFO]
[INFO] --- maven-enforcer-plugin:3.0.0-M3:enforce (enforce-maven) @ bitrepository-integrity-service ---
[INFO]
[INFO] --- jacoco-maven-plugin:0.8.5:prepare-agent (default) @ bitrepository-integrity-service ---
[INFO] argLine set to -javaagent:/home/cibuild01/.m2/repository/org/jacoco/org.jacoco.agent/0.8.5/org.jacoco.agent-0.8.5-runtime.jar=destfile=/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integrity-service/target/jacoco.exec
[INFO]
[INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ bitrepository-integrity-service ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 15 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.8.1:compile (default-compile) @ bitrepository-integrity-service ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 72 source files to /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integrity-service/target/classes
[INFO]
[INFO] --- forbiddenapis:2.7:check (default) @ bitrepository-integrity-service ---
[INFO] Scanning for classes to check...
[INFO] Reading bundled API signatures: jdk-unsafe-1.8
[INFO] Reading bundled API signatures: jdk-deprecated-1.8
[INFO] Reading bundled API signatures: jdk-non-portable
[INFO] Reading bundled API signatures: jdk-reflection
[INFO] Loading classes to check...
[INFO] Scanning classes for violations...
[INFO] Scanned 85 class file(s) for forbidden API invocations (in 0.18s), 0 error(s).
[INFO]
[INFO] --- forbiddenapis:2.7:testCheck (default) @ bitrepository-integrity-service ---
[INFO] Scanning for classes to check...
[WARNING] Classes directory does not exist, forbiddenapis check skipped: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integrity-service/target/test-classes
[INFO]
[INFO] --- maven-resources-plugin:3.1.0:testResources (default-testResources) @ bitrepository-integrity-service ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 3 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.8.1:testCompile (default-testCompile) @ bitrepository-integrity-service ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 26 source files to /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integrity-service/target/test-classes
[WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integrity-service/src/test/java/org/bitrepository/integrityservice/workflow/SaltedChecksumWorkflowTest.java:[113,9] verifyZeroInteractions(java.lang.Object...) in org.mockito.Mockito has been deprecated
[WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integrity-service/src/test/java/org/bitrepository/integrityservice/workflow/SaltedChecksumWorkflowTest.java:[114,9] verifyZeroInteractions(java.lang.Object...) in org.mockito.Mockito has been deprecated
[WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integrity-service/src/test/java/org/bitrepository/integrityservice/workflow/SaltedChecksumWorkflowTest.java:[145,9] verifyZeroInteractions(java.lang.Object...) in org.mockito.Mockito has been deprecated
[WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integrity-service/src/test/java/org/bitrepository/integrityservice/workflow/step/GetChecksumForFileStepTest.java:[84,22] found raw type: org.mockito.stubbing.Answer
missing type arguments for generic class org.mockito.stubbing.Answer<T>
[WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integrity-service/src/test/java/org/bitrepository/integrityservice/workflow/step/GetChecksumForFileStepTest.java:[111,22] found raw type: org.mockito.stubbing.Answer
missing type arguments for generic class org.mockito.stubbing.Answer<T>
[WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integrity-service/src/test/java/org/bitrepository/integrityservice/workflow/step/GetChecksumForFileStepTest.java:[148,22] found raw type: org.mockito.stubbing.Answer
missing type arguments for generic class org.mockito.stubbing.Answer<T>
[INFO]
[INFO] --- maven-surefire-plugin:3.0.0-M4:test (default-test) @ bitrepository-integrity-service ---
[INFO]
[INFO] -------------------------------------------------------
[INFO] T E S T S
[INFO] -------------------------------------------------------
[INFO] Running TestSuite
Starting test project Integration Service Test
Suite: Surefire suite
Starting testcase BasicIntegrityReporterTest
Test starting: checksumIssuesTest
Description: Verifies that missing files are reported correctly
Step: Report a checksum issue
Step: Report another checksum issue on the same pillar
Step: Report a checksum issue on another pillar
Test success: checksumIssuesTest
Test starting: deletedFilesTest
Description: Verifies that the hasIntegrityIssues() reports deleted files correctly
Step: Report a delete file for a new Reporter
Test success: deletedFilesTest
Test starting: missingChecksumTest
Description: Verifies that missing checksums are reported correctly
Step: Report a missing checksum
Step: Report another missing checksum on the same pillar
Step: Report a missing checksum on another pillar
Test success: missingChecksumTest
Test starting: missingFilesTest
Description: Verifies that missing files are reported correctly
Step: Report a missing file
Step: Report another missing file on the same pillar
Step: Report a missing file on another pillar
Test success: missingFilesTest
Test starting: noIntegrityIssuesTest
Description: Verifies that missing files are reported correctly
Step: Create a clean reporter
Test success: noIntegrityIssuesTest
Test starting: obsoleteChecksumTest
Description: Verifies that obsolete checksums are reported correctly
Step: Report a obsolete checksum
Step: Report another obsolete checksum on the same pillar
Step: Report a obsolete checksum on another pillar
Test success: obsoleteChecksumTest
Starting testcase GetFileStepTest
Test starting: testNegativeReply
Description: Test the step for getting the file can handle FAILURE operation event.
Test success: testNegativeReply
Test starting: testPositiveReply
Description: Test the step for getting the file can handle COMPLETE operation event.
Test success: testPositiveReply
Starting testcase IntegrityAlerterTest
Test starting: testIntegrityFailed
Description: Test the IntegrityFailed method for the IntegrityAlerter
Step: Call the function for integrity failure.
13:45:40.044 WARN o.b.i.a.IntegrityAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@5d8edf2[origDateTime=2022-02-15T13:45:40.030+01:00, alarmCode=INTEGRITY_ISSUE, alarmRaiser=IntegrityAlerterTest, alarmText=Testaintegrity alarm, fileID=<null>(default), collectionID=TwoPillarCollection]
Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@e9fa0ea[correlationID=083a070c-6bbd-4ee1-85b3-0aeaf7d9965f, collectionID=TwoPillarCollection, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-IntegrityAlerterTest-cibuild01-contributor, from=IntegrityAlerterTest, to=<null>(default), version=31, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@5d8edf2[origDateTime=2022-02-15T13:45:40.030+01:00, alarmCode=INTEGRITY_ISSUE, alarmRaiser=IntegrityAlerterTest, alarmText=Testaintegrity alarm, fileID=<null>(default), collectionID=TwoPillarCollection]]
Test success: testIntegrityFailed
Test starting: testOperationFailed
Description: Test the OperationFailed method for the IntegrityAlerter
Step: Call the function for integrity failure.
13:45:40.269 WARN o.b.i.a.IntegrityAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@1703e50d[origDateTime=2022-02-15T13:45:40.267+01:00, alarmCode=FAILED_OPERATION, alarmRaiser=IntegrityAlerterTest, alarmText=Testing the ability to fail., fileID=<null>(default), collectionID=TwoPillarCollection]
Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@4f1150f5[correlationID=90ce5910-2810-4f5b-adbb-dff036c10a3b, collectionID=TwoPillarCollection, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-IntegrityAlerterTest-cibuild01-contributor, from=IntegrityAlerterTest, to=<null>(default), version=31, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@1703e50d[origDateTime=2022-02-15T13:45:40.267+01:00, alarmCode=FAILED_OPERATION, alarmRaiser=IntegrityAlerterTest, alarmText=Testing the ability to fail., fileID=<null>(default), collectionID=TwoPillarCollection]]
Test success: testOperationFailed
Starting testcase IntegrityInformationCollectorTest
Test starting: testCollectorGetChecksums
Description: Tests that the collector calls the GetChecksumsClient
Step: Define variables
Step: Setup a GetChecksumsClient for test purpose.
Step: Call the getChecksumsClient on the collector.
Step: Call the getChecksumsClient on the collector four times more.
Test success: testCollectorGetChecksums
Test starting: testCollectorGetFile
Description: Tests that the collector calls the GetFileClient
Step: Define variables
Step: Setup a GetFileClient for test purpose.
Step: Call the GetFileClient on the collector.
Step: Call the GetFileClient on the collector four times more.
Test success: testCollectorGetFile
Test starting: testCollectorGetFileIDs
Description: Tests that the collector calls the GetFileClient
Step: Define variables
Step: Setup a GetFileIDsClient for test purpose.
Step: Call the getFileIDs on the collector.
Step: Call the getFileIDs on the collector four times more.
Test success: testCollectorGetFileIDs
Test starting: testCollectorHandleChecksumClientFailures
Description: Test that the IntegrityInformationCollector works as a fault-barrier.
Step: Setup variables for the test
Step: Setup a failing GetChecksumClient for test purpose.
Step: Verify that the collector does not fail, just because the GetChecksumClient does so
Test success: testCollectorHandleChecksumClientFailures
Test starting: testCollectorHandleGetFileClientFailures
Description: Test that the IntegrityInformationCollector works as a fault-barrier.
Step: Define variables
Step: Setup a GetFileClient for test purpose, and ensure that it throws an error when called.
Step: Verify that the collector does not fail, just because the GetFileClient does so
Test success: testCollectorHandleGetFileClientFailures
Test starting: testCollectorHandleGetFileIDsClientFailures
Description: Test that the IntegrityInformationCollector works as a fault-barrier.
Step: Setup variables for the test
Step: Setup a DyingGetFileIDsClient for test purpose.
Step: Verify that the collector does not fail, just because the GetChecksumClient does so
Test success: testCollectorHandleGetFileIDsClientFailures
Test starting: testCollectorHandlePutFileClientFailures
Description: Test that the IntegrityInformationCollector works as a fault-barrier.
Step: Define variables
Step: Setup a PutFileClient for test purpose, and ensure that it throws an error when called.
Step: Verify that the collector does not fail, just because the PutFileClient does so
Test success: testCollectorHandlePutFileClientFailures
Test starting: testCollectorPutFile
Description: Tests that the collector calls the PutFileClient
Step: Define variables
Step: Setup a PutFileClient for test purpose.
Step: Call the PutFileClient on the collector.
Step: Call the PutFileClient on the collector four times more.
Test success: testCollectorPutFile
Starting testcase RepairMissingFilesWorkflowTest
Test starting: testFailedGetFile
Description: Test that the workflow does not try to put a file, if it fails to get it.
Step: Prepare for calls to mocks to fail when performing get-file
Step: Run missing checksum step.
13:45:40.625 ERROR o.b.i.w.RepairMissingFilesWorkflow - Failure in step: 'Performing GetFile for 'test-file-1'.'.
java.lang.IllegalStateException: Aborting workflow due to failure getting the file 'test-file-1'. Cause: null: null: FAILED: , failure
at org.bitrepository.integrityservice.workflow.step.GetFileStep.performStep(GetFileStep.java:74)
at org.bitrepository.service.workflow.Workflow.performStep(Workflow.java:63)
at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflow.getFileStep(RepairMissingFilesWorkflow.java:174)
at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflow.repairMissingFiles(RepairMissingFilesWorkflow.java:114)
at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflow.start(RepairMissingFilesWorkflow.java:88)
at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflowTest.testFailedGetFile(RepairMissingFilesWorkflowTest.java:199)
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.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:134)
at org.testng.internal.TestInvoker.invokeMethod(TestInvoker.java:597)
at org.testng.internal.TestInvoker.invokeTestMethod(TestInvoker.java:173)
at org.testng.internal.MethodRunner.runInSequence(MethodRunner.java:46)
at org.testng.internal.TestInvoker$MethodInvocationAgent.invoke(TestInvoker.java:816)
at org.testng.internal.TestInvoker.invokeTestMethods(TestInvoker.java:146)
at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:146)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:128)
at java.util.ArrayList.forEach(ArrayList.java:1249)
at org.testng.TestRunner.privateRun(TestRunner.java:766)
at org.testng.TestRunner.run(TestRunner.java:587)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:384)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:378)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:337)
at org.testng.SuiteRunner.run(SuiteRunner.java:286)
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:53)
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:96)
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1187)
at org.testng.TestNG.runSuitesLocally(TestNG.java:1109)
at org.testng.TestNG.runSuites(TestNG.java:1039)
at org.testng.TestNG.run(TestNG.java:1007)
at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:135)
at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:193)
at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:94)
at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:146)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:377)
at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:138)
at org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:465)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:451)
13:45:40.638 WARN o.b.i.w.RepairMissingFilesWorkflow - Error occured during repair of missing file, 'test-file-1'. Tries to continue.
java.lang.RuntimeException: Failed to run step Performing GetFile for 'test-file-1'.
at org.bitrepository.service.workflow.Workflow.performStep(Workflow.java:69)
at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflow.getFileStep(RepairMissingFilesWorkflow.java:174)
at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflow.repairMissingFiles(RepairMissingFilesWorkflow.java:114)
at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflow.start(RepairMissingFilesWorkflow.java:88)
at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflowTest.testFailedGetFile(RepairMissingFilesWorkflowTest.java:199)
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.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:134)
at org.testng.internal.TestInvoker.invokeMethod(TestInvoker.java:597)
at org.testng.internal.TestInvoker.invokeTestMethod(TestInvoker.java:173)
at org.testng.internal.MethodRunner.runInSequence(MethodRunner.java:46)
at org.testng.internal.TestInvoker$MethodInvocationAgent.invoke(TestInvoker.java:816)
at org.testng.internal.TestInvoker.invokeTestMethods(TestInvoker.java:146)
at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:146)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:128)
at java.util.ArrayList.forEach(ArrayList.java:1249)
at org.testng.TestRunner.privateRun(TestRunner.java:766)
at org.testng.TestRunner.run(TestRunner.java:587)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:384)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:378)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:337)
at org.testng.SuiteRunner.run(SuiteRunner.java:286)
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:53)
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:96)
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1187)
at org.testng.TestNG.runSuitesLocally(TestNG.java:1109)
at org.testng.TestNG.runSuites(TestNG.java:1039)
at org.testng.TestNG.run(TestNG.java:1007)
at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:135)
at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:193)
at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:94)
at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:146)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:377)
at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:138)
at org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:465)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:451)
Caused by: java.lang.IllegalStateException: Aborting workflow due to failure getting the file 'test-file-1'. Cause: null: null: FAILED: , failure
at org.bitrepository.integrityservice.workflow.step.GetFileStep.performStep(GetFileStep.java:74)
at org.bitrepository.service.workflow.Workflow.performStep(Workflow.java:63)
... 37 common frames omitted
Test success: testFailedGetFile
Test starting: testFailedPutFile
Description: Test that the workflow makes calls to the collector for get and put file, even when put file fails.
Step: Prepare for calls to mocks
Step: Run workflow to repair missing files.
13:45:40.747 ERROR o.b.i.w.RepairMissingFilesWorkflow - Failure in step: 'Performing PutFile for 'test-file-1'.'.
java.lang.IllegalStateException: Aborting workflow due to failure putting the file 'test-file-1'. Cause: null: null: FAILED: , failure
at org.bitrepository.integrityservice.workflow.step.PutFileStep.performStep(PutFileStep.java:88)
at org.bitrepository.service.workflow.Workflow.performStep(Workflow.java:63)
at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflow.putFileStep(RepairMissingFilesWorkflow.java:189)
at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflow.repairMissingFiles(RepairMissingFilesWorkflow.java:115)
at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflow.start(RepairMissingFilesWorkflow.java:88)
at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflowTest.testFailedPutFile(RepairMissingFilesWorkflowTest.java:249)
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.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:134)
at org.testng.internal.TestInvoker.invokeMethod(TestInvoker.java:597)
at org.testng.internal.TestInvoker.invokeTestMethod(TestInvoker.java:173)
at org.testng.internal.MethodRunner.runInSequence(MethodRunner.java:46)
at org.testng.internal.TestInvoker$MethodInvocationAgent.invoke(TestInvoker.java:816)
at org.testng.internal.TestInvoker.invokeTestMethods(TestInvoker.java:146)
at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:146)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:128)
at java.util.ArrayList.forEach(ArrayList.java:1249)
at org.testng.TestRunner.privateRun(TestRunner.java:766)
at org.testng.TestRunner.run(TestRunner.java:587)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:384)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:378)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:337)
at org.testng.SuiteRunner.run(SuiteRunner.java:286)
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:53)
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:96)
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1187)
at org.testng.TestNG.runSuitesLocally(TestNG.java:1109)
at org.testng.TestNG.runSuites(TestNG.java:1039)
at org.testng.TestNG.run(TestNG.java:1007)
at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:135)
at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:193)
at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:94)
at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:146)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:377)
at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:138)
at org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:465)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:451)
13:45:40.752 WARN o.b.i.w.RepairMissingFilesWorkflow - Error occured during repair of missing file, 'test-file-1'. Tries to continue.
java.lang.RuntimeException: Failed to run step Performing PutFile for 'test-file-1'.
at org.bitrepository.service.workflow.Workflow.performStep(Workflow.java:69)
at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflow.putFileStep(RepairMissingFilesWorkflow.java:189)
at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflow.repairMissingFiles(RepairMissingFilesWorkflow.java:115)
at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflow.start(RepairMissingFilesWorkflow.java:88)
at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflowTest.testFailedPutFile(RepairMissingFilesWorkflowTest.java:249)
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.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:134)
at org.testng.internal.TestInvoker.invokeMethod(TestInvoker.java:597)
at org.testng.internal.TestInvoker.invokeTestMethod(TestInvoker.java:173)
at org.testng.internal.MethodRunner.runInSequence(MethodRunner.java:46)
at org.testng.internal.TestInvoker$MethodInvocationAgent.invoke(TestInvoker.java:816)
at org.testng.internal.TestInvoker.invokeTestMethods(TestInvoker.java:146)
at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:146)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:128)
at java.util.ArrayList.forEach(ArrayList.java:1249)
at org.testng.TestRunner.privateRun(TestRunner.java:766)
at org.testng.TestRunner.run(TestRunner.java:587)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:384)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:378)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:337)
at org.testng.SuiteRunner.run(SuiteRunner.java:286)
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:53)
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:96)
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1187)
at org.testng.TestNG.runSuitesLocally(TestNG.java:1109)
at org.testng.TestNG.runSuites(TestNG.java:1039)
at org.testng.TestNG.run(TestNG.java:1007)
at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:135)
at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:193)
at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:94)
at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:146)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:377)
at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:138)
at org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:465)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:451)
Caused by: java.lang.IllegalStateException: Aborting workflow due to failure putting the file 'test-file-1'. Cause: null: null: FAILED: , failure
at org.bitrepository.integrityservice.workflow.step.PutFileStep.performStep(PutFileStep.java:88)
at org.bitrepository.service.workflow.Workflow.performStep(Workflow.java:63)
... 37 common frames omitted
Test success: testFailedPutFile
Test starting: testNoMissingFiles
Description: Test that the workflow does nothing, when it has no missing files.
Step: Prepare for calls to mocks
Step: Run workflow for repairing missing files.
Test success: testNoMissingFiles
Test starting: testSuccesRepair
Description: Test that the workflow makes calls to the collector, when a file is missing
Step: Prepare for calls to mocks to handle a repair
Step: Run workflow for repairing missing files.
13:45:41.534 WARN o.b.i.w.RepairMissingFilesWorkflow - Issue deleting file from FileExchange
org.apache.http.conn.HttpHostConnectException: Connect to localhost:80 [localhost/127.0.0.1, localhost/0:0:0:0:0:0:0:1] failed: Connection refused (Connection refused)
at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:156)
at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:376)
at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:393)
at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236)
at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:186)
at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:89)
at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110)
at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:185)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:108)
at org.bitrepository.protocol.http.HttpFileExchange.deleteFile(HttpFileExchange.java:261)
at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflow.deleteUrl(RepairMissingFilesWorkflow.java:204)
at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflow.repairMissingFiles(RepairMissingFilesWorkflow.java:116)
at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflow.start(RepairMissingFilesWorkflow.java:88)
at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflowTest.testSuccesRepair(RepairMissingFilesWorkflowTest.java:160)
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.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:134)
at org.testng.internal.TestInvoker.invokeMethod(TestInvoker.java:597)
at org.testng.internal.TestInvoker.invokeTestMethod(TestInvoker.java:173)
at org.testng.internal.MethodRunner.runInSequence(MethodRunner.java:46)
at org.testng.internal.TestInvoker$MethodInvocationAgent.invoke(TestInvoker.java:816)
at org.testng.internal.TestInvoker.invokeTestMethods(TestInvoker.java:146)
at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:146)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:128)
at java.util.ArrayList.forEach(ArrayList.java:1249)
at org.testng.TestRunner.privateRun(TestRunner.java:766)
at org.testng.TestRunner.run(TestRunner.java:587)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:384)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:378)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:337)
at org.testng.SuiteRunner.run(SuiteRunner.java:286)
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:53)
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:96)
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1187)
at org.testng.TestNG.runSuitesLocally(TestNG.java:1109)
at org.testng.TestNG.runSuites(TestNG.java:1039)
at org.testng.TestNG.run(TestNG.java:1007)
at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:135)
at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:193)
at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:94)
at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:146)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:377)
at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:138)
at org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:465)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:451)
Caused by: java.net.ConnectException: Connection refused (Connection refused)
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:589)
at org.apache.http.conn.socket.PlainConnectionSocketFactory.connectSocket(PlainConnectionSocketFactory.java:75)
at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:142)
... 47 common frames omitted
Test success: testSuccesRepair
Starting testcase UpdateFileIDsStepTest
Test starting: testAbortWorkflowWhenNegativeReply
Description: Test the step for updating the file ids will throw an WorkflowAbortedExceptionwhen AbortOnFailedContributor is set to true and a FAILED event is received.
13:45:41.624 WARN o.b.i.c.IntegrityCollectorEventHandler - Component failure for 'test-pillar-1'.
13:45:41.625 WARN o.b.i.c.IntegrityCollectorEventHandler - Failure: null: null: FAILED: , Operation failed
Test success: testAbortWorkflowWhenNegativeReply
Test starting: testContinueWorkflowWhenNegativeReply
Description: Test the step for updating the file ids will continue when getting an FAILED operation event when AbortOnFailedContributor is set to false
13:45:41.698 WARN o.b.i.c.IntegrityCollectorEventHandler - Component failure for 'test-pillar-1'.
13:45:41.704 WARN o.b.i.c.IntegrityCollectorEventHandler - Failure: null: null: FAILED: , Operation failed
Test success: testContinueWorkflowWhenNegativeReply
Test starting: testIngestOfResults
Description: Test the step for updating the file ids can ingest the data correctly into the store.
Test success: testIngestOfResults
Test starting: testPartialResults
Description: Test that the number of partial is used for generating more than one request.
Step: Setup the collector mock to generate a isPartialResult=true event the first time and a isPartialResult=false the second time
Test success: testPartialResults
Test starting: testPositiveReply
Description: Test the step for updating the file ids can handle COMPLETE operation event.
Test success: testPositiveReply
Test starting: testRetryCollectionWhenNegativeReply
Description: Test the step for updating the file ids will retry on a FAILED event
13:45:42.030 WARN o.b.i.c.IntegrityCollectorEventHandler - Component failure for 'test-pillar-1'.
13:45:42.031 WARN o.b.i.c.IntegrityCollectorEventHandler - Failure: null: null: FAILED: , Operation failed
Test success: testRetryCollectionWhenNegativeReply
Starting testcase FileInfoTest
Test starting: testFileInfo
Description: Tests the FileInfo element. Adds all data and extracts it again.
Step: Setup the file info.
Step: Change the checksum
Step: Change the date for last file id check
Step: Change the date for last checksum check
Test success: testFileInfo
Starting testcase HandleChecksumValidationStepTest
Test starting: testAuditTrailsForChecksumErrors
Description: Test audit trails for checksum errors. Verify that a pillar with a single checksum will be pointed out as the possible cause.
Step: Test step on data without checksum error
Step: Test step on data where only two pillars have the file and they disagree about the checksum.
number of files in the collection2
number of fileinfos: 3
Step: remove the last auditinfo
Step: Test step on data where two pillars have one checksum and the last pillar has a different one
Test success: testAuditTrailsForChecksumErrors
Test starting: testChecksumMajority
Description: Test the checksum integrity validator when two pillars have one checksum and the last pillar has another checksum.
Step: Add data to the cache
Step: Perform the checksum validation step
Step: Validate the file ids
Test success: testChecksumMajority
Test starting: testMissingAtOnePillar
Description: Test the checksum integrity validator when one pillar is missing the data.
Step: Update the cache with identitical data for both pillars.
Step: Perform the step
Step: Validate the file ids
Test success: testMissingAtOnePillar
Test starting: testNoData
Description: Test the checksum integrity validator without any data in the cache.
Step: Validate the file ids
Test success: testNoData
Test starting: testSimilarData
Description: Test the checksum integrity validator when all pillars have similar data.
Step: Add data to the cache
Step: Perform the step
Step: Validate the file ids
Test success: testSimilarData
Test starting: testThreeDisagreeingChecksums
Description: Test the checksum integrity validator when all pillars have different checksums.
Step: Add data to the cache
Step: Perform the step
Step: Validate the file ids
Test success: testThreeDisagreeingChecksums
Test starting: testTwoDisagreeingChecksums
Description: Test the checksum integrity validator when only two pillar has data, but it it different.
Step: Add data to the cache
Step: Perform the step
Step: Validate the file ids
Test success: testTwoDisagreeingChecksums
Starting testcase IntegrityDBToolsTest
Test starting: testAddCollectionSuccess
Description: Tests that a new collection can be added to the integrity database
Step: Extract initial list of collections
Step: Add the new collection
Test success: testAddCollectionSuccess
Test starting: testAddExistingCollection
Description: Tests that an existing collectionID cannot be added to the integrity database.
Step: Extract initial list of collections.
Step: Attempt to add the new collection.
Test success: testAddExistingCollection
Test starting: testRemoveNonExistingCollection
Description: Tests that a non existing collection can't be removed from the integrity database.
Step: Extract initial list of collections.
Step: Attempt to remove the non-existing collection.
Test success: testRemoveNonExistingCollection
Starting testcase UpdateChecksumsStepTest
Test starting: testAbortWorkflowWhenNegativeReply
Description: Test the step for updating the checksums will abort the workflow in case of FAILURE operation event and AbortOnFailedContributor = true .
13:46:00.964 WARN o.b.i.c.IntegrityCollectorEventHandler - Component failure for 'test-pillar-1'.
13:46:00.965 WARN o.b.i.c.IntegrityCollectorEventHandler - Failure: null: null: FAILED: , Problem encountered
Test success: testAbortWorkflowWhenNegativeReply
Test starting: testCallForChangingChecksumStates
Description: Test the step for updating the checksums delivers the results to the integrity model.
Test success: testCallForChangingChecksumStates
Test starting: testContinueWorkflowNegativeReply
Description: Test the step for updating the checksums will continue the workflow in case of FAILURE operation event and AbortOnFailedContributor = false .
13:46:01.099 WARN o.b.i.c.IntegrityCollectorEventHandler - Component failure for 'test-pillar-1'.
13:46:01.100 WARN o.b.i.c.IntegrityCollectorEventHandler - Failure: null: null: FAILED: , Problem encountered
Test success: testContinueWorkflowNegativeReply
Test starting: testFullChecksumCollection
Description: Test that the full list of checksums is requested.
Test success: testFullChecksumCollection
Test starting: testIncrementalChecksumCollection
Description: Test that only the list of new checksums is requested.
Test success: testIncrementalChecksumCollection
Test starting: testIngestOfResults
Description: Test the step for updating the checksums delivers the results to the integrity model.
Test success: testIngestOfResults
Test starting: testPartialResults
Description: Test that the number of partial is used for generating more than one request.
Step: Setup the collector mock to generate a isPartialResult=true event the first time and a isPartialResult=false the second time
Test success: testPartialResults
Test starting: testPositiveReply
Description: Test the step for updating the checksums can handle COMPLETE operation event.
Test success: testPositiveReply
Test starting: testRetryCollectionWhenNegativeReply
Description: Test the step for updating the file ids will retry on a FAILED event
13:46:01.428 WARN o.b.i.c.IntegrityCollectorEventHandler - Component failure for 'test-pillar-1'.
13:46:01.429 WARN o.b.i.c.IntegrityCollectorEventHandler - Failure: null: null: FAILED: , Problem encountered
Test success: testRetryCollectionWhenNegativeReply
Starting testcase IntegrityWorkflowManagerTest
Test starting: collectionSpecificWorkflows
Description: Verifies that the IntegrityWorkflowManager loads correctly for workflows configured for specific collection.
Step: Create a IntegrityWorkflowManager based on a workflow with different schedules for collection 1 and 2 (daily and hourly)
Test success: collectionSpecificWorkflows
Test starting: noWorkflowPackage
Description: Verifies that the IntegrityWorkflowManager loads correctly for at workflow configuration with a workflow class name without a package scope (located in the deafult workflow package).
Step: Create a IntegrityWorkflowManager based on a single Testworkflow with a daily schedule in a to collection system, where the className is just the simplename
Test success: noWorkflowPackage
Test starting: noWorkflowSettings
Description: Verifies that the IntegrityWorkflowManager loads correctly for missing reference settings a workflow settings element.
Step: Create a IntegrityWorkflowManager based on a workflowsettingsless configuration
Test success: noWorkflowSettings
Test starting: normalWorkflowSettings
Description: Verifies that the IntegrityWorkflowManager loads correctly for at normally defined workflow.
Step: Create a IntegrityWorkflowManager based on a single Testworkflow with a daily schedule in a to collection system
Test success: normalWorkflowSettings
Test starting: startWorkflow
Description: Verifies that the that it is possible to manually start a workflow.
Step: Call the startWorkflow with a workflow defined in the configuration
Test success: startWorkflow
Test starting: unscheduledWorkflow
Description: Verifies that the IntegrityWorkflowManager loads workflow correctly for workflows without a defined schedule meaning they are never run automatically.
Step: Create a IntegrityWorkflowManager based on a single Testworkflow without a schedule
Test success: unscheduledWorkflow
Starting testcase MaxChecksumAgeProviderTest
Test starting: testNoPillarSpecificSetting
Description: Test the MaxChecksumAge when no settings are defined for the specific pillar
Step: Create a MaxChecksumAgeProvider with settings containing a default MaxAge of 10 and no pillar specific settings
Test success: testNoPillarSpecificSetting
Test starting: testNoSettings
Description: Test the MaxChecksumAge when no settings are defined
Step: Create a MaxChecksumAgeProvider with null settings and a default MaxAge of 100
Test success: testNoSettings
Test starting: testPillarSpecificSetting
Description: Test the MaxChecksumAge when a value has been defined for specific pillars
Step: Create a MaxChecksumAgeProvider with settings containing a default MaxAge of 10, pillar1MaxChecksumAge of 1001 and pillar2 MaxChecksumAge of 1002
Test success: testPillarSpecificSetting
Starting testcase SaltedChecksumWorkflowTest
Test starting: testInconsistentChecksums
Description: Test that the workflow discovers and handles inconsistent checksums
Step: Prepare for calls to mocks
Step: Run workflow for checking salted checksum.
13:46:01.905 WARN o.b.i.w.SaltedChecksumWorkflow - Failure in checksum salted checksum: Inconsistent salted checksum found for file 'test-file-1' with checksumspec 'HMAC_MD5' and salt '24430245f06f0f4661f9c59f472bbf7f6a7a'. The pillars had the checksums: {pillar2=efefcefc, pillar1=bfecefef}
Test success: testInconsistentChecksums
Test starting: testNoFilesInCollection
Description: Test that the workflow does nothing, when it has no files in the collection.
Step: Prepare for calls to mocks
Step: Run workflow for checking salted checksum.
Test success: testNoFilesInCollection
Test starting: testNoReceivedChecksums
Description: Test that the workflow handles the case, when no checksums are received
Step: Prepare for calls to mocks
Step: Run workflow for checking salted checksum.
13:46:02.011 WARN o.b.i.c.SimpleChecksumEventHandler - Failure: null: null: FAILED: ,
13:46:02.012 WARN o.b.i.w.SaltedChecksumWorkflow - Failure in checksum salted checksum: No checksums with checksumSpec 'org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@418ceffa[checksumType=HMAC_MD5, checksumSalt={100,-94,-95,59,-4,-28,47,79,-112,-8,-76,63,-64,-46,-51,-102,83,9}, otherChecksumType=<null>(default)]' received for file 'test-file-1'.
Test success: testNoReceivedChecksums
Test starting: testOneComponentFailureAndTwoOtherAgreeOnChecksum
Description: Test that the workflow works when both pillars deliver the same checksum.
Step: Prepare for calls to mocks
Step: Run workflow for checking salted checksum.
13:46:02.065 WARN o.b.i.c.SimpleChecksumEventHandler - Component failure for 'pillar3'.
13:46:02.065 WARN o.b.i.c.SimpleChecksumEventHandler - Failure: null: null: FAILED: , COMPONENT FAILED
Test success: testOneComponentFailureAndTwoOtherAgreeOnChecksum
Test starting: testOneComponentFailureAndTwoOtherDisagreeOnChecksum
Description: Test that the workflow works when both pillars deliver the same checksum.
Step: Prepare for calls to mocks
Step: Run workflow for checking salted checksum.
13:46:02.127 WARN o.b.i.c.SimpleChecksumEventHandler - Component failure for 'pillar3'.
13:46:02.128 WARN o.b.i.c.SimpleChecksumEventHandler - Failure: null: null: FAILED: , COMPONENT FAILED
13:46:02.128 WARN o.b.i.w.SaltedChecksumWorkflow - Failure in checksum salted checksum: Inconsistent salted checksum found for file 'test-file-1' with checksumspec 'HMAC_MD5' and salt 'a025ce47f3578f41acfb40afa6f486d5828d'. The pillars had the checksums: {pillar2=efefcefc, pillar1=bfecefef}
Test success: testOneComponentFailureAndTwoOtherDisagreeOnChecksum
Test starting: testSuccess
Description: Test that the workflow works when both pillars deliver the same checksum.
Step: Prepare for calls to mocks
Step: Run workflow for checking salted checksum.
Test success: testSuccess
Test starting: testConstructor
Test success: testConstructor
Test starting: testFailContributor
Test success: testFailContributor
Test starting: testFinishContributor
Test success: testFinishContributor
Test starting: testReloadContributors
Test success: testReloadContributors
Test starting: testRetry
Test success: testRetry
Test starting: testSucceed
Test success: testSucceed
Starting testcase IntegrityDAOTest
Test starting: initialStateExtractionTest
Description: Tests the initial state of the IntegrityModel. Should not contain any data.
Test success: initialStateExtractionTest
Test starting: instantiationTest
Description: Testing the connection to the integrity database.
Test success: instantiationTest
Test starting: reinitialiseDatabaseTest
Description: Testing the connection to the integrity database.
Step: Setup manually.
Step: Close the connection and create another one.
Test success: reinitialiseDatabaseTest
Test starting: testCorrectDateHandling
Description: Testing the correct ingest and extraction of file and checksum dates
Test success: testCorrectDateHandling
Test starting: testDeletingEntry
Description: Tests the deletion of an FileID entry from a collection. Checks that it does not effect another collection with a fileID equal to the deleted
Step: Create data
Step: Ensure that the data is present
Step: Delete the entry for the first pillar
Step: Delete the entry for the second pillar
Step: Check that the data in the extra collection is still present
Test success: testDeletingEntry
Test starting: testDeletingNonExistingEntry
Description: Tests the deletion of an nonexisting FileID entry.
Step: Create data
Step: Delete a nonexisting entry
Test success: testDeletingNonExistingEntry
Test starting: testExtractCollectionFileSize
Description: Tests that the accumulated size of the collection can be extracted
Step: Insert test data into database
Step: Check the reported size of the first pillar in the collection
Step: Check the reported size of the second pillar in the collection
Step: Check the reported size of the whole collection
Test success: testExtractCollectionFileSize
Test starting: testExtractingAllKnownFilesForPillars
Description: Tests that known files can be extracted for specific pillars.
Step: Insert two files into database for a pillar
Step: Insert a file to the extra collection for the common pillar
Step: Extract all the existing file ids for the pillar for collection 'TwoPillarCollection'
Step: Extract the single fileID for the extra collection
Step: Extract all the existing file ids for another pillar
Test success: testExtractingAllKnownFilesForPillars
Test starting: testExtractingAllKnownFilesForPillarsLimits
Description: Tests the limits for extracting files for specific pillars.
Step: Insert two files into database for a pillar
Step: Extract with a maximum of 1
Step: Extract with a minimum of 1 and maximum of infinite
Test success: testExtractingAllKnownFilesForPillarsLimits
Test starting: testExtractingAllMissingFiles
Description: Tests that missing files can be extracted.
Step: Insert two files into database for a pillar and mark them as missing
Step: Check the number of files in collection and on pillars
Step: Extract missing files
Test success: testExtractingAllMissingFiles
Test starting: testExtractingAllMissingFilesForPillarsLimits
Description: Tests the limits for extracting missing files for specific pillars.
Step: Insert two files into database for a pillar and set them to missing
Step: Extract with a maximum of 1
Step: Extract with a minimum of 1 and maximum of infinite
Test success: testExtractingAllMissingFilesForPillarsLimits
Test starting: testFindInconsistentChecksum
Description: Testing the localization of inconsistent checksums
Step: Update the database with 2 inconsistent files and one consistent file.
Step: Find the files with inconsistent checksums
Test success: testFindInconsistentChecksum
Test starting: testFindOrphanFiles
Description: Tests the ability to find orphan files.
Step: Create data
Test success: testFindOrphanFiles
Test starting: testGetFileIDAtIndex
Description: Tests that a fileID at a given index can be extracted.
Step: Extract a fileID from the empty database
Step: Insert test data into database
Step: Extract the first fileID
Step: Extract a fileID at an incomprehendable index from the database
Test success: testGetFileIDAtIndex
Test starting: testGetLatestChecksumDateEntryForCollection
Description: Tests that checksum date entries can be retrieved and manipulated.
Step: Create data
Test success: testGetLatestChecksumDateEntryForCollection
Test starting: testGetLatestFileDateEntryForCollection
Description: Tests that checksum date entries can be retrieved and manipulated.
Step: Create data
Test success: testGetLatestFileDateEntryForCollection
Test starting: testIngestOfChecksumsData
Description: Tests the ingesting of checksums data
Step: Create data
Step: Extract the data
Step: Check that the extra collection is untouched by the ingest
Test success: testIngestOfChecksumsData
Test starting: testIngestOfFileIDsData
Description: Tests the ingesting of file ids data
Step: Create data
Step: Extract the data
Step: Check that the extra collection is untouched by the ingest
Test success: testIngestOfFileIDsData
Test starting: testMissingChecksums
Description: Testing the checksum validation, when only one pillar has a checksum for a file.
Step: Update the database with 1 file, missing its checksum on one pillar.
Step: Finding the files with inconsistent checksums
Test success: testMissingChecksums
Test starting: testMissingChecksumsChecksumNotUpdated
Description: Testing the checksum validation, when only one pillar has a checksum for a file.
Step: Update the database with 1 file, no missing checksums.
Step: Finding the files with inconsistent checksums
Step: Updating the checksum for one pillar, and checking that the other pillars checksum is now missing
Step: Finding the files with inconsistent checksums
Test success: testMissingChecksumsChecksumNotUpdated
Test starting: testNoChecksums
Description: Testing the checksum validation, when no checksums exists.
Step: Update the database with 2 inconsistent files and one consistent file.
Step: Finding the files with inconsistent checksums
Test success: testNoChecksums
Test starting: testOutdatedChecksums
Description: Testing the checksum validation, when only one pillar has a checksum for a file.
Step: Update the database with one file, one pillar having an outdated checksum.
Step: Finding the files with inconsistent checksums
Test success: testOutdatedChecksums
Starting testcase MissingChecksumTests
Test starting: testMissingChecksumAndStep
Description: Test that files initially are set to checksum-state unknown, and to missing in the missing checksum step.
Step: Ingest file to database
Step: Run missing checksum step.
Test success: testMissingChecksumAndStep
Test starting: testMissingChecksumDuringSecondIngest
Description: Test that checksums are set to missing, when not found during GetChecksum, even though they have been found before.
Step: Ingest file to database
Step: Add checksum results for both pillar.
Step: Check whether checksum is missing
Step: Add checksum results for only the second pillar.
Step: Check whether checksum is missing
Test success: testMissingChecksumDuringSecondIngest
Test starting: testMissingChecksumForFirstGetChecksums
Description: Test that checksums are set to missing, when not found during GetChecksum.
Step: Ingest file to database
Step: Add checksum results for only one pillar.
Step: Check whether checksum is missing
Test success: testMissingChecksumForFirstGetChecksums
Starting testcase PutFileStepTest
Test starting: testNegativeReply
Description: Test the step for getting the file can handle FAILURE operation event.
Test success: testNegativeReply
Test starting: testPositiveReply
Description: Test the step for getting the file can handle COMPLETE operation event.
Test success: testPositiveReply
Starting testcase IntegrityDatabaseTest
Test starting: initialStateExtractionTest
Description: Tests the initial state of the IntegrityModel. Should not contain any data.
Step: Test the 'findChecksumsOlderThan'
Step: Test the 'findMissingChecksums'
Step: Test the 'findMissingFiles'
Step: Test the 'getAllFileIDs'
Step: Test the 'getFileInfos'
Step: Test the 'getPillarCollectionMetrics'
Test success: initialStateExtractionTest
Test starting: instantiationTest
Description: Tests that the connection can be instantaited.
Test success: instantiationTest
Test starting: testDeletingEntry
Description: Tests the deletion of an FileID entry.
Step: Create data
Step: Delete the entry
Test success: testDeletingEntry
Test starting: testIngestOfChecksumsData
Description: Tests the ingesting of checksums data
Step: Create data
Step: Extract the data
Test success: testIngestOfChecksumsData
Test starting: testIngestOfFileIDsData
Description: Tests the ingesting of file ids data
Step: Create data
Step: Extract the data
Test success: testIngestOfFileIDsData
Starting testcase GetChecksumForFileStepTest
Test starting: testComponentFailure
Description: Test step for retrieving the checksum of a single file, when one pillar fails.
Step: Setup mock answers
Step: Validate the file ids
13:46:45.466 WARN o.b.i.c.SimpleChecksumEventHandler - Component failure for 'test-pillar-3'.
13:46:45.467 WARN o.b.i.c.SimpleChecksumEventHandler - Failure: null: null: FAILED: , COMPONENT FAILED
Test success: testComponentFailure
Test starting: testFullData
Description: Test step for retrieving the checksum of a single file, when all three pillars deliver results.
Step: Setup mock answers
Step: Validate the checksum results
Test success: testFullData
Test starting: testNoResults
Description: Test step for retrieving the checksum of a single file, when no results are delivered.
Step: Setup mock answers
Step: Validate the checksum results
Test success: testNoResults
Finished testcase
Finished suite
Finished project
[INFO] Tests run: 104, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 70.835 s - in TestSuite
[INFO]
[INFO] Results:
[INFO]
[INFO] Tests run: 104, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[JENKINS] Recording test results
[INFO]
[INFO] --- jacoco-maven-plugin:0.8.5:report (report) @ bitrepository-integrity-service ---
[INFO] Loading execution data file /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integrity-service/target/jacoco.exec
[INFO] Analyzed bundle 'Bitrepository Integrity Service' with 79 classes
[INFO]
[INFO] --- maven-war-plugin:3.3.0:war (default-war) @ bitrepository-integrity-service ---
[INFO] Packaging webapp
[INFO] Assembling webapp [bitrepository-integrity-service] in [/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integrity-service/target/bitrepository-integrity-service-1.10-SNAPSHOT]
[INFO] Processing war project
[INFO] Copying webapp resources [/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integrity-service/src/main/webapp]
[INFO] Building war: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integrity-service/target/bitrepository-integrity-service-1.10-SNAPSHOT.war
[INFO]
[INFO] --- maven-jar-plugin:3.2.0:test-jar (default) @ bitrepository-integrity-service ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integrity-service/target/bitrepository-integrity-service-1.10-SNAPSHOT-tests.jar
[INFO]
[INFO] --- maven-source-plugin:3.2.1:jar-no-fork (attach-sources-no-fork) @ bitrepository-integrity-service ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integrity-service/target/bitrepository-integrity-service-1.10-SNAPSHOT-sources.jar
[INFO]
[INFO] --- maven-assembly-plugin:3.3.0:single (distribution) @ bitrepository-integrity-service ---
[INFO] Reading assembly descriptor: src/main/assembly/assembly.xml
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integrity-service/target/bitrepository-integrity-service-1.10-SNAPSHOT-distribution.tar.gz
[INFO]
[INFO] --- maven-install-plugin:3.0.0-M1:install (default-install) @ bitrepository-integrity-service ---
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integrity-service/target/bitrepository-integrity-service-1.10-SNAPSHOT.war to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integrity-service/1.10-SNAPSHOT/bitrepository-integrity-service-1.10-SNAPSHOT.war
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integrity-service/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integrity-service/1.10-SNAPSHOT/bitrepository-integrity-service-1.10-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integrity-service/target/bitrepository-integrity-service-1.10-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integrity-service/1.10-SNAPSHOT/bitrepository-integrity-service-1.10-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integrity-service/target/bitrepository-integrity-service-1.10-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integrity-service/1.10-SNAPSHOT/bitrepository-integrity-service-1.10-SNAPSHOT-sources.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integrity-service/target/bitrepository-integrity-service-1.10-SNAPSHOT-distribution.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integrity-service/1.10-SNAPSHOT/bitrepository-integrity-service-1.10-SNAPSHOT-distribution.tar.gz
[INFO]
[INFO] --- maven-deploy-plugin:3.0.0-M1:deploy (default-deploy) @ bitrepository-integrity-service ---
[INFO] Downloading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integrity-service/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integrity-service/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 67.7 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integrity-service/1.10-SNAPSHOT/bitrepository-integrity-service-1.10-20220215.124650-63.war
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integrity-service/1.10-SNAPSHOT/bitrepository-integrity-service-1.10-20220215.124650-63.war (21538 KB at 30900.2 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integrity-service/1.10-SNAPSHOT/bitrepository-integrity-service-1.10-20220215.124650-63.pom
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integrity-service/1.10-SNAPSHOT/bitrepository-integrity-service-1.10-20220215.124650-63.pom (6 KB at 174.9 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integrity-service/1.10-SNAPSHOT/bitrepository-integrity-service-1.10-20220215.124650-63-tests.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integrity-service/1.10-SNAPSHOT/bitrepository-integrity-service-1.10-20220215.124650-63-tests.jar (186 KB at 5446.6 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integrity-service/1.10-SNAPSHOT/bitrepository-integrity-service-1.10-20220215.124650-63-sources.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integrity-service/1.10-SNAPSHOT/bitrepository-integrity-service-1.10-20220215.124650-63-sources.jar (144 KB at 4942.2 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integrity-service/1.10-SNAPSHOT/bitrepository-integrity-service-1.10-20220215.124650-63-distribution.tar.gz
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integrity-service/1.10-SNAPSHOT/bitrepository-integrity-service-1.10-20220215.124650-63-distribution.tar.gz (21530 KB at 29819.2 KB/sec)
[INFO] Downloading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integrity-service/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integrity-service/maven-metadata.xml (495 B at 43.9 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integrity-service/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integrity-service/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 94.8 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integrity-service/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integrity-service/maven-metadata.xml (495 B at 21.0 KB/sec)
[JENKINS] Archiving disabled
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Alarm Service 1.10-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:3.1.0:clean (default-clean) @ bitrepository-alarm-service ---
[INFO]
[INFO] --- maven-enforcer-plugin:3.0.0-M3:enforce (enforce-maven) @ bitrepository-alarm-service ---
[INFO]
[INFO] --- jacoco-maven-plugin:0.8.5:prepare-agent (default) @ bitrepository-alarm-service ---
[INFO] argLine set to -javaagent:/home/cibuild01/.m2/repository/org/jacoco/org.jacoco.agent/0.8.5/org.jacoco.agent-0.8.5-runtime.jar=destfile=/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-alarm-service/target/jacoco.exec
[INFO]
[INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ bitrepository-alarm-service ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 8 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.8.1:compile (default-compile) @ bitrepository-alarm-service ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 27 source files to /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-alarm-service/target/classes
[INFO]
[INFO] --- forbiddenapis:2.7:check (default) @ bitrepository-alarm-service ---
[INFO] Scanning for classes to check...
[INFO] Reading bundled API signatures: jdk-unsafe-1.8
[INFO] Reading bundled API signatures: jdk-deprecated-1.8
[INFO] Reading bundled API signatures: jdk-non-portable
[INFO] Reading bundled API signatures: jdk-reflection
[INFO] Loading classes to check...
[INFO] Scanning classes for violations...
[INFO] Scanned 27 class file(s) for forbidden API invocations (in 0.09s), 0 error(s).
[INFO]
[INFO] --- forbiddenapis:2.7:testCheck (default) @ bitrepository-alarm-service ---
[INFO] Scanning for classes to check...
[WARNING] Classes directory does not exist, forbiddenapis check skipped: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-alarm-service/target/test-classes
[INFO]
[INFO] --- maven-resources-plugin:3.1.0:testResources (default-testResources) @ bitrepository-alarm-service ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.8.1:testCompile (default-testCompile) @ bitrepository-alarm-service ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 6 source files to /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-alarm-service/target/test-classes
[INFO]
[INFO] --- maven-surefire-plugin:3.0.0-M4:test (default-test) @ bitrepository-alarm-service ---
[INFO]
[INFO] -------------------------------------------------------
[INFO] T E S T S
[INFO] -------------------------------------------------------
[INFO] Running TestSuite
Starting test project Alarm Service Test
Suite: Surefire suite
Starting testcase AlarmDatabaseTest
Test starting: AlarmDatabaseExtractionTest
Description: Testing the connection to the alarm service database especially with regards to extracting the data from it.
Step: Setup the variables and constants.
Step: Adds the variables to the settings and instantaites the database cache
Step: Populate the database with two alarms.
Step: Try to extract all the data from the database.
Step: Try to extract the alarms for component 1.
Step: Try to extract the alarms for component 2.
Step: Try to extract the alarms for the alarm code 'COMPONENT_FAILURE'.
Step: Try to extract the alarms for the alarm code 'CHECKSUM_ALARM'.
Step: Try to extract the new alarm.
Step: Try to extract the old alarm.
Step: Try to extract the alarms for the file id.
Step: Try to extract the alarms for the collection id.
Step: Try to extract the oldest alarm from the database.
Step: Try to extract the newest alarm from the database.
Test success: AlarmDatabaseExtractionTest
Test starting: AlarmDatabaseLargeIngestionTest
Description: Testing the ingestion of a large texts into the database
Step: Setup and create alarm
Step: Insert the data into the database
Test success: AlarmDatabaseLargeIngestionTest
Test starting: alarmDatabaseCorrectTimestampTest
Description: Testing the correct ingest and extraction of alarm dates
Step: Prepare, check and ingest alarms
Step: Extract and check alarms
Test success: alarmDatabaseCorrectTimestampTest
Step: Cleanup after test.
Starting testcase AlarmHandlerTest
Test starting: alarmMediatorTest
Description: Test the mediator handling of alarm messages.
Step: Setup mediator and create alarm handler.
Step: Try giving it a non-alarm message
13:47:02.104 WARN o.b.alarm.handling.AlarmMediator - Recieved unexpected message: 'org.bitrepository.bitrepositorymessages.Message@27ad844d[correlationID=<null>(default), collectionID=<null>(default), destination=<null>(default), replyTo=<null>(default), from=<null>(default), to=<null>(default), version=<null>(default), minVersion=<null>(default)]'
Step: Giv the mediator an AlarmMessage
Step: Close the mediator.
Test success: alarmMediatorTest
Starting testcase AlarmExceptionTest
Test starting: alarmExceptionTest
Description: Tests that AlarmExceptions can be thrown.
Test success: alarmExceptionTest
Starting testcase AlarmDatabaseExtractionModelTest
Test starting: alarmExceptionTest
Description: Test the AlarmDatabaseExtractionModel class
Step: Define constants etc.
Step: Create an empty model
Step: Test the AlarmCode
Step: Test the ascending
Step: Test the ComponentID
Step: Test the EndDate
Step: Test the FileID
Step: Test the MaxCount
Step: Test the StartDate
Step: Test the CollectionID
Test success: alarmExceptionTest
Finished testcase
Finished suite
Finished project
[INFO] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 7.791 s - in TestSuite
[INFO]
[INFO] Results:
[INFO]
[INFO] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[JENKINS] Recording test results
[INFO]
[INFO] --- jacoco-maven-plugin:0.8.5:report (report) @ bitrepository-alarm-service ---
[INFO] Loading execution data file /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-alarm-service/target/jacoco.exec
[INFO] Analyzed bundle 'Bitrepository Alarm Service' with 23 classes
[INFO]
[INFO] --- maven-war-plugin:3.3.0:war (default-war) @ bitrepository-alarm-service ---
[INFO] Packaging webapp
[INFO] Assembling webapp [bitrepository-alarm-service] in [/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-alarm-service/target/bitrepository-alarm-service-1.10-SNAPSHOT]
[INFO] Processing war project
[INFO] Copying webapp resources [/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-alarm-service/src/main/webapp]
[INFO] Building war: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-alarm-service/target/bitrepository-alarm-service-1.10-SNAPSHOT.war
[INFO]
[INFO] --- maven-jar-plugin:3.2.0:test-jar (default) @ bitrepository-alarm-service ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-alarm-service/target/bitrepository-alarm-service-1.10-SNAPSHOT-tests.jar
[INFO]
[INFO] --- maven-source-plugin:3.2.1:jar-no-fork (attach-sources-no-fork) @ bitrepository-alarm-service ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-alarm-service/target/bitrepository-alarm-service-1.10-SNAPSHOT-sources.jar
[INFO]
[INFO] --- maven-assembly-plugin:3.3.0:single (distribution) @ bitrepository-alarm-service ---
[INFO] Reading assembly descriptor: src/main/assembly/assembly.xml
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-alarm-service/target/bitrepository-alarm-service-1.10-SNAPSHOT-distribution.tar.gz
[INFO]
[INFO] --- maven-install-plugin:3.0.0-M1:install (default-install) @ bitrepository-alarm-service ---
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-alarm-service/target/bitrepository-alarm-service-1.10-SNAPSHOT.war to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-alarm-service/1.10-SNAPSHOT/bitrepository-alarm-service-1.10-SNAPSHOT.war
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-alarm-service/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-alarm-service/1.10-SNAPSHOT/bitrepository-alarm-service-1.10-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-alarm-service/target/bitrepository-alarm-service-1.10-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-alarm-service/1.10-SNAPSHOT/bitrepository-alarm-service-1.10-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-alarm-service/target/bitrepository-alarm-service-1.10-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-alarm-service/1.10-SNAPSHOT/bitrepository-alarm-service-1.10-SNAPSHOT-sources.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-alarm-service/target/bitrepository-alarm-service-1.10-SNAPSHOT-distribution.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-alarm-service/1.10-SNAPSHOT/bitrepository-alarm-service-1.10-SNAPSHOT-distribution.tar.gz
[INFO]
[INFO] --- maven-deploy-plugin:3.0.0-M1:deploy (default-deploy) @ bitrepository-alarm-service ---
[INFO] Downloading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-alarm-service/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-alarm-service/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 70.9 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-alarm-service/1.10-SNAPSHOT/bitrepository-alarm-service-1.10-20220215.124706-63.war
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-alarm-service/1.10-SNAPSHOT/bitrepository-alarm-service-1.10-20220215.124706-63.war (21403 KB at 36275.3 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-alarm-service/1.10-SNAPSHOT/bitrepository-alarm-service-1.10-20220215.124706-63.pom
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-alarm-service/1.10-SNAPSHOT/bitrepository-alarm-service-1.10-20220215.124706-63.pom (4 KB at 165.5 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-alarm-service/1.10-SNAPSHOT/bitrepository-alarm-service-1.10-20220215.124706-63-tests.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-alarm-service/1.10-SNAPSHOT/bitrepository-alarm-service-1.10-20220215.124706-63-tests.jar (77 KB at 3325.7 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-alarm-service/1.10-SNAPSHOT/bitrepository-alarm-service-1.10-20220215.124706-63-sources.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-alarm-service/1.10-SNAPSHOT/bitrepository-alarm-service-1.10-20220215.124706-63-sources.jar (47 KB at 2101.4 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-alarm-service/1.10-SNAPSHOT/bitrepository-alarm-service-1.10-20220215.124706-63-distribution.tar.gz
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-alarm-service/1.10-SNAPSHOT/bitrepository-alarm-service-1.10-20220215.124706-63-distribution.tar.gz (21402 KB at 35669.2 KB/sec)
[INFO] Downloading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-alarm-service/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-alarm-service/maven-metadata.xml (491 B at 22.8 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-alarm-service/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-alarm-service/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 40.5 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-alarm-service/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-alarm-service/maven-metadata.xml (491 B at 19.2 KB/sec)
[JENKINS] Archiving disabled
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Audit Trail Service 1.10-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:3.1.0:clean (default-clean) @ bitrepository-audit-trail-service ---
[INFO]
[INFO] --- maven-enforcer-plugin:3.0.0-M3:enforce (enforce-maven) @ bitrepository-audit-trail-service ---
[INFO]
[INFO] --- jacoco-maven-plugin:0.8.5:prepare-agent (default) @ bitrepository-audit-trail-service ---
[INFO] argLine set to -javaagent:/home/cibuild01/.m2/repository/org/jacoco/org.jacoco.agent/0.8.5/org.jacoco.agent-0.8.5-runtime.jar=destfile=/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-audit-trail-service/target/jacoco.exec
[INFO]
[INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ bitrepository-audit-trail-service ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 11 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.8.1:compile (default-compile) @ bitrepository-audit-trail-service ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 24 source files to /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-audit-trail-service/target/classes
[INFO]
[INFO] --- forbiddenapis:2.7:check (default) @ bitrepository-audit-trail-service ---
[INFO] Scanning for classes to check...
[INFO] Reading bundled API signatures: jdk-unsafe-1.8
[INFO] Reading bundled API signatures: jdk-deprecated-1.8
[INFO] Reading bundled API signatures: jdk-non-portable
[INFO] Reading bundled API signatures: jdk-reflection
[INFO] Loading classes to check...
[INFO] Scanning classes for violations...
[INFO] Scanned 29 class file(s) for forbidden API invocations (in 0.12s), 0 error(s).
[INFO]
[INFO] --- forbiddenapis:2.7:testCheck (default) @ bitrepository-audit-trail-service ---
[INFO] Scanning for classes to check...
[WARNING] Classes directory does not exist, forbiddenapis check skipped: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-audit-trail-service/target/test-classes
[INFO]
[INFO] --- maven-resources-plugin:3.1.0:testResources (default-testResources) @ bitrepository-audit-trail-service ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 3 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.8.1:testCompile (default-testCompile) @ bitrepository-audit-trail-service ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 8 source files to /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-audit-trail-service/target/test-classes
[INFO]
[INFO] --- maven-surefire-plugin:3.0.0-M4:test (default-test) @ bitrepository-audit-trail-service ---
[INFO]
[INFO] -------------------------------------------------------
[INFO] T E S T S
[INFO] -------------------------------------------------------
[INFO] Running TestSuite
Starting test project Core module test
Suite: Surefire suite
Starting testcase AuditDatabaseTest
Test starting: AuditDatabaseExtractionTest
Description: Testing the connection to the audit trail service database especially with regards to extracting the data from it.
Step: Setup the variables and constants.
Step: Adds the variables to the settings and instantaites the database cache
Step: Validate that the database is empty and then populate it.
Step: Extract the audit trails
Step: Test the extraction of FileID
Step: Test the extraction of CollectionID
Step: Perform extraction based on the component id.
Step: Perform extraction based on the sequence number restriction
Step: Perform extraction based on actor id restriction.
Step: Perform extraction based on operation restriction.
Step: Perform extraction based on date restriction.
Step: Perform extraction based on fingerprint restriction.
Step: Perform extraction based on operationID restriction.
Test success: AuditDatabaseExtractionTest
Test starting: AuditDatabaseGoodIngestTest
Description: Testing good case ingest of audittrails into the database
Step: Adds the variables to the settings and instantaites the database cache
Step: Build test data
Test success: AuditDatabaseGoodIngestTest
Test starting: AuditDatabaseIngestTest
Description: Testing ingest of audittrails into the database
Step: Adds the variables to the settings and instantaites the database cache
Step: Test ingesting with all data
Step: Test ingesting with no timestamp
Step: Test ingesting with no file action
Step: Test ingesting with no actor
Step: Test ingesting with no audit info
Step: Test ingesting with no file id
Step: Test ingesting with no info
Step: Test ingesting with no component id
Step: Test ingesting with no sequence number
Step: Test ingest with very long auditInfo (255+)
Step: Test ingest with very long info (255+)
Test success: AuditDatabaseIngestTest
Test starting: AuditDatabasePreservationTest
Description: Tests the functions related to the preservation of the database.
Step: Adds the variables to the settings and instantaites the database cache
Step: Validate the preservation sequence number
Step: Validate the insertion of the preservation sequence number
Test success: AuditDatabasePreservationTest
Test starting: auditDatabaseCorrectTimestampTest
Description: Testing the correct ingest and extraction of audittrail dates
Test success: auditDatabaseCorrectTimestampTest
Starting testcase AuditServiceDatabaseMigrationTest
Test starting: testMigratingAuditServiceDatabase
Description: Tests that the database can be migrated to latest version with the provided scripts.
Step: Validate setup
Step: Perform migration
13:47:26.811 WARN o.b.service.database.DatabaseUtils - Migrating AuditServiceDB from version 2 to 3.
13:47:27.178 WARN o.b.service.database.DatabaseUtils - Migrating AuditServiceDB from version 3 to 4.
13:47:27.241 WARN o.b.service.database.DatabaseUtils - Migrating AuditServiceDB from version 4 to 5.
13:47:27.370 WARN o.b.service.database.DatabaseUtils - Migrating AuditServiceDB from version 5 to 6.
Test success: testMigratingAuditServiceDatabase
Starting testcase AuditCollectorTest
Test starting: auditCollectorIntervalTest
Description: Test that the collector calls the AuditClient at the correct intervals.
Test success: auditCollectorIntervalTest
Starting testcase IncrementalCollectorTest
Test starting: collectionIDFailureTest
Description: Tests what happens when a wrong collection id is received.
Step:
Step: Start a collection with two contributors
Step: Send an auditTrail result from contributor 1 with a wrong collection id.
13:47:30.807 WARN o.b.a.collector.IncrementalCollector - Received bad collection id! Expected 'dummy-collection', but got 'FalseCollection1644929250698'.
Test success: collectionIDFailureTest
Test starting: contributorFailureTest
Description: Tests that the collector is able to collect from the remaining contributors if a contributor fails.
Step:
Step: Start a collection with two contributors
Step: Send a audit trail result from contributor 2 with the PartialResults boolean set to true and a failed event from contributor 1
13:47:30.928 WARN o.b.a.collector.IncrementalCollector - Event: null: null: COMPONENT_FAILED: ContributorID Contributor1 ResponseCode: REQUEST_NOT_SUPPORTED
13:47:30.929 WARN o.b.a.collector.IncrementalCollector - Event: null: null: FAILED: ,
Step: Send another audit trail result from contributor 2 with PartialResults set to false
13:47:30.933 ERROR o.b.a.collector.IncrementalCollector - Problem in collecting audittrails, collection will not be complete for collection 'dummy-collection'
org.bitrepository.client.exceptions.NegativeResponseException:
at org.bitrepository.access.getaudittrails.BlockingAuditTrailClient.getAuditTrails(BlockingAuditTrailClient.java:65)
at org.bitrepository.audittrails.collector.IncrementalCollector.collect(IncrementalCollector.java:134)
at org.bitrepository.audittrails.collector.IncrementalCollector.performCollection(IncrementalCollector.java:111)
at org.bitrepository.audittrails.collector.IncrementalCollectorTest$CollectionRunner.run(IncrementalCollectorTest.java:352)
at java.lang.Thread.run(Thread.java:745)
Test success: contributorFailureTest
Test starting: multipleIncrementTest
Description: Verifies the behaviour in the case where the adit trails needs to be reteived in multiple requests because of MaxNumberOfResults limits.
Step: Start a collection with two contributors
Step: Send a audit trail result from contributor 1 and 2 with the PartialResults boolean set to true
Step: Send another audit trail result from the contributors, now with PartialResults set to false
Test success: multipleIncrementTest
Test starting: singleIncrementTest
Description: Verifies the behaviour in the simplest case with just one result set
Step: Start a collection with two contributors
Step: Send a audit trail result from contributor 1
Step: Send a audit trail result from contributor 2
Test success: singleIncrementTest
Starting testcase LocalAuditPreservationTest
Test starting: auditPreservationIngestTest
Description: Tests the ingest of the audit trail preservation.
Step: Setup variables and settings for the test
Step: Create the preserver and populate the store
Step: Call the preservation of audit trails now.
Test success: auditPreservationIngestTest
Starting testcase AuditPreservationEventHandlerTest
Test starting: auditPreservationEventHandlerTest
Description: Test the handling of the audit trail event handler.
Step: Setup
Step: Test the handling of another complete event.
Test success: auditPreservationEventHandlerTest
Finished testcase
Finished suite
Finished project
[INFO] Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 21.732 s - in TestSuite
[INFO]
[INFO] Results:
[INFO]
[INFO] Tests run: 13, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[JENKINS] Recording test results
[INFO]
[INFO] --- jacoco-maven-plugin:0.8.5:report (report) @ bitrepository-audit-trail-service ---
[INFO] Loading execution data file /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-audit-trail-service/target/jacoco.exec
[INFO] Analyzed bundle 'Bitrepository Audit Trail Service' with 24 classes
[INFO]
[INFO] --- maven-war-plugin:3.3.0:war (default-war) @ bitrepository-audit-trail-service ---
[INFO] Packaging webapp
[INFO] Assembling webapp [bitrepository-audit-trail-service] in [/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-audit-trail-service/target/bitrepository-audit-trail-service-1.10-SNAPSHOT]
[INFO] Processing war project
[INFO] Copying webapp resources [/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-audit-trail-service/src/main/webapp]
[INFO] Building war: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-audit-trail-service/target/bitrepository-audit-trail-service-1.10-SNAPSHOT.war
[INFO]
[INFO] --- maven-jar-plugin:3.2.0:test-jar (default) @ bitrepository-audit-trail-service ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-audit-trail-service/target/bitrepository-audit-trail-service-1.10-SNAPSHOT-tests.jar
[INFO]
[INFO] --- maven-source-plugin:3.2.1:jar-no-fork (attach-sources-no-fork) @ bitrepository-audit-trail-service ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-audit-trail-service/target/bitrepository-audit-trail-service-1.10-SNAPSHOT-sources.jar
[INFO]
[INFO] --- maven-assembly-plugin:3.3.0:single (distribution) @ bitrepository-audit-trail-service ---
[INFO] Reading assembly descriptor: src/main/assembly/assembly.xml
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-audit-trail-service/target/bitrepository-audit-trail-service-1.10-SNAPSHOT-distribution.tar.gz
[INFO]
[INFO] --- maven-install-plugin:3.0.0-M1:install (default-install) @ bitrepository-audit-trail-service ---
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-audit-trail-service/target/bitrepository-audit-trail-service-1.10-SNAPSHOT.war to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-audit-trail-service/1.10-SNAPSHOT/bitrepository-audit-trail-service-1.10-SNAPSHOT.war
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-audit-trail-service/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-audit-trail-service/1.10-SNAPSHOT/bitrepository-audit-trail-service-1.10-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-audit-trail-service/target/bitrepository-audit-trail-service-1.10-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-audit-trail-service/1.10-SNAPSHOT/bitrepository-audit-trail-service-1.10-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-audit-trail-service/target/bitrepository-audit-trail-service-1.10-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-audit-trail-service/1.10-SNAPSHOT/bitrepository-audit-trail-service-1.10-SNAPSHOT-sources.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-audit-trail-service/target/bitrepository-audit-trail-service-1.10-SNAPSHOT-distribution.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-audit-trail-service/1.10-SNAPSHOT/bitrepository-audit-trail-service-1.10-SNAPSHOT-distribution.tar.gz
[INFO]
[INFO] --- maven-deploy-plugin:3.0.0-M1:deploy (default-deploy) @ bitrepository-audit-trail-service ---
[INFO] Downloading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-audit-trail-service/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-audit-trail-service/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 94.9 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-audit-trail-service/1.10-SNAPSHOT/bitrepository-audit-trail-service-1.10-20220215.124736-63.war
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-audit-trail-service/1.10-SNAPSHOT/bitrepository-audit-trail-service-1.10-20220215.124736-63.war (21440 KB at 36154.2 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-audit-trail-service/1.10-SNAPSHOT/bitrepository-audit-trail-service-1.10-20220215.124736-63.pom
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-audit-trail-service/1.10-SNAPSHOT/bitrepository-audit-trail-service-1.10-20220215.124736-63.pom (4 KB at 193.8 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-audit-trail-service/1.10-SNAPSHOT/bitrepository-audit-trail-service-1.10-20220215.124736-63-tests.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-audit-trail-service/1.10-SNAPSHOT/bitrepository-audit-trail-service-1.10-20220215.124736-63-tests.jar (264 KB at 7522.2 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-audit-trail-service/1.10-SNAPSHOT/bitrepository-audit-trail-service-1.10-20220215.124736-63-sources.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-audit-trail-service/1.10-SNAPSHOT/bitrepository-audit-trail-service-1.10-20220215.124736-63-sources.jar (60 KB at 1867.1 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-audit-trail-service/1.10-SNAPSHOT/bitrepository-audit-trail-service-1.10-20220215.124736-63-distribution.tar.gz
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-audit-trail-service/1.10-SNAPSHOT/bitrepository-audit-trail-service-1.10-20220215.124736-63-distribution.tar.gz (21440 KB at 27451.2 KB/sec)
[INFO] Downloading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-audit-trail-service/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-audit-trail-service/maven-metadata.xml (497 B at 40.4 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-audit-trail-service/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-audit-trail-service/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 94.9 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-audit-trail-service/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-audit-trail-service/maven-metadata.xml (497 B at 28.6 KB/sec)
[JENKINS] Archiving disabled
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Reference Pillar 1.10-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:3.1.0:clean (default-clean) @ bitrepository-reference-pillar ---
[INFO]
[INFO] --- maven-enforcer-plugin:3.0.0-M3:enforce (enforce-maven) @ bitrepository-reference-pillar ---
[INFO]
[INFO] --- jacoco-maven-plugin:0.8.5:prepare-agent (default) @ bitrepository-reference-pillar ---
[INFO] argLine set to -javaagent:/home/cibuild01/.m2/repository/org/jacoco/org.jacoco.agent/0.8.5/org.jacoco.agent-0.8.5-runtime.jar=destfile=/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/jacoco.exec
[INFO]
[INFO] --- maven-dependency-plugin:3.1.2:unpack-dependencies (unpack-shared-sqlscripts) @ bitrepository-reference-pillar ---
[INFO] Unpacking /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-service/target/bitrepository-service-1.10-SNAPSHOT.jar to /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/classes with includes "**/*.sql" and excludes ""
[INFO]
[INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ bitrepository-reference-pillar ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 13 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.8.1:compile (default-compile) @ bitrepository-reference-pillar ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 44 source files to /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/classes
[WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/src/main/java/org/bitrepository/pillar/store/checksumdatabase/ChecksumExtractor.java:[236,25] explicit call to close() on an auto-closeable resource
[WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/src/main/java/org/bitrepository/pillar/store/checksumdatabase/ChecksumExtractor.java:[304,25] explicit call to close() on an auto-closeable resource
[WARNING] /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/src/main/java/org/bitrepository/pillar/store/checksumdatabase/ChecksumExtractor.java:[347,25] explicit call to close() on an auto-closeable resource
[INFO]
[INFO] --- forbiddenapis:2.7:check (default) @ bitrepository-reference-pillar ---
[INFO] Scanning for classes to check...
[INFO] Reading bundled API signatures: jdk-unsafe-1.8
[INFO] Reading bundled API signatures: jdk-deprecated-1.8
[INFO] Reading bundled API signatures: jdk-non-portable
[INFO] Reading bundled API signatures: jdk-reflection
[INFO] Loading classes to check...
[INFO] Scanning classes for violations...
[INFO] Scanned 44 class file(s) for forbidden API invocations (in 0.17s), 0 error(s).
[INFO]
[INFO] --- forbiddenapis:2.7:testCheck (default) @ bitrepository-reference-pillar ---
[INFO] Scanning for classes to check...
[WARNING] Classes directory does not exist, forbiddenapis check skipped: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/test-classes
[INFO]
[INFO] --- maven-resources-plugin:3.1.0:testResources (default-testResources) @ bitrepository-reference-pillar ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 13 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.8.1:testCompile (default-testCompile) @ bitrepository-reference-pillar ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 73 source files to /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/test-classes
[INFO]
[INFO] --- maven-surefire-plugin:3.0.0-M4:test (default-test) @ bitrepository-reference-pillar ---
[INFO]
[INFO] -------------------------------------------------------
[INFO] T E S T S
[INFO] -------------------------------------------------------
[INFO] Running TestSuite
Starting test project Reference Pillar Test
Suite: Surefire suite
Starting testcase ArchiveDirectoryTest
Test starting: testArchiveDirectoryExistingFile
Description: Test the ArchiveDirectory when the file exists
Step: Setup
Step: Validate the existence of the file
Step: Delete the file.
Test success: testArchiveDirectoryExistingFile
Test starting: testArchiveDirectoryExistingFolderFile
Description: Test the ArchiveDirectory when the file exists
Step: Setup
Step: Validate the existence of the file
Step: Delete the file.
Test success: testArchiveDirectoryExistingFolderFile
Test starting: testArchiveDirectoryMissingFile
Description: Test the ArchiveDirectory when the file is missing.
Step: Setup
Step: Validate the existence of the file
Step: Delete the file.
Test success: testArchiveDirectoryMissingFile
Test starting: testArchiveDirectoryMissingFolderFile
Description: Test the ArchiveDirectory when the file is missing.
Step: Setup
Step: Validate the existence of the file
Step: Delete the file.
Test success: testArchiveDirectoryMissingFolderFile
Test starting: testArchiveDirectoryMoveFileToArchive
Description: Testing the error scenarios when moving a file from tmp to archive for the ArchiveDirectory.
Step: Setup
Step: Moving file from tmp to archive
Step: Create file in both tmp and archive.
Step: Moving file from tmp to archive
Step: Remove the file from archive and try again
Test success: testArchiveDirectoryMoveFileToArchive
Test starting: testArchiveDirectoryMoveFolderFileToArchive
Description: Testing the error scenarios when moving a file from tmp to archive for the ArchiveDirectory.
Step: Setup
Step: Moving file from tmp to archive
Step: Create file in both tmp and archive.
Step: Moving file from tmp to archive
Step: Remove the file from archive and try again
Test success: testArchiveDirectoryMoveFolderFileToArchive
Test starting: testArchiveDirectoryNewFile
Description: Testing the ArchiveDirectory handling of a new file.
Step: Setup
Step: Retrieve tmp file
Step: Request a new file for the tmp dir
Step: Retrieve tmp file
Step: Request another new file with the same name
Step: Move the file from tmp to archive
Test success: testArchiveDirectoryNewFile
Test starting: testArchiveDirectoryNewFolderFile
Description: Testing the ArchiveDirectory handling of a new file.
Step: Setup
Step: Retrieve tmp file
Step: Request a new file for the tmp dir
Step: Retrieve tmp file
Step: Request another new file with the same name
Step: Move the file from tmp to archive
Test success: testArchiveDirectoryNewFolderFile
Test starting: testArchiveDirectoryRemoveFile
Description: Testing the error scenarios when removing files from the archive.
Step: Setup
Step: Remove nonexisting file from archive
Step: Remove nonexisting file from tmp
Step: Create file in both tmp, archive and retain directories.
Step: Remove the file from archive and tmp
Test success: testArchiveDirectoryRemoveFile
Test starting: testArchiveDirectoryRemoveFolderFile
Description: Testing the error scenarios when removing files from the archive.
Step: Setup
Step: Remove nonexisting file from archive
Step: Remove nonexisting file from tmp
Step: Create file in both tmp, archive and retain directories.
Step: Remove the file from archive and tmp
Test success: testArchiveDirectoryRemoveFolderFile
Starting testcase ChecksumEntryTest
Test starting: testExtendedTestCase
Description: Test the ChecksumEntry
Step: Create a ChecksumEntry
Test success: testExtendedTestCase
Starting testcase DeleteFileTest
Added fixture: Initialize a new Pillar.
Test starting: badCaseIdentification
Description: Tests the identification for a DeleteFile operation on the checksum pillar for the failure scenario, when the file is missing.
Step: Set up constants and variables.
Step: Setup for delivering pillar id and not having the file
Step: Create and send the identify request message.
Result: Received message on TEST-TOPIC-badCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileResponse@7388d94d[correlationID=526fee29-e305-4113-9a14-9e351f0b3252, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseIdentification-cibuild01-contributor, from=Pillar-badCaseIdentification, to=badCaseIdentification, version=31, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@6da14f7f[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], fileID=DefaultFilebadCaseIdentification, pillarID=Pillar-badCaseIdentification, pillarChecksumSpec=<null>(default), timeToDeliver=<null>(default)]
Step: Retrieve and validate the response getPillarID() the pillar.
Test success: badCaseIdentification
Added fixture: Initialize a new Pillar.
Test starting: badCaseOperationMissingVerification
Description: Tests the DeleteFile functionality of the pillar for the failure scenario, where it does not have the file.
Step: Set up constants and variables.
Step: Setup for delivering pillar id and having the file
Step: Create and send the actual DeleteFile message to the pillar.
Result: Received message on TEST-TOPIC-badCaseOperationMissingVerification-cibuild01 : org.bitrepository.bitrepositorymessages.DeleteFileFinalResponse@6d9bcf19[correlationID=876226c0-c4ab-463a-a288-14b86541193f, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationMissingVerification-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationMissingVerification-cibuild01-contributor, from=Pillar-badCaseOperationMissingVerification, to=badCaseOperationMissingVerification, version=31, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@23b4f0a9[responseCode=EXISTING_FILE_CHECKSUM_FAILURE, responseText=No mandatory checksum for destructive operation was supplied.], pillarID=Pillar-badCaseOperationMissingVerification, fileID=DefaultFilebadCaseOperationMissingVerification, checksumDataForExistingFile=<null>(default)]
13:47:49.065 WARN o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@56f8ab05[origDateTime=2022-02-15T13:47:49.064+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCaseOperationMissingVerification, alarmText=No mandatory checksum for destructive operation was supplied., fileID=DefaultFilebadCaseOperationMissingVerification, collectionID=TwoPillarCollection]
Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@652855c4[correlationID=afaa2d16-8bb5-4dd1-b6f1-1da7e5a0f42f, collectionID=TwoPillarCollection, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationMissingVerification-cibuild01-contributor, from=Pillar-badCaseOperationMissingVerification, to=<null>(default), version=31, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@56f8ab05[origDateTime=2022-02-15T13:47:49.064+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCaseOperationMissingVerification, alarmText=No mandatory checksum for destructive operation was supplied., fileID=DefaultFilebadCaseOperationMissingVerification, collectionID=TwoPillarCollection]]
Step: Retrieve the FinalResponse for the DeleteFile request
Step: Pillar should have sent an alarm
Test success: badCaseOperationMissingVerification
Added fixture: Initialize a new Pillar.
Test starting: badCaseOperationNoFile
Description: Tests the DeleteFile functionality of the pillar for the failure scenario, where it does not have the file.
Step: Set up constants and variables.
Step: Setup for delivering pillar id and not having the file
Step: Create and send the actual DeleteFile message to the pillar.
Result: Received message on TEST-TOPIC-badCaseOperationNoFile-cibuild01 : org.bitrepository.bitrepositorymessages.DeleteFileFinalResponse@51f91d19[correlationID=fe44da8a-ba90-4f99-bdaa-873ed7b6f3f3, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=31, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@5ce593bc[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileID=DefaultFilebadCaseOperationNoFile, checksumDataForExistingFile=<null>(default)]
Step: Retrieve the FinalResponse for the DeleteFile request
Test success: badCaseOperationNoFile
Added fixture: Initialize a new Pillar.
Test starting: goodCaseIdentification
Description: Tests the identification for a DeleteFile operation on the pillar for the successful scenario.
Step: Set up constants and variables.
Step: Setup for having the file and delivering pillar id
Step: Create and send the identify request message.
Result: Received message on TEST-TOPIC-goodCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileResponse@7ae3591b[correlationID=f8659fbd-4853-4a2e-96aa-55bf5e0d0754, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseIdentification-cibuild01-contributor, from=Pillar-goodCaseIdentification, to=goodCaseIdentification, version=31, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@67954d71[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], fileID=DefaultFilegoodCaseIdentification, pillarID=Pillar-goodCaseIdentification, pillarChecksumSpec=<null>(default), timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@234421ca[timeMeasureUnit=MILLISECONDS, timeMeasureValue=1000]]
Step: Retrieve and validate the response getPillarID() the pillar.
Test success: goodCaseIdentification
Starting testcase GetAuditTrailsTest
Added fixture: Initialize a new Pillar.
Test starting: checksumPillarGetAuditTrailsMaximumNumberOfResults
Description: Tests the GetAuditTrails functionality of the pillar for the successful scenario, where a limited number of audit trails are requested.
Step: Set up constants and variables.
Step: Send the request for the limited amount of audit trails to the pillar.
Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsMaximumNumberOfResults-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsProgressResponse@5c18ad5d[correlationID=066fa26d-3060-45f4-b747-7b01a2a1b2df, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsMaximumNumberOfResults-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults, to=Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults, version=31, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@497ccf3[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to extract the requested audit trails.], contributor=Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults, resultAddress=<null>(default)]
Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsMaximumNumberOfResults-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsFinalResponse@5fdfa35d[correlationID=066fa26d-3060-45f4-b747-7b01a2a1b2df, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsMaximumNumberOfResults-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults, to=Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults, version=31, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@43165282[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], contributor=Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@2976d625[resultAddress=<null>(default), auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@693afcd1[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@4bdd6fe0[sequenceNumber=1, fileID=fileID1644929272008, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=CHECKSUM_CALCULATED, actionDateTime=2022-02-15T13:47:52.011+01:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@3aaeb65b[sequenceNumber=2, fileID=fileID1644929272008, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=DELETE_FILE, actionDateTime=2022-02-15T13:47:52.011+01:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@25f688d5[sequenceNumber=3, fileID=fileID1644929272008, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=FAILURE, actionDateTime=2022-02-15T13:47:52.011+01:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@1b1434ce[sequenceNumber=4, fileID=fileID1644929272008, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=FILE_MOVED, actionDateTime=2022-02-15T13:47:52.011+01:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@3b96ea23[sequenceNumber=5, fileID=fileID1644929272008, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=GET_CHECKSUMS, actionDateTime=2022-02-15T13:47:52.012+01:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails]}]], partialResult=true]
Step: Validate the final response
Test success: checksumPillarGetAuditTrailsMaximumNumberOfResults
Added fixture: Initialize a new Pillar.
Test starting: checksumPillarGetAuditTrailsSpecificRequests
Description: Tests the GetAuditTrails functionality of the pillar for the successful scenario, where a specific audit trail are requested.
Step: Set up constants and variables.
Step: Send the identification request
Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsResponse@4cbf1c30[correlationID=2b5f24bb-a4a2-4118-878a-e7acfc8d5f36, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSpecificRequests-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSpecificRequests, to=Pillar-checksumPillarGetAuditTrailsSpecificRequests, version=31, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@3c5095df[responseCode=IDENTIFICATION_POSITIVE, responseText=<null>(default)]]
Step: Retrieve and validate the response.
Step: Make and send the request for the actual GetAuditTrails operation
Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsProgressResponse@71c264e5[correlationID=2b5f24bb-a4a2-4118-878a-e7acfc8d5f36, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSpecificRequests-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSpecificRequests, to=Pillar-checksumPillarGetAuditTrailsSpecificRequests, version=31, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@4528a871[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to extract the requested audit trails.], contributor=Pillar-checksumPillarGetAuditTrailsSpecificRequests, resultAddress=<null>(default)]
Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsFinalResponse@7d6e2366[correlationID=2b5f24bb-a4a2-4118-878a-e7acfc8d5f36, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSpecificRequests-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSpecificRequests, to=Pillar-checksumPillarGetAuditTrailsSpecificRequests, version=31, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@357f0cc9[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], contributor=Pillar-checksumPillarGetAuditTrailsSpecificRequests, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@57f8a3cf[resultAddress=<null>(default), auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@5713e261[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@5b6a9ef6[sequenceNumber=1, fileID=fileID1644929272287, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=OTHER, actionDateTime=2022-02-15T13:47:52.287+01:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails]}]], partialResult=false]
Step: Receive and validate the progress response.
Step: Receive and validate the final response
Step: Make another request, where both ingested audit trails is requested
Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsProgressResponse@16bed816[correlationID=2b5f24bb-a4a2-4118-878a-e7acfc8d5f36, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSpecificRequests-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSpecificRequests, to=Pillar-checksumPillarGetAuditTrailsSpecificRequests, version=31, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@4cae7d5[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to extract the requested audit trails.], contributor=Pillar-checksumPillarGetAuditTrailsSpecificRequests, resultAddress=<null>(default)]
Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsFinalResponse@4c821dc7[correlationID=2b5f24bb-a4a2-4118-878a-e7acfc8d5f36, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSpecificRequests-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSpecificRequests, to=Pillar-checksumPillarGetAuditTrailsSpecificRequests, version=31, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@4390b78f[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], contributor=Pillar-checksumPillarGetAuditTrailsSpecificRequests, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@230ea983[resultAddress=<null>(default), auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@70290678[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@5b6a9ef6[sequenceNumber=1, fileID=fileID1644929272287, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=OTHER, actionDateTime=2022-02-15T13:47:52.287+01:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@2c99419f[sequenceNumber=2, fileID=notThisFile, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=UnknownActor, actionOnFile=FAILURE, actionDateTime=2022-02-15T13:47:52.289+01:00, info=badInfo, operationID=operationID, certificateID=certificateid, auditTrailInformation=WrongAuditTrail]}]], partialResult=false]
Step: Receive and validate the progress response.
Step: Receive and validate the final response
Test success: checksumPillarGetAuditTrailsSpecificRequests
Added fixture: Initialize a new Pillar.
Test starting: checksumPillarGetAuditTrailsSuccessful
Description: Tests the GetAuditTrails functionality of the pillar for the successful scenario, where all audit trails are requested.
Step: Set up constants and variables.
Step: Send the identification request
Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSuccessful-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsResponse@71702d3f[correlationID=fad8a575-e8d7-4de2-adcb-efb9403d226e, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSuccessful-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSuccessful-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSuccessful, to=Pillar-checksumPillarGetAuditTrailsSuccessful, version=31, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@6f9d1785[responseCode=IDENTIFICATION_POSITIVE, responseText=<null>(default)]]
Step: Make and send the request for the actual GetAuditTrails operation
Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSuccessful-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsProgressResponse@f9b97dc[correlationID=fad8a575-e8d7-4de2-adcb-efb9403d226e, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSuccessful-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSuccessful-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSuccessful, to=Pillar-checksumPillarGetAuditTrailsSuccessful, version=31, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@25ea3a5f[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to extract the requested audit trails.], contributor=Pillar-checksumPillarGetAuditTrailsSuccessful, resultAddress=<null>(default)]
Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSuccessful-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsFinalResponse@5503e208[correlationID=fad8a575-e8d7-4de2-adcb-efb9403d226e, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSuccessful-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSuccessful-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSuccessful, to=Pillar-checksumPillarGetAuditTrailsSuccessful, version=31, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@5225f612[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], contributor=Pillar-checksumPillarGetAuditTrailsSuccessful, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@1d3aefd[resultAddress=<null>(default), auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@751f445a[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@3f46fb53[sequenceNumber=1, fileID=fileid, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=actor, actionOnFile=OTHER, actionDateTime=2022-02-15T13:47:52.588+01:00, info=info, operationID=operationID, certificateID=certificateID, auditTrailInformation=auditTrail]}]], partialResult=false]
Step: Receive and validate the progress response.
Step: Receive and validate the final response
Test success: checksumPillarGetAuditTrailsSuccessful
Starting testcase GetFileIDsTest
Added fixture: Initialize a new Pillar.
Test starting: badCaseIdentification
Description: Tests the identification for a GetFileIDs operation on the pillar for the failure scenario, when the file is missing.
Step: Set up constants and variables.
Step: Setup for delivering pillar id and not having the file
Step: Create and send the identify request message.
13:47:52.854 WARN o.b.p.m.IdentifyPillarsForGetFileIDsRequestHandler - The following file is missing 'DefaultFilebadCaseIdentification' at collection 'TwoPillarCollection'.
Result: Received message on TEST-TOPIC-badCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsResponse@4eef2522[correlationID=41bd221f-6601-452d-88a2-ea1494ccc9ba, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseIdentification-cibuild01-contributor, from=Pillar-badCaseIdentification, to=badCaseIdentification, version=31, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@c62d08a[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseIdentification, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@7b0f5814[fileID=DefaultFilebadCaseIdentification, allFileIDs=<null>(default)], timeToDeliver=<null>(default)]
Step: Retrieve and validate the response getPillarID() the pillar.
Test success: badCaseIdentification
Added fixture: Initialize a new Pillar.
Test starting: badCaseOperationNoFile
Description: Tests the GetFileIDs functionality of the pillar for the failure scenario, where it does not have the file.
Step: Set up constants and variables.
Step: Setup for not having the file
Step: Create and send the actual GetFileIDs message to the pillar.
13:47:54.142 WARN o.b.p.m.GetFileIDsRequestHandler - The following file is missing 'DefaultFilebadCaseOperationNoFile' at collection 'TwoPillarCollection'.
Result: Received message on TEST-TOPIC-badCaseOperationNoFile-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsFinalResponse@6e089bcb[correlationID=2945031c-58d0-4414-818a-c93d320ef97f, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=31, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@38a2fbc3[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@a8dedda[fileID=DefaultFilebadCaseOperationNoFile, allFileIDs=<null>(default)], resultingFileIDs=<null>(default), partialResult=<null>(default)]
13:47:54.150 WARN o.b.p.m.GetFileIDsRequestHandler - The following file is missing 'DefaultFilebadCaseOperationNoFile' at collection 'TwoPillarCollection'.
Result: Received message on TEST-TOPIC-badCaseOperationNoFile-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsFinalResponse@7e753fd6[correlationID=2945031c-58d0-4414-818a-c93d320ef97f, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=31, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@51a6af38[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@a8dedda[fileID=DefaultFilebadCaseOperationNoFile, allFileIDs=<null>(default)], resultingFileIDs=<null>(default), partialResult=<null>(default)]
Step: Retrieve the FinalResponse for the GetFileIDs request
Test success: badCaseOperationNoFile
Result: The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.GetFileIDsFinalResponse@7e753fd6[correlationID=2945031c-58d0-4414-818a-c93d320ef97f, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=31, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@51a6af38[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@a8dedda[fileID=DefaultFilebadCaseOperationNoFile, allFileIDs=<null>(default)], resultingFileIDs=<null>(default), partialResult=<null>(default)]
13:47:55.157 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.GetFileIDsFinalResponse@7e753fd6[correlationID=2945031c-58d0-4414-818a-c93d320ef97f, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=31, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@51a6af38[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@a8dedda[fileID=DefaultFilebadCaseOperationNoFile, allFileIDs=<null>(default)], resultingFileIDs=<null>(default), partialResult=<null>(default)]
Added fixture: Initialize a new Pillar.
Test starting: goodCaseIdentification
Description: Tests the identification for a GetFileIDs operation on the pillar for the successful scenario.
Step: Set up constants and variables.
Step: Setup for having the file and delivering pillar id
Step: Create and send the identify request message.
Result: Received message on TEST-TOPIC-goodCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsResponse@19158d56[correlationID=b7684432-5668-4aed-a73e-b2833ea63cae, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseIdentification-cibuild01-contributor, from=Pillar-goodCaseIdentification, to=goodCaseIdentification, version=31, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@3f02dc34[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], pillarID=Pillar-goodCaseIdentification, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@7f49fa1d[fileID=DefaultFilegoodCaseIdentification, allFileIDs=<null>(default)], timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@6e211727[timeMeasureUnit=MILLISECONDS, timeMeasureValue=1000]]
Step: Retrieve and validate the response getPillarID() the pillar.
Test success: goodCaseIdentification
Test starting: componentIDTest
Test success: componentIDTest
Starting testcase PutFileTest
Added fixture: Initialize a new Pillar.
Test starting: badCaseIdentification
Description: Tests the identification for a PutFile operation on the pillar for the failure scenario, when the file already exists.
Step: Set up constants and variables.
Step: Setup for already having the file and delivering pillar id
Step: Create and send the identify request message.
Result: Received message on TEST-TOPIC-badCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileResponse@13b0755e[correlationID=8d30d60e-a179-484a-8555-01a5e21ce0ce, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseIdentification-cibuild01-contributor, from=Pillar-badCaseIdentification, to=badCaseIdentification, version=31, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@21259314[responseCode=DUPLICATE_FILE_FAILURE, responseText=<null>(default)], pillarID=Pillar-badCaseIdentification, fileID=DefaultFilebadCaseIdentification, pillarChecksumSpec=<null>(default), checksumDataForExistingFile=<null>(default), timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@19f3c1f7[timeMeasureUnit=MILLISECONDS, timeMeasureValue=1000]]
Step: Retrieve and validate the response getPillarID() the pillar.
Test success: badCaseIdentification
Added fixture: Initialize a new Pillar.
Test starting: badCaseOperationFileAlreadyExists
Description: Tests the PutFile operation on the pillar for the failure scenario, when the file already exists.
Step: Set up constants and variables.
Step: Setup for already having the file and delivering pillar id
Step: Create and send the identify request message.
Result: Received message on TEST-TOPIC-badCaseOperationFileAlreadyExists-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileFinalResponse@1a4eb337[correlationID=21df66bf-8352-4341-96cd-2ea13b7f1b4a, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationFileAlreadyExists-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationFileAlreadyExists-cibuild01-contributor, from=Pillar-badCaseOperationFileAlreadyExists, to=badCaseOperationFileAlreadyExists, version=31, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@cec9f23[responseCode=DUPLICATE_FILE_FAILURE, responseText=We already have the file], pillarID=Pillar-badCaseOperationFileAlreadyExists, pillarChecksumSpec=<null>(default), fileID=DefaultFilebadCaseOperationFileAlreadyExists, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForNewFile=<null>(default), checksumDataForExistingFile=<null>(default)]
Step: Retrieve the FinalResponse for the PutFile request
Test success: badCaseOperationFileAlreadyExists
Added fixture: Initialize a new Pillar.
Test starting: badCasePutOperationNoValidationChecksum
Description: Tests the PutFile operation on the pillar for the failure scenario, when no validation checksum is given but required.
Step: Set up constants and variables.
Step: Setup for not already having the file and delivering pillar id
Step: Create and send the identify request message.
Result: Received message on TEST-TOPIC-badCasePutOperationNoValidationChecksum-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileFinalResponse@3713ebe9[correlationID=a8f9ee81-73ec-473d-9390-d50b7a5c4645, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCasePutOperationNoValidationChecksum-cibuild01, replyTo=TEST-TOPIC-Pillar-badCasePutOperationNoValidationChecksum-cibuild01-contributor, from=Pillar-badCasePutOperationNoValidationChecksum, to=badCasePutOperationNoValidationChecksum, version=31, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@c04a1ca[responseCode=NEW_FILE_CHECKSUM_FAILURE, responseText=A checksum is required for the PutFile operation to be performed.], pillarID=Pillar-badCasePutOperationNoValidationChecksum, pillarChecksumSpec=<null>(default), fileID=DefaultFilebadCasePutOperationNoValidationChecksum, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForNewFile=<null>(default), checksumDataForExistingFile=<null>(default)]
13:47:59.449 WARN o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@7f37f6b6[origDateTime=2022-02-15T13:47:59.449+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCasePutOperationNoValidationChecksum, alarmText=A checksum is required for the PutFile operation to be performed., fileID=DefaultFilebadCasePutOperationNoValidationChecksum, collectionID=TwoPillarCollection]
Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@4cb3e76c[correlationID=8534b595-a018-4065-96f6-392c7aeb1b95, collectionID=TwoPillarCollection, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-Pillar-badCasePutOperationNoValidationChecksum-cibuild01-contributor, from=Pillar-badCasePutOperationNoValidationChecksum, to=<null>(default), version=31, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@7f37f6b6[origDateTime=2022-02-15T13:47:59.449+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCasePutOperationNoValidationChecksum, alarmText=A checksum is required for the PutFile operation to be performed., fileID=DefaultFilebadCasePutOperationNoValidationChecksum, collectionID=TwoPillarCollection]]
Step: Retrieve the FinalResponse for the PutFile request
Step: Pillar should have sent an alarm
Test success: badCasePutOperationNoValidationChecksum
Added fixture: Initialize a new Pillar.
Test starting: goodCaseIdentification
Description: Tests the identification for a PutFile operation on the pillar for the successful scenario.
Step: Set up constants and variables.
Step: Setup for not already having the file and delivering pillar id
Step: Create and send the identify request message.
Result: Received message on TEST-TOPIC-goodCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileResponse@52c0c594[correlationID=a6fa0f29-a2b0-4cfe-aa7d-a10f7e45f6f1, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseIdentification-cibuild01-contributor, from=Pillar-goodCaseIdentification, to=goodCaseIdentification, version=31, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@370d49d1[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], pillarID=Pillar-goodCaseIdentification, fileID=DefaultFilegoodCaseIdentification, pillarChecksumSpec=<null>(default), checksumDataForExistingFile=<null>(default), timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@581cd446[timeMeasureUnit=MILLISECONDS, timeMeasureValue=1000]]
Step: Retrieve and validate the response getPillarID() the pillar.
Test success: goodCaseIdentification
Added fixture: Initialize a new Pillar.
Test starting: goodCaseOperationWithChecksumReturn
Description: Tests the PutFile operation on the pillar for the success scenario, when requesting the cheksum of the file returned.
Step: Set up constants and variables.
Step: Setup for not already having the file and delivering pillar id, and delivering an answer for the checksum request
Step: Create and send the identify request message.
Result: Received message on TEST-TOPIC-goodCaseOperationWithChecksumReturn-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileProgressResponse@5e077a32[correlationID=bb719b2f-5447-4406-9a71-874ef4d95907, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationWithChecksumReturn-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationWithChecksumReturn-cibuild01-contributor, from=Pillar-goodCaseOperationWithChecksumReturn, to=goodCaseOperationWithChecksumReturn, version=31, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@55c7ba5[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Started to receive data.], pillarID=Pillar-goodCaseOperationWithChecksumReturn, pillarChecksumSpec=<null>(default), fileID=DefaultFilegoodCaseOperationWithChecksumReturn, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt]
Result: Received message on TEST-TOPIC-goodCaseOperationWithChecksumReturn-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileFinalResponse@43a304ee[correlationID=bb719b2f-5447-4406-9a71-874ef4d95907, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationWithChecksumReturn-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationWithChecksumReturn-cibuild01-contributor, from=Pillar-goodCaseOperationWithChecksumReturn, to=goodCaseOperationWithChecksumReturn, version=31, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@7fb57b7c[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], pillarID=Pillar-goodCaseOperationWithChecksumReturn, pillarChecksumSpec=<null>(default), fileID=DefaultFilegoodCaseOperationWithChecksumReturn, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForNewFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@e76aa[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@35cf5d9[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2022-02-15T13:48:00.946+01:00], checksumDataForExistingFile=<null>(default)]
Step: Retrieve the ProgressResponse for the GetFileIDs request
Step: Retrieve the FinalResponse for the PutFile request
Test success: goodCaseOperationWithChecksumReturn
Starting testcase ReferenceArchiveTest
Added fixture: Initialize the Reference pillar cache with an empty file in default collection TwoPillarCollection
Test starting: testReferenceArchive
Description: Test the ReferenceArchive.
Step: Setup
Step: test 'hasFile'
Step: Test 'getFile'
Step: Test getAllFileIDs
Step: Test 'getFileAsInputstream'
Step: Delete, recreate and delete again
Step: Try to delete missing file.
Step: Replace a file, which does not exist in the filedir.
Step: Copy a file into the tmpDir and then use replace.
Step: Try performing the replace, when the file in the tempdir has been removed.
Test success: testReferenceArchive
Test starting: getPillarCollectionsTest
Test success: getPillarCollectionsTest
Starting testcase ChecksumDatabaseTest
Test starting: testChecksumDatabaseExtraction
Description: Test the extraction of data from the checksum database.
Step: Check whether the default entry exists.
Step: Extract calculation date
Step: Extract the checksum
Step: Extract the whole entry
Step: Extract all entries
Test success: testChecksumDatabaseExtraction
Test starting: testDeletion
Description: Test that data can be deleted from the database.
Step: Check whether the default entry exists.
Step: Remove the default entry
Test success: testDeletion
Test starting: testExtractionOfMissingData
Description: Test the handling of bad arguments.
Step: Try to get the date of a wrong file id.
Step: Try to get the date of a wrong file id.
Step: Try to remove a bad file id
Test success: testExtractionOfMissingData
Test starting: testGetChecksumResult
Description: Tests the restrictions on the GetChecksumResult call to the database.
Step: Instantiate database with appropriate data.
Step: Test with no time restrictions
Step: Test with time restrictions from epoc to now
Step: Test with very strict time restrictions around the default date
Step: Test with too new a lower limit
Step: Test with exact date as both upper and lower limit
Step: Test with date limit from 1 millis before as lower and exact date a upper limit
Step: Test with date limit from exact date as lower and 1 millis after date a upper limit
Step: Test with too old an upper limit
Test success: testGetChecksumResult
Test starting: testGetFileIDsRestrictions
Description: Tests the restrictions on the GetFileIDs call to the database.
Step: Instantiate database with appropriate data.
Step: Test with no time restrictions and 10000 max_results
Step: Test with minimum-date earlier than first file
Step: Test with maximum-date earlier than first file
Step: Test with minimum-date set to later than second file.
Step: Test with maximum-date set to later than second file.
Step: Test with minimum-date set to middle date.
Step: Test with maximum-date set to middle date.
Step: Test with both minimum-date and maximum-date set to middle date.
Step: Test the first file-id, with no other restrictions
Step: Test the second file-id, with no other restrictions
Step: Test the date for the first file-id, while requesting the second file-id
Test success: testGetFileIDsRestrictions
Test starting: testGetFileIDsWithOldChecksums
Description: Tests the restrictions on the GetFileIDsWithOldChecksums call to the database.
Step: Instantiate database with appropriate data.
Step: Extract all entries with checksum date older than now
Step: Extract all entries with checksum date older than epoch
Step: Extract all entries with checksum date older than middle date
Test success: testGetFileIDsWithOldChecksums
Test starting: testReplacingExistingEntry
Description: Test that an entry can be replaced by another in the database.
Step: Check whether the default entry exists.
Step: Replace the checksum and date
Test success: testReplacingExistingEntry
Test starting: testSpecifiedEntryExtraction
Description: Test that specific entries can be extracted. Has two entries in the database: one for the current timestamp and one for the epoch.
Step: Instantiate database with appropriate data.
Step: Extract with out restrictions
Step: Extract with a maximum of 1 entry
Step: Extract all dates older than this tests instantiation
Step: Extract all dates newer than this tests instantiation
Step: Extract all dates older than the newest instance
Step: Extract all dates newer than the oldest instantiation
Test success: testSpecifiedEntryExtraction
Starting testcase FullPillarModelTest
Test starting: testPillarModelBasicFunctionality
Description: Test the basic functions of the full reference pillar model.
Step: Check the pillar id in the pillar model
Step: Ask whether it can handle a file of size 0
Step: Ask whether it can handle a file of maximum size
Step: Check the ChecksumPillarSpec
Test success: testPillarModelBasicFunctionality
Test starting: testPillarModelHasFile
Description: Test that the file exists, when placed in the archive and cache
Step: Setup
Step: Check whether file exists and retrieve it.
Step: Verify that no exceptions are thrown when verifying file existance.
Step: Check retrieval of non-default checksum
Test success: testPillarModelHasFile
Test starting: testPillarModelNoFile
Description: Test that the file exists, when placed in the archive and cache
Step: Setup
Step: Check whether file exists and try to retrieve it.
Step: Verify that anexceptions are thrown when verifying file existance.
13:48:15.450 WARN o.b.pillar.store.FileStorageModel - The file 'DefaultFile' has been requested, but we do not have that file in collection 'TwoPillarCollection'!
Test success: testPillarModelNoFile
Starting testcase GeneralMessageHandlingTest
Added fixture: Initialize a new Pillar.
Test starting: testPillarMessageHandler
Description: Test the handling of the PillarMessageHandler super-class.
Step: Setup
Step: Test the pillar ID
Test success: testPillarMessageHandler
Added fixture: Initialize a new Pillar.
Test starting: testPillarMessageHandlerValidateFileIDFormatDefaultFileId
Description: Test the validation of file id formats of the PillarMessageHandler super-class on the default file id
Test success: testPillarMessageHandlerValidateFileIDFormatDefaultFileId
Added fixture: Initialize a new Pillar.
Test starting: testPillarMessageHandlerValidateFileIDFormatEnvHomePathFileId
Description: Test the validation of file id formats of the PillarMessageHandler super-class on a file id containing path relative paths from the environment variable home folder
Test success: testPillarMessageHandlerValidateFileIDFormatEnvHomePathFileId
Added fixture: Initialize a new Pillar.
Test starting: testPillarMessageHandlerValidateFileIDFormatFolderFileId
Description: Test the validation of file id formats of the PillarMessageHandler super-class on a file id with directory path
Test success: testPillarMessageHandlerValidateFileIDFormatFolderFileId
Added fixture: Initialize a new Pillar.
Test starting: testPillarMessageHandlerValidateFileIDFormatParentFolderFileId
Description: Test the validation of file id formats of the PillarMessageHandler super-class on a file id containing path to a parent directory
Test success: testPillarMessageHandlerValidateFileIDFormatParentFolderFileId
Added fixture: Initialize a new Pillar.
Test starting: testPillarMessageHandlerValidateFileIDFormatRootPathFileId
Description: Test the validation of file id formats of the PillarMessageHandler super-class on a file id containing path from the root folder
Test success: testPillarMessageHandlerValidateFileIDFormatRootPathFileId
Added fixture: Initialize a new Pillar.
Test starting: testPillarMessageHandlerValidateFileIDFormatSubFolderToParentFolderFileId
Description: Test the validation of file id formats of the PillarMessageHandler super-class on a file id containing path to a parent directory, but starting with a sub-folder
Test success: testPillarMessageHandlerValidateFileIDFormatSubFolderToParentFolderFileId
Added fixture: Initialize a new Pillar.
Test starting: testPillarMessageHandlerValidateFileIDFormatTildeHomePathFileId
Description: Test the validation of file id formats of the PillarMessageHandler super-class on a file id containing path relative paths from the tilde home folder
Test success: testPillarMessageHandlerValidateFileIDFormatTildeHomePathFileId
Added fixture: Initialize a new Pillar.
Test starting: testPillarMessageHandlerValidateFileIDFormatTooLong
Description: Test the validation of file id formats of the PillarMessageHandler super-class on a file id which has more characters than required
Test success: testPillarMessageHandlerValidateFileIDFormatTooLong
Starting testcase GetChecksumsTest
Added fixture: Initialize a new Pillar.
Test starting: badCaseIdentification
Description: Tests the identification for a GetChecksums operation on the pillar for the failure scenario, when the file is missing.
Step: Set up constants and variables.
Step: Setup for delivering pillar id and not having the file
Step: Create and send the identify request message.
Result: Received message on TEST-TOPIC-badCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsResponse@66d67401[correlationID=79a9089c-e223-4fa2-8cd8-579eea9cd0e2, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseIdentification-cibuild01-contributor, from=Pillar-badCaseIdentification, to=badCaseIdentification, version=31, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@2c66e656[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@1e7815cf[fileID=DefaultFilebadCaseIdentification, allFileIDs=<null>(default)], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@278c46e6[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], pillarID=Pillar-badCaseIdentification, pillarChecksumSpec=<null>(default), timeToDeliver=<null>(default)]
Step: Retrieve and validate the response getPillarID() the pillar.
Test success: badCaseIdentification
Added fixture: Initialize a new Pillar.
Test starting: badCaseOperationNoFile
Description: Tests the GetChecksums functionality of the pillar for the failure scenario, where it does not have the file.
Step: Set up constants and variables.
Step: Setup for not having the file
Step: Create and send the actual GetChecksums message to the pillar.
13:48:18.865 WARN o.b.p.m.GetChecksumsRequestHandler - The following file is missing 'DefaultFilebadCaseOperationNoFile' at collection 'TwoPillarCollection'.
Result: Received message on TEST-TOPIC-badCaseOperationNoFile-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@17c53e0a[correlationID=7b296a42-1b19-4e84-99e7-11e85fa4698b, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=31, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@5a044773[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2ef0f923[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultingChecksums=<null>(default), partialResult=<null>(default)]
13:48:18.872 WARN o.b.p.m.GetChecksumsRequestHandler - The following file is missing 'DefaultFilebadCaseOperationNoFile' at collection 'TwoPillarCollection'.
Result: Received message on TEST-TOPIC-badCaseOperationNoFile-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@59501e6[correlationID=7b296a42-1b19-4e84-99e7-11e85fa4698b, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=31, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@7d52e1f8[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2ef0f923[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultingChecksums=<null>(default), partialResult=<null>(default)]
13:48:18.875 WARN o.b.p.m.GetChecksumsRequestHandler - The following file is missing 'DefaultFilebadCaseOperationNoFile' at collection 'TwoPillarCollection'.
Result: Received message on TEST-TOPIC-badCaseOperationNoFile-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@5239ebe3[correlationID=7b296a42-1b19-4e84-99e7-11e85fa4698b, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=31, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@7f0e5a73[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2ef0f923[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultingChecksums=<null>(default), partialResult=<null>(default)]
Step: Retrieve the FinalResponse for the GetChecksums request
Test success: badCaseOperationNoFile
Result: The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@59501e6[correlationID=7b296a42-1b19-4e84-99e7-11e85fa4698b, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=31, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@7d52e1f8[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2ef0f923[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultingChecksums=<null>(default), partialResult=<null>(default)]
org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@5239ebe3[correlationID=7b296a42-1b19-4e84-99e7-11e85fa4698b, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=31, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@7f0e5a73[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2ef0f923[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultingChecksums=<null>(default), partialResult=<null>(default)]
13:48:19.880 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@59501e6[correlationID=7b296a42-1b19-4e84-99e7-11e85fa4698b, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=31, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@7d52e1f8[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2ef0f923[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultingChecksums=<null>(default), partialResult=<null>(default)]
org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@5239ebe3[correlationID=7b296a42-1b19-4e84-99e7-11e85fa4698b, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=31, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@7f0e5a73[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2ef0f923[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultingChecksums=<null>(default), partialResult=<null>(default)]
Added fixture: Initialize a new Pillar.
Test starting: goodCaseIdentification
Description: Tests the identification for a GetChecksums operation on the pillar for the successful scenario.
Step: Set up constants and variables.
Step: Setup for having the file and delivering pillar id
Step: Create and send the identify request message.
Result: Received message on TEST-TOPIC-goodCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsResponse@751a1a56[correlationID=ece67893-8d5e-4126-ad79-a6dee16451bb, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseIdentification-cibuild01-contributor, from=Pillar-goodCaseIdentification, to=goodCaseIdentification, version=31, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@5c263c07[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@75050599[fileID=DefaultFilegoodCaseIdentification, allFileIDs=<null>(default)], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1abeae00[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], pillarID=Pillar-goodCaseIdentification, pillarChecksumSpec=<null>(default), timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@3fd3dfab[timeMeasureUnit=MILLISECONDS, timeMeasureValue=1000]]
Step: Retrieve and validate the response getPillarID() the pillar.
Test success: goodCaseIdentification
Added fixture: Initialize a new Pillar.
Test starting: goodCaseOperationAllFiles
Description: Tests the GetChecksums operation on the pillar for the successful scenario, when requesting all files.
Step: Set up constants and variables.
Step: Setup for having the file and delivering result-set
Step: Create and send the actual GetChecksums message to the pillar.
Result: Received message on TEST-TOPIC-goodCaseOperationAllFiles-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsProgressResponse@38ca37d1[correlationID=ab2a8669-e655-42ab-952c-f6e7a61a7dff, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationAllFiles-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationAllFiles-cibuild01-contributor, from=Pillar-goodCaseOperationAllFiles, to=goodCaseOperationAllFiles, version=31, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@539f34df[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to calculate checksums.], pillarID=Pillar-goodCaseOperationAllFiles, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@5ced1c1c[fileID=<null>(default), allFileIDs=true], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2cdb272f[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultAddress=<null>(default)]
Result: Received message on TEST-TOPIC-goodCaseOperationAllFiles-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@280b3f43[correlationID=ab2a8669-e655-42ab-952c-f6e7a61a7dff, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationAllFiles-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationAllFiles-cibuild01-contributor, from=Pillar-goodCaseOperationAllFiles, to=goodCaseOperationAllFiles, version=31, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@6ec67e8d[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], pillarID=Pillar-goodCaseOperationAllFiles, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2cdb272f[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultingChecksums=org.bitrepository.bitrepositoryelements.ResultingChecksums@34682730[resultAddress=<null>(default), checksumDataItems={org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@32735c69[fileID=DefaultFile, checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2022-02-15T13:48:21.310+01:00],org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@43739c43[fileID=goodCaseOperationAllFiles-cibuild01--Test-File-1644929301299, checksumValue={18,52,-52,-52,-52,-52,67,34}, calculationTimestamp=1970-01-01T01:00:00.000+01:00]}], partialResult=false]
Step: Retrieve the ProgressResponse for the GetChecksums request
Step: Retrieve the FinalResponse for the GetChecksums request
Test success: goodCaseOperationAllFiles
Added fixture: Initialize a new Pillar.
Test starting: goodCaseOperationSingleFile
Description: Tests the GetChecksums operation on the pillar for the successful scenario when requesting one specific file.
Step: Set up constants and variables.
Step: Setup for having the file and delivering result-set
Step: Create and send the actual GetChecksums message to the pillar.
Result: Received message on TEST-TOPIC-goodCaseOperationSingleFile-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsProgressResponse@62c7095c[correlationID=21861108-51c4-41bf-b2b1-52f9da3e1f90, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationSingleFile-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationSingleFile-cibuild01-contributor, from=Pillar-goodCaseOperationSingleFile, to=goodCaseOperationSingleFile, version=31, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@53ffe34b[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to calculate checksums.], pillarID=Pillar-goodCaseOperationSingleFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@595126c[fileID=DefaultFilegoodCaseOperationSingleFile, allFileIDs=<null>(default)], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@24c25bcb[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultAddress=<null>(default)]
Result: Received message on TEST-TOPIC-goodCaseOperationSingleFile-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@7e953be6[correlationID=21861108-51c4-41bf-b2b1-52f9da3e1f90, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationSingleFile-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationSingleFile-cibuild01-contributor, from=Pillar-goodCaseOperationSingleFile, to=goodCaseOperationSingleFile, version=31, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@52dc7ac4[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], pillarID=Pillar-goodCaseOperationSingleFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@24c25bcb[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultingChecksums=org.bitrepository.bitrepositoryelements.ResultingChecksums@7f770481[resultAddress=<null>(default), checksumDataItems={org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@495d04a7[fileID=DefaultFilegoodCaseOperationSingleFile, checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2022-02-15T13:48:21.509+01:00]}], partialResult=false]
Step: Retrieve the ProgressResponse for the GetChecksums request
Step: Retrieve the FinalResponse for the GetChecksums request
Test success: goodCaseOperationSingleFile
Added fixture: Initialize a new Pillar.
Test starting: testRestrictions
Description: Tests that the restrictions are correctly passed on to the cache.
Step: Set up constants and variables.
Step: Setup for only delivering result-set when the correct restrictions are given.
Step: Create and send the actual GetChecksums message to the pillar.
Result: Received message on TEST-TOPIC-testRestrictions-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsProgressResponse@29346a21[correlationID=a30998d8-9b27-4d2e-bc29-c33fb1a7182e, collectionID=TwoPillarCollection, destination=TEST-TOPIC-testRestrictions-cibuild01, replyTo=TEST-TOPIC-Pillar-testRestrictions-cibuild01-contributor, from=Pillar-testRestrictions, to=testRestrictions, version=31, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@58e256e3[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to calculate checksums.], pillarID=Pillar-testRestrictions, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@287acdcd[fileID=<null>(default), allFileIDs=true], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@3ab7798b[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultAddress=<null>(default)]
Result: Received message on TEST-TOPIC-testRestrictions-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@3058799e[correlationID=a30998d8-9b27-4d2e-bc29-c33fb1a7182e, collectionID=TwoPillarCollection, destination=TEST-TOPIC-testRestrictions-cibuild01, replyTo=TEST-TOPIC-Pillar-testRestrictions-cibuild01-contributor, from=Pillar-testRestrictions, to=testRestrictions, version=31, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@7a477438[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], pillarID=Pillar-testRestrictions, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@3ab7798b[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultingChecksums=org.bitrepository.bitrepositoryelements.ResultingChecksums@42dda18[resultAddress=<null>(default), checksumDataItems={org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@5d79037[fileID=DefaultFile, checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2022-02-15T13:48:21.768+01:00]}], partialResult=false]
Step: Retrieve the ProgressResponse for the GetChecksums request
Step: Retrieve the FinalResponse for the GetChecksums request
Test success: testRestrictions
Starting testcase RecalculateChecksumWorkflowTest
Added fixture: Initialize the Reference pillar cache with an empty file in default collection TwoPillarCollection
Test starting: testWorkflowDoesNotRecalculateWhenNotNeeded
Description: Test that the workflow does not recalculates the workflows, when the maximum age has not yet been met.
Step: Create and run workflow
Test success: testWorkflowDoesNotRecalculateWhenNotNeeded
Added fixture: Initialize the Reference pillar cache with an empty file in default collection TwoPillarCollection
Test starting: testWorkflowRecalculatesChecksum
Description: Test that the workflow recalculates the workflows, when the maximum age has been met.
Step: Create and run workflow
Test success: testWorkflowRecalculatesChecksum
Starting testcase ChecksumDatabaseMigrationTest
Test starting: testMigratingChecksumDatabaseFromV3ToV4
Description: Tests that the checksums table can be migrated from version 3 to 4, e.g. changing the column calculatedchecksumdate from timestamp to bigint.
Step: Ensure cleanup
13:48:22.521 WARN o.b.common.utils.FileUtils - Could not delete '/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/test/referencepillar/checksumdb-for-migration'
Step: Unzipping and connecting to checksum database version 3
Step: Validate setup
Step: Ingest a entry to the database with a date for the calculationdate
Step: Perform migration
13:48:22.941 WARN o.b.service.database.DatabaseUtils - Migrating ChecksumDB from version 3 to 4.
Step: Validate the migration
Test success: testMigratingChecksumDatabaseFromV3ToV4
Starting testcase ChecksumPillarModelTest
Test starting: testPillarModelBasicFunctionality
Description: Test the basic functions of the full reference pillar model.
Step: Check the pillar id in the pillar model
Step: Ask whether it can handle a file of size 0
Step: Ask whether it can handle a file of maximum size
Step: Check the ChecksumPillarSpec
Step: Checkum whether the checksum pillar should download
Test success: testPillarModelBasicFunctionality
Test starting: testPillarModelHasFile
Description: Test that the file exists, when placed in the archive and cache
Step: Setup
Step: Check whether file exists and retrieve it.
Step: Check whether file exists.
Step: Ask for the checksum data for the file with different checksum specs
Step: Ask for the checksum entry for the file with different checksum specs
Step: Ask for the checksum for the file with different checksum specs
Step: Check extraction of checksum result set
Step: Check retrieval of non-default checksum
Step: Check retrieval of non-default checksum result set
Step: Test retrieval of single checksum result set
Test success: testPillarModelHasFile
Test starting: testPillarModelNoFile
Description: Test that the file exists, when placed in the archive and cache
Step: Setup
Step: Check whether file exists and try to retrieve it.
Step: Verify that anexceptions are thrown when verifying file existance.
Test success: testPillarModelNoFile
Starting testcase MediatorTest
Test starting: testMediatorRuntimeExceptionHandling
Description: Tests the handling of a runtime exception
Step: Setup create and start the mediator.
Step: Send a request to the mediator.
13:48:25.033 WARN o.b.pillar.MediatorTest$TestMediator - Unexpected exception caught.
java.lang.RuntimeException: I am supposed to throw a RuntimeException
at org.bitrepository.pillar.MediatorTest$ErroneousRequestHandler.processRequest(MediatorTest.java:122)
at org.bitrepository.pillar.MediatorTest$ErroneousRequestHandler.processRequest(MediatorTest.java:113)
at org.bitrepository.pillar.messagehandler.PillarMediator.handleRequest(PillarMediator.java:80)
at org.bitrepository.service.contributor.AbstractContributorMediator$GeneralRequestHandler.onMessage(AbstractContributorMediator.java:101)
at org.bitrepository.protocol.messagebus.SimpleMessageBus.lambda$sendMessage$0(SimpleMessageBus.java:73)
at java.lang.Iterable.forEach(Iterable.java:75)
at org.bitrepository.protocol.messagebus.SimpleMessageBus.sendMessage(SimpleMessageBus.java:73)
at org.bitrepository.pillar.MediatorTest.testMediatorRuntimeExceptionHandling(MediatorTest.java:84)
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.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:134)
at org.testng.internal.TestInvoker.invokeMethod(TestInvoker.java:597)
at org.testng.internal.TestInvoker.invokeTestMethod(TestInvoker.java:173)
at org.testng.internal.MethodRunner.runInSequence(MethodRunner.java:46)
at org.testng.internal.TestInvoker$MethodInvocationAgent.invoke(TestInvoker.java:816)
at org.testng.internal.TestInvoker.invokeTestMethods(TestInvoker.java:146)
at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:146)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:128)
at java.util.ArrayList.forEach(ArrayList.java:1249)
at org.testng.TestRunner.privateRun(TestRunner.java:766)
at org.testng.TestRunner.run(TestRunner.java:587)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:384)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:378)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:337)
at org.testng.SuiteRunner.run(SuiteRunner.java:286)
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:53)
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:96)
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1187)
at org.testng.TestNG.runSuitesLocally(TestNG.java:1109)
at org.testng.TestNG.runSuites(TestNG.java:1039)
at org.testng.TestNG.run(TestNG.java:1007)
at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:135)
at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:193)
at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:94)
at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:146)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:377)
at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:138)
at org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:465)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:451)
Result: Received message on TEST-TOPIC-testMediatorRuntimeExceptionHandling-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetStatusResponse@c3bb4f4[correlationID=00e17a6a-75a7-4e9c-bde6-eada90ca1d9e, collectionID=TwoPillarCollection, destination=TEST-TOPIC-testMediatorRuntimeExceptionHandling-cibuild01, replyTo=TEST-TOPIC-MediatorUnderTest-cibuild01-contributor, from=MediatorUnderTest, to=MediatorUnderTest, version=31, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@1cbb6f32[responseCode=FAILURE, responseText=java.lang.RuntimeException: I am supposed to throw a RuntimeException], contributor=TEST-TOPIC-cibuild01, timeToDeliver=<null>(default)]
13:48:25.036 WARN o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@4aff4a33[origDateTime=2022-02-15T13:48:25.035+01:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MediatorUnderTest, alarmText=java.lang.RuntimeException: I am supposed to throw a RuntimeException, fileID=<null>(default), collectionID=<null>(default)]
Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@1b32cb8c[correlationID=89c52718-acde-4b91-95cd-c84f517238c9, collectionID=<null>(default), destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-MediatorUnderTest-cibuild01-contributor, from=MediatorUnderTest, to=<null>(default), version=31, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@4aff4a33[origDateTime=2022-02-15T13:48:25.035+01:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MediatorUnderTest, alarmText=java.lang.RuntimeException: I am supposed to throw a RuntimeException, fileID=<null>(default), collectionID=<null>(default)]]
Test success: testMediatorRuntimeExceptionHandling
Starting testcase ReplaceFileTest
Added fixture: Initialize a new Pillar.
Test starting: badCaseIdentification
Description: Tests the identification for a ReplaceFile operation on the pillar for the failure scenario, when the file does not exist.
Step: Set up constants and variables.
Step: Setup for not having the file and delivering pillar id
Step: Create and send the identify request message.
Result: Received message on TEST-TOPIC-badCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileResponse@32e4ad7a[correlationID=7c6f5d8c-6598-4e35-82bd-a6f91c640bfe, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseIdentification-cibuild01-contributor, from=Pillar-badCaseIdentification, to=badCaseIdentification, version=31, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@2f61a56e[responseCode=FILE_NOT_FOUND_FAILURE, responseText=Could not find the requested file to delete.], fileID=DefaultFile, pillarID=Pillar-badCaseIdentification, pillarChecksumSpec=<null>(default), timeToDeliver=<null>(default)]
Step: Retrieve and validate the response getPillarID() the pillar.
Test success: badCaseIdentification
Added fixture: Initialize a new Pillar.
Test starting: badCaseOperationMissingFile
Description: Tests the ReplaceFile operation on the pillar for the failure scenario, when the file is missing.
Step: Set up constants and variables.
Step: Setup for not having the file and delivering pillar id
Step: Create and send the identify request message.
Result: Received message on TEST-TOPIC-badCaseOperationMissingFile-cibuild01 : org.bitrepository.bitrepositorymessages.ReplaceFileFinalResponse@35a10a89[correlationID=d5240feb-9e43-4bf4-9d80-02fefcc3e46e, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationMissingFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationMissingFile-cibuild01-contributor, from=Pillar-badCaseOperationMissingFile, to=badCaseOperationMissingFile, version=31, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@113ebc60[responseCode=FILE_NOT_FOUND_FAILURE, responseText=The file 'DefaultFile' has been requested, but we do not have that file!], pillarID=Pillar-badCaseOperationMissingFile, pillarChecksumSpec=<null>(default), fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForExistingFile=<null>(default), checksumDataForNewFile=<null>(default)]
Step: Retrieve the FinalResponse for the ReplaceFile request
Test success: badCaseOperationMissingFile
Added fixture: Initialize a new Pillar.
Test starting: badCaseOperationNoDestructiveChecksum
Description: Tests the ReplaceFile operation on the pillar for the failure scenario, when no validation checksum is given for the destructive action, but though is required.
Step: Set up constants and variables.
Step: Setup for having the file and delivering pillar id
Step: Create and send the identify request message.
Result: Received message on TEST-TOPIC-badCaseOperationNoDestructiveChecksum-cibuild01 : org.bitrepository.bitrepositorymessages.ReplaceFileFinalResponse@1df42cb3[correlationID=8074e084-57df-46c1-9886-0ea533a5e281, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoDestructiveChecksum-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoDestructiveChecksum-cibuild01-contributor, from=Pillar-badCaseOperationNoDestructiveChecksum, to=badCaseOperationNoDestructiveChecksum, version=31, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@4a1c5782[responseCode=EXISTING_FILE_CHECKSUM_FAILURE, responseText=According to the contract a checksum for file to be deleted during the replacing operation is required.], pillarID=Pillar-badCaseOperationNoDestructiveChecksum, pillarChecksumSpec=<null>(default), fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForExistingFile=<null>(default), checksumDataForNewFile=<null>(default)]
13:48:27.581 WARN o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@3f3ecfd4[origDateTime=2022-02-15T13:48:27.580+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCaseOperationNoDestructiveChecksum, alarmText=According to the contract a checksum for file to be deleted during the replacing operation is required., fileID=DefaultFile, collectionID=TwoPillarCollection]
Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@59b89eba[correlationID=5a46e846-cbf1-4223-8cf2-ef4fc93f4021, collectionID=TwoPillarCollection, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoDestructiveChecksum-cibuild01-contributor, from=Pillar-badCaseOperationNoDestructiveChecksum, to=<null>(default), version=31, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@3f3ecfd4[origDateTime=2022-02-15T13:48:27.580+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCaseOperationNoDestructiveChecksum, alarmText=According to the contract a checksum for file to be deleted during the replacing operation is required., fileID=DefaultFile, collectionID=TwoPillarCollection]]
Step: Retrieve the FinalResponse for the ReplaceFile request
Step: Pillar should have sent an alarm
Test success: badCaseOperationNoDestructiveChecksum
Added fixture: Initialize a new Pillar.
Test starting: badCaseOperationNoValidationChecksum
Description: Tests the ReplaceFile operation on the pillar for the failure scenario, when no validation checksum is given for the new file, but though is required.
Step: Set up constants and variables.
Step: Setup for having the file and delivering pillar id
Step: Create and send the identify request message.
Result: Received message on TEST-TOPIC-badCaseOperationNoValidationChecksum-cibuild01 : org.bitrepository.bitrepositorymessages.ReplaceFileFinalResponse@7df6fdd3[correlationID=b53377c1-fef7-4555-9770-420bf93e63a2, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoValidationChecksum-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoValidationChecksum-cibuild01-contributor, from=Pillar-badCaseOperationNoValidationChecksum, to=badCaseOperationNoValidationChecksum, version=31, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@45dfa4de[responseCode=NEW_FILE_CHECKSUM_FAILURE, responseText=According to the contract a checksum for new file in the replacing operation is required.], pillarID=Pillar-badCaseOperationNoValidationChecksum, pillarChecksumSpec=<null>(default), fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForExistingFile=<null>(default), checksumDataForNewFile=<null>(default)]
13:48:27.748 WARN o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@5eb52775[origDateTime=2022-02-15T13:48:27.748+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCaseOperationNoValidationChecksum, alarmText=According to the contract a checksum for new file in the replacing operation is required., fileID=DefaultFile, collectionID=TwoPillarCollection]
Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@28bbadf0[correlationID=cee99127-4b31-48c5-9ead-917fd9c43495, collectionID=TwoPillarCollection, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoValidationChecksum-cibuild01-contributor, from=Pillar-badCaseOperationNoValidationChecksum, to=<null>(default), version=31, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@5eb52775[origDateTime=2022-02-15T13:48:27.748+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCaseOperationNoValidationChecksum, alarmText=According to the contract a checksum for new file in the replacing operation is required., fileID=DefaultFile, collectionID=TwoPillarCollection]]
Step: Retrieve the FinalResponse for the ReplaceFile request
Step: Pillar should have sent an alarm
Test success: badCaseOperationNoValidationChecksum
Added fixture: Initialize a new Pillar.
Test starting: badCaseOperationWrongDestructiveChecksum
Description: Tests the ReplaceFile operation on the pillar for the failure scenario, when the checksum for the destructive action is different from the one in the cache.
Step: Set up constants and variables.
Step: Setup for having the file and delivering pillar id
Step: Create and send the identify request message.
13:48:27.885 WARN o.b.p.m.ReplaceFileRequestHandler - Failed to handle replace operation on file 'DefaultFile' since the request had the checksum '1234cccccccc4321' where our local file has the value '1234cccccccc4322'. Sending alarm and respond failure.
Result: Received message on TEST-TOPIC-badCaseOperationWrongDestructiveChecksum-cibuild01 : org.bitrepository.bitrepositorymessages.ReplaceFileFinalResponse@3b6a4049[correlationID=8ef9e6f8-e71b-4c2f-b0c6-b97e9781cbfa, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationWrongDestructiveChecksum-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationWrongDestructiveChecksum-cibuild01-contributor, from=Pillar-badCaseOperationWrongDestructiveChecksum, to=badCaseOperationWrongDestructiveChecksum, version=31, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@d4a6f4c[responseCode=EXISTING_FILE_CHECKSUM_FAILURE, responseText=Requested to replace the file 'DefaultFile' with checksum '1234cccccccc4321', but our file had a different checksum.], pillarID=Pillar-badCaseOperationWrongDestructiveChecksum, pillarChecksumSpec=<null>(default), fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForExistingFile=<null>(default), checksumDataForNewFile=<null>(default)]
13:48:27.887 WARN o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@cb52715[origDateTime=2022-02-15T13:48:27.887+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCaseOperationWrongDestructiveChecksum, alarmText=Requested to replace the file 'DefaultFile' with checksum '1234cccccccc4321', but our file had a different checksum., fileID=DefaultFile, collectionID=TwoPillarCollection]
Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@7a9b780e[correlationID=65fb2895-32ce-49af-aa82-d9913ecc5c2e, collectionID=TwoPillarCollection, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationWrongDestructiveChecksum-cibuild01-contributor, from=Pillar-badCaseOperationWrongDestructiveChecksum, to=<null>(default), version=31, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@cb52715[origDateTime=2022-02-15T13:48:27.887+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCaseOperationWrongDestructiveChecksum, alarmText=Requested to replace the file 'DefaultFile' with checksum '1234cccccccc4321', but our file had a different checksum., fileID=DefaultFile, collectionID=TwoPillarCollection]]
Step: Retrieve the FinalResponse for the ReplaceFile request
Step: Pillar should have sent an alarm
Test success: badCaseOperationWrongDestructiveChecksum
Added fixture: Initialize a new Pillar.
Test starting: goodCaseIdentification
Description: Tests the identification for a ReplaceFile operation on the pillar for the successful scenario.
Step: Set up constants and variables.
Step: Setup for having the file and delivering pillar id
Step: Create and send the identify request message.
Result: Received message on TEST-TOPIC-goodCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileResponse@1f4fb161[correlationID=5c3bfae0-8be2-4e90-88bc-88082b9bbe48, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseIdentification-cibuild01-contributor, from=Pillar-goodCaseIdentification, to=goodCaseIdentification, version=31, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@443adfbb[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], fileID=DefaultFile, pillarID=Pillar-goodCaseIdentification, pillarChecksumSpec=<null>(default), timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@5a914616[timeMeasureUnit=MILLISECONDS, timeMeasureValue=1000]]
Step: Retrieve and validate the response getPillarID() the pillar.
Test success: goodCaseIdentification
Added fixture: Initialize a new Pillar.
Test starting: goodCaseOperation
Description: Tests the ReplaceFile operation on the pillar for the success scenario.
Step: Set up constants and variables.
Step: Setup for already having the file and delivering pillar id
Step: Create and send the identify request message.
Result: Received message on TEST-TOPIC-goodCaseOperation-cibuild01 : org.bitrepository.bitrepositorymessages.ReplaceFileProgressResponse@1114bfcd[correlationID=322d66d2-7355-41f7-82ea-59eae7d5c9cb, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperation-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperation-cibuild01-contributor, from=Pillar-goodCaseOperation, to=goodCaseOperation, version=31, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@3d965cb4[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Performing the ReplaceFileRequest for file 'DefaultFile' at 'TwoPillarCollection'.], pillarID=Pillar-goodCaseOperation, pillarChecksumSpec=<null>(default), fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt]
Result: Received message on TEST-TOPIC-goodCaseOperation-cibuild01 : org.bitrepository.bitrepositorymessages.ReplaceFileFinalResponse@4c251ec7[correlationID=322d66d2-7355-41f7-82ea-59eae7d5c9cb, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperation-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperation-cibuild01-contributor, from=Pillar-goodCaseOperation, to=goodCaseOperation, version=31, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@78fb2a59[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], pillarID=Pillar-goodCaseOperation, pillarChecksumSpec=<null>(default), fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForExistingFile=<null>(default), checksumDataForNewFile=<null>(default)]
Step: Retrieve the ProgressResponse for the GetFileIDs request
Step: Retrieve the FinalResponse for the ReplaceFile request
Test success: goodCaseOperation
Added fixture: Initialize a new Pillar.
Test starting: goodCaseOperationWithChecksumsReturn
Description: Tests the ReplaceFile operation on the pillar for the success scenario, when requesting both the cheksums of the file returned.
Step: Set up constants and variables.
Step: Setup for already having the file and delivering pillar id
Step: Create and send the identify request message.
Result: Received message on TEST-TOPIC-goodCaseOperationWithChecksumsReturn-cibuild01 : org.bitrepository.bitrepositorymessages.ReplaceFileProgressResponse@61c613f9[correlationID=ee98d2c0-bee8-4985-944d-037a69051ce1, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationWithChecksumsReturn-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationWithChecksumsReturn-cibuild01-contributor, from=Pillar-goodCaseOperationWithChecksumsReturn, to=goodCaseOperationWithChecksumsReturn, version=31, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@48eeccae[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Performing the ReplaceFileRequest for file 'DefaultFile' at 'TwoPillarCollection'.], pillarID=Pillar-goodCaseOperationWithChecksumsReturn, pillarChecksumSpec=<null>(default), fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt]
Result: Received message on TEST-TOPIC-goodCaseOperationWithChecksumsReturn-cibuild01 : org.bitrepository.bitrepositorymessages.ReplaceFileFinalResponse@4307fd63[correlationID=ee98d2c0-bee8-4985-944d-037a69051ce1, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationWithChecksumsReturn-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationWithChecksumsReturn-cibuild01-contributor, from=Pillar-goodCaseOperationWithChecksumsReturn, to=goodCaseOperationWithChecksumsReturn, version=31, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@6c9d00a4[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], pillarID=Pillar-goodCaseOperationWithChecksumsReturn, pillarChecksumSpec=<null>(default), fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@3d958f15[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@3a0bfb5[checksumType=HMAC_SHA512, checksumSalt={97,98}, otherChecksumType=<null>(default)], checksumValue={18,52,-52,-52,-52,-52,67,34}, calculationTimestamp=2022-02-15T13:48:30.317+01:00], checksumDataForNewFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@7fb0a647[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7bac1135[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2022-02-15T13:48:30.321+01:00]]
Step: Retrieve the ProgressResponse for the GetFileIDs request
Step: Retrieve the FinalResponse for the ReplaceFile request
Test success: goodCaseOperationWithChecksumsReturn
Starting testcase GetFileTest
Added fixture: Initialize a new Pillar.
Test starting: badCaseIdentification
Description: Tests the identification for a GetFile operation on the checksum pillar for the failure scenario, when the file is missing.
Step: Set up constants and variables.
Step: Setup for throwing an exception when asked to verify file existence
Step: Create and send the identify request message.
Result: Received message on TEST-TOPIC-badCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileResponse@332c8aba[correlationID=af9aa3ad-9b53-41b6-985a-3d26a9fe17ca, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseIdentification-cibuild01-contributor, from=Pillar-badCaseIdentification, to=badCaseIdentification, version=31, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@18a08c75[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], fileID=DefaultFilebadCaseIdentification, pillarID=Pillar-badCaseIdentification, timeToDeliver=<null>(default)]
Step: Retrieve and validate the response getPillarID() the pillar.
Test success: badCaseIdentification
Added fixture: Initialize a new Pillar.
Test starting: goodCaseIdentification
Description: Tests the identification for a GetFile operation on the pillar for the successful scenario.
Step: Set up constants and variables.
Step: Setup for having the file and delivering pillar id
Step: Create and send the identify request message.
Result: Received message on TEST-TOPIC-goodCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileResponse@79dd885a[correlationID=90a89020-bc0f-4943-a1da-51d9b7fcc452, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseIdentification-cibuild01-contributor, from=Pillar-goodCaseIdentification, to=goodCaseIdentification, version=31, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@2ad4909d[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], fileID=DefaultFilegoodCaseIdentification, pillarID=Pillar-goodCaseIdentification, timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@4b880ae3[timeMeasureUnit=MILLISECONDS, timeMeasureValue=1000]]
Step: Retrieve and validate the response getPillarID() the pillar.
Test success: goodCaseIdentification
Finished testcase
Finished suite
Finished project
[INFO] Tests run: 72, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 51.943 s - in TestSuite
[INFO]
[INFO] Results:
[INFO]
[INFO] Tests run: 72, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[JENKINS] Recording test results
[INFO]
[INFO] --- jacoco-maven-plugin:0.8.5:report (report) @ bitrepository-reference-pillar ---
[INFO] Loading execution data file /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/jacoco.exec
[INFO] Analyzed bundle 'Bitrepository Reference Pillar' with 41 classes
[INFO]
[INFO] --- maven-jar-plugin:3.2.0:jar (default-jar) @ bitrepository-reference-pillar ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.10-SNAPSHOT.jar
[INFO]
[INFO] --- maven-jar-plugin:3.2.0:test-jar (default) @ bitrepository-reference-pillar ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.10-SNAPSHOT-tests.jar
[INFO]
[INFO] --- maven-source-plugin:3.2.1:jar-no-fork (attach-sources-no-fork) @ bitrepository-reference-pillar ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.10-SNAPSHOT-sources.jar
[INFO]
[INFO] --- maven-assembly-plugin:3.3.0:single (distribution) @ bitrepository-reference-pillar ---
[INFO] Reading assembly descriptor: src/main/assembly/assembly.xml
[INFO] Reading assembly descriptor: src/test/assembly/assembly.xml
[INFO] Reading assembly descriptor: src/main/assembly/deploy-assembly.xml
[INFO] Reading assembly descriptor: src/test/assembly/test-deploy-assembly.xml
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.10-SNAPSHOT-distribution.tar.gz
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.10-SNAPSHOT-acceptance-test.tar.gz
[WARNING] Entry: bitrepository-reference-pillar-1.10-SNAPSHOT/lib/bitrepository-reference-pillar-1.10-SNAPSHOT-tests.jar longer than 100 characters.
[WARNING] Resulting tar file can only be processed successfully by GNU compatible tar commands
[WARNING] Entry: bitrepository-reference-pillar-1.10-SNAPSHOT/lib/listenablefuture-9999.0-empty-to-avoid-conflict-with-guava.jar longer than 100 characters.
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.10-SNAPSHOT-deploy.tar.gz
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.10-SNAPSHOT-acceptance-test-deploy.tar.gz
[INFO]
[INFO] --- maven-install-plugin:3.0.0-M1:install (default-install) @ bitrepository-reference-pillar ---
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.10-SNAPSHOT.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-SNAPSHOT.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.10-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.10-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-SNAPSHOT-sources.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.10-SNAPSHOT-distribution.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-SNAPSHOT-distribution.tar.gz
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.10-SNAPSHOT-acceptance-test.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-SNAPSHOT-acceptance-test.tar.gz
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.10-SNAPSHOT-deploy.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-SNAPSHOT-deploy.tar.gz
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.10-SNAPSHOT-acceptance-test-deploy.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-SNAPSHOT-acceptance-test-deploy.tar.gz
[INFO]
[INFO] --- maven-deploy-plugin:3.0.0-M1:deploy (default-deploy) @ bitrepository-reference-pillar ---
[INFO] Downloading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/maven-metadata.xml (3 KB at 115.5 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20220215.124841-63.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20220215.124841-63.jar (128 KB at 1248.1 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20220215.124841-63.pom
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20220215.124841-63.pom (6 KB at 233.7 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20220215.124841-63-tests.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20220215.124841-63-tests.jar (251 KB at 7355.1 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20220215.124841-63-sources.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20220215.124841-63-sources.jar (106 KB at 4232.5 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20220215.124841-63-distribution.tar.gz
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20220215.124841-63-distribution.tar.gz (14768 KB at 24130.2 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20220215.124841-63-acceptance-test.tar.gz
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20220215.124841-63-acceptance-test.tar.gz (21346 KB at 32292.2 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20220215.124841-63-deploy.tar.gz
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20220215.124841-63-deploy.tar.gz (4 KB at 117.2 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20220215.124841-63-acceptance-test-deploy.tar.gz
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20220215.124841-63-acceptance-test-deploy.tar.gz (4 KB at 98.8 KB/sec)
[INFO] Downloading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/maven-metadata.xml (494 B at 21.9 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/maven-metadata.xml (3 KB at 77.0 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/maven-metadata.xml (494 B at 11.8 KB/sec)
[JENKINS] Archiving disabled
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Monitoring Service 1.10-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:3.1.0:clean (default-clean) @ bitrepository-monitoring-service ---
[INFO]
[INFO] --- maven-enforcer-plugin:3.0.0-M3:enforce (enforce-maven) @ bitrepository-monitoring-service ---
[INFO]
[INFO] --- jacoco-maven-plugin:0.8.5:prepare-agent (default) @ bitrepository-monitoring-service ---
[INFO] argLine set to -javaagent:/home/cibuild01/.m2/repository/org/jacoco/org.jacoco.agent/0.8.5/org.jacoco.agent-0.8.5-runtime.jar=destfile=/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/target/jacoco.exec
[INFO]
[INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ bitrepository-monitoring-service ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/src/main/resources
[INFO]
[INFO] --- maven-compiler-plugin:3.8.1:compile (default-compile) @ bitrepository-monitoring-service ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 15 source files to /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/target/classes
[INFO]
[INFO] --- forbiddenapis:2.7:check (default) @ bitrepository-monitoring-service ---
[INFO] Scanning for classes to check...
[INFO] Reading bundled API signatures: jdk-unsafe-1.8
[INFO] Reading bundled API signatures: jdk-deprecated-1.8
[INFO] Reading bundled API signatures: jdk-non-portable
[INFO] Reading bundled API signatures: jdk-reflection
[INFO] Loading classes to check...
[INFO] Scanning classes for violations...
[INFO] Scanned 18 class file(s) for forbidden API invocations (in 0.08s), 0 error(s).
[INFO]
[INFO] --- forbiddenapis:2.7:testCheck (default) @ bitrepository-monitoring-service ---
[INFO] Scanning for classes to check...
[WARNING] Classes directory does not exist, forbiddenapis check skipped: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/target/test-classes
[INFO]
[INFO] --- maven-resources-plugin:3.1.0:testResources (default-testResources) @ bitrepository-monitoring-service ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/src/test/resources
[INFO]
[INFO] --- maven-compiler-plugin:3.8.1:testCompile (default-testCompile) @ bitrepository-monitoring-service ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 7 source files to /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/target/test-classes
[INFO]
[INFO] --- maven-surefire-plugin:3.0.0-M4:test (default-test) @ bitrepository-monitoring-service ---
[INFO]
[INFO] -------------------------------------------------------
[INFO] T E S T S
[INFO] -------------------------------------------------------
[INFO] Running TestSuite
Starting test project Core module test
Suite: Surefire suite
Starting testcase StatusEventHandlerTest
Test starting: testStatusEventHandler
Description: Test the GetStatusEventHandler handling of events
Step: Setup
Step: Validate initial calls to the mocks
Step: Test an unhandled event.
Step: Test the Complete event
Step: Test the Failed event
Step: Test the component complete status
Test success: testStatusEventHandler
Starting testcase ComponentStatusStoreTest
Test starting: testComponentStatus
Description: Tests the compontent status
Step: Setup
Step: Validate the initial content
Step: Update the replay counts and validate
Step: Test what happens when an invalid component id attempted to be updated.
13:48:48.693 WARN o.b.m.status.ComponentStatusStore - Got status from an unexpected component: BAD-COMPONENT-ID
Step: Try giving it a positive status
Test success: testComponentStatus
Starting testcase StatusCollectorTest
Test starting: testStatusCollector
Description: Tests the status collector.
Step: Setup
Step: Create the collector
Step: Start the collector
Step: wait 2 * the interval
Step: wait the interval + delay again
Test success: testStatusCollector
Starting testcase MonitorAlerterTest
Test starting: testMonitorAlerter
Description: Tests the org.bitrepository.monitoringservice.alarm.BasicMonitoringServiceAlerter
Step: Setup
Step: Create the alerter, but ignore the part of actually sending the alarms. Just log it.
Step: Check statuses with an empty map.
Step: Check the status when a positive entry exists.
Step: Check the status when a negative entry exists.
13:48:53.182 WARN o.b.m.a.BasicMonitoringServiceAlerter - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@1fcfcf37[origDateTime=2022-02-15T13:48:53.169+01:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MonitorAlerterUnderTest, alarmText=The following components have become unresponsive: [TestMonitorService], fileID=<null>(default), collectionID=<null>(default)]
Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@54087bdb[correlationID=7c5ff074-af3e-48da-a1db-f0e011e25935, collectionID=<null>(default), destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-MonitorAlerterUnderTest-cibuild01-contributor, from=MonitorAlerterUnderTest, to=<null>(default), version=31, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@1fcfcf37[origDateTime=2022-02-15T13:48:53.169+01:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MonitorAlerterUnderTest, alarmText=The following components have become unresponsive: [TestMonitorService], fileID=<null>(default), collectionID=<null>(default)]]
Test success: testMonitorAlerter
Finished testcase
Finished suite
Finished project
[INFO] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 7.741 s - in TestSuite
[INFO]
[INFO] Results:
[INFO]
[INFO] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[JENKINS] Recording test results
[INFO]
[INFO] --- jacoco-maven-plugin:0.8.5:report (report) @ bitrepository-monitoring-service ---
[INFO] Loading execution data file /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/target/jacoco.exec
[INFO] Analyzed bundle 'Bitrepository Monitoring Service' with 14 classes
[INFO]
[INFO] --- maven-war-plugin:3.3.0:war (default-war) @ bitrepository-monitoring-service ---
[INFO] Packaging webapp
[INFO] Assembling webapp [bitrepository-monitoring-service] in [/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.10-SNAPSHOT]
[INFO] Processing war project
[INFO] Copying webapp resources [/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/src/main/webapp]
[INFO] Building war: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.10-SNAPSHOT.war
[INFO]
[INFO] --- maven-jar-plugin:3.2.0:test-jar (default) @ bitrepository-monitoring-service ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.10-SNAPSHOT-tests.jar
[INFO]
[INFO] --- maven-source-plugin:3.2.1:jar-no-fork (attach-sources-no-fork) @ bitrepository-monitoring-service ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.10-SNAPSHOT-sources.jar
[INFO]
[INFO] --- maven-assembly-plugin:3.3.0:single (distribution) @ bitrepository-monitoring-service ---
[INFO] Reading assembly descriptor: src/main/assembly/assembly.xml
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.10-SNAPSHOT-distribution.tar.gz
[INFO]
[INFO] --- maven-install-plugin:3.0.0-M1:install (default-install) @ bitrepository-monitoring-service ---
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.10-SNAPSHOT.war to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/bitrepository-monitoring-service-1.10-SNAPSHOT.war
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/bitrepository-monitoring-service-1.10-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.10-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/bitrepository-monitoring-service-1.10-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.10-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/bitrepository-monitoring-service-1.10-SNAPSHOT-sources.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.10-SNAPSHOT-distribution.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/bitrepository-monitoring-service-1.10-SNAPSHOT-distribution.tar.gz
[INFO]
[INFO] --- maven-deploy-plugin:3.0.0-M1:deploy (default-deploy) @ bitrepository-monitoring-service ---
[INFO] Downloading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 109.5 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/bitrepository-monitoring-service-1.10-20220215.124857-63.war
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/bitrepository-monitoring-service-1.10-20220215.124857-63.war (21393 KB at 36197.9 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/bitrepository-monitoring-service-1.10-20220215.124857-63.pom
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/bitrepository-monitoring-service-1.10-20220215.124857-63.pom (4 KB at 133.3 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/bitrepository-monitoring-service-1.10-20220215.124857-63-tests.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/bitrepository-monitoring-service-1.10-20220215.124857-63-tests.jar (15 KB at 503.7 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/bitrepository-monitoring-service-1.10-20220215.124857-63-sources.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/bitrepository-monitoring-service-1.10-20220215.124857-63-sources.jar (22 KB at 779.4 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/bitrepository-monitoring-service-1.10-20220215.124857-63-distribution.tar.gz
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/bitrepository-monitoring-service-1.10-20220215.124857-63-distribution.tar.gz (21392 KB at 31785.2 KB/sec)
[INFO] Downloading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/maven-metadata.xml (496 B at 25.5 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 43.1 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/maven-metadata.xml (496 B at 26.9 KB/sec)
[JENKINS] Archiving disabled
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Webclient 1.10-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:3.1.0:clean (default-clean) @ bitrepository-webclient ---
[INFO]
[INFO] --- maven-enforcer-plugin:3.0.0-M3:enforce (enforce-maven) @ bitrepository-webclient ---
[INFO]
[INFO] --- jacoco-maven-plugin:0.8.5:prepare-agent (default) @ bitrepository-webclient ---
[INFO] argLine set to -javaagent:/home/cibuild01/.m2/repository/org/jacoco/org.jacoco.agent/0.8.5/org.jacoco.agent-0.8.5-runtime.jar=destfile=/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/target/jacoco.exec
[INFO]
[INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ bitrepository-webclient ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.8.1:compile (default-compile) @ bitrepository-webclient ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 13 source files to /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/target/classes
[INFO]
[INFO] --- forbiddenapis:2.7:check (default) @ bitrepository-webclient ---
[INFO] Scanning for classes to check...
[INFO] Reading bundled API signatures: jdk-unsafe-1.8
[INFO] Reading bundled API signatures: jdk-deprecated-1.8
[INFO] Reading bundled API signatures: jdk-non-portable
[INFO] Reading bundled API signatures: jdk-reflection
[INFO] Loading classes to check...
[INFO] Scanning classes for violations...
[INFO] Scanned 13 class file(s) for forbidden API invocations (in 0.10s), 0 error(s).
[INFO]
[INFO] --- forbiddenapis:2.7:testCheck (default) @ bitrepository-webclient ---
[INFO] Scanning for classes to check...
[WARNING] Classes directory does not exist, forbiddenapis check skipped: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/target/test-classes
[INFO]
[INFO] --- maven-resources-plugin:3.1.0:testResources (default-testResources) @ bitrepository-webclient ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/src/test/resources
[INFO]
[INFO] --- maven-compiler-plugin:3.8.1:testCompile (default-testCompile) @ bitrepository-webclient ---
[INFO] No sources to compile
[INFO]
[INFO] --- maven-surefire-plugin:3.0.0-M4:test (default-test) @ bitrepository-webclient ---
[INFO] No tests to run.
[JENKINS] Recording test results[INFO]
[INFO] --- jacoco-maven-plugin:0.8.5:report (report) @ bitrepository-webclient ---
[INFO] Skipping JaCoCo execution due to missing execution data file.
[INFO]
[INFO] --- maven-war-plugin:3.3.0:war (default-war) @ bitrepository-webclient ---
[INFO] Packaging webapp
[INFO] Assembling webapp [bitrepository-webclient] in [/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/target/bitrepository-webclient-1.10-SNAPSHOT]
[INFO] Processing war project
[INFO] Copying webapp webResources [/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/src/main/webapp] to [/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/target/bitrepository-webclient-1.10-SNAPSHOT]
[INFO] Copying webapp resources [/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/src/main/webapp]
[INFO] Building war: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/target/bitrepository-webclient-1.10-SNAPSHOT.war
[INFO]
[INFO] --- maven-jar-plugin:3.2.0:test-jar (default) @ bitrepository-webclient ---
[WARNING] JAR will be empty - no content was marked for inclusion!
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/target/bitrepository-webclient-1.10-SNAPSHOT-tests.jar
[INFO]
[INFO] --- maven-source-plugin:3.2.1:jar-no-fork (attach-sources-no-fork) @ bitrepository-webclient ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/target/bitrepository-webclient-1.10-SNAPSHOT-sources.jar
[INFO]
[INFO] --- maven-assembly-plugin:3.3.0:single (distribution) @ bitrepository-webclient ---
[INFO] Reading assembly descriptor: src/main/assembly/assembly.xml
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/target/bitrepository-webclient-1.10-SNAPSHOT-distribution.tar.gz
[INFO]
[INFO] --- maven-install-plugin:3.0.0-M1:install (default-install) @ bitrepository-webclient ---
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/target/bitrepository-webclient-1.10-SNAPSHOT.war to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/bitrepository-webclient-1.10-SNAPSHOT.war
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/bitrepository-webclient-1.10-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/target/bitrepository-webclient-1.10-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/bitrepository-webclient-1.10-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/target/bitrepository-webclient-1.10-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/bitrepository-webclient-1.10-SNAPSHOT-sources.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/target/bitrepository-webclient-1.10-SNAPSHOT-distribution.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/bitrepository-webclient-1.10-SNAPSHOT-distribution.tar.gz
[INFO]
[INFO] --- maven-deploy-plugin:3.0.0-M1:deploy (default-deploy) @ bitrepository-webclient ---
[INFO] Downloading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 128.6 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/bitrepository-webclient-1.10-20220215.124903-63.war
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/bitrepository-webclient-1.10-20220215.124903-63.war (15550 KB at 32127.0 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/bitrepository-webclient-1.10-20220215.124903-63.pom
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/bitrepository-webclient-1.10-20220215.124903-63.pom (3 KB at 142.0 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/bitrepository-webclient-1.10-20220215.124903-63-tests.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/bitrepository-webclient-1.10-20220215.124903-63-tests.jar (3 KB at 100.6 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/bitrepository-webclient-1.10-20220215.124903-63-sources.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/bitrepository-webclient-1.10-20220215.124903-63-sources.jar (20 KB at 951.3 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/bitrepository-webclient-1.10-20220215.124903-63-distribution.tar.gz
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/bitrepository-webclient-1.10-20220215.124903-63-distribution.tar.gz (15545 KB at 34621.3 KB/sec)
[INFO] Downloading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/maven-metadata.xml (487 B at 36.6 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 70.7 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/maven-metadata.xml (487 B at 26.4 KB/sec)
[JENKINS] Archiving disabled
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Integration 1.10-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:3.1.0:clean (default-clean) @ bitrepository-integration ---
[INFO]
[INFO] --- maven-enforcer-plugin:3.0.0-M3:enforce (enforce-maven) @ bitrepository-integration ---
[INFO]
[INFO] --- jacoco-maven-plugin:0.8.5:prepare-agent (default) @ bitrepository-integration ---
[INFO] argLine set to -javaagent:/home/cibuild01/.m2/repository/org/jacoco/org.jacoco.agent/0.8.5/org.jacoco.agent-0.8.5-runtime.jar=destfile=/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/target/jacoco.exec
[INFO]
[INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ bitrepository-integration ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 33 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.8.1:compile (default-compile) @ bitrepository-integration ---
[INFO] No sources to compile
[INFO]
[INFO] --- forbiddenapis:2.7:check (default) @ bitrepository-integration ---
[INFO] Scanning for classes to check...
[WARNING] No classes found in '/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/target/classes' (includes=[**/*.class], excludes=null), forbiddenapis check skipped.
[INFO]
[INFO] --- forbiddenapis:2.7:testCheck (default) @ bitrepository-integration ---
[INFO] Scanning for classes to check...
[WARNING] Classes directory does not exist, forbiddenapis check skipped: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/target/test-classes
[INFO]
[INFO] --- maven-resources-plugin:3.1.0:testResources (default-testResources) @ bitrepository-integration ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO]
[INFO] --- maven-compiler-plugin:3.8.1:testCompile (default-testCompile) @ bitrepository-integration ---
[INFO] No sources to compile
[INFO]
[INFO] --- maven-surefire-plugin:3.0.0-M4:test (default-test) @ bitrepository-integration ---
[JENKINS] Recording test results[INFO]
[INFO] --- jacoco-maven-plugin:0.8.5:report (report) @ bitrepository-integration ---
[INFO] Skipping JaCoCo execution due to missing execution data file.
[INFO]
[INFO] --- maven-jar-plugin:3.2.0:jar (default-jar) @ bitrepository-integration ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/target/bitrepository-integration-1.10-SNAPSHOT.jar
[INFO]
[INFO] --- maven-jar-plugin:3.2.0:test-jar (default) @ bitrepository-integration ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/target/bitrepository-integration-1.10-SNAPSHOT-tests.jar
[INFO]
[INFO] --- maven-source-plugin:3.2.1:jar-no-fork (attach-sources-no-fork) @ bitrepository-integration ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/target/bitrepository-integration-1.10-SNAPSHOT-sources.jar
[INFO]
[INFO] --- maven-assembly-plugin:3.3.0:single (make-assembly) @ bitrepository-integration ---
[INFO] Reading assembly descriptor: src/main/assembly/assembly.xml
[INFO] Reading assembly descriptor: src/main/assembly/tools-assembly.xml
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/target/bitrepository-integration-1.10-SNAPSHOT-quickstart.tar.gz
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/target/bitrepository-integration-1.10-SNAPSHOT-tools.tar.gz
[WARNING] Entry: bitrepository-integration-1.10-SNAPSHOT/lib/bitrepository-reference-pillar-1.10-SNAPSHOT-distribution.tar.gz longer than 100 characters.
[WARNING] Resulting tar file can only be processed successfully by GNU compatible tar commands
[INFO]
[INFO] --- maven-install-plugin:3.0.0-M1:install (default-install) @ bitrepository-integration ---
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/target/bitrepository-integration-1.10-SNAPSHOT.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-SNAPSHOT.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/target/bitrepository-integration-1.10-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/target/bitrepository-integration-1.10-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-SNAPSHOT-sources.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/target/bitrepository-integration-1.10-SNAPSHOT-quickstart.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-SNAPSHOT-quickstart.tar.gz
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/target/bitrepository-integration-1.10-SNAPSHOT-tools.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-SNAPSHOT-tools.tar.gz
[INFO]
[INFO] --- maven-deploy-plugin:3.0.0-M1:deploy (default-deploy) @ bitrepository-integration ---
[INFO] Downloading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 73.8 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-20220215.124919-63.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-20220215.124919-63.jar (33 KB at 1152.8 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-20220215.124919-63.pom
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-20220215.124919-63.pom (4 KB at 182.3 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-20220215.124919-63-tests.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-20220215.124919-63-tests.jar (3 KB at 145.3 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-20220215.124919-63-sources.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-20220215.124919-63-sources.jar (33 KB at 1396.6 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-20220215.124919-63-quickstart.tar.gz
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-20220215.124919-63-quickstart.tar.gz (125107 KB at 31576.7 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-20220215.124919-63-tools.tar.gz
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-20220215.124919-63-tools.tar.gz (139821 KB at 33148.6 KB/sec)
[INFO] Downloading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/maven-metadata.xml (489 B at 43.4 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 116.0 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/maven-metadata.xml (489 B at 31.8 KB/sec)
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Bitrepository ...................................... SUCCESS [ 5.161 s]
[INFO] Bitrepository Reference Settings ................... SUCCESS [ 8.235 s]
[INFO] Bitrepository Core ................................. SUCCESS [ 40.367 s]
[INFO] Bitrepository Client ............................... SUCCESS [01:07 min]
[INFO] Bitrepository Service .............................. SUCCESS [ 16.824 s]
[INFO] Bitrepository Integrity Service .................... SUCCESS [01:21 min]
[INFO] Bitrepository Alarm Service ........................ SUCCESS [ 15.071 s]
[INFO] Bitrepository Audit Trail Service .................. SUCCESS [ 29.808 s]
[INFO] Bitrepository Reference Pillar ..................... SUCCESS [01:05 min]
[INFO] Bitrepository Monitoring Service ................... SUCCESS [ 15.315 s]
[INFO] Bitrepository Webclient ............................ SUCCESS [ 5.119 s]
[INFO] Bitrepository Integration .......................... SUCCESS [ 23.581 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 06:21 min
[INFO] Finished at: 2022-02-15T13:49:32+01:00
[INFO] Final Memory: 76M/278M
[INFO] ------------------------------------------------------------------------
channel stopped
Started indexing related Jira issue keys
Successfully indexed related Jira issue keys
Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered
Triggering a new build of Bitrepository-deploy-ci-test
Finished: SUCCESS
Console Output
Help us localize this page