[INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building Bitrepository Reference Pillar 1.6-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-reference-pillar --- [INFO] [INFO] --- maven-dependency-plugin:2.8:unpack-dependencies (unpack-shared-sqlscripts) @ bitrepository-reference-pillar --- [INFO] Unpacking /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-service/target/bitrepository-service-1.6-SNAPSHOT.jar to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/classes with includes "**/*.sql" and excludes "" [INFO] [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ bitrepository-reference-pillar --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 10 resources [INFO] [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ bitrepository-reference-pillar --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 44 source files to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/classes [INFO] [INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ bitrepository-reference-pillar --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 12 resources [INFO] [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ bitrepository-reference-pillar --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 70 source files to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/test-classes [INFO] [INFO] --- maven-surefire-plugin:2.17:test (default-test) @ bitrepository-reference-pillar --- [INFO] Surefire report directory: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/surefire-reports ------------------------------------------------------- T E S T S ------------------------------------------------------- Running TestSuite Configuring TestNG with: TestNG652Configurator Starting test project Reference Pillar Test Suite: Surefire suite Starting testcase ArchiveDirectoryTest Test starting: testArchiveDirectoryExistingFile Description: Test the ArchiveDirectory when the file exists Step: Setup Step: Validate the existence of the file Step: Delete the file. Test success: testArchiveDirectoryExistingFile Test starting: 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: 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: 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: 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 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: 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: 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 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 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. 02:23:36.883 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) ~[test-classes/:na] at org.bitrepository.pillar.MediatorTest$ErroneousRequestHandler.processRequest(MediatorTest.java:113) ~[test-classes/:na] at org.bitrepository.pillar.messagehandler.PillarMediator.handleRequest(PillarMediator.java:76) ~[classes/:na] at org.bitrepository.service.contributor.AbstractContributorMediator$GeneralRequestHandler.onMessage(AbstractContributorMediator.java:101) [bitrepository-service-1.6-SNAPSHOT.jar:1.6-SNAPSHOT] at org.bitrepository.protocol.messagebus.SimpleMessageBus.lambda$sendMessage$0(SimpleMessageBus.java:48) [bitrepository-core-1.6-SNAPSHOT.jar:1.6-SNAPSHOT] at org.bitrepository.protocol.messagebus.SimpleMessageBus$$Lambda$1/1798165471.accept(Unknown Source) [bitrepository-core-1.6-SNAPSHOT.jar:1.6-SNAPSHOT] at java.lang.Iterable.forEach(Iterable.java:75) [na:1.8.0_11] at org.bitrepository.protocol.messagebus.SimpleMessageBus.sendMessage(SimpleMessageBus.java:48) [bitrepository-core-1.6-SNAPSHOT.jar:1.6-SNAPSHOT] at org.bitrepository.pillar.MediatorTest.testMediatorRuntimeExceptionHandling(MediatorTest.java:84) [test-classes/:na] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_11] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_11] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_11] at java.lang.reflect.Method.invoke(Method.java:483) ~[na:1.8.0_11] at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84) [testng-6.8.8.jar:na] at org.testng.internal.Invoker.invokeMethod(Invoker.java:714) [testng-6.8.8.jar:na] at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901) [testng-6.8.8.jar:na] at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231) [testng-6.8.8.jar:na] at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127) [testng-6.8.8.jar:na] at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111) [testng-6.8.8.jar:na] at org.testng.TestRunner.privateRun(TestRunner.java:767) [testng-6.8.8.jar:na] at org.testng.TestRunner.run(TestRunner.java:617) [testng-6.8.8.jar:na] at org.testng.SuiteRunner.runTest(SuiteRunner.java:348) [testng-6.8.8.jar:na] at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:343) [testng-6.8.8.jar:na] at org.testng.SuiteRunner.privateRun(SuiteRunner.java:305) [testng-6.8.8.jar:na] at org.testng.SuiteRunner.run(SuiteRunner.java:254) [testng-6.8.8.jar:na] at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) [testng-6.8.8.jar:na] at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) [testng-6.8.8.jar:na] at org.testng.TestNG.runSuitesSequentially(TestNG.java:1224) [testng-6.8.8.jar:na] at org.testng.TestNG.runSuitesLocally(TestNG.java:1149) [testng-6.8.8.jar:na] at org.testng.TestNG.run(TestNG.java:1057) [testng-6.8.8.jar:na] at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:115) [surefire-testng-2.17.jar:2.17] at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:204) [surefire-testng-2.17.jar:2.17] at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:107) [surefire-testng-2.17.jar:2.17] at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:112) [surefire-testng-2.17.jar:2.17] at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) [surefire-booter-2.17.jar:2.17] at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) [surefire-booter-2.17.jar:2.17] at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) [surefire-booter-2.17.jar:2.17] Result: Received message on TEST-TOPIC-testMediatorRuntimeExceptionHandling-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetStatusResponse@202d9236[correlationID=c60c9927-be60-4c2e-a99f-d8b11582f140, collectionID=TwoPillarCollection, destination=TEST-TOPIC-testMediatorRuntimeExceptionHandling-cibuild01, replyTo=TEST-TOPIC-MediatorUnderTest-cibuild01-contributor, from=MediatorUnderTest, to=MediatorUnderTest, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@1f782c05[responseCode=FAILURE, responseText=java.lang.RuntimeException: I am supposed to throw a RuntimeException], contributor=TEST-TOPIC-cibuild01, timeToDeliver=] 02:23:36.887 WARN o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@7ecda95b[origDateTime=2015-10-15T02:23:36.887+02:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MediatorUnderTest, alarmText=java.lang.RuntimeException: I am supposed to throw a RuntimeException, fileID=, collectionID=] Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@22da2fe6[correlationID=557e70a2-6e11-43cb-8529-4b4ac9eb5446, collectionID=, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-MediatorUnderTest-cibuild01-contributor, from=MediatorUnderTest, to=, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@7ecda95b[origDateTime=2015-10-15T02:23:36.887+02:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MediatorUnderTest, alarmText=java.lang.RuntimeException: I am supposed to throw a RuntimeException, fileID=, collectionID=]] Test success: testMediatorRuntimeExceptionHandling Test starting: componentIDTest Test success: componentIDTest Starting testcase PutFileTest Added fixture: Initialize a new Pillar. Test starting: badCaseIdentification Description: Tests the identification for a PutFile operation on the pillar for the failure scenario, when the file already exists. Step: Set up constants and variables. Step: Setup for already having the file and delivering pillar id Step: Create and send the identify request message. Result: Received message on TEST-TOPIC-badCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileResponse@1ee5632d[correlationID=403ee54f-df8c-4bd0-a0f0-5c0d193cd2ad, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseIdentification-cibuild01-contributor, from=Pillar-badCaseIdentification, to=badCaseIdentification, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@52a7928a[responseCode=DUPLICATE_FILE_FAILURE, responseText=], pillarID=Pillar-badCaseIdentification, fileID=DefaultFilebadCaseIdentification, pillarChecksumSpec=, checksumDataForExistingFile=, timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@563ccd31[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@2c8b8de0[correlationID=3f5e575a-d18e-4937-8231-2c2534467be2, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationFileAlreadyExists-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationFileAlreadyExists-cibuild01-contributor, from=Pillar-badCaseOperationFileAlreadyExists, to=badCaseOperationFileAlreadyExists, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@4fb57fb3[responseCode=DUPLICATE_FILE_FAILURE, responseText=We already have the file], pillarID=Pillar-badCaseOperationFileAlreadyExists, pillarChecksumSpec=, fileID=DefaultFilebadCaseOperationFileAlreadyExists, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForNewFile=, checksumDataForExistingFile=] 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@58c42c8c[correlationID=d38caff3-8f91-4b3d-ac6b-daa1a424f8e5, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCasePutOperationNoValidationChecksum-cibuild01, replyTo=TEST-TOPIC-Pillar-badCasePutOperationNoValidationChecksum-cibuild01-contributor, from=Pillar-badCasePutOperationNoValidationChecksum, to=badCasePutOperationNoValidationChecksum, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@3af236d0[responseCode=NEW_FILE_CHECKSUM_FAILURE, responseText=A checksum is required for the PutFile operation to be performed.], pillarID=Pillar-badCasePutOperationNoValidationChecksum, pillarChecksumSpec=, fileID=DefaultFilebadCasePutOperationNoValidationChecksum, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForNewFile=, checksumDataForExistingFile=] 02:23:40.424 WARN o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@23564dd2[origDateTime=2015-10-15T02:23:40.423+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@54895681[correlationID=a47cc060-767f-486e-833c-5f0c303ce1e4, collectionID=TwoPillarCollection, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-Pillar-badCasePutOperationNoValidationChecksum-cibuild01-contributor, from=Pillar-badCasePutOperationNoValidationChecksum, to=, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@23564dd2[origDateTime=2015-10-15T02:23:40.423+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@67e77f52[correlationID=ebf27b81-cf33-4804-bf8a-b770d2c87ab4, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseIdentification-cibuild01-contributor, from=Pillar-goodCaseIdentification, to=goodCaseIdentification, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@7ead1d80[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], pillarID=Pillar-goodCaseIdentification, fileID=DefaultFilegoodCaseIdentification, pillarChecksumSpec=, checksumDataForExistingFile=, timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@1d1bf7bf[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@45d389f2[correlationID=3f7a02d9-c32f-48cf-84b7-553ffbfa054e, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationWithChecksumReturn-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationWithChecksumReturn-cibuild01-contributor, from=Pillar-goodCaseOperationWithChecksumReturn, to=goodCaseOperationWithChecksumReturn, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@308e87a1[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Started to receive data.], pillarID=Pillar-goodCaseOperationWithChecksumReturn, pillarChecksumSpec=, 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@60a01cb[correlationID=3f7a02d9-c32f-48cf-84b7-553ffbfa054e, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationWithChecksumReturn-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationWithChecksumReturn-cibuild01-contributor, from=Pillar-goodCaseOperationWithChecksumReturn, to=goodCaseOperationWithChecksumReturn, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@4efb13f1[responseCode=OPERATION_COMPLETED, responseText=], pillarID=Pillar-goodCaseOperationWithChecksumReturn, pillarChecksumSpec=, fileID=DefaultFilegoodCaseOperationWithChecksumReturn, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForNewFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@7bb4ed71[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@5112b7[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2015-10-15T02:23:42.247+02:00], checksumDataForExistingFile=] Step: Retrieve the ProgressResponse for the GetFileIDs request Step: Retrieve the FinalResponse for the PutFile request Test success: goodCaseOperationWithChecksumReturn Starting testcase ReferenceArchiveTest Added fixture: Initialize the Reference pillar cache with an empty file in default collection TwoPillarCollection Test starting: testReferenceArchive Description: Test the ReferenceArchive. Step: Setup Step: test 'hasFile' Step: Test 'getFile' Step: Test getAllFileIDs Step: Test 'getFileAsInputstream' Step: Delete, recreate and delete again Step: Try to delete missing file. Step: Replace a file, which does not exist in the filedir. Step: Copy a file into the tmpDir and then use replace. Step: Try performing the replace, when the file in the tempdir has been removed. Test success: testReferenceArchive 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@66e1b2a[correlationID=0e3a296b-1737-4934-8d2f-44f9fdea8679, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseIdentification-cibuild01-contributor, from=Pillar-badCaseIdentification, to=badCaseIdentification, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@343db2f6[responseCode=FILE_NOT_FOUND_FAILURE, responseText=Could not find the requested file to delete.], fileID=DefaultFile, pillarID=Pillar-badCaseIdentification, pillarChecksumSpec=, timeToDeliver=] 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@78d6c244[correlationID=126fb23b-c9bb-44bd-9d77-08921084d937, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationMissingFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationMissingFile-cibuild01-contributor, from=Pillar-badCaseOperationMissingFile, to=badCaseOperationMissingFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@448086ab[responseCode=FILE_NOT_FOUND_FAILURE, responseText=The file 'DefaultFile' has been requested, but we do not have that file!], pillarID=Pillar-badCaseOperationMissingFile, pillarChecksumSpec=, fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForExistingFile=, checksumDataForNewFile=] 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@38e7860c[correlationID=38aac4cc-148f-4f59-8487-fe35f12bda6f, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoDestructiveChecksum-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoDestructiveChecksum-cibuild01-contributor, from=Pillar-badCaseOperationNoDestructiveChecksum, to=badCaseOperationNoDestructiveChecksum, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@62158991[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=, fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForExistingFile=, checksumDataForNewFile=] 02:23:49.082 WARN o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@40738846[origDateTime=2015-10-15T02:23:49.081+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@1255de25[correlationID=311e2426-f6b1-4c42-98c2-6c915c3fe19f, collectionID=TwoPillarCollection, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoDestructiveChecksum-cibuild01-contributor, from=Pillar-badCaseOperationNoDestructiveChecksum, to=, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@40738846[origDateTime=2015-10-15T02:23:49.081+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@45ad3cd8[correlationID=1a1d7096-3fc7-4e37-9053-2d802e9277ff, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoValidationChecksum-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoValidationChecksum-cibuild01-contributor, from=Pillar-badCaseOperationNoValidationChecksum, to=badCaseOperationNoValidationChecksum, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@2b90cc1[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=, fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForExistingFile=, checksumDataForNewFile=] 02:23:49.304 WARN o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@5a2f401a[origDateTime=2015-10-15T02:23:49.303+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@6bdedbbd[correlationID=66ab0cea-fbdc-4195-9ee6-52fd95b66ba9, collectionID=TwoPillarCollection, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoValidationChecksum-cibuild01-contributor, from=Pillar-badCaseOperationNoValidationChecksum, to=, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@5a2f401a[origDateTime=2015-10-15T02:23:49.303+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. 02:23:49.536 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@6eb00cbe[correlationID=3f30e862-c585-456f-a1e1-50a8ac9e0ce2, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationWrongDestructiveChecksum-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationWrongDestructiveChecksum-cibuild01-contributor, from=Pillar-badCaseOperationWrongDestructiveChecksum, to=badCaseOperationWrongDestructiveChecksum, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@74e4be21[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=, fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForExistingFile=, checksumDataForNewFile=] 02:23:49.538 WARN o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@4d174189[origDateTime=2015-10-15T02:23:49.538+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@628bd77e[correlationID=9259e090-5e34-44dc-8556-fc014a75c073, collectionID=TwoPillarCollection, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationWrongDestructiveChecksum-cibuild01-contributor, from=Pillar-badCaseOperationWrongDestructiveChecksum, to=, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@4d174189[origDateTime=2015-10-15T02:23:49.538+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@70f91ae3[correlationID=4d1f2c85-9534-4818-951b-63e597b480e7, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseIdentification-cibuild01-contributor, from=Pillar-goodCaseIdentification, to=goodCaseIdentification, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@601d9f3a[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], fileID=DefaultFile, pillarID=Pillar-goodCaseIdentification, pillarChecksumSpec=, timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@5c2a3f0c[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@5d6b5d3d[correlationID=f915db0a-3fbb-4a7e-9690-cdca81be91a4, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperation-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperation-cibuild01-contributor, from=Pillar-goodCaseOperation, to=goodCaseOperation, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@464d5365[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Performing the ReplaceFileRequest for file 'DefaultFile' at 'TwoPillarCollection'.], pillarID=Pillar-goodCaseOperation, pillarChecksumSpec=, 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@2cacd55e[correlationID=f915db0a-3fbb-4a7e-9690-cdca81be91a4, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperation-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperation-cibuild01-contributor, from=Pillar-goodCaseOperation, to=goodCaseOperation, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@2ba9f743[responseCode=OPERATION_COMPLETED, responseText=], pillarID=Pillar-goodCaseOperation, pillarChecksumSpec=, fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForExistingFile=, checksumDataForNewFile=] 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@7744195[correlationID=fc173935-1b37-4060-bf60-0088f2810445, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationWithChecksumsReturn-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationWithChecksumsReturn-cibuild01-contributor, from=Pillar-goodCaseOperationWithChecksumsReturn, to=goodCaseOperationWithChecksumsReturn, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@77f529a6[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Performing the ReplaceFileRequest for file 'DefaultFile' at 'TwoPillarCollection'.], pillarID=Pillar-goodCaseOperationWithChecksumsReturn, pillarChecksumSpec=, 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@7d47b021[correlationID=fc173935-1b37-4060-bf60-0088f2810445, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationWithChecksumsReturn-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationWithChecksumsReturn-cibuild01-contributor, from=Pillar-goodCaseOperationWithChecksumsReturn, to=goodCaseOperationWithChecksumsReturn, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@6516181f[responseCode=OPERATION_COMPLETED, responseText=], pillarID=Pillar-goodCaseOperationWithChecksumsReturn, pillarChecksumSpec=, fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@40cb95c1[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1ead3c67[checksumType=HMAC_SHA512, checksumSalt={97,98}, otherChecksumType=], checksumValue={18,52,-52,-52,-52,-52,67,34}, calculationTimestamp=2015-10-15T02:23:52.765+02:00], checksumDataForNewFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@5e2b512b[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@ba87c11[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2015-10-15T02:23:52.765+02:00]] Step: Retrieve the ProgressResponse for the GetFileIDs request Step: Retrieve the FinalResponse for the ReplaceFile request Test success: goodCaseOperationWithChecksumsReturn Test starting: getPillarCollectionsTest Test success: getPillarCollectionsTest Starting testcase 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. 02:23:55.859 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 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. 02:23:56.053 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@18d396eb[correlationID=983ed30d-0cd8-4daf-ab5c-48186fd896b0, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseIdentification-cibuild01-contributor, from=Pillar-badCaseIdentification, to=badCaseIdentification, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@2bee1c13[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseIdentification, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@1859b996[fileID=DefaultFilebadCaseIdentification, allFileIDs=], timeToDeliver=] 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. 02:23:58.154 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@322eb1a[correlationID=ad00c17a-048b-450c-a85c-e0afaa5b78fb, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@2b4ba2d9[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@69f24965[fileID=DefaultFilebadCaseOperationNoFile, allFileIDs=], resultingFileIDs=, partialResult=] 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@7ee9920a[correlationID=9e98fa34-6453-414d-a438-f89529e9c8b0, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseIdentification-cibuild01-contributor, from=Pillar-goodCaseIdentification, to=goodCaseIdentification, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@4154ecd3[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], pillarID=Pillar-goodCaseIdentification, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@b53ce18[fileID=DefaultFilegoodCaseIdentification, allFileIDs=], timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@2a666c8e[timeMeasureUnit=MILLISECONDS, timeMeasureValue=1000]] Step: Retrieve and validate the response getPillarID() the pillar. Test success: goodCaseIdentification 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@77aeba9b[correlationID=c8d4295e-06b8-4f72-948e-2827272d8a04, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseIdentification-cibuild01-contributor, from=Pillar-badCaseIdentification, to=badCaseIdentification, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@1db5de29[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], fileID=DefaultFilebadCaseIdentification, pillarID=Pillar-badCaseIdentification, timeToDeliver=] 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@58d4fe33[correlationID=1a1bbb95-3aa5-413d-ae49-57b7cd605421, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseIdentification-cibuild01-contributor, from=Pillar-goodCaseIdentification, to=goodCaseIdentification, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@1952ad9d[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], fileID=DefaultFilegoodCaseIdentification, pillarID=Pillar-goodCaseIdentification, timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@71c74011[timeMeasureUnit=MILLISECONDS, timeMeasureValue=1000]] Step: Retrieve and validate the response getPillarID() the pillar. Test success: goodCaseIdentification 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 ChecksumEntryTest Test starting: testExtendedTestCase Description: Test the ChecksumEntry Step: Create a ChecksumEntry Step: Change the value of the checksum Step: Change the value of the calculation date Test success: testExtendedTestCase 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@4fb42efa[correlationID=0f588336-5807-4718-ad55-b435460d3396, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseIdentification-cibuild01-contributor, from=Pillar-badCaseIdentification, to=badCaseIdentification, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@35599228[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@51ac72f7[fileID=DefaultFilebadCaseIdentification, allFileIDs=], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@15324f25[checksumType=MD5, checksumSalt=, otherChecksumType=], pillarID=Pillar-badCaseIdentification, pillarChecksumSpec=, timeToDeliver=] 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. 02:24:05.178 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@15ade272[correlationID=ffe03433-7870-40bf-b5d5-ad942971ef30, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@225890bc[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@d426e01[checksumType=MD5, checksumSalt=, otherChecksumType=], resultingChecksums=, partialResult=] 02:24:05.217 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@183435c0[correlationID=ffe03433-7870-40bf-b5d5-ad942971ef30, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@69862a1[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@d426e01[checksumType=MD5, checksumSalt=, otherChecksumType=], resultingChecksums=, partialResult=] 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@183435c0[correlationID=ffe03433-7870-40bf-b5d5-ad942971ef30, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@69862a1[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@d426e01[checksumType=MD5, checksumSalt=, otherChecksumType=], resultingChecksums=, partialResult=] 02:24:06.251 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@183435c0[correlationID=ffe03433-7870-40bf-b5d5-ad942971ef30, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@69862a1[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@d426e01[checksumType=MD5, checksumSalt=, otherChecksumType=], resultingChecksums=, partialResult=] 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@7a0eb939[correlationID=e0b16b2a-c863-461d-8ffd-d068f59a3b30, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseIdentification-cibuild01-contributor, from=Pillar-goodCaseIdentification, to=goodCaseIdentification, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@54a7d1b9[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@209f0986[fileID=DefaultFilegoodCaseIdentification, allFileIDs=], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@c0b10ae[checksumType=MD5, checksumSalt=, otherChecksumType=], pillarID=Pillar-goodCaseIdentification, pillarChecksumSpec=, timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@3c3a767[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@6a0a0f12[correlationID=c2dcfabf-02d6-4641-970c-7e83559a811a, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationAllFiles-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationAllFiles-cibuild01-contributor, from=Pillar-goodCaseOperationAllFiles, to=goodCaseOperationAllFiles, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@b6fea12[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to calculate checksums.], pillarID=Pillar-goodCaseOperationAllFiles, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@75c095a5[fileID=, allFileIDs=true], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@689fe2a3[checksumType=MD5, checksumSalt=, otherChecksumType=], resultAddress=] Result: Received message on TEST-TOPIC-goodCaseOperationAllFiles-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@409df37d[correlationID=c2dcfabf-02d6-4641-970c-7e83559a811a, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationAllFiles-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationAllFiles-cibuild01-contributor, from=Pillar-goodCaseOperationAllFiles, to=goodCaseOperationAllFiles, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@2ab1c7a9[responseCode=OPERATION_COMPLETED, responseText=], pillarID=Pillar-goodCaseOperationAllFiles, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@689fe2a3[checksumType=MD5, checksumSalt=, otherChecksumType=], resultingChecksums=org.bitrepository.bitrepositoryelements.ResultingChecksums@6e818345[resultAddress=, checksumDataItems={org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@3d9c69f8[fileID=DefaultFile, checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2015-10-15T02:24:07.790+02:00],org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@1235732d[fileID=goodCaseOperationAllFiles-cibuild01--Test-File-1444868647785, 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@3b32f0b4[correlationID=ac3a6d78-ecaa-48e0-98dc-4dff293d3d2d, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationSingleFile-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationSingleFile-cibuild01-contributor, from=Pillar-goodCaseOperationSingleFile, to=goodCaseOperationSingleFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@77d7d2d0[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to calculate checksums.], pillarID=Pillar-goodCaseOperationSingleFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@63075ad1[fileID=DefaultFilegoodCaseOperationSingleFile, allFileIDs=], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@5fa0943d[checksumType=MD5, checksumSalt=, otherChecksumType=], resultAddress=] Result: Received message on TEST-TOPIC-goodCaseOperationSingleFile-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@73bb782d[correlationID=ac3a6d78-ecaa-48e0-98dc-4dff293d3d2d, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationSingleFile-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationSingleFile-cibuild01-contributor, from=Pillar-goodCaseOperationSingleFile, to=goodCaseOperationSingleFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@3a3375d8[responseCode=OPERATION_COMPLETED, responseText=], pillarID=Pillar-goodCaseOperationSingleFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@5fa0943d[checksumType=MD5, checksumSalt=, otherChecksumType=], resultingChecksums=org.bitrepository.bitrepositoryelements.ResultingChecksums@63bb719d[resultAddress=, checksumDataItems={org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@38e100ab[fileID=DefaultFilegoodCaseOperationSingleFile, checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2015-10-15T02:24:08.026+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@78a46d7b[correlationID=f937cb56-3635-4ccf-b135-d1930c13e125, collectionID=TwoPillarCollection, destination=TEST-TOPIC-testRestrictions-cibuild01, replyTo=TEST-TOPIC-Pillar-testRestrictions-cibuild01-contributor, from=Pillar-testRestrictions, to=testRestrictions, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@2726b2f3[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to calculate checksums.], pillarID=Pillar-testRestrictions, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@3509f32d[fileID=, allFileIDs=true], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1f9a5d3b[checksumType=MD5, checksumSalt=, otherChecksumType=], resultAddress=] Result: Received message on TEST-TOPIC-testRestrictions-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@440e2406[correlationID=f937cb56-3635-4ccf-b135-d1930c13e125, collectionID=TwoPillarCollection, destination=TEST-TOPIC-testRestrictions-cibuild01, replyTo=TEST-TOPIC-Pillar-testRestrictions-cibuild01-contributor, from=Pillar-testRestrictions, to=testRestrictions, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@56adb75e[responseCode=OPERATION_COMPLETED, responseText=], pillarID=Pillar-testRestrictions, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1f9a5d3b[checksumType=MD5, checksumSalt=, otherChecksumType=], resultingChecksums=org.bitrepository.bitrepositoryelements.ResultingChecksums@2cc7b63d[resultAddress=, checksumDataItems={org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@6179551b[fileID=DefaultFile, checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2015-10-15T02:24:08.222+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 ChecksumDatabaseMigrationTest Test starting: testMigratingDatabaseChecksumsTable Description: Tests that the checksums table can be migrated from version 1 to 2, e.g. getting the column collectionid, which should be set to the default in settings. Step: Validate setup Step: Ingest a entry to the database without the collection id Step: Perform migration 02:24:09.172 WARN o.b.service.database.DatabaseUtils - Migrating the checksums table from version 1 to 2 in the ChecksumDatabase. 02:24:09.218 WARN o.b.service.database.DatabaseUtils - Migrating ChecksumDB from version 2 to 3. Step: Validate the entry Test success: testMigratingDatabaseChecksumsTable 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@32fefbe6[correlationID=9636f20b-290c-4a93-a42d-f79c886defaa, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsMaximumNumberOfResults-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults, to=Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@3e92bded[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to extract the requested audit trails.], contributor=Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults, resultAddress=] Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsMaximumNumberOfResults-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsFinalResponse@505f6511[correlationID=9636f20b-290c-4a93-a42d-f79c886defaa, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsMaximumNumberOfResults-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults, to=Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@3dfb1626[responseCode=OPERATION_COMPLETED, responseText=], contributor=Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@52c919f3[resultAddress=, auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@5c70eda4[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@77ac7cd6[sequenceNumber=1, fileID=fileId1444868649443, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=CHECKSUM_CALCULATED, actionDateTime=2015-10-15T02:24:09.443+02:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@12830e23[sequenceNumber=2, fileID=fileId1444868649443, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=DELETE_FILE, actionDateTime=2015-10-15T02:24:09.443+02:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@81f9b01[sequenceNumber=3, fileID=fileId1444868649443, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=FAILURE, actionDateTime=2015-10-15T02:24:09.443+02:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@53d94a6b[sequenceNumber=4, fileID=fileId1444868649443, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=FILE_MOVED, actionDateTime=2015-10-15T02:24:09.443+02:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@4707d60a[sequenceNumber=5, fileID=fileId1444868649443, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=GET_CHECKSUMS, actionDateTime=2015-10-15T02:24:09.443+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@5b256ab5[correlationID=2bc0030a-c0c8-4899-aa24-228dad3cc200, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSpecificRequests-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSpecificRequests, to=Pillar-checksumPillarGetAuditTrailsSpecificRequests, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@2a2cdba0[responseCode=IDENTIFICATION_POSITIVE, responseText=]] 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@5b084c4c[correlationID=2bc0030a-c0c8-4899-aa24-228dad3cc200, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSpecificRequests-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSpecificRequests, to=Pillar-checksumPillarGetAuditTrailsSpecificRequests, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@2b08f55a[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to extract the requested audit trails.], contributor=Pillar-checksumPillarGetAuditTrailsSpecificRequests, resultAddress=] Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsFinalResponse@67b5da40[correlationID=2bc0030a-c0c8-4899-aa24-228dad3cc200, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSpecificRequests-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSpecificRequests, to=Pillar-checksumPillarGetAuditTrailsSpecificRequests, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@4ff3af97[responseCode=OPERATION_COMPLETED, responseText=], contributor=Pillar-checksumPillarGetAuditTrailsSpecificRequests, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@5680f009[resultAddress=, auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@3a4e6da6[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@73e0c775[sequenceNumber=1, fileID=fileId1444868649643, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=OTHER, actionDateTime=2015-10-15T02:24:09.643+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@213d5189[correlationID=2bc0030a-c0c8-4899-aa24-228dad3cc200, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSpecificRequests-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSpecificRequests, to=Pillar-checksumPillarGetAuditTrailsSpecificRequests, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@70eced1f[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to extract the requested audit trails.], contributor=Pillar-checksumPillarGetAuditTrailsSpecificRequests, resultAddress=] Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsFinalResponse@39068df9[correlationID=2bc0030a-c0c8-4899-aa24-228dad3cc200, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSpecificRequests-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSpecificRequests, to=Pillar-checksumPillarGetAuditTrailsSpecificRequests, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@4ca83ec3[responseCode=OPERATION_COMPLETED, responseText=], contributor=Pillar-checksumPillarGetAuditTrailsSpecificRequests, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@7d29fc6[resultAddress=, auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@10c11e36[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@73e0c775[sequenceNumber=1, fileID=fileId1444868649643, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=OTHER, actionDateTime=2015-10-15T02:24:09.643+02:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@1da53092[sequenceNumber=2, fileID=notThisFile, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=UnknownActor, actionOnFile=FAILURE, actionDateTime=2015-10-15T02:24:09.643+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@289fff3c[correlationID=2c0de0fd-8ab0-4898-a4ee-0c10dc2b8629, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSuccessful-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSuccessful-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSuccessful, to=Pillar-checksumPillarGetAuditTrailsSuccessful, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@6872201[responseCode=IDENTIFICATION_POSITIVE, responseText=]] Step: Make and send the request for the actual GetAuditTrails operation Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSuccessful-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsProgressResponse@669ae205[correlationID=2c0de0fd-8ab0-4898-a4ee-0c10dc2b8629, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSuccessful-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSuccessful-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSuccessful, to=Pillar-checksumPillarGetAuditTrailsSuccessful, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@19984625[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to extract the requested audit trails.], contributor=Pillar-checksumPillarGetAuditTrailsSuccessful, resultAddress=] Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSuccessful-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsFinalResponse@4e293c35[correlationID=2c0de0fd-8ab0-4898-a4ee-0c10dc2b8629, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSuccessful-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSuccessful-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSuccessful, to=Pillar-checksumPillarGetAuditTrailsSuccessful, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@718198db[responseCode=OPERATION_COMPLETED, responseText=], contributor=Pillar-checksumPillarGetAuditTrailsSuccessful, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@40bac624[resultAddress=, auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@1bc80978[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@1c8746a0[sequenceNumber=1, fileID=fileid, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=actor, actionOnFile=OTHER, actionDateTime=2015-10-15T02:24:09.760+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 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@5b7e2a88[correlationID=ab92a854-68f7-4e5d-ae78-61944d7dfc8a, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseIdentification-cibuild01-contributor, from=Pillar-badCaseIdentification, to=badCaseIdentification, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@6984f7d1[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], fileID=DefaultFilebadCaseIdentification, pillarID=Pillar-badCaseIdentification, pillarChecksumSpec=, timeToDeliver=] 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@6ce7d6ab[correlationID=c31db5cd-6560-40bd-8090-7b65f644f97a, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationMissingVerification-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationMissingVerification-cibuild01-contributor, from=Pillar-badCaseOperationMissingVerification, to=badCaseOperationMissingVerification, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@49d658bf[responseCode=EXISTING_FILE_CHECKSUM_FAILURE, responseText=No mandatory checksum for destructive operation was supplied.], pillarID=Pillar-badCaseOperationMissingVerification, fileID=DefaultFilebadCaseOperationMissingVerification, checksumDataForExistingFile=] 02:24:11.216 WARN o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@68893394[origDateTime=2015-10-15T02:24:11.216+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@3a89f2a0[correlationID=fbb31a7d-e157-4151-846a-7ad66690b595, collectionID=TwoPillarCollection, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationMissingVerification-cibuild01-contributor, from=Pillar-badCaseOperationMissingVerification, to=, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@68893394[origDateTime=2015-10-15T02:24:11.216+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@762261fd[correlationID=5353d0f4-f2b8-4606-8f14-e3d42f09b4b1, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@7b0d42b6[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileID=DefaultFilebadCaseOperationNoFile, checksumDataForExistingFile=] Result: Received message on TEST-TOPIC-badCaseOperationNoFile-cibuild01 : org.bitrepository.bitrepositorymessages.DeleteFileFinalResponse@6a73f164[correlationID=5353d0f4-f2b8-4606-8f14-e3d42f09b4b1, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@fbb585e[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileID=DefaultFilebadCaseOperationNoFile, checksumDataForExistingFile=] Result: Received message on TEST-TOPIC-badCaseOperationNoFile-cibuild01 : org.bitrepository.bitrepositorymessages.DeleteFileFinalResponse@5e7aa27e[correlationID=5353d0f4-f2b8-4606-8f14-e3d42f09b4b1, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@2b778004[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileID=DefaultFilebadCaseOperationNoFile, checksumDataForExistingFile=] 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@6a73f164[correlationID=5353d0f4-f2b8-4606-8f14-e3d42f09b4b1, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@fbb585e[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileID=DefaultFilebadCaseOperationNoFile, checksumDataForExistingFile=] org.bitrepository.bitrepositorymessages.DeleteFileFinalResponse@5e7aa27e[correlationID=5353d0f4-f2b8-4606-8f14-e3d42f09b4b1, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@2b778004[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileID=DefaultFilebadCaseOperationNoFile, checksumDataForExistingFile=] 02:24:12.661 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: org.bitrepository.bitrepositorymessages.DeleteFileFinalResponse@6a73f164[correlationID=5353d0f4-f2b8-4606-8f14-e3d42f09b4b1, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@fbb585e[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileID=DefaultFilebadCaseOperationNoFile, checksumDataForExistingFile=] org.bitrepository.bitrepositorymessages.DeleteFileFinalResponse@5e7aa27e[correlationID=5353d0f4-f2b8-4606-8f14-e3d42f09b4b1, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@2b778004[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileID=DefaultFilebadCaseOperationNoFile, checksumDataForExistingFile=] 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@30741e9b[correlationID=10b2a81e-f3b0-4209-8867-dc027dd745e9, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseIdentification-cibuild01-contributor, from=Pillar-goodCaseIdentification, to=goodCaseIdentification, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@1435b17[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], fileID=DefaultFilegoodCaseIdentification, pillarID=Pillar-goodCaseIdentification, pillarChecksumSpec=, timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@2b3b25ad[timeMeasureUnit=MILLISECONDS, timeMeasureValue=1000]] Step: Retrieve and validate the response getPillarID() the pillar. Test success: goodCaseIdentification Finished testcase Finished suite Finished project Tests run: 57, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 61.966 sec - in TestSuite Results : Tests run: 57, Failures: 0, Errors: 0, Skipped: 0 [JENKINS] Recording test results [INFO] [INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ bitrepository-reference-pillar --- [INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.6-SNAPSHOT.jar [INFO] [INFO] --- maven-jar-plugin:2.4:test-jar (default) @ bitrepository-reference-pillar --- [INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.6-SNAPSHOT-tests.jar [INFO] [INFO] --- maven-source-plugin:2.2.1:jar-no-fork (attach-sources-no-fork) @ bitrepository-reference-pillar --- [INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.6-SNAPSHOT-sources.jar [INFO] [INFO] --- maven-assembly-plugin:2.4: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-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.6-SNAPSHOT-distribution.tar.gz [INFO] Building tar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.6-SNAPSHOT-acceptance-test.tar.gz [WARNING] Entry: bitrepository-reference-pillar-1.6-SNAPSHOT/lib/bitrepository-reference-pillar-1.6-SNAPSHOT-tests.jar longer than 100 characters. [WARNING] Resulting tar file can only be processed successfully by GNU compatible tar commands [INFO] Building tar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.6-SNAPSHOT-deploy.tar.gz [INFO] Building tar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.6-SNAPSHOT-acceptance-test-deploy.tar.gz [INFO] [INFO] --- maven-install-plugin:2.5.1:install (default-install) @ bitrepository-reference-pillar --- [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.6-SNAPSHOT.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.6-SNAPSHOT/bitrepository-reference-pillar-1.6-SNAPSHOT.jar [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.6-SNAPSHOT/bitrepository-reference-pillar-1.6-SNAPSHOT.pom [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.6-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.6-SNAPSHOT/bitrepository-reference-pillar-1.6-SNAPSHOT-tests.jar [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.6-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.6-SNAPSHOT/bitrepository-reference-pillar-1.6-SNAPSHOT-sources.jar [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.6-SNAPSHOT-distribution.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.6-SNAPSHOT/bitrepository-reference-pillar-1.6-SNAPSHOT-distribution.tar.gz [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.6-SNAPSHOT-acceptance-test.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.6-SNAPSHOT/bitrepository-reference-pillar-1.6-SNAPSHOT-acceptance-test.tar.gz [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.6-SNAPSHOT-deploy.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.6-SNAPSHOT/bitrepository-reference-pillar-1.6-SNAPSHOT-deploy.tar.gz [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.6-SNAPSHOT-acceptance-test-deploy.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.6-SNAPSHOT/bitrepository-reference-pillar-1.6-SNAPSHOT-acceptance-test-deploy.tar.gz [JENKINS] Archiving disabled