SuccessConsole Output

[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] Deleting /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target
[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 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@5cc85ffc[correlationID=bf7a6ede-d1f3-48bf-b08c-c72c5e0c241f, 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@189f2184[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@30ffc3c0[correlationID=5d8b7894-30ca-41a7-ba2b-c4217e334508, 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@76b8b6a6[responseCode=EXISTING_FILE_CHECKSUM_FAILURE, responseText=No mandatory checksum for destructive operation was supplied.], pillarID=Pillar-badCaseOperationMissingVerification, fileID=DefaultFilebadCaseOperationMissingVerification, checksumDataForExistingFile=<null>(default)]
12:21:06.216 WARN  o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@6d9bcf19[origDateTime=2021-06-10T12:21:06.212+02: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@23b4f0a9[correlationID=6a68f771-2dd6-4946-b1a7-515aec6e0e62, 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@6d9bcf19[origDateTime=2021-06-10T12:21:06.212+02: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@627dfd9f[correlationID=bab999d8-10c6-4544-b9b1-4cfcd119dca0, 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@35e64c7b[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@776d50d6[correlationID=734b0c20-ef7c-44a2-81e6-b6f258c4317c, 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@43815bc[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], fileID=DefaultFilegoodCaseIdentification, pillarID=Pillar-goodCaseIdentification, pillarChecksumSpec=<null>(default), timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@122bfaac[timeMeasureUnit=MILLISECONDS, timeMeasureValue=1000]]
        Step: Retrieve and validate the response getPillarID() the pillar.
      Test success: goodCaseIdentification
    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.
12:21:10.021 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 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.
12:21:13.513 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@e31d9c2[correlationID=d21cb680-3f54-4c3b-b25e-7328878b0e51, 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@10e5c13c[responseCode=FAILURE, responseText=java.lang.RuntimeException: I am supposed to throw a RuntimeException], contributor=TEST-TOPIC-cibuild01, timeToDeliver=<null>(default)]
12:21:13.516 WARN  o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@796ed904[origDateTime=2021-06-10T12:21:13.514+02: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@7991e022[correlationID=3cbb2a5d-8477-4a74-b87d-f12e8019a662, 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@796ed904[origDateTime=2021-06-10T12:21:13.514+02: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
      Test starting: componentIDTest
      Test success: componentIDTest
    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 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
    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@24ab86eb[correlationID=9ff7276a-8718-4cef-ba1a-a468516f3bf5, 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@7e8235b2[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@347d6885[correlationID=9ff7276a-8718-4cef-ba1a-a468516f3bf5, 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@12af47f4[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], contributor=Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@670132b9[resultAddress=<null>(default), auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@33a7a5ca[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@6cc1da7b[sequenceNumber=1, fileID=fileID1623320474899, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=CHECKSUM_CALCULATED, actionDateTime=2021-06-10T12:21:14.904+02:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@439a0f0[sequenceNumber=2, fileID=fileID1623320474899, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=DELETE_FILE, actionDateTime=2021-06-10T12:21:14.904+02:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@6ac3ce34[sequenceNumber=3, fileID=fileID1623320474899, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=FAILURE, actionDateTime=2021-06-10T12:21:14.905+02:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@6444bf53[sequenceNumber=4, fileID=fileID1623320474899, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=FILE_MOVED, actionDateTime=2021-06-10T12:21:14.905+02:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@634a3a2[sequenceNumber=5, fileID=fileID1623320474899, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=GET_CHECKSUMS, actionDateTime=2021-06-10T12:21:14.905+02: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@4022a256[correlationID=3edfa179-8c47-473f-a076-f8f1db69676b, 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@48430066[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@761eaf72[correlationID=3edfa179-8c47-473f-a076-f8f1db69676b, 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@237b93f5[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@73ebf7cc[correlationID=3edfa179-8c47-473f-a076-f8f1db69676b, 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@440f434f[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], contributor=Pillar-checksumPillarGetAuditTrailsSpecificRequests, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@47690183[resultAddress=<null>(default), auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@38f2c6a0[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@148b13e5[sequenceNumber=1, fileID=fileID1623320475121, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=OTHER, actionDateTime=2021-06-10T12:21:15.121+02: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@2a202f00[correlationID=3edfa179-8c47-473f-a076-f8f1db69676b, 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@25ca56de[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@b234301[correlationID=3edfa179-8c47-473f-a076-f8f1db69676b, 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@47fb7dbb[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], contributor=Pillar-checksumPillarGetAuditTrailsSpecificRequests, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@6c88026b[resultAddress=<null>(default), auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@1b03d582[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@148b13e5[sequenceNumber=1, fileID=fileID1623320475121, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=OTHER, actionDateTime=2021-06-10T12:21:15.121+02:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@aa9b6a8[sequenceNumber=2, fileID=notThisFile, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=UnknownActor, actionOnFile=FAILURE, actionDateTime=2021-06-10T12:21:15.121+02: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@697b105e[correlationID=8ed79e3b-2966-431e-821a-7c7a967ec832, 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@6c54bc3[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@dcaa310[correlationID=8ed79e3b-2966-431e-821a-7c7a967ec832, 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@2492f6fb[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@155afbd7[correlationID=8ed79e3b-2966-431e-821a-7c7a967ec832, 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@396d21ec[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], contributor=Pillar-checksumPillarGetAuditTrailsSuccessful, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@61e7d7f2[resultAddress=<null>(default), auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@52f1d01b[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@10371dd1[sequenceNumber=1, fileID=fileid, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=actor, actionOnFile=OTHER, actionDateTime=2021-06-10T12:21:15.345+02: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.
12:21:15.591 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@1f1d7c52[correlationID=1a276a92-c461-4f49-bc1a-26357e04dd57, 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@735b638[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseIdentification, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@369bd5ca[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.
12:21:16.819 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@1f05b63d[correlationID=fddf76b2-cc7a-4bc6-b315-8835f90d2ea5, 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@524b1c70[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@2ddb0d1a[fileID=DefaultFilebadCaseOperationNoFile, allFileIDs=<null>(default)], resultingFileIDs=<null>(default), partialResult=<null>(default)]
12:21:16.825 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@708a0150[correlationID=fddf76b2-cc7a-4bc6-b315-8835f90d2ea5, 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@7a282bad[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@2ddb0d1a[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@708a0150[correlationID=fddf76b2-cc7a-4bc6-b315-8835f90d2ea5, 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@7a282bad[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@2ddb0d1a[fileID=DefaultFilebadCaseOperationNoFile, allFileIDs=<null>(default)], resultingFileIDs=<null>(default), partialResult=<null>(default)]
12:21:17.830 WARN  o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: 
org.bitrepository.bitrepositorymessages.GetFileIDsFinalResponse@708a0150[correlationID=fddf76b2-cc7a-4bc6-b315-8835f90d2ea5, 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@7a282bad[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@2ddb0d1a[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@6198bac2[correlationID=cdef1437-f492-42d2-9127-47ed1e7f41cc, 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@4193b8a5[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], pillarID=Pillar-goodCaseIdentification, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@2de1a93d[fileID=DefaultFilegoodCaseIdentification, allFileIDs=<null>(default)], timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@7102b480[timeMeasureUnit=MILLISECONDS, timeMeasureValue=1000]]
        Step: Retrieve and validate the response getPillarID() the pillar.
      Test success: goodCaseIdentification
    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@f4352c6[correlationID=3d731203-2ef5-45f5-b9a2-b084fb34d9be, 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@2b60acb3[responseCode=DUPLICATE_FILE_FAILURE, responseText=<null>(default)], pillarID=Pillar-badCaseIdentification, fileID=DefaultFilebadCaseIdentification, pillarChecksumSpec=<null>(default), checksumDataForExistingFile=<null>(default), timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@a99f50e[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@1a4e3cbb[correlationID=bbeafe6d-2b5b-4b1f-9872-d1592c2c59bf, 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@7cb8ae89[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@6827f0b7[correlationID=29a3ae3f-a0da-4ab7-b36b-c0ae97a09b7b, 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@516ffa73[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)]
12:21:21.782 WARN  o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@1607278e[origDateTime=2021-06-10T12:21:21.782+02: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@8aedeb4[correlationID=70fb0a86-8fb4-478b-84c6-02e81954923a, 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@1607278e[origDateTime=2021-06-10T12:21:21.782+02: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@30a7dcd4[correlationID=a1614fda-dabc-4df1-807d-c3e52e82a60c, 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@6d575860[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], pillarID=Pillar-goodCaseIdentification, fileID=DefaultFilegoodCaseIdentification, pillarChecksumSpec=<null>(default), checksumDataForExistingFile=<null>(default), timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@5e9e1383[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@47e869c4[correlationID=a729e8f7-2c07-4612-ae35-71785430f5ae, 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@5a2c6a67[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@11db4d00[correlationID=a729e8f7-2c07-4612-ae35-71785430f5ae, 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@5bd5ace9[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@b439e50[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@48b4fecb[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2021-06-10T12:21:23.225+02: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 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@3b5a4aa5[correlationID=a4f11623-111e-4473-a8af-af84d62d5903, 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@d12009f[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@19e578e9[correlationID=d2a02a56-16c1-4fda-a8af-ee49dcbfc03c, 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@6d2d7a55[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@329ba591[correlationID=9de4987c-e73e-4a37-b01c-e821df18eb30, 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@6d448772[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)]
12:21:26.849 WARN  o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@614a32ef[origDateTime=2021-06-10T12:21:26.848+02: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@3683407d[correlationID=2e6e4ef0-4ef2-49fc-b4fb-ca9a18f915bb, 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@614a32ef[origDateTime=2021-06-10T12:21:26.848+02: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@61650e2d[correlationID=2e999817-951f-4f69-8935-12a0024f2510, 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@50e86638[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)]
12:21:27.061 WARN  o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@5acee0a3[origDateTime=2021-06-10T12:21:27.061+02: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@1c00809b[correlationID=8b36e794-1c36-4435-b474-3619b99f0a54, 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@5acee0a3[origDateTime=2021-06-10T12:21:27.061+02: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.
12:21:27.276 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@5b8d700c[correlationID=a9a5562f-0ab3-4228-8b9c-8b9ed7485cfb, 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@1cc5de12[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)]
12:21:27.282 WARN  o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@17e1a5e[origDateTime=2021-06-10T12:21:27.282+02: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@3d330fe6[correlationID=3f6bea47-c6ae-4ac2-9076-8d1b1265a823, 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@17e1a5e[origDateTime=2021-06-10T12:21:27.282+02: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@b1d3434[correlationID=bebde093-19bd-4ba8-9bfd-0836382a2d7d, 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@4ab317b6[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], fileID=DefaultFile, pillarID=Pillar-goodCaseIdentification, pillarChecksumSpec=<null>(default), timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@79a3ff22[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@6a2affb6[correlationID=6907e46f-8e89-4dde-91a0-1b71718a9607, 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@683cd50d[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@23f7ed9d[correlationID=6907e46f-8e89-4dde-91a0-1b71718a9607, 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@1e9d611a[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@54362745[correlationID=c1df5828-171d-49e4-a99e-17293485b1a0, 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@7b14953f[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@12f2f402[correlationID=c1df5828-171d-49e4-a99e-17293485b1a0, 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@4d10360e[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@74918273[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@5c6f7b6b[checksumType=HMAC_SHA512, checksumSalt={97,98}, otherChecksumType=<null>(default)], checksumValue={18,52,-52,-52,-52,-52,67,34}, calculationTimestamp=2021-06-10T12:21:29.875+02:00], checksumDataForNewFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@5938d600[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@15d42b6f[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2021-06-10T12:21:29.876+02:00]]
        Step: Retrieve the ProgressResponse for the GetFileIDs request
        Step: Retrieve the FinalResponse for the ReplaceFile request
      Test success: goodCaseOperationWithChecksumsReturn
      Test starting: getPillarCollectionsTest
      Test success: getPillarCollectionsTest
    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 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@70054599[correlationID=28cd6b67-91ba-4f9d-a342-30ebae5a2f2c, 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@68fc6e20[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@51252d61[correlationID=61fdf4ee-9b25-4ff3-a634-948815a6cc7b, 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@423692e1[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], fileID=DefaultFilegoodCaseIdentification, pillarID=Pillar-goodCaseIdentification, timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@1060a720[timeMeasureUnit=MILLISECONDS, timeMeasureValue=1000]]
        Step: Retrieve and validate the response getPillarID() the pillar.
      Test success: goodCaseIdentification
    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
12:21:33.949 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
12:21:36.862 WARN  o.b.service.database.DatabaseUtils - Migrating ChecksumDB from version 3 to 4.
        Step: Validate the migration
      Test success: testMigratingChecksumDatabaseFromV3ToV4
    Starting testcase ChecksumEntryTest
      Test starting: testExtendedTestCase
        Description: Test the ChecksumEntry
        Step: Create a ChecksumEntry
      Test success: testExtendedTestCase
    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 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@73439017[correlationID=18121d85-5a9e-4596-b4cd-fef9d4a82c54, 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@4ed665fc[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@b36d3d0[fileID=DefaultFilebadCaseIdentification, allFileIDs=<null>(default)], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@3994d744[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.
12:21:47.931 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@1ac7dd90[correlationID=9b75fae1-2922-4b68-8a69-be081bf46400, 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@73616745[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@173d786c[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultingChecksums=<null>(default), partialResult=<null>(default)]
12:21:47.935 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@32753297[correlationID=9b75fae1-2922-4b68-8a69-be081bf46400, 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@4ad630d3[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@173d786c[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultingChecksums=<null>(default), partialResult=<null>(default)]
12:21:47.938 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@21e64dbc[correlationID=9b75fae1-2922-4b68-8a69-be081bf46400, 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@3a1c329d[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@173d786c[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@32753297[correlationID=9b75fae1-2922-4b68-8a69-be081bf46400, 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@4ad630d3[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@173d786c[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultingChecksums=<null>(default), partialResult=<null>(default)]
org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@21e64dbc[correlationID=9b75fae1-2922-4b68-8a69-be081bf46400, 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@3a1c329d[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@173d786c[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultingChecksums=<null>(default), partialResult=<null>(default)]
12:21:48.942 WARN  o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: 
org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@32753297[correlationID=9b75fae1-2922-4b68-8a69-be081bf46400, 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@4ad630d3[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@173d786c[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultingChecksums=<null>(default), partialResult=<null>(default)]
org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@21e64dbc[correlationID=9b75fae1-2922-4b68-8a69-be081bf46400, 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@3a1c329d[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@173d786c[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@33521792[correlationID=a2cda190-adb9-4c55-9190-2ea86c51f5c5, 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@6339a9ff[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@2410e665[fileID=DefaultFilegoodCaseIdentification, allFileIDs=<null>(default)], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@518c8fc1[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], pillarID=Pillar-goodCaseIdentification, pillarChecksumSpec=<null>(default), timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@72c1ece5[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@610dfe1d[correlationID=a7c3d86a-ad43-4da0-b1a2-7159db6d6fa9, 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@2a85f871[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to calculate checksums.], pillarID=Pillar-goodCaseOperationAllFiles, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@7f625d4e[fileID=<null>(default), allFileIDs=true], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6fa802c[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultAddress=<null>(default)]
          Result: Received message on TEST-TOPIC-goodCaseOperationAllFiles-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@3becd5bf[correlationID=a7c3d86a-ad43-4da0-b1a2-7159db6d6fa9, 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@6b206a6f[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], pillarID=Pillar-goodCaseOperationAllFiles, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6fa802c[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultingChecksums=org.bitrepository.bitrepositoryelements.ResultingChecksums@1982e17c[resultAddress=<null>(default), checksumDataItems={org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@36592a07[fileID=DefaultFile, checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2021-06-10T12:21:50.254+02:00],org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@6b45405e[fileID=goodCaseOperationAllFiles-cibuild01--Test-File-1623320510247, 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@786e3f66[correlationID=73555b8a-6a71-48e3-9f26-a43ae31be204, 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@466373a9[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to calculate checksums.], pillarID=Pillar-goodCaseOperationSingleFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@581cbf4c[fileID=DefaultFilegoodCaseOperationSingleFile, allFileIDs=<null>(default)], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@f8ff413[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultAddress=<null>(default)]
          Result: Received message on TEST-TOPIC-goodCaseOperationSingleFile-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@6936f8b[correlationID=73555b8a-6a71-48e3-9f26-a43ae31be204, 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@5bb0bacb[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], pillarID=Pillar-goodCaseOperationSingleFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@f8ff413[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultingChecksums=org.bitrepository.bitrepositoryelements.ResultingChecksums@666b882e[resultAddress=<null>(default), checksumDataItems={org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@1634c79c[fileID=DefaultFilegoodCaseOperationSingleFile, checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2021-06-10T12:21:50.461+02: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@31d6da7f[correlationID=18c8e247-3c8e-40e9-acbd-857afd2d1211, 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@ba56309[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to calculate checksums.], pillarID=Pillar-testRestrictions, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@3769c94[fileID=<null>(default), allFileIDs=true], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@65867030[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultAddress=<null>(default)]
          Result: Received message on TEST-TOPIC-testRestrictions-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@62844bdd[correlationID=18c8e247-3c8e-40e9-acbd-857afd2d1211, 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@4299c1af[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], pillarID=Pillar-testRestrictions, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@65867030[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultingChecksums=org.bitrepository.bitrepositoryelements.ResultingChecksums@75bc6754[resultAddress=<null>(default), checksumDataItems={org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@236d8e23[fileID=DefaultFile, checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2021-06-10T12:21:50.630+02:00]}], partialResult=false]
        Step: Retrieve the ProgressResponse for the GetChecksums request
        Step: Retrieve the FinalResponse for the GetChecksums request
      Test success: testRestrictions
      Finished testcase
  Finished suite
Finished project
[INFO] Tests run: 72, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 51.085 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 74.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-20210610.102158-61.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20210610.102158-61.jar (128 KB at 1260.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-20210610.102158-61.pom
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20210610.102158-61.pom (6 KB at 389.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-20210610.102158-61-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-20210610.102158-61-tests.jar (251 KB at 9618.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-20210610.102158-61-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-20210610.102158-61-sources.jar (106 KB at 5038.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-20210610.102158-61-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-20210610.102158-61-distribution.tar.gz (14768 KB at 33037.0 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-20210610.102158-61-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-20210610.102158-61-acceptance-test.tar.gz (21345 KB at 34650.8 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-20210610.102158-61-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-20210610.102158-61-deploy.tar.gz (4 KB at 113.3 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-20210610.102158-61-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-20210610.102158-61-acceptance-test-deploy.tar.gz (4 KB at 134.3 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 32.2 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 99.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 20.1 KB/sec)
[JENKINS] Archiving disabled