[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] Deleting /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target [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 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 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 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@7c22d4f[correlationID=5c8de9a7-46d6-44ed-a1c9-3ea5cbd0c444, 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@5f59185e[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@1e886a5b[correlationID=7021568e-5cbb-4caf-9186-71b7d7e110bc, 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@d816dde[responseCode=EXISTING_FILE_CHECKSUM_FAILURE, responseText=No mandatory checksum for destructive operation was supplied.], pillarID=Pillar-badCaseOperationMissingVerification, fileID=DefaultFilebadCaseOperationMissingVerification, checksumDataForExistingFile=] 02:23:27.493 WARN o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@6c451c9c[origDateTime=2015-12-08T02:23:27.493+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCaseOperationMissingVerification, alarmText=No mandatory checksum for destructive operation was supplied., fileID=DefaultFilebadCaseOperationMissingVerification, collectionID=TwoPillarCollection] Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@31c269fd[correlationID=535cc4fa-93dd-4da0-bfa3-06b4e6ee3c24, 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@6c451c9c[origDateTime=2015-12-08T02:23:27.493+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCaseOperationMissingVerification, alarmText=No mandatory checksum for destructive operation was supplied., fileID=DefaultFilebadCaseOperationMissingVerification, collectionID=TwoPillarCollection]] Step: Retrieve the FinalResponse for the DeleteFile request Step: Pillar should have sent an alarm Test success: badCaseOperationMissingVerification Added fixture: Initialize a new Pillar. Test starting: badCaseOperationNoFile Description: Tests the DeleteFile functionality of the pillar for the failure scenario, where it does not have the file. Step: Set up constants and variables. Step: Setup for delivering pillar id and not having the file Step: Create and send the actual DeleteFile message to the pillar. Result: Received message on TEST-TOPIC-badCaseOperationNoFile-cibuild01 : org.bitrepository.bitrepositorymessages.DeleteFileFinalResponse@415e0bcb[correlationID=d4673681-a184-476f-a4de-5ea2e5668408, 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@194152cf[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 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@2b97cc1f[correlationID=b5406915-bd87-49da-8ba7-c0f1f6fdd42c, 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@60723d6a[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], fileID=DefaultFilegoodCaseIdentification, pillarID=Pillar-goodCaseIdentification, pillarChecksumSpec=, timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@18324f97[timeMeasureUnit=MILLISECONDS, timeMeasureValue=1000]] Step: Retrieve and validate the response getPillarID() the pillar. Test success: goodCaseIdentification Starting testcase FullPillarModelTest Test starting: testPillarModelBasicFunctionality Description: Test the basic functions of the full reference pillar model. Step: Check the pillar id in the pillar model Step: Ask whether it can handle a file of size 0 Step: Ask whether it can handle a file of maximum size Step: Check the ChecksumPillarSpec Test success: testPillarModelBasicFunctionality Test starting: testPillarModelHasFile Description: Test that the file exists, when placed in the archive and cache Step: Setup Step: Check whether file exists and retrieve it. Step: Verify that no exceptions are thrown when verifying file existance. Step: Check retrieval of non-default checksum Test success: testPillarModelHasFile Test starting: testPillarModelNoFile Description: Test that the file exists, when placed in the archive and cache Step: Setup Step: Check whether file exists and try to retrieve it. Step: Verify that anexceptions are thrown when verifying file existance. 02:23:33.431 WARN o.b.pillar.store.FileStorageModel - The file 'DefaultFile' has been requested, but we do not have that file in collection 'TwoPillarCollection'! Test success: testPillarModelNoFile Starting testcase GetAuditTrailsTest Added fixture: Initialize a new Pillar. Test starting: checksumPillarGetAuditTrailsMaximumNumberOfResults Description: Tests the GetAuditTrails functionality of the pillar for the successful scenario, where a limited number of audit trails are requested. Step: Set up constants and variables. Step: Send the request for the limited amount of audit trails to the pillar. Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsMaximumNumberOfResults-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsProgressResponse@2e66bc32[correlationID=fb14e407-7bf0-4951-bf94-e20550955328, 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@54d8c20d[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@36681447[correlationID=fb14e407-7bf0-4951-bf94-e20550955328, 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@4d21c56e[responseCode=OPERATION_COMPLETED, responseText=], contributor=Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@726aa968[resultAddress=, auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@7100dea[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@712cfb63[sequenceNumber=1, fileID=fileID1449537813751, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=CHECKSUM_CALCULATED, actionDateTime=2015-12-08T02:23:33.753+01:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@32e54a9d[sequenceNumber=2, fileID=fileID1449537813751, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=DELETE_FILE, actionDateTime=2015-12-08T02:23:33.754+01:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@15639440[sequenceNumber=3, fileID=fileID1449537813751, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=FAILURE, actionDateTime=2015-12-08T02:23:33.754+01:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@121bb45b[sequenceNumber=4, fileID=fileID1449537813751, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=FILE_MOVED, actionDateTime=2015-12-08T02:23:33.755+01:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@4faa298[sequenceNumber=5, fileID=fileID1449537813751, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=GET_CHECKSUMS, actionDateTime=2015-12-08T02:23:33.755+01:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails]}]], partialResult=true] Step: Validate the final response Test success: checksumPillarGetAuditTrailsMaximumNumberOfResults Added fixture: Initialize a new Pillar. Test starting: checksumPillarGetAuditTrailsSpecificRequests Description: Tests the GetAuditTrails functionality of the pillar for the successful scenario, where a specific audit trail are requested. Step: Set up constants and variables. Step: Send the identification request Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsResponse@7d78f3d5[correlationID=a57e8736-785f-460a-b576-3b98c629b85b, 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@a4b5ce3[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@4b4eced1[correlationID=a57e8736-785f-460a-b576-3b98c629b85b, 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@71926a36[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@216e9ca3[correlationID=a57e8736-785f-460a-b576-3b98c629b85b, 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@75120e58[responseCode=OPERATION_COMPLETED, responseText=], contributor=Pillar-checksumPillarGetAuditTrailsSpecificRequests, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@48976e6d[resultAddress=, auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@2a367e93[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@7f6874f2[sequenceNumber=1, fileID=fileID1449537814527, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=OTHER, actionDateTime=2015-12-08T02:23:34.527+01:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails]}]], partialResult=false] Step: Receive and validate the progress response. Step: Receive and validate the final response Step: Make another request, where both ingested audit trails is requested Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsProgressResponse@1a6dc589[correlationID=a57e8736-785f-460a-b576-3b98c629b85b, 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@697a34af[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@70211df5[correlationID=a57e8736-785f-460a-b576-3b98c629b85b, 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@4c5228e7[responseCode=OPERATION_COMPLETED, responseText=], contributor=Pillar-checksumPillarGetAuditTrailsSpecificRequests, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@38e7ed69[resultAddress=, auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@806996[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@7f6874f2[sequenceNumber=1, fileID=fileID1449537814527, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=OTHER, actionDateTime=2015-12-08T02:23:34.527+01:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@78b612c6[sequenceNumber=2, fileID=notThisFile, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=UnknownActor, actionOnFile=FAILURE, actionDateTime=2015-12-08T02:23:34.527+01:00, info=badInfo, operationID=operationID, certificateID=certificateid, auditTrailInformation=WrongAuditTrail]}]], partialResult=false] Step: Receive and validate the progress response. Step: Receive and validate the final response Test success: checksumPillarGetAuditTrailsSpecificRequests Added fixture: Initialize a new Pillar. Test starting: checksumPillarGetAuditTrailsSuccessful Description: Tests the GetAuditTrails functionality of the pillar for the successful scenario, where all audit trails are requested. Step: Set up constants and variables. Step: Send the identification request Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSuccessful-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsResponse@4ed4a7e4[correlationID=2699e59e-7229-4d66-854e-034007146362, 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@1c7350b0[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@55651434[correlationID=2699e59e-7229-4d66-854e-034007146362, 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@3bc4ef12[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@50448409[correlationID=2699e59e-7229-4d66-854e-034007146362, 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@5634a861[responseCode=OPERATION_COMPLETED, responseText=], contributor=Pillar-checksumPillarGetAuditTrailsSuccessful, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@2b0dc227[resultAddress=, auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@37ad042b[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@43bdaa1b[sequenceNumber=1, fileID=fileid, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=actor, actionOnFile=OTHER, actionDateTime=2015-12-08T02:23:34.927+01:00, info=info, operationID=operationID, certificateID=certificateID, auditTrailInformation=auditTrail]}]], partialResult=false] Step: Receive and validate the progress response. Step: Receive and validate the final response Test success: checksumPillarGetAuditTrailsSuccessful Test starting: componentIDTest Test success: componentIDTest Starting testcase ReferenceArchiveTest Added fixture: Initialize the Reference pillar cache with an empty file in default collection TwoPillarCollection Test starting: testReferenceArchive Description: Test the ReferenceArchive. Step: Setup Step: test 'hasFile' Step: Test 'getFile' Step: Test getAllFileIDs Step: Test 'getFileAsInputstream' Step: Delete, recreate and delete again Step: Try to delete missing file. Step: Replace a file, which does not exist in the filedir. Step: Copy a file into the tmpDir and then use replace. Step: Try performing the replace, when the file in the tempdir has been removed. Test success: testReferenceArchive Test starting: getPillarCollectionsTest Test success: getPillarCollectionsTest Starting testcase 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 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@11c713b7[correlationID=76073c6a-64d3-4d8b-a89c-df6e4b7f5886, 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@2251b3bc[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@285005b8[correlationID=a1c2054a-59c4-4cf9-98c2-5aedc8a7bfdd, 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@5b1efaaf[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], fileID=DefaultFilegoodCaseIdentification, pillarID=Pillar-goodCaseIdentification, timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@27585351[timeMeasureUnit=MILLISECONDS, timeMeasureValue=1000]] Step: Retrieve and validate the response getPillarID() the pillar. Test success: goodCaseIdentification Starting testcase PutFileTest Added fixture: Initialize a new Pillar. Test starting: badCaseIdentification Description: Tests the identification for a PutFile operation on the pillar for the failure scenario, when the file already exists. Step: Set up constants and variables. Step: Setup for already having the file and delivering pillar id Step: Create and send the identify request message. Result: Received message on TEST-TOPIC-badCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileResponse@7ed49a7f[correlationID=58d1fa5b-c02a-4c6f-a409-dfab293706e2, 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@1cd6b1bd[responseCode=DUPLICATE_FILE_FAILURE, responseText=], pillarID=Pillar-badCaseIdentification, fileID=DefaultFilebadCaseIdentification, pillarChecksumSpec=, checksumDataForExistingFile=, timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@443cdaa4[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@33d28f0a[correlationID=f928db7a-4eb9-4e3c-8ced-0d5ae0f877eb, 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@48d739f[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@4e958f08[correlationID=a0a349aa-14bb-436d-b917-d2fbee80723c, 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@71c0b742[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:45.536 WARN o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@3bbb8c16[origDateTime=2015-12-08T02:23:45.536+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCasePutOperationNoValidationChecksum, alarmText=A checksum is required for the PutFile operation to be performed., fileID=DefaultFilebadCasePutOperationNoValidationChecksum, collectionID=TwoPillarCollection] Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@73e1ecd0[correlationID=134ade42-7188-4a3a-9d6a-a37d8b4b490a, 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@3bbb8c16[origDateTime=2015-12-08T02:23:45.536+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCasePutOperationNoValidationChecksum, alarmText=A checksum is required for the PutFile operation to be performed., fileID=DefaultFilebadCasePutOperationNoValidationChecksum, collectionID=TwoPillarCollection]] Step: Retrieve the FinalResponse for the PutFile request Step: Pillar should have sent an alarm Test success: badCasePutOperationNoValidationChecksum Added fixture: Initialize a new Pillar. Test starting: goodCaseIdentification Description: Tests the identification for a PutFile operation on the pillar for the successful scenario. Step: Set up constants and variables. Step: Setup for not already having the file and delivering pillar id Step: Create and send the identify request message. Result: Received message on TEST-TOPIC-goodCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileResponse@35ac9ebd[correlationID=a52954f5-e831-4735-a74f-588cdc69897e, 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@56c0a61e[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], pillarID=Pillar-goodCaseIdentification, fileID=DefaultFilegoodCaseIdentification, pillarChecksumSpec=, checksumDataForExistingFile=, timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@421ead7e[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@3f357c9d[correlationID=a43b60ad-a083-482f-a91a-d1a81d7424dd, 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@fe42a09[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@1ffd0114[correlationID=a43b60ad-a083-482f-a91a-d1a81d7424dd, 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@b3857e2[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@25a290ee[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@37d0d373[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2015-12-08T02:23:47.164+01:00], checksumDataForExistingFile=] Step: Retrieve the ProgressResponse for the GetFileIDs request Step: Retrieve the FinalResponse for the PutFile request Test success: goodCaseOperationWithChecksumReturn 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 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@ff5d4f1[correlationID=051a6e3c-1e18-468a-ab09-625f9617b3e1, 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@194224ca[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@56872fcb[correlationID=6365d016-8899-4acc-b89d-a93056119005, 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@7b3c2ae0[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@31533eb1[correlationID=78fa3eda-be4f-44a9-8cb9-02a862afb942, 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@1fb71788[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:51.425 WARN o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@8cb7185[origDateTime=2015-12-08T02:23:51.424+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCaseOperationNoDestructiveChecksum, alarmText=According to the contract a checksum for file to be deleted during the replacing operation is required., fileID=DefaultFile, collectionID=TwoPillarCollection] Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@4dac40b[correlationID=e7c45d27-2c84-4939-87f8-6749da380840, 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@8cb7185[origDateTime=2015-12-08T02:23:51.424+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCaseOperationNoDestructiveChecksum, alarmText=According to the contract a checksum for file to be deleted during the replacing operation is required., fileID=DefaultFile, collectionID=TwoPillarCollection]] Step: Retrieve the FinalResponse for the ReplaceFile request Step: Pillar should have sent an alarm Test success: badCaseOperationNoDestructiveChecksum Added fixture: Initialize a new Pillar. Test starting: badCaseOperationNoValidationChecksum Description: Tests the ReplaceFile operation on the pillar for the failure scenario, when no validation checksum is given for the new file, but though is required. Step: Set up constants and variables. Step: Setup for having the file and delivering pillar id Step: Create and send the identify request message. Result: Received message on TEST-TOPIC-badCaseOperationNoValidationChecksum-cibuild01 : org.bitrepository.bitrepositorymessages.ReplaceFileFinalResponse@43778371[correlationID=0018f550-9673-4d54-b6f7-1f659fabb141, 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@71beada8[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:51.924 WARN o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@17f41739[origDateTime=2015-12-08T02:23:51.924+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCaseOperationNoValidationChecksum, alarmText=According to the contract a checksum for new file in the replacing operation is required., fileID=DefaultFile, collectionID=TwoPillarCollection] Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@2b3b1124[correlationID=9cd8cdbe-4aac-4892-b780-be0a034ac2ef, 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@17f41739[origDateTime=2015-12-08T02:23:51.924+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCaseOperationNoValidationChecksum, alarmText=According to the contract a checksum for new file in the replacing operation is required., fileID=DefaultFile, collectionID=TwoPillarCollection]] Step: Retrieve the FinalResponse for the ReplaceFile request Step: Pillar should have sent an alarm Test success: badCaseOperationNoValidationChecksum Added fixture: Initialize a new Pillar. Test starting: badCaseOperationWrongDestructiveChecksum Description: Tests the ReplaceFile operation on the pillar for the failure scenario, when the checksum for the destructive action is different from the one in the cache. Step: Set up constants and variables. Step: Setup for having the file and delivering pillar id Step: Create and send the identify request message. 02:23:52.113 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@4b00d59[correlationID=40d62d6d-9d71-4cab-bc0a-bc324640240f, 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@7c048b30[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:52.115 WARN o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@309cf657[origDateTime=2015-12-08T02:23:52.114+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCaseOperationWrongDestructiveChecksum, alarmText=Requested to replace the file 'DefaultFile' with checksum '1234cccccccc4321', but our file had a different checksum., fileID=DefaultFile, collectionID=TwoPillarCollection] Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@4d4c4b14[correlationID=74a2fd73-8c3e-42c7-8131-c4b562c199a1, 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@309cf657[origDateTime=2015-12-08T02:23:52.114+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCaseOperationWrongDestructiveChecksum, alarmText=Requested to replace the file 'DefaultFile' with checksum '1234cccccccc4321', but our file had a different checksum., fileID=DefaultFile, collectionID=TwoPillarCollection]] Step: Retrieve the FinalResponse for the ReplaceFile request Step: Pillar should have sent an alarm Test success: badCaseOperationWrongDestructiveChecksum Added fixture: Initialize a new Pillar. Test starting: goodCaseIdentification Description: Tests the identification for a ReplaceFile operation on the pillar for the successful scenario. Step: Set up constants and variables. Step: Setup for having the file and delivering pillar id Step: Create and send the identify request message. Result: Received message on TEST-TOPIC-goodCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileResponse@6d5508a5[correlationID=c9268bbe-4f18-46e2-b630-59129e5c4277, 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@103bcc9f[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], fileID=DefaultFile, pillarID=Pillar-goodCaseIdentification, pillarChecksumSpec=, timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@106802ea[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@3e12c5de[correlationID=315e3032-3f58-48b6-a15f-b0fdf43d9328, 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@3e55d844[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@2b3abeeb[correlationID=315e3032-3f58-48b6-a15f-b0fdf43d9328, 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@3aeb267[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@14c5283[correlationID=daa629c1-1c4f-4ade-bf58-d0a0e2b20d77, 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@1eb7ec59[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@46748b04[correlationID=daa629c1-1c4f-4ade-bf58-d0a0e2b20d77, 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@3e71a1f8[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@5d4a34ff[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7cbede2b[checksumType=HMAC_SHA512, checksumSalt={97,98}, otherChecksumType=], checksumValue={18,52,-52,-52,-52,-52,67,34}, calculationTimestamp=2015-12-08T02:23:55.047+01:00], checksumDataForNewFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@1ef04613[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2d3d4a54[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2015-12-08T02:23:55.048+01:00]] Step: Retrieve the ProgressResponse for the GetFileIDs request Step: Retrieve the FinalResponse for the ReplaceFile request Test success: goodCaseOperationWithChecksumsReturn 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:23:59.954 WARN o.b.service.database.DatabaseUtils - Migrating the checksums table from version 1 to 2 in the ChecksumDatabase. 02:24:00.040 WARN o.b.service.database.DatabaseUtils - Migrating ChecksumDB from version 2 to 3. Step: Validate the entry Test success: testMigratingDatabaseChecksumsTable 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 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@4a0c04ab[correlationID=5bd49597-877c-41bb-b79a-6a5a40d0b5b2, 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@453439e[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@2d33795c[fileID=DefaultFilebadCaseIdentification, allFileIDs=], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@779ef5cb[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:02.886 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@7fdf7359[correlationID=c13db677-f85c-4728-9e07-fb84ae7964c8, 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@4a36a35d[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@52ba21e4[checksumType=MD5, checksumSalt=, otherChecksumType=], resultingChecksums=, partialResult=] 02:24:02.891 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@2e1c5d1f[correlationID=c13db677-f85c-4728-9e07-fb84ae7964c8, 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@2d2afc39[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@52ba21e4[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@2e1c5d1f[correlationID=c13db677-f85c-4728-9e07-fb84ae7964c8, 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@2d2afc39[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@52ba21e4[checksumType=MD5, checksumSalt=, otherChecksumType=], resultingChecksums=, partialResult=] 02:24:03.911 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@2e1c5d1f[correlationID=c13db677-f85c-4728-9e07-fb84ae7964c8, 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@2d2afc39[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@52ba21e4[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@5bed0ff4[correlationID=983a8a37-023b-4f42-be09-eec5123c7c39, 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@17a5ae7b[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@7e4dddee[fileID=DefaultFilegoodCaseIdentification, allFileIDs=], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@183a84f4[checksumType=MD5, checksumSalt=, otherChecksumType=], pillarID=Pillar-goodCaseIdentification, pillarChecksumSpec=, timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@2b9bbaa8[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@5315210d[correlationID=83f78e7c-188b-4f8c-bc2f-3830d7794be6, 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@3f5f79d8[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to calculate checksums.], pillarID=Pillar-goodCaseOperationAllFiles, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@5dc1597f[fileID=, allFileIDs=true], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@11896af6[checksumType=MD5, checksumSalt=, otherChecksumType=], resultAddress=] Result: Received message on TEST-TOPIC-goodCaseOperationAllFiles-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@2262bc86[correlationID=83f78e7c-188b-4f8c-bc2f-3830d7794be6, 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@3872867d[responseCode=OPERATION_COMPLETED, responseText=], pillarID=Pillar-goodCaseOperationAllFiles, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@11896af6[checksumType=MD5, checksumSalt=, otherChecksumType=], resultingChecksums=org.bitrepository.bitrepositoryelements.ResultingChecksums@4f72078d[resultAddress=, checksumDataItems={org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@2e4d252[fileID=DefaultFile, checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2015-12-08T02:24:05.622+01:00],org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@3555d804[fileID=goodCaseOperationAllFiles-cibuild01--Test-File-1449537845618, 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@c555e1e[correlationID=21d2e677-e7e0-48c1-a878-ac5cab382903, 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@64e247e[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to calculate checksums.], pillarID=Pillar-goodCaseOperationSingleFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@66df362c[fileID=DefaultFilegoodCaseOperationSingleFile, allFileIDs=], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@125ba798[checksumType=MD5, checksumSalt=, otherChecksumType=], resultAddress=] Result: Received message on TEST-TOPIC-goodCaseOperationSingleFile-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@3458be63[correlationID=21d2e677-e7e0-48c1-a878-ac5cab382903, 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@43c20142[responseCode=OPERATION_COMPLETED, responseText=], pillarID=Pillar-goodCaseOperationSingleFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@125ba798[checksumType=MD5, checksumSalt=, otherChecksumType=], resultingChecksums=org.bitrepository.bitrepositoryelements.ResultingChecksums@5cb32140[resultAddress=, checksumDataItems={org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@139b3a29[fileID=DefaultFilegoodCaseOperationSingleFile, checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2015-12-08T02:24:05.726+01:00]}], partialResult=false] Step: Retrieve the ProgressResponse for the GetChecksums request Step: Retrieve the FinalResponse for the GetChecksums request Test success: goodCaseOperationSingleFile Added fixture: Initialize a new Pillar. Test starting: testRestrictions Description: Tests that the restrictions are correctly passed on to the cache. Step: Set up constants and variables. Step: Setup for only delivering result-set when the correct restrictions are given. Step: Create and send the actual GetChecksums message to the pillar. Result: Received message on TEST-TOPIC-testRestrictions-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsProgressResponse@3733b1f4[correlationID=d3a31f9f-285e-4591-9c24-5a13f1067448, 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@70f0c352[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to calculate checksums.], pillarID=Pillar-testRestrictions, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@4e93d23e[fileID=, allFileIDs=true], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@743b7025[checksumType=MD5, checksumSalt=, otherChecksumType=], resultAddress=] Result: Received message on TEST-TOPIC-testRestrictions-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@5eadc347[correlationID=d3a31f9f-285e-4591-9c24-5a13f1067448, 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@28b16193[responseCode=OPERATION_COMPLETED, responseText=], pillarID=Pillar-testRestrictions, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@743b7025[checksumType=MD5, checksumSalt=, otherChecksumType=], resultingChecksums=org.bitrepository.bitrepositoryelements.ResultingChecksums@78e34499[resultAddress=, checksumDataItems={org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@5776a9f8[fileID=DefaultFile, checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2015-12-08T02:24:05.893+01:00]}], partialResult=false] Step: Retrieve the ProgressResponse for the GetChecksums request Step: Retrieve the FinalResponse for the GetChecksums request Test success: testRestrictions Starting testcase 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 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:24:19.512 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:80) ~[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:73) [bitrepository-core-1.6-SNAPSHOT.jar:1.6-SNAPSHOT] at org.bitrepository.protocol.messagebus.SimpleMessageBus$$Lambda$1/1174586025.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:73) [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@2da7ef3e[correlationID=5cca22e9-0f86-4941-8054-84b6e094c2b8, 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@67cc5a38[responseCode=FAILURE, responseText=java.lang.RuntimeException: I am supposed to throw a RuntimeException], contributor=TEST-TOPIC-cibuild01, timeToDeliver=] 02:24:19.513 WARN o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@f4e235e[origDateTime=2015-12-08T02:24:19.513+01: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@1d82e396[correlationID=a17293b9-96b8-4f6d-87ba-93ef45e250a1, collectionID=, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-MediatorUnderTest-cibuild01-contributor, from=MediatorUnderTest, to=, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@f4e235e[origDateTime=2015-12-08T02:24:19.513+01:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MediatorUnderTest, alarmText=java.lang.RuntimeException: I am supposed to throw a RuntimeException, fileID=, collectionID=]] Test success: testMediatorRuntimeExceptionHandling 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:24:19.612 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@2197990b[correlationID=1c622488-d395-410b-9f74-1056dfd53bd2, 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@17eb5661[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseIdentification, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@63b0aeb1[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:24:21.127 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@34fe89a5[correlationID=66ebe7bc-f9f6-449b-a57a-957fb8bcf484, 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@71acf065[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@3705e3fb[fileID=DefaultFilebadCaseOperationNoFile, allFileIDs=], resultingFileIDs=, partialResult=] 02:24:21.142 WARN o.b.p.m.GetFileIDsRequestHandler - The following file is missing 'DefaultFilebadCaseOperationNoFile' at collection 'TwoPillarCollection'. Result: Received message on TEST-TOPIC-badCaseOperationNoFile-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsFinalResponse@5a349644[correlationID=66ebe7bc-f9f6-449b-a57a-957fb8bcf484, 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@42b6acc2[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@3705e3fb[fileID=DefaultFilebadCaseOperationNoFile, allFileIDs=], resultingFileIDs=, partialResult=] 02:24:21.146 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@1a819769[correlationID=66ebe7bc-f9f6-449b-a57a-957fb8bcf484, 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@6479b4cb[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@3705e3fb[fileID=DefaultFilebadCaseOperationNoFile, allFileIDs=], resultingFileIDs=, partialResult=] Step: Retrieve the FinalResponse for the GetFileIDs request Test success: badCaseOperationNoFile Result: The following messages haven't been handled by the testcase: org.bitrepository.bitrepositorymessages.GetFileIDsFinalResponse@5a349644[correlationID=66ebe7bc-f9f6-449b-a57a-957fb8bcf484, 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@42b6acc2[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@3705e3fb[fileID=DefaultFilebadCaseOperationNoFile, allFileIDs=], resultingFileIDs=, partialResult=] org.bitrepository.bitrepositorymessages.GetFileIDsFinalResponse@1a819769[correlationID=66ebe7bc-f9f6-449b-a57a-957fb8bcf484, 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@6479b4cb[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@3705e3fb[fileID=DefaultFilebadCaseOperationNoFile, allFileIDs=], resultingFileIDs=, partialResult=] 02:24:22.168 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: org.bitrepository.bitrepositorymessages.GetFileIDsFinalResponse@5a349644[correlationID=66ebe7bc-f9f6-449b-a57a-957fb8bcf484, 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@42b6acc2[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@3705e3fb[fileID=DefaultFilebadCaseOperationNoFile, allFileIDs=], resultingFileIDs=, partialResult=] org.bitrepository.bitrepositorymessages.GetFileIDsFinalResponse@1a819769[correlationID=66ebe7bc-f9f6-449b-a57a-957fb8bcf484, 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@6479b4cb[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@3705e3fb[fileID=DefaultFilebadCaseOperationNoFile, allFileIDs=], resultingFileIDs=, partialResult=] 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@52813ba4[correlationID=15e1f714-dd7b-44ac-8cad-c6cbdd7cefe4, 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@62291850[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], pillarID=Pillar-goodCaseIdentification, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@2518245b[fileID=DefaultFilegoodCaseIdentification, allFileIDs=], timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@45c8db36[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: 68.281 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