[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 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 11:25:38.300 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 11:25:41.085 WARN o.b.service.database.DatabaseUtils - Migrating ChecksumDB from version 3 to 4. Step: Validate the migration Test success: testMigratingChecksumDatabaseFromV3ToV4 Starting testcase ChecksumPillarModelTest Test starting: testPillarModelBasicFunctionality Description: Test the basic functions of the full reference pillar model. Step: Check the pillar id in the pillar model Step: Ask whether it can handle a file of size 0 Step: Ask whether it can handle a file of maximum size Step: Check the ChecksumPillarSpec Step: Checkum whether the checksum pillar should download Test success: testPillarModelBasicFunctionality Test starting: testPillarModelHasFile Description: Test that the file exists, when placed in the archive and cache Step: Setup Step: Check whether file exists and retrieve it. Step: Check whether file exists. Step: Ask for the checksum data for the file with different checksum specs Step: Ask for the checksum entry for the file with different checksum specs Step: Ask for the checksum for the file with different checksum specs Step: Check extraction of checksum result set Step: Check retrieval of non-default checksum Step: Check retrieval of non-default checksum result set Step: Test retrieval of single checksum result set Test success: testPillarModelHasFile Test starting: testPillarModelNoFile Description: Test that the file exists, when placed in the archive and cache Step: Setup Step: Check whether file exists and try to retrieve it. Step: Verify that anexceptions are thrown when verifying file existance. Test success: testPillarModelNoFile Starting testcase 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 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. 11:25:46.153 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@763a53c1[correlationID=0542f36c-4a82-4956-90b7-76221d41901f, 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@1935b63b[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseIdentification, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@77cc9049[fileID=DefaultFilebadCaseIdentification, allFileIDs=(default)], timeToDeliver=(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. 11:25:47.422 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@4a47a1b5[correlationID=369e4e31-caf6-4551-bf29-d9bd79a4d807, 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@71adebf0[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@215512b9[fileID=DefaultFilebadCaseOperationNoFile, allFileIDs=(default)], resultingFileIDs=(default), partialResult=(default)] Step: Retrieve the FinalResponse for the GetFileIDs request Test success: badCaseOperationNoFile 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@1919382c[correlationID=1daac6f5-7b4a-4b36-b7d1-f701d071969a, 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@235b4c49[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], pillarID=Pillar-goodCaseIdentification, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@a0825c1[fileID=DefaultFilegoodCaseIdentification, allFileIDs=(default)], timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@29b489a9[timeMeasureUnit=MILLISECONDS, timeMeasureValue=1000]] Step: Retrieve and validate the response getPillarID() the pillar. Test success: goodCaseIdentification 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. 11:25:50.879 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@72dd302[correlationID=ed587334-8c99-469f-b793-ac6ebc04bc98, 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@4cf7e832[responseCode=FAILURE, responseText=java.lang.RuntimeException: I am supposed to throw a RuntimeException], contributor=TEST-TOPIC-cibuild01, timeToDeliver=(default)] 11:25:50.884 WARN o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@34b01423[origDateTime=2020-09-08T11:25:50.880+02:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MediatorUnderTest, alarmText=java.lang.RuntimeException: I am supposed to throw a RuntimeException, fileID=(default), collectionID=(default)] Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@5d6c7474[correlationID=cda035aa-cbfd-4408-b2f6-a5c9d6f84ab6, collectionID=(default), destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-MediatorUnderTest-cibuild01-contributor, from=MediatorUnderTest, to=(default), version=31, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@34b01423[origDateTime=2020-09-08T11:25:50.880+02:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MediatorUnderTest, alarmText=java.lang.RuntimeException: I am supposed to throw a RuntimeException, fileID=(default), collectionID=(default)]] Test success: testMediatorRuntimeExceptionHandling 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 Test starting: getPillarCollectionsTest Test success: getPillarCollectionsTest Starting testcase ChecksumDatabaseTest Test starting: testChecksumDatabaseExtraction Description: Test the extraction of data from the checksum database. Step: Check whether the default entry exists. Step: Extract calculation date Step: Extract the checksum Step: Extract the whole entry Step: Extract all entries Test success: testChecksumDatabaseExtraction Test starting: testDeletion Description: Test that data can be deleted from the database. Step: Check whether the default entry exists. Step: Remove the default entry Test success: testDeletion Test starting: testExtractionOfMissingData Description: Test the handling of bad arguments. Step: Try to get the date of a wrong file id. Step: Try to get the date of a wrong file id. Step: Try to remove a bad file id Test success: testExtractionOfMissingData Test starting: testGetChecksumResult Description: Tests the restrictions on the GetChecksumResult call to the database. Step: Instantiate database with appropriate data. Step: Test with no time restrictions Step: Test with time restrictions from epoc to now Step: Test with very strict time restrictions around the default date Step: Test with too new a lower limit Step: Test with exact date as both upper and lower limit Step: Test with date limit from 1 millis before as lower and exact date a upper limit Step: Test with date limit from exact date as lower and 1 millis after date a upper limit Step: Test with too old an upper limit Test success: testGetChecksumResult Test starting: testGetFileIDsRestrictions Description: Tests the restrictions on the GetFileIDs call to the database. Step: Instantiate database with appropriate data. Step: Test with no time restrictions and 10000 max_results Step: Test with minimum-date earlier than first file Step: Test with maximum-date earlier than first file Step: Test with minimum-date set to later than second file. Step: Test with maximum-date set to later than second file. Step: Test with minimum-date set to middle date. Step: Test with maximum-date set to middle date. Step: Test with both minimum-date and maximum-date set to middle date. Step: Test the first file-id, with no other restrictions Step: Test the second file-id, with no other restrictions Step: Test the date for the first file-id, while requesting the second file-id Test success: testGetFileIDsRestrictions Test starting: testGetFileIDsWithOldChecksums Description: Tests the restrictions on the GetFileIDsWithOldChecksums call to the database. Step: Instantiate database with appropriate data. Step: Extract all entries with checksum date older than now Step: Extract all entries with checksum date older than epoch Step: Extract all entries with checksum date older than middle date Test success: testGetFileIDsWithOldChecksums Test starting: testReplacingExistingEntry Description: Test that an entry can be replaced by another in the database. Step: Check whether the default entry exists. Step: Replace the checksum and date Test success: testReplacingExistingEntry Test starting: testSpecifiedEntryExtraction Description: Test that specific entries can be extracted. Has two entries in the database: one for the current timestamp and one for the epoch. Step: Instantiate database with appropriate data. Step: Extract with out restrictions Step: Extract with a maximum of 1 entry Step: Extract all dates older than this tests instantiation Step: Extract all dates newer than this tests instantiation Step: Extract all dates older than the newest instance Step: Extract all dates newer than the oldest instantiation Test success: testSpecifiedEntryExtraction Starting testcase 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@13808cf6[correlationID=5b2c9acd-a65a-4750-b1ab-c2d72d74172f, 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@11d176f8[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], fileID=DefaultFilebadCaseIdentification, pillarID=Pillar-badCaseIdentification, pillarChecksumSpec=(default), timeToDeliver=(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@10cfaef3[correlationID=99efa0d7-85ba-490f-8ede-39eac9c41244, 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@3063f4cc[responseCode=EXISTING_FILE_CHECKSUM_FAILURE, responseText=No mandatory checksum for destructive operation was supplied.], pillarID=Pillar-badCaseOperationMissingVerification, fileID=DefaultFilebadCaseOperationMissingVerification, checksumDataForExistingFile=(default)] 11:26:01.914 WARN o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@1f001021[origDateTime=2020-09-08T11:26:01.910+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@72558d04[correlationID=3d91b8c9-c214-4c90-b517-65773d185c9d, collectionID=TwoPillarCollection, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationMissingVerification-cibuild01-contributor, from=Pillar-badCaseOperationMissingVerification, to=(default), version=31, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@1f001021[origDateTime=2020-09-08T11:26:01.910+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@69464a0f[correlationID=b42bea60-c3c9-44f7-9477-a999e016d038, 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@3f2f83d5[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileID=DefaultFilebadCaseOperationNoFile, checksumDataForExistingFile=(default)] Result: Received message on TEST-TOPIC-badCaseOperationNoFile-cibuild01 : org.bitrepository.bitrepositorymessages.DeleteFileFinalResponse@45983773[correlationID=b42bea60-c3c9-44f7-9477-a999e016d038, 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@1e551bfd[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileID=DefaultFilebadCaseOperationNoFile, checksumDataForExistingFile=(default)] Step: Retrieve the FinalResponse for the DeleteFile request Test success: badCaseOperationNoFile Result: The following messages haven't been handled by the testcase: org.bitrepository.bitrepositorymessages.DeleteFileFinalResponse@45983773[correlationID=b42bea60-c3c9-44f7-9477-a999e016d038, 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@1e551bfd[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileID=DefaultFilebadCaseOperationNoFile, checksumDataForExistingFile=(default)] 11:26:03.155 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: org.bitrepository.bitrepositorymessages.DeleteFileFinalResponse@45983773[correlationID=b42bea60-c3c9-44f7-9477-a999e016d038, 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@1e551bfd[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileID=DefaultFilebadCaseOperationNoFile, checksumDataForExistingFile=(default)] 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@487d0a60[correlationID=062e6d24-2126-4ca9-96d6-50f2b0cb1e81, 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@ab116aa[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], fileID=DefaultFilegoodCaseIdentification, pillarID=Pillar-goodCaseIdentification, pillarChecksumSpec=(default), timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@1e1df33a[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. 11:26:05.214 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 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@5a4f633f[correlationID=fb06d864-02b2-4675-afc5-c265ac91f554, 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@64252544[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to extract the requested audit trails.], contributor=Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults, resultAddress=(default)] Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsMaximumNumberOfResults-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsFinalResponse@7569a46b[correlationID=fb06d864-02b2-4675-afc5-c265ac91f554, 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@48d2bc6b[responseCode=OPERATION_COMPLETED, responseText=(default)], contributor=Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@386ff939[resultAddress=(default), auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@3938204d[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@1ca91fd[sequenceNumber=1, fileID=fileID1599557165407, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=CHECKSUM_CALCULATED, actionDateTime=2020-09-08T11:26:05.409+02:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@5c26544b[sequenceNumber=2, fileID=fileID1599557165407, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=DELETE_FILE, actionDateTime=2020-09-08T11:26:05.409+02:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@1bc7c8c7[sequenceNumber=3, fileID=fileID1599557165407, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=FAILURE, actionDateTime=2020-09-08T11:26:05.410+02:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@6305b9ba[sequenceNumber=4, fileID=fileID1599557165407, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=FILE_MOVED, actionDateTime=2020-09-08T11:26:05.410+02:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@3695995e[sequenceNumber=5, fileID=fileID1599557165407, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=GET_CHECKSUMS, actionDateTime=2020-09-08T11:26:05.410+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@29ff3af[correlationID=b02c0dae-4538-4126-96e0-e250e7a2de2d, 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@445371c0[responseCode=IDENTIFICATION_POSITIVE, responseText=(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@254fe08[correlationID=b02c0dae-4538-4126-96e0-e250e7a2de2d, 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@7f2b7766[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to extract the requested audit trails.], contributor=Pillar-checksumPillarGetAuditTrailsSpecificRequests, resultAddress=(default)] Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsFinalResponse@2029d432[correlationID=b02c0dae-4538-4126-96e0-e250e7a2de2d, 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@6411cb24[responseCode=OPERATION_COMPLETED, responseText=(default)], contributor=Pillar-checksumPillarGetAuditTrailsSpecificRequests, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@4110dd10[resultAddress=(default), auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@65a41213[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@bc2c2d1[sequenceNumber=1, fileID=fileID1599557165636, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=OTHER, actionDateTime=2020-09-08T11:26:05.636+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@61606066[correlationID=b02c0dae-4538-4126-96e0-e250e7a2de2d, 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@26dfd907[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to extract the requested audit trails.], contributor=Pillar-checksumPillarGetAuditTrailsSpecificRequests, resultAddress=(default)] Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsFinalResponse@632e7345[correlationID=b02c0dae-4538-4126-96e0-e250e7a2de2d, 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@7ee7e1bb[responseCode=OPERATION_COMPLETED, responseText=(default)], contributor=Pillar-checksumPillarGetAuditTrailsSpecificRequests, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@1c66dd51[resultAddress=(default), auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@4429383b[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@bc2c2d1[sequenceNumber=1, fileID=fileID1599557165636, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=OTHER, actionDateTime=2020-09-08T11:26:05.636+02:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@548dcfa0[sequenceNumber=2, fileID=notThisFile, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=UnknownActor, actionOnFile=FAILURE, actionDateTime=2020-09-08T11:26:05.636+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@1f3c0098[correlationID=0823d8a7-dd9c-42e7-8ffd-b8a51920b8bc, 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@12cad0bf[responseCode=IDENTIFICATION_POSITIVE, responseText=(default)]] Step: Make and send the request for the actual GetAuditTrails operation Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSuccessful-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsProgressResponse@4560f8dc[correlationID=0823d8a7-dd9c-42e7-8ffd-b8a51920b8bc, 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@4f21e242[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to extract the requested audit trails.], contributor=Pillar-checksumPillarGetAuditTrailsSuccessful, resultAddress=(default)] Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSuccessful-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsFinalResponse@30e603fe[correlationID=0823d8a7-dd9c-42e7-8ffd-b8a51920b8bc, 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@746d6275[responseCode=OPERATION_COMPLETED, responseText=(default)], contributor=Pillar-checksumPillarGetAuditTrailsSuccessful, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@3609c23c[resultAddress=(default), auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@76fa054d[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@7603119f[sequenceNumber=1, fileID=fileid, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=actor, actionOnFile=OTHER, actionDateTime=2020-09-08T11:26:05.850+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 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@2f95761e[correlationID=75d9f4cf-7bc4-4b35-8ab0-fb1b2926b424, 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@19a2b4c7[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@b48be28[fileID=DefaultFilebadCaseIdentification, allFileIDs=(default)], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@141dd31c[checksumType=MD5, checksumSalt=(default), otherChecksumType=(default)], pillarID=Pillar-badCaseIdentification, pillarChecksumSpec=(default), timeToDeliver=(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. 11:26:07.231 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@56f4226[correlationID=3d89c5ba-f29f-4533-8d0d-274a32a96331, 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@4c841ccb[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@443fae4a[checksumType=MD5, checksumSalt=(default), otherChecksumType=(default)], resultingChecksums=(default), partialResult=(default)] 11:26:07.236 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@2e4d2aaf[correlationID=3d89c5ba-f29f-4533-8d0d-274a32a96331, 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@42c309e9[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@443fae4a[checksumType=MD5, checksumSalt=(default), otherChecksumType=(default)], resultingChecksums=(default), partialResult=(default)] 11:26:07.238 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@5e5ebb7c[correlationID=3d89c5ba-f29f-4533-8d0d-274a32a96331, 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@1901fa4a[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@443fae4a[checksumType=MD5, checksumSalt=(default), otherChecksumType=(default)], resultingChecksums=(default), partialResult=(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@2e4d2aaf[correlationID=3d89c5ba-f29f-4533-8d0d-274a32a96331, 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@42c309e9[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@443fae4a[checksumType=MD5, checksumSalt=(default), otherChecksumType=(default)], resultingChecksums=(default), partialResult=(default)] org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@5e5ebb7c[correlationID=3d89c5ba-f29f-4533-8d0d-274a32a96331, 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@1901fa4a[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@443fae4a[checksumType=MD5, checksumSalt=(default), otherChecksumType=(default)], resultingChecksums=(default), partialResult=(default)] 11:26:08.240 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@2e4d2aaf[correlationID=3d89c5ba-f29f-4533-8d0d-274a32a96331, 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@42c309e9[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@443fae4a[checksumType=MD5, checksumSalt=(default), otherChecksumType=(default)], resultingChecksums=(default), partialResult=(default)] org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@5e5ebb7c[correlationID=3d89c5ba-f29f-4533-8d0d-274a32a96331, 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@1901fa4a[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@443fae4a[checksumType=MD5, checksumSalt=(default), otherChecksumType=(default)], resultingChecksums=(default), partialResult=(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@5695fad9[correlationID=37affd4a-f961-4500-adbd-7136858675d1, 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@590b7982[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@2032cd25[fileID=DefaultFilegoodCaseIdentification, allFileIDs=(default)], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2a45c12[checksumType=MD5, checksumSalt=(default), otherChecksumType=(default)], pillarID=Pillar-goodCaseIdentification, pillarChecksumSpec=(default), timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@7b1e2dad[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@6d27e8ae[correlationID=03570b89-26d5-4059-8281-08c803c2d7dd, 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@2158339b[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to calculate checksums.], pillarID=Pillar-goodCaseOperationAllFiles, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@669503af[fileID=(default), allFileIDs=true], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@742218ee[checksumType=MD5, checksumSalt=(default), otherChecksumType=(default)], resultAddress=(default)] Result: Received message on TEST-TOPIC-goodCaseOperationAllFiles-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@4d8e293[correlationID=03570b89-26d5-4059-8281-08c803c2d7dd, 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@7223fd84[responseCode=OPERATION_COMPLETED, responseText=(default)], pillarID=Pillar-goodCaseOperationAllFiles, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@742218ee[checksumType=MD5, checksumSalt=(default), otherChecksumType=(default)], resultingChecksums=org.bitrepository.bitrepositoryelements.ResultingChecksums@edaff21[resultAddress=(default), checksumDataItems={org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@195aff0f[fileID=DefaultFile, checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2020-09-08T11:26:09.573+02:00],org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@5ad55acd[fileID=goodCaseOperationAllFiles-cibuild01--Test-File-1599557169566, 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@37be0d45[correlationID=fd1fd515-ac78-45b6-9506-a73086e1670b, 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@2537b655[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to calculate checksums.], pillarID=Pillar-goodCaseOperationSingleFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@2e2a1bdc[fileID=DefaultFilegoodCaseOperationSingleFile, allFileIDs=(default)], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@688ebf26[checksumType=MD5, checksumSalt=(default), otherChecksumType=(default)], resultAddress=(default)] Result: Received message on TEST-TOPIC-goodCaseOperationSingleFile-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@2f9d4357[correlationID=fd1fd515-ac78-45b6-9506-a73086e1670b, 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@3780cdef[responseCode=OPERATION_COMPLETED, responseText=(default)], pillarID=Pillar-goodCaseOperationSingleFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@688ebf26[checksumType=MD5, checksumSalt=(default), otherChecksumType=(default)], resultingChecksums=org.bitrepository.bitrepositoryelements.ResultingChecksums@498ac438[resultAddress=(default), checksumDataItems={org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@54e025a0[fileID=DefaultFilegoodCaseOperationSingleFile, checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2020-09-08T11:26:09.777+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@40939164[correlationID=733bdc25-d012-42e9-a905-fd64ed58f1dc, 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@35aeef9b[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to calculate checksums.], pillarID=Pillar-testRestrictions, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@6d0d853f[fileID=(default), allFileIDs=true], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2926c1dc[checksumType=MD5, checksumSalt=(default), otherChecksumType=(default)], resultAddress=(default)] Result: Received message on TEST-TOPIC-testRestrictions-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@75e26d2d[correlationID=733bdc25-d012-42e9-a905-fd64ed58f1dc, 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@3772963d[responseCode=OPERATION_COMPLETED, responseText=(default)], pillarID=Pillar-testRestrictions, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2926c1dc[checksumType=MD5, checksumSalt=(default), otherChecksumType=(default)], resultingChecksums=org.bitrepository.bitrepositoryelements.ResultingChecksums@3657d991[resultAddress=(default), checksumDataItems={org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@2960c6a6[fileID=DefaultFile, checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2020-09-08T11:26:09.993+02:00]}], partialResult=false] Step: Retrieve the ProgressResponse for the GetChecksums request Step: Retrieve the FinalResponse for the GetChecksums request Test success: testRestrictions 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 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@188df7c7[correlationID=dd1b0160-c769-48e3-9e07-fbd2ea71412b, 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@10013c81[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], fileID=DefaultFilebadCaseIdentification, pillarID=Pillar-badCaseIdentification, timeToDeliver=(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@20a4c67d[correlationID=924ca699-0179-4ef8-a22d-4cbfcbe58a75, 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@bf9d0e[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], fileID=DefaultFilegoodCaseIdentification, pillarID=Pillar-goodCaseIdentification, timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@50693c4e[timeMeasureUnit=MILLISECONDS, timeMeasureValue=1000]] Step: Retrieve and validate the response getPillarID() the pillar. Test success: goodCaseIdentification 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@52ac730b[correlationID=fabb2f80-0bbc-48c2-ad91-7cfd953ec580, 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@15013c85[responseCode=FILE_NOT_FOUND_FAILURE, responseText=Could not find the requested file to delete.], fileID=DefaultFile, pillarID=Pillar-badCaseIdentification, pillarChecksumSpec=(default), timeToDeliver=(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@16d337f[correlationID=b95f2459-edef-4c7b-9ed1-582b6b5365e9, 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@8394219[responseCode=FILE_NOT_FOUND_FAILURE, responseText=The file 'DefaultFile' has been requested, but we do not have that file!], pillarID=Pillar-badCaseOperationMissingFile, pillarChecksumSpec=(default), fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForExistingFile=(default), checksumDataForNewFile=(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@179d0438[correlationID=89a39240-5d24-44ee-ab7b-05dfe926bb0b, 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@87ffc8f[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=(default), fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForExistingFile=(default), checksumDataForNewFile=(default)] 11:26:14.946 WARN o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@12252194[origDateTime=2020-09-08T11:26:14.945+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@1895e169[correlationID=5f1afb24-327b-4567-a328-123dbe2cca28, collectionID=TwoPillarCollection, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoDestructiveChecksum-cibuild01-contributor, from=Pillar-badCaseOperationNoDestructiveChecksum, to=(default), version=31, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@12252194[origDateTime=2020-09-08T11:26:14.945+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@7034bb18[correlationID=e6cf9f56-f81a-46a1-9733-a250080045df, 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@7bf5bd4f[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=(default), fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForExistingFile=(default), checksumDataForNewFile=(default)] 11:26:15.113 WARN o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@5fb27796[origDateTime=2020-09-08T11:26:15.113+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@4263f02f[correlationID=91a0b6a9-f54c-4fc8-a8c0-0aadfcc74a5f, collectionID=TwoPillarCollection, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoValidationChecksum-cibuild01-contributor, from=Pillar-badCaseOperationNoValidationChecksum, to=(default), version=31, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@5fb27796[origDateTime=2020-09-08T11:26:15.113+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. 11:26:15.319 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@6cb8fa25[correlationID=a29a63c7-df27-4c6e-9ab1-f1a7d58ef196, 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@4b27ddfb[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=(default), fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForExistingFile=(default), checksumDataForNewFile=(default)] 11:26:15.321 WARN o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@7cb89abf[origDateTime=2020-09-08T11:26:15.320+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@61c93d04[correlationID=5a74aa65-a687-4893-bc9b-5586d5a47dad, collectionID=TwoPillarCollection, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationWrongDestructiveChecksum-cibuild01-contributor, from=Pillar-badCaseOperationWrongDestructiveChecksum, to=(default), version=31, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@7cb89abf[origDateTime=2020-09-08T11:26:15.320+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@281f4497[correlationID=0f66b8c9-cfd8-43e1-91bb-295f1fab5f16, 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@1bc271aa[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], fileID=DefaultFile, pillarID=Pillar-goodCaseIdentification, pillarChecksumSpec=(default), timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@84ee47e[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@5b3d1fe9[correlationID=958449e7-19e3-4e41-97be-6523d80187e9, 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@6cfcd230[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Performing the ReplaceFileRequest for file 'DefaultFile' at 'TwoPillarCollection'.], pillarID=Pillar-goodCaseOperation, pillarChecksumSpec=(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@1faef660[correlationID=958449e7-19e3-4e41-97be-6523d80187e9, 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@2c5f702b[responseCode=OPERATION_COMPLETED, responseText=(default)], pillarID=Pillar-goodCaseOperation, pillarChecksumSpec=(default), fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForExistingFile=(default), checksumDataForNewFile=(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@14644607[correlationID=e1ffb4a9-897e-44e0-ac40-92d6ed7b0253, 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@5f536620[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Performing the ReplaceFileRequest for file 'DefaultFile' at 'TwoPillarCollection'.], pillarID=Pillar-goodCaseOperationWithChecksumsReturn, pillarChecksumSpec=(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@78707c5b[correlationID=e1ffb4a9-897e-44e0-ac40-92d6ed7b0253, 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@7ee1077f[responseCode=OPERATION_COMPLETED, responseText=(default)], pillarID=Pillar-goodCaseOperationWithChecksumsReturn, pillarChecksumSpec=(default), fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@488332da[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@c252f8c[checksumType=HMAC_SHA512, checksumSalt={97,98}, otherChecksumType=(default)], checksumValue={18,52,-52,-52,-52,-52,67,34}, calculationTimestamp=2020-09-08T11:26:17.925+02:00], checksumDataForNewFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@77cc18f7[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1e0338e[checksumType=MD5, checksumSalt=(default), otherChecksumType=(default)], checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2020-09-08T11:26:17.928+02:00]] Step: Retrieve the ProgressResponse for the GetFileIDs request Step: Retrieve the FinalResponse for the ReplaceFile request Test success: goodCaseOperationWithChecksumsReturn Starting testcase ChecksumEntryTest Test starting: testExtendedTestCase Description: Test the ChecksumEntry Step: Create a ChecksumEntry Test success: testExtendedTestCase 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@3c562c33[correlationID=b9741249-a601-4294-9976-52b58d0ba682, 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@5888b01d[responseCode=DUPLICATE_FILE_FAILURE, responseText=(default)], pillarID=Pillar-badCaseIdentification, fileID=DefaultFilebadCaseIdentification, pillarChecksumSpec=(default), checksumDataForExistingFile=(default), timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@5acd7897[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@425dc996[correlationID=df6fd0fd-81ce-48bf-bd1a-577707865876, 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@3a44411d[responseCode=DUPLICATE_FILE_FAILURE, responseText=We already have the file], pillarID=Pillar-badCaseOperationFileAlreadyExists, pillarChecksumSpec=(default), fileID=DefaultFilebadCaseOperationFileAlreadyExists, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForNewFile=(default), checksumDataForExistingFile=(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@4c01cb27[correlationID=e8a95776-7b52-42bd-9684-e7e35825dabc, 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@7abc7f5d[responseCode=NEW_FILE_CHECKSUM_FAILURE, responseText=A checksum is required for the PutFile operation to be performed.], pillarID=Pillar-badCasePutOperationNoValidationChecksum, pillarChecksumSpec=(default), fileID=DefaultFilebadCasePutOperationNoValidationChecksum, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForNewFile=(default), checksumDataForExistingFile=(default)] 11:26:21.475 WARN o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@56b0789a[origDateTime=2020-09-08T11:26:21.475+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@3d789233[correlationID=eda44035-54c2-40ab-a8f7-ee6065b03135, collectionID=TwoPillarCollection, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-Pillar-badCasePutOperationNoValidationChecksum-cibuild01-contributor, from=Pillar-badCasePutOperationNoValidationChecksum, to=(default), version=31, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@56b0789a[origDateTime=2020-09-08T11:26:21.475+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@3b53625[correlationID=0599a487-c952-4846-8fed-2ef29be0d0da, 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@54849f4c[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], pillarID=Pillar-goodCaseIdentification, fileID=DefaultFilegoodCaseIdentification, pillarChecksumSpec=(default), checksumDataForExistingFile=(default), timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@d81c848[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@41d284c1[correlationID=9d88bbb0-653c-4144-9fa4-fd397e3ad8b9, 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@40af423a[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Started to receive data.], pillarID=Pillar-goodCaseOperationWithChecksumReturn, pillarChecksumSpec=(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@7322151e[correlationID=9d88bbb0-653c-4144-9fa4-fd397e3ad8b9, 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@26836337[responseCode=OPERATION_COMPLETED, responseText=(default)], pillarID=Pillar-goodCaseOperationWithChecksumReturn, pillarChecksumSpec=(default), fileID=DefaultFilegoodCaseOperationWithChecksumReturn, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForNewFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@1c074b4f[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@153680ed[checksumType=MD5, checksumSalt=(default), otherChecksumType=(default)], checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2020-09-08T11:26:22.806+02:00], checksumDataForExistingFile=(default)] Step: Retrieve the ProgressResponse for the GetFileIDs request Step: Retrieve the FinalResponse for the PutFile request Test success: goodCaseOperationWithChecksumReturn Test starting: componentIDTest Test success: componentIDTest Finished testcase Finished suite Finished project [INFO] Tests run: 72, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 48.976 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 99.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-20200908.092630-55.jar [INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20200908.092630-55.jar (128 KB at 5786.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-20200908.092630-55.pom [INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20200908.092630-55.pom (6 KB at 365.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-20200908.092630-55-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-20200908.092630-55-tests.jar (251 KB at 9616.6 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-20200908.092630-55-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-20200908.092630-55-sources.jar (106 KB at 6224.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-20200908.092630-55-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-20200908.092630-55-distribution.tar.gz (14768 KB at 36463.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-20200908.092630-55-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-20200908.092630-55-acceptance-test.tar.gz (21345 KB at 30979.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-20200908.092630-55-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-20200908.092630-55-deploy.tar.gz (4 KB at 100.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-20200908.092630-55-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-20200908.092630-55-acceptance-test-deploy.tar.gz (4 KB at 159.9 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 60.3 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 86.6 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 18.6 KB/sec) [JENKINS] Archiving disabled