SuccessConsole Output

Skipping 485 KB.. Full Log
e file from archive and tmp
      Test success: testArchiveDirectoryRemoveFile
      Test starting: testArchiveDirectoryRemoveFolderFile
        Description: Testing the error scenarios when removing files from the archive.
        Step: Setup
        Step: Remove nonexisting file from archive
        Step: Remove nonexisting file from tmp
        Step: Create file in both tmp, archive and retain directories.
        Step: Remove the file from archive and tmp
      Test success: testArchiveDirectoryRemoveFolderFile
    Starting testcase ChecksumDatabaseMigrationTest
      Test starting: testMigratingChecksumDatabaseFromV3ToV4
        Description: Tests that the checksums table can be migrated from version 3 to 4, e.g. changing the column calculatedchecksumdate from timestamp to bigint.
        Step: Ensure cleanup
15:22:49.598 WARN  o.b.common.utils.FileUtils - Could not delete '/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/test/referencepillar/checksumdb-for-migration'
        Step: Unzipping and connecting to checksum database version 3
        Step: Validate setup
        Step: Ingest a entry to the database with a date for the calculationdate
        Step: Perform migration
15:22:53.368 WARN  o.b.service.database.DatabaseUtils - Migrating ChecksumDB from version 3 to 4.
        Step: Validate the migration
      Test success: testMigratingChecksumDatabaseFromV3ToV4
    Starting testcase ChecksumEntryTest
      Test starting: testExtendedTestCase
        Description: Test the ChecksumEntry
        Step: Create a ChecksumEntry
      Test success: testExtendedTestCase
    Starting testcase 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@5af6378e[correlationID=67c68cdc-6d95-4788-956b-4639a231537b, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsMaximumNumberOfResults-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults, to=Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@205b3a1a[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to extract the requested audit trails.], contributor=Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults, resultAddress=<null>(default)]
          Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsMaximumNumberOfResults-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsFinalResponse@73ccc475[correlationID=67c68cdc-6d95-4788-956b-4639a231537b, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsMaximumNumberOfResults-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults, to=Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@4184bced[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], contributor=Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@117bb3a4[resultAddress=<null>(default), auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@4d78dd9d[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@5802572b[sequenceNumber=1, fileID=fileID1487427774636, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=CHECKSUM_CALCULATED, actionDateTime=2017-02-18T15:22:54.638+01:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@3c05fb12[sequenceNumber=2, fileID=fileID1487427774636, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=DELETE_FILE, actionDateTime=2017-02-18T15:22:54.639+01:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@702f99a5[sequenceNumber=3, fileID=fileID1487427774636, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=FAILURE, actionDateTime=2017-02-18T15:22:54.639+01:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@7b303608[sequenceNumber=4, fileID=fileID1487427774636, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=FILE_MOVED, actionDateTime=2017-02-18T15:22:54.639+01:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@31419d4a[sequenceNumber=5, fileID=fileID1487427774636, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=GET_CHECKSUMS, actionDateTime=2017-02-18T15:22:54.640+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@59fe8d94[correlationID=853599f1-2b3e-43be-af40-e228dbc053a6, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSpecificRequests-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSpecificRequests, to=Pillar-checksumPillarGetAuditTrailsSpecificRequests, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@479f5c35[responseCode=IDENTIFICATION_POSITIVE, responseText=<null>(default)]]
        Step: Retrieve and validate the response.
        Step: Make and send the request for the actual GetAuditTrails operation
          Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsProgressResponse@194e116d[correlationID=853599f1-2b3e-43be-af40-e228dbc053a6, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSpecificRequests-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSpecificRequests, to=Pillar-checksumPillarGetAuditTrailsSpecificRequests, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@3471bdfd[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to extract the requested audit trails.], contributor=Pillar-checksumPillarGetAuditTrailsSpecificRequests, resultAddress=<null>(default)]
          Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsFinalResponse@93231b2[correlationID=853599f1-2b3e-43be-af40-e228dbc053a6, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSpecificRequests-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSpecificRequests, to=Pillar-checksumPillarGetAuditTrailsSpecificRequests, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@cf97391[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], contributor=Pillar-checksumPillarGetAuditTrailsSpecificRequests, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@65d5de1a[resultAddress=<null>(default), auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@5cf21908[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@44d51c85[sequenceNumber=1, fileID=fileID1487427775032, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=OTHER, actionDateTime=2017-02-18T15:22:55.032+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@3f78a75[correlationID=853599f1-2b3e-43be-af40-e228dbc053a6, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSpecificRequests-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSpecificRequests, to=Pillar-checksumPillarGetAuditTrailsSpecificRequests, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@4819a11f[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to extract the requested audit trails.], contributor=Pillar-checksumPillarGetAuditTrailsSpecificRequests, resultAddress=<null>(default)]
          Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsFinalResponse@46fdb4d[correlationID=853599f1-2b3e-43be-af40-e228dbc053a6, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSpecificRequests-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSpecificRequests, to=Pillar-checksumPillarGetAuditTrailsSpecificRequests, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@68b2ce71[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], contributor=Pillar-checksumPillarGetAuditTrailsSpecificRequests, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@57a94530[resultAddress=<null>(default), auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@52bd1783[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@44d51c85[sequenceNumber=1, fileID=fileID1487427775032, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=OTHER, actionDateTime=2017-02-18T15:22:55.032+01:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@28f20b2a[sequenceNumber=2, fileID=notThisFile, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=UnknownActor, actionOnFile=FAILURE, actionDateTime=2017-02-18T15:22:55.032+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@66cdde2b[correlationID=97a7e18a-fc03-4d39-bc08-57d994b06f32, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSuccessful-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSuccessful-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSuccessful, to=Pillar-checksumPillarGetAuditTrailsSuccessful, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@68321229[responseCode=IDENTIFICATION_POSITIVE, responseText=<null>(default)]]
        Step: Make and send the request for the actual GetAuditTrails operation
          Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSuccessful-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsProgressResponse@53ce41e7[correlationID=97a7e18a-fc03-4d39-bc08-57d994b06f32, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSuccessful-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSuccessful-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSuccessful, to=Pillar-checksumPillarGetAuditTrailsSuccessful, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@5d9cd8b7[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to extract the requested audit trails.], contributor=Pillar-checksumPillarGetAuditTrailsSuccessful, resultAddress=<null>(default)]
          Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSuccessful-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsFinalResponse@55a869a9[correlationID=97a7e18a-fc03-4d39-bc08-57d994b06f32, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSuccessful-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSuccessful-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSuccessful, to=Pillar-checksumPillarGetAuditTrailsSuccessful, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@2d739a6f[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], contributor=Pillar-checksumPillarGetAuditTrailsSuccessful, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@c93275f[resultAddress=<null>(default), auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@37711f1a[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@2182cd7c[sequenceNumber=1, fileID=fileid, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=actor, actionOnFile=OTHER, actionDateTime=2017-02-18T15:22:55.324+01:00, info=info, operationID=operationID, certificateID=certificateID, auditTrailInformation=auditTrail]}]], partialResult=false]
        Step: Receive and validate the progress response.
        Step: Receive and validate the final response
      Test success: checksumPillarGetAuditTrailsSuccessful
    Starting testcase 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@20120154[correlationID=99d064c6-60bb-4a24-8dbb-31443adbf340, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseIdentification-cibuild01-contributor, from=Pillar-badCaseIdentification, to=badCaseIdentification, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@78ceb8cd[responseCode=DUPLICATE_FILE_FAILURE, responseText=<null>(default)], pillarID=Pillar-badCaseIdentification, fileID=DefaultFilebadCaseIdentification, pillarChecksumSpec=<null>(default), checksumDataForExistingFile=<null>(default), timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@afee49e[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@33a267f[correlationID=7fa544d2-0859-4d8d-a9c3-1b4177b8a11b, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationFileAlreadyExists-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationFileAlreadyExists-cibuild01-contributor, from=Pillar-badCaseOperationFileAlreadyExists, to=badCaseOperationFileAlreadyExists, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@6a94ccde[responseCode=DUPLICATE_FILE_FAILURE, responseText=We already have the file], pillarID=Pillar-badCaseOperationFileAlreadyExists, pillarChecksumSpec=<null>(default), fileID=DefaultFilebadCaseOperationFileAlreadyExists, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForNewFile=<null>(default), checksumDataForExistingFile=<null>(default)]
        Step: Retrieve the FinalResponse for the PutFile request
      Test success: badCaseOperationFileAlreadyExists
        Added fixture: Initialize a new Pillar.
      Test starting: badCasePutOperationNoValidationChecksum
        Description: Tests the PutFile operation on the pillar for the failure scenario, when no validation checksum is given but required.
        Step: Set up constants and variables.
        Step: Setup for not already having the file and delivering pillar id
        Step: Create and send the identify request message.
          Result: Received message on TEST-TOPIC-badCasePutOperationNoValidationChecksum-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileFinalResponse@325410ce[correlationID=49134de7-6cbd-4d31-b52a-cba3b22b257a, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCasePutOperationNoValidationChecksum-cibuild01, replyTo=TEST-TOPIC-Pillar-badCasePutOperationNoValidationChecksum-cibuild01-contributor, from=Pillar-badCasePutOperationNoValidationChecksum, to=badCasePutOperationNoValidationChecksum, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@7e7254d1[responseCode=NEW_FILE_CHECKSUM_FAILURE, responseText=A checksum is required for the PutFile operation to be performed.], pillarID=Pillar-badCasePutOperationNoValidationChecksum, pillarChecksumSpec=<null>(default), fileID=DefaultFilebadCasePutOperationNoValidationChecksum, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForNewFile=<null>(default), checksumDataForExistingFile=<null>(default)]
15:22:58.292 WARN  o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@36d56d5d[origDateTime=2017-02-18T15:22:58.292+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@3e549525[correlationID=4f9a0b17-4036-484d-b8da-68d09224e0fa, collectionID=TwoPillarCollection, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-Pillar-badCasePutOperationNoValidationChecksum-cibuild01-contributor, from=Pillar-badCasePutOperationNoValidationChecksum, to=<null>(default), version=30, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@36d56d5d[origDateTime=2017-02-18T15:22:58.292+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@4aee166d[correlationID=24186612-21e5-4123-8adc-dfabe1670e4b, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseIdentification-cibuild01-contributor, from=Pillar-goodCaseIdentification, to=goodCaseIdentification, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@20865ff2[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], pillarID=Pillar-goodCaseIdentification, fileID=DefaultFilegoodCaseIdentification, pillarChecksumSpec=<null>(default), checksumDataForExistingFile=<null>(default), timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@1a7c593b[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@75288f47[correlationID=7c8666cb-92ee-45a9-b089-62f30ab659ff, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationWithChecksumReturn-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationWithChecksumReturn-cibuild01-contributor, from=Pillar-goodCaseOperationWithChecksumReturn, to=goodCaseOperationWithChecksumReturn, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@4effab3b[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Started to receive data.], pillarID=Pillar-goodCaseOperationWithChecksumReturn, pillarChecksumSpec=<null>(default), fileID=DefaultFilegoodCaseOperationWithChecksumReturn, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt]
          Result: Received message on TEST-TOPIC-goodCaseOperationWithChecksumReturn-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileFinalResponse@42491839[correlationID=7c8666cb-92ee-45a9-b089-62f30ab659ff, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationWithChecksumReturn-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationWithChecksumReturn-cibuild01-contributor, from=Pillar-goodCaseOperationWithChecksumReturn, to=goodCaseOperationWithChecksumReturn, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@732af580[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], pillarID=Pillar-goodCaseOperationWithChecksumReturn, pillarChecksumSpec=<null>(default), fileID=DefaultFilegoodCaseOperationWithChecksumReturn, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForNewFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@40bf2ead[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@5ce76938[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2017-02-18T15:23:02.178+01:00], checksumDataForExistingFile=<null>(default)]
        Step: Retrieve the ProgressResponse for the GetFileIDs request
        Step: Retrieve the FinalResponse for the PutFile request
      Test success: goodCaseOperationWithChecksumReturn
    Starting testcase ReferenceArchiveTest
        Added fixture: Initialize the Reference pillar cache with an empty file in default collection TwoPillarCollection
      Test starting: testReferenceArchive
        Description: Test the ReferenceArchive.
        Step: Setup
        Step: test 'hasFile'
        Step: Test 'getFile'
        Step: Test getAllFileIDs
        Step: Test 'getFileAsInputstream'
        Step: Delete, recreate and delete again
        Step: Try to delete missing file.
        Step: Replace a file, which does not exist in the filedir.
        Step: Copy a file into the tmpDir and then use replace.
        Step: Try performing the replace, when the file in the tempdir has been removed.
      Test success: testReferenceArchive
      Test starting: getPillarCollectionsTest
      Test success: getPillarCollectionsTest
    Starting testcase 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@1cbd2c1a[correlationID=88c87980-a02f-422e-aec4-ece54c57d7d3, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseIdentification-cibuild01-contributor, from=Pillar-badCaseIdentification, to=badCaseIdentification, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@4e125be1[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], fileID=DefaultFilebadCaseIdentification, pillarID=Pillar-badCaseIdentification, pillarChecksumSpec=<null>(default), timeToDeliver=<null>(default)]
        Step: Retrieve and validate the response getPillarID() the pillar.
      Test success: badCaseIdentification
        Added fixture: Initialize a new Pillar.
      Test starting: badCaseOperationMissingVerification
        Description: Tests the DeleteFile functionality of the pillar for the failure scenario, where it does not have the file.
        Step: Set up constants and variables.
        Step: Setup for delivering pillar id and having the file 
        Step: Create and send the actual DeleteFile message to the pillar.
          Result: Received message on TEST-TOPIC-badCaseOperationMissingVerification-cibuild01 : org.bitrepository.bitrepositorymessages.DeleteFileFinalResponse@661a5ac0[correlationID=c2b582f9-e02f-483d-972f-69ffe2d2c3e0, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationMissingVerification-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationMissingVerification-cibuild01-contributor, from=Pillar-badCaseOperationMissingVerification, to=badCaseOperationMissingVerification, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@444456cb[responseCode=EXISTING_FILE_CHECKSUM_FAILURE, responseText=No mandatory checksum for destructive operation was supplied.], pillarID=Pillar-badCaseOperationMissingVerification, fileID=DefaultFilebadCaseOperationMissingVerification, checksumDataForExistingFile=<null>(default)]
15:23:06.819 WARN  o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@bd211[origDateTime=2017-02-18T15:23:06.819+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@34f3448a[correlationID=7eb3ad83-fe4a-4ecc-92d7-f7b9db583132, collectionID=TwoPillarCollection, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationMissingVerification-cibuild01-contributor, from=Pillar-badCaseOperationMissingVerification, to=<null>(default), version=30, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@bd211[origDateTime=2017-02-18T15:23:06.819+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@13126d46[correlationID=1d657726-04bd-4578-8bac-a8e4720fa6c3, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@53c1792d[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileID=DefaultFilebadCaseOperationNoFile, checksumDataForExistingFile=<null>(default)]
        Step: Retrieve the FinalResponse for the DeleteFile request
      Test success: badCaseOperationNoFile
        Added fixture: Initialize a new Pillar.
      Test starting: goodCaseIdentification
        Description: Tests the identification for a DeleteFile operation on the pillar for the successful scenario.
        Step: Set up constants and variables.
        Step: Setup for having the file and delivering pillar id
        Step: Create and send the identify request message.
          Result: Received message on TEST-TOPIC-goodCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileResponse@9be2619[correlationID=d759e90d-f600-4eac-a847-9d2ec5687c52, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseIdentification-cibuild01-contributor, from=Pillar-goodCaseIdentification, to=goodCaseIdentification, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@5bbfd031[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], fileID=DefaultFilegoodCaseIdentification, pillarID=Pillar-goodCaseIdentification, pillarChecksumSpec=<null>(default), timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@5b3f2fe1[timeMeasureUnit=MILLISECONDS, timeMeasureValue=1000]]
        Step: Retrieve and validate the response getPillarID() the pillar.
      Test success: goodCaseIdentification
    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@3c79c7fa[correlationID=25db2732-ad86-41ba-b041-78efb1cc3010, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseIdentification-cibuild01-contributor, from=Pillar-badCaseIdentification, to=badCaseIdentification, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@2b3d662e[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@7889b4cb[fileID=DefaultFilebadCaseIdentification, allFileIDs=<null>(default)], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2b04b7dd[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], pillarID=Pillar-badCaseIdentification, pillarChecksumSpec=<null>(default), timeToDeliver=<null>(default)]
        Step: Retrieve and validate the response getPillarID() the pillar.
      Test success: badCaseIdentification
        Added fixture: Initialize a new Pillar.
      Test starting: badCaseOperationNoFile
        Description: Tests the GetChecksums functionality of the pillar for the failure scenario, where it does not have the file.
        Step: Set up constants and variables.
        Step: Setup for not having the file
        Step: Create and send the actual GetChecksums message to the pillar.
15:23:11.330 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@7aa91a69[correlationID=434be3e4-b4b0-4d09-9b96-1b631edf6e07, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@133a8a9f[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7764db24[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultingChecksums=<null>(default), partialResult=<null>(default)]
15:23:11.341 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@5ab0b773[correlationID=434be3e4-b4b0-4d09-9b96-1b631edf6e07, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@b5ceafa[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7764db24[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultingChecksums=<null>(default), partialResult=<null>(default)]
        Step: Retrieve the FinalResponse for the GetChecksums request
      Test success: badCaseOperationNoFile
          Result: The following messages haven't been handled by the testcase: 
org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@5ab0b773[correlationID=434be3e4-b4b0-4d09-9b96-1b631edf6e07, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@b5ceafa[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7764db24[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultingChecksums=<null>(default), partialResult=<null>(default)]
15:23:12.359 WARN  o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: 
org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@5ab0b773[correlationID=434be3e4-b4b0-4d09-9b96-1b631edf6e07, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@b5ceafa[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7764db24[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultingChecksums=<null>(default), partialResult=<null>(default)]
        Added fixture: Initialize a new Pillar.
      Test starting: goodCaseIdentification
        Description: Tests the identification for a GetChecksums operation on the pillar for the successful scenario.
        Step: Set up constants and variables.
        Step: Setup for having the file and delivering pillar id
        Step: Create and send the identify request message.
          Result: Received message on TEST-TOPIC-goodCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsResponse@72fad01f[correlationID=e142405a-780d-49ab-8381-4020c9012337, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseIdentification-cibuild01-contributor, from=Pillar-goodCaseIdentification, to=goodCaseIdentification, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@7ab212f9[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@2a7d12c8[fileID=DefaultFilegoodCaseIdentification, allFileIDs=<null>(default)], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@25be3c66[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], pillarID=Pillar-goodCaseIdentification, pillarChecksumSpec=<null>(default), timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@1e07ae6[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@e4e4643[correlationID=59a0cd11-d4a1-4467-bfe1-9e7c74931222, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationAllFiles-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationAllFiles-cibuild01-contributor, from=Pillar-goodCaseOperationAllFiles, to=goodCaseOperationAllFiles, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@35632dcd[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to calculate checksums.], pillarID=Pillar-goodCaseOperationAllFiles, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@185d151b[fileID=<null>(default), allFileIDs=true], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@4e9b4e98[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultAddress=<null>(default)]
          Result: Received message on TEST-TOPIC-goodCaseOperationAllFiles-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@7ac13392[correlationID=59a0cd11-d4a1-4467-bfe1-9e7c74931222, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationAllFiles-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationAllFiles-cibuild01-contributor, from=Pillar-goodCaseOperationAllFiles, to=goodCaseOperationAllFiles, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@51509c7d[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], pillarID=Pillar-goodCaseOperationAllFiles, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@4e9b4e98[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultingChecksums=org.bitrepository.bitrepositoryelements.ResultingChecksums@2dd72304[resultAddress=<null>(default), checksumDataItems={org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@58e21dde[fileID=DefaultFile, checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2017-02-18T15:23:14.068+01:00],org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@2b4ce8f3[fileID=goodCaseOperationAllFiles-cibuild01--Test-File-1487427794048, 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@51336aad[correlationID=ab43f6f6-041b-407a-9995-bfc3bc62edf9, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationSingleFile-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationSingleFile-cibuild01-contributor, from=Pillar-goodCaseOperationSingleFile, to=goodCaseOperationSingleFile, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@166323b9[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to calculate checksums.], pillarID=Pillar-goodCaseOperationSingleFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@7e4061bb[fileID=DefaultFilegoodCaseOperationSingleFile, allFileIDs=<null>(default)], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@28c7ae7f[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultAddress=<null>(default)]
          Result: Received message on TEST-TOPIC-goodCaseOperationSingleFile-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@626bcfc8[correlationID=ab43f6f6-041b-407a-9995-bfc3bc62edf9, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationSingleFile-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationSingleFile-cibuild01-contributor, from=Pillar-goodCaseOperationSingleFile, to=goodCaseOperationSingleFile, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@6d9a46d7[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], pillarID=Pillar-goodCaseOperationSingleFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@28c7ae7f[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultingChecksums=org.bitrepository.bitrepositoryelements.ResultingChecksums@102abf66[resultAddress=<null>(default), checksumDataItems={org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@58b4f4a[fileID=DefaultFilegoodCaseOperationSingleFile, checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2017-02-18T15:23:15.195+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@125490ea[correlationID=2460c632-a0e7-4e0e-ac2d-47f843bb03b3, collectionID=TwoPillarCollection, destination=TEST-TOPIC-testRestrictions-cibuild01, replyTo=TEST-TOPIC-Pillar-testRestrictions-cibuild01-contributor, from=Pillar-testRestrictions, to=testRestrictions, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@7dda1470[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to calculate checksums.], pillarID=Pillar-testRestrictions, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@28e04625[fileID=<null>(default), allFileIDs=true], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@130a38c5[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultAddress=<null>(default)]
          Result: Received message on TEST-TOPIC-testRestrictions-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@256f298e[correlationID=2460c632-a0e7-4e0e-ac2d-47f843bb03b3, collectionID=TwoPillarCollection, destination=TEST-TOPIC-testRestrictions-cibuild01, replyTo=TEST-TOPIC-Pillar-testRestrictions-cibuild01-contributor, from=Pillar-testRestrictions, to=testRestrictions, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@8bbd0c7[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], pillarID=Pillar-testRestrictions, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@130a38c5[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultingChecksums=org.bitrepository.bitrepositoryelements.ResultingChecksums@22406e9b[resultAddress=<null>(default), checksumDataItems={org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@60ceb606[fileID=DefaultFile, checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2017-02-18T15:23:15.510+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 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.
15:23:15.781 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@3447daf1[correlationID=1df843a6-079d-493d-be88-bcfeb9d89487, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseIdentification-cibuild01-contributor, from=Pillar-badCaseIdentification, to=badCaseIdentification, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@4134db1e[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseIdentification, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@6b0e9e[fileID=DefaultFilebadCaseIdentification, allFileIDs=<null>(default)], timeToDeliver=<null>(default)]
        Step: Retrieve and validate the response getPillarID() the pillar.
      Test success: badCaseIdentification
        Added fixture: Initialize a new Pillar.
      Test starting: badCaseOperationNoFile
        Description: Tests the GetFileIDs functionality of the pillar for the failure scenario, where it does not have the file.
        Step: Set up constants and variables.
        Step: Setup for not having the file
        Step: Create and send the actual GetFileIDs message to the pillar.
15:23:17.000 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@27294098[correlationID=f0b11497-9803-4a4d-bea0-bc5bc730c08b, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@e35d91b[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@78a9991a[fileID=DefaultFilebadCaseOperationNoFile, allFileIDs=<null>(default)], resultingFileIDs=<null>(default), partialResult=<null>(default)]
15:23:17.019 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@edc900a[correlationID=f0b11497-9803-4a4d-bea0-bc5bc730c08b, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@3a09b982[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@78a9991a[fileID=DefaultFilebadCaseOperationNoFile, allFileIDs=<null>(default)], resultingFileIDs=<null>(default), partialResult=<null>(default)]
15:23:17.021 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@528a7eea[correlationID=f0b11497-9803-4a4d-bea0-bc5bc730c08b, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@383ce871[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@78a9991a[fileID=DefaultFilebadCaseOperationNoFile, allFileIDs=<null>(default)], resultingFileIDs=<null>(default), partialResult=<null>(default)]
        Step: Retrieve the FinalResponse for the GetFileIDs request
      Test success: badCaseOperationNoFile
          Result: The following messages haven't been handled by the testcase: 
org.bitrepository.bitrepositorymessages.GetFileIDsFinalResponse@edc900a[correlationID=f0b11497-9803-4a4d-bea0-bc5bc730c08b, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@3a09b982[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@78a9991a[fileID=DefaultFilebadCaseOperationNoFile, allFileIDs=<null>(default)], resultingFileIDs=<null>(default), partialResult=<null>(default)]
org.bitrepository.bitrepositorymessages.GetFileIDsFinalResponse@528a7eea[correlationID=f0b11497-9803-4a4d-bea0-bc5bc730c08b, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@383ce871[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@78a9991a[fileID=DefaultFilebadCaseOperationNoFile, allFileIDs=<null>(default)], resultingFileIDs=<null>(default), partialResult=<null>(default)]
15:23:18.056 WARN  o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: 
org.bitrepository.bitrepositorymessages.GetFileIDsFinalResponse@edc900a[correlationID=f0b11497-9803-4a4d-bea0-bc5bc730c08b, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@3a09b982[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@78a9991a[fileID=DefaultFilebadCaseOperationNoFile, allFileIDs=<null>(default)], resultingFileIDs=<null>(default), partialResult=<null>(default)]
org.bitrepository.bitrepositorymessages.GetFileIDsFinalResponse@528a7eea[correlationID=f0b11497-9803-4a4d-bea0-bc5bc730c08b, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@383ce871[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@78a9991a[fileID=DefaultFilebadCaseOperationNoFile, allFileIDs=<null>(default)], resultingFileIDs=<null>(default), partialResult=<null>(default)]
        Added fixture: Initialize a new Pillar.
      Test starting: goodCaseIdentification
        Description: Tests the identification for a GetFileIDs operation on the pillar for the successful scenario.
        Step: Set up constants and variables.
        Step: Setup for having the file and delivering pillar id
        Step: Create and send the identify request message.
          Result: Received message on TEST-TOPIC-goodCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsResponse@8d70fd[correlationID=8b73f1ec-cec9-464c-81c8-e22d44938089, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseIdentification-cibuild01-contributor, from=Pillar-goodCaseIdentification, to=goodCaseIdentification, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@7db8560[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], pillarID=Pillar-goodCaseIdentification, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@280b0df9[fileID=DefaultFilegoodCaseIdentification, allFileIDs=<null>(default)], timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@3f75a353[timeMeasureUnit=MILLISECONDS, timeMeasureValue=1000]]
        Step: Retrieve and validate the response getPillarID() the pillar.
      Test success: goodCaseIdentification
    Starting testcase MediatorTest
      Test starting: testMediatorRuntimeExceptionHandling
        Description: Tests the handling of a runtime exception
        Step: Setup create and start the mediator.
        Step: Send a request to the mediator.
15:23:20.789 WARN  o.b.pillar.MediatorTest$TestMediator - Unexpected exception caught.
java.lang.RuntimeException: I am supposed to throw a RuntimeException
	at org.bitrepository.pillar.MediatorTest$ErroneousRequestHandler.processRequest(MediatorTest.java:122)
	at org.bitrepository.pillar.MediatorTest$ErroneousRequestHandler.processRequest(MediatorTest.java:113)
	at org.bitrepository.pillar.messagehandler.PillarMediator.handleRequest(PillarMediator.java:80)
	at org.bitrepository.service.contributor.AbstractContributorMediator$GeneralRequestHandler.onMessage(AbstractContributorMediator.java:101)
	at org.bitrepository.protocol.messagebus.SimpleMessageBus.lambda$sendMessage$2(SimpleMessageBus.java:73)
	at org.bitrepository.protocol.messagebus.SimpleMessageBus$$Lambda$1/912404637.accept(Unknown Source)
	at java.lang.Iterable.forEach(Iterable.java:75)
	at org.bitrepository.protocol.messagebus.SimpleMessageBus.sendMessage(SimpleMessageBus.java:73)
	at org.bitrepository.pillar.MediatorTest.testMediatorRuntimeExceptionHandling(MediatorTest.java:84)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:483)
	at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:86)
	at org.testng.internal.Invoker.invokeMethod(Invoker.java:643)
	at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:820)
	at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1128)
	at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:129)
	at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:112)
	at org.testng.TestRunner.privateRun(TestRunner.java:782)
	at org.testng.TestRunner.run(TestRunner.java:632)
	at org.testng.SuiteRunner.runTest(SuiteRunner.java:366)
	at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:361)
	at org.testng.SuiteRunner.privateRun(SuiteRunner.java:319)
	at org.testng.SuiteRunner.run(SuiteRunner.java:268)
	at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
	at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
	at org.testng.TestNG.runSuitesSequentially(TestNG.java:1244)
	at org.testng.TestNG.runSuitesLocally(TestNG.java:1169)
	at org.testng.TestNG.run(TestNG.java:1064)
	at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:115)
	at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:204)
	at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:107)
	at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:112)
	at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
          Result: Received message on TEST-TOPIC-testMediatorRuntimeExceptionHandling-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetStatusResponse@4a9cd434[correlationID=08ec778d-ea32-48b5-b428-28b665ab8b1e, collectionID=TwoPillarCollection, destination=TEST-TOPIC-testMediatorRuntimeExceptionHandling-cibuild01, replyTo=TEST-TOPIC-MediatorUnderTest-cibuild01-contributor, from=MediatorUnderTest, to=MediatorUnderTest, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@48c865c1[responseCode=FAILURE, responseText=java.lang.RuntimeException: I am supposed to throw a RuntimeException], contributor=TEST-TOPIC-cibuild01, timeToDeliver=<null>(default)]
15:23:20.791 WARN  o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@63157033[origDateTime=2017-02-18T15:23:20.791+01:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MediatorUnderTest, alarmText=java.lang.RuntimeException: I am supposed to throw a RuntimeException, fileID=<null>(default), collectionID=<null>(default)]
          Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@4f843511[correlationID=1194b7d6-4bb6-463d-b017-8221d5214f59, collectionID=<null>(default), destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-MediatorUnderTest-cibuild01-contributor, from=MediatorUnderTest, to=<null>(default), version=30, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@63157033[origDateTime=2017-02-18T15:23:20.791+01:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MediatorUnderTest, alarmText=java.lang.RuntimeException: I am supposed to throw a RuntimeException, fileID=<null>(default), collectionID=<null>(default)]]
      Test success: testMediatorRuntimeExceptionHandling
    Starting testcase ChecksumDatabaseTest
      Test starting: testChecksumDatabaseExtraction
        Description: Test the extraction of data from the checksum database.
        Step: Check whether the default entry exists.
        Step: Extract calculation date
        Step: Extract the checksum
        Step: Extract the whole entry
        Step: Extract all entries
      Test success: testChecksumDatabaseExtraction
      Test starting: testDeletion
        Description: Test that data can be deleted from the database.
        Step: Check whether the default entry exists.
        Step: Remove the default entry
      Test success: testDeletion
      Test starting: testExtractionOfMissingData
        Description: Test the handling of bad arguments.
        Step: Try to get the date of a wrong file id.
        Step: Try to get the date of a wrong file id.
        Step: Try to remove a bad file id
      Test success: testExtractionOfMissingData
      Test starting: testGetChecksumResult
        Description: Tests the restrictions on the GetChecksumResult call to the database.
        Step: Instantiate database with appropriate data.
        Step: Test with no time restrictions
        Step: Test with time restrictions from epoc to now
        Step: Test with very strict time restrictions around the default date
        Step: Test with too new a lower limit
        Step: Test with exact date as both upper and lower limit
        Step: Test with date limit from 1 millis before as lower and exact date a upper limit
        Step: Test with date limit from exact date as lower and 1 millis after date a upper limit
        Step: Test with too old an upper limit
      Test success: testGetChecksumResult
      Test starting: testGetFileIDsRestrictions
        Description: Tests the restrictions on the GetFileIDs call to the database.
        Step: Instantiate database with appropriate data.
        Step: Test with no time restrictions and 10000 max_results
        Step: Test with minimum-date earlier than first file
        Step: Test with maximum-date earlier than first file
        Step: Test with minimum-date set to later than second file.
        Step: Test with maximum-date set to later than second file.
        Step: Test with minimum-date set to middle date.
        Step: Test with maximum-date set to middle date.
        Step: Test with both minimum-date and maximum-date set to middle date.
        Step: Test the first file-id, with no other restrictions
        Step: Test the second file-id, with no other restrictions
        Step: Test the date for the first file-id, while requesting the second file-id
      Test success: testGetFileIDsRestrictions
      Test starting: testGetFileIDsWithOldChecksums
        Description: Tests the restrictions on the GetFileIDsWithOldChecksums call to the database.
        Step: Instantiate database with appropriate data.
        Step: Extract all entries with checksum date older than now
        Step: Extract all entries with checksum date older than epoch
        Step: Extract all entries with checksum date older than middle date
      Test success: testGetFileIDsWithOldChecksums
      Test starting: testReplacingExistingEntry
        Description: Test that an entry can be replaced by another in the database.
        Step: Check whether the default entry exists.
        Step: Replace the checksum and date
      Test success: testReplacingExistingEntry
      Test starting: testSpecifiedEntryExtraction
        Description: Test that specific entries can be extracted. Has two entries in the database: one for the current timestamp and one for the epoch.
        Step: Instantiate database with appropriate data.
        Step: Extract with out restrictions
        Step: Extract with a maximum of 1 entry
        Step: Extract all dates older than this tests instantiation
        Step: Extract all dates newer than this tests instantiation
        Step: Extract all dates older than the newest instance
        Step: Extract all dates newer than the oldest instantiation
      Test success: testSpecifiedEntryExtraction
      Test starting: componentIDTest
      Test success: componentIDTest
    Starting testcase RecalculateChecksumWorkflowTest
        Added fixture: Initialize the Reference pillar cache with an empty file in default collection TwoPillarCollection
      Test starting: testWorkflowDoesNotRecalculateWhenNotNeeded
        Description: Test that the workflow does not recalculates the workflows, when the maximum age has not yet been met.
        Step: Create and run workflow
      Test success: testWorkflowDoesNotRecalculateWhenNotNeeded
        Added fixture: Initialize the Reference pillar cache with an empty file in default collection TwoPillarCollection
      Test starting: testWorkflowRecalculatesChecksum
        Description: Test that the workflow recalculates the workflows, when the maximum age has been met.
        Step: Create and run workflow
      Test success: testWorkflowRecalculatesChecksum
    Starting testcase 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 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@48cec56d[correlationID=8145c3a6-a452-4d03-bed2-5962e71e47ac, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseIdentification-cibuild01-contributor, from=Pillar-badCaseIdentification, to=badCaseIdentification, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@50de5919[responseCode=FILE_NOT_FOUND_FAILURE, responseText=Could not find the requested file to delete.], fileID=DefaultFile, pillarID=Pillar-badCaseIdentification, pillarChecksumSpec=<null>(default), timeToDeliver=<null>(default)]
        Step: Retrieve and validate the response getPillarID() the pillar.
      Test success: badCaseIdentification
        Added fixture: Initialize a new Pillar.
      Test starting: badCaseOperationMissingFile
        Description: Tests the ReplaceFile operation on the pillar for the failure scenario, when the file is missing.
        Step: Set up constants and variables.
        Step: Setup for not having the file and delivering pillar id
        Step: Create and send the identify request message.
          Result: Received message on TEST-TOPIC-badCaseOperationMissingFile-cibuild01 : org.bitrepository.bitrepositorymessages.ReplaceFileFinalResponse@95ad3af[correlationID=e8a7229f-97c4-459b-ac30-61dd51275509, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationMissingFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationMissingFile-cibuild01-contributor, from=Pillar-badCaseOperationMissingFile, to=badCaseOperationMissingFile, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@b6d99bc[responseCode=FILE_NOT_FOUND_FAILURE, responseText=The file 'DefaultFile' has been requested, but we do not have that file!], pillarID=Pillar-badCaseOperationMissingFile, pillarChecksumSpec=<null>(default), fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForExistingFile=<null>(default), checksumDataForNewFile=<null>(default)]
        Step: Retrieve the FinalResponse for the ReplaceFile request
      Test success: badCaseOperationMissingFile
        Added fixture: Initialize a new Pillar.
      Test starting: badCaseOperationNoDestructiveChecksum
        Description: Tests the ReplaceFile operation on the pillar for the failure scenario, when no validation checksum is given for the destructive action, but though is required.
        Step: Set up constants and variables.
        Step: Setup for having the file and delivering pillar id
        Step: Create and send the identify request message.
          Result: Received message on TEST-TOPIC-badCaseOperationNoDestructiveChecksum-cibuild01 : org.bitrepository.bitrepositorymessages.ReplaceFileFinalResponse@3a8be13b[correlationID=5af57736-9b35-4a97-b00e-0921f6f58be3, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoDestructiveChecksum-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoDestructiveChecksum-cibuild01-contributor, from=Pillar-badCaseOperationNoDestructiveChecksum, to=badCaseOperationNoDestructiveChecksum, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@20aef53a[responseCode=EXISTING_FILE_CHECKSUM_FAILURE, responseText=According to the contract a checksum for file to be deleted during the replacing operation is required.], pillarID=Pillar-badCaseOperationNoDestructiveChecksum, pillarChecksumSpec=<null>(default), fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForExistingFile=<null>(default), checksumDataForNewFile=<null>(default)]
15:23:39.118 WARN  o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@68cebde1[origDateTime=2017-02-18T15:23:39.118+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@2a76a05b[correlationID=8949f2c9-af8f-4779-8c67-de696da71f09, collectionID=TwoPillarCollection, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoDestructiveChecksum-cibuild01-contributor, from=Pillar-badCaseOperationNoDestructiveChecksum, to=<null>(default), version=30, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@68cebde1[origDateTime=2017-02-18T15:23:39.118+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@9086215[correlationID=b7424d97-eaae-4492-9def-b5dc17faa541, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoValidationChecksum-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoValidationChecksum-cibuild01-contributor, from=Pillar-badCaseOperationNoValidationChecksum, to=badCaseOperationNoValidationChecksum, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@6511ed25[responseCode=NEW_FILE_CHECKSUM_FAILURE, responseText=According to the contract a checksum for new file in the replacing operation is required.], pillarID=Pillar-badCaseOperationNoValidationChecksum, pillarChecksumSpec=<null>(default), fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForExistingFile=<null>(default), checksumDataForNewFile=<null>(default)]
15:23:39.389 WARN  o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@7cd92d04[origDateTime=2017-02-18T15:23:39.389+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@10089762[correlationID=e88841fb-3827-4b1d-83d2-e088a3af8048, collectionID=TwoPillarCollection, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoValidationChecksum-cibuild01-contributor, from=Pillar-badCaseOperationNoValidationChecksum, to=<null>(default), version=30, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@7cd92d04[origDateTime=2017-02-18T15:23:39.389+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.
15:23:39.541 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@17d428b0[correlationID=e920f968-e5c4-44a6-9df9-465582108db0, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationWrongDestructiveChecksum-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationWrongDestructiveChecksum-cibuild01-contributor, from=Pillar-badCaseOperationWrongDestructiveChecksum, to=badCaseOperationWrongDestructiveChecksum, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@2f568a26[responseCode=EXISTING_FILE_CHECKSUM_FAILURE, responseText=Requested to replace the file 'DefaultFile' with checksum '1234cccccccc4321', but our file had a different checksum.], pillarID=Pillar-badCaseOperationWrongDestructiveChecksum, pillarChecksumSpec=<null>(default), fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForExistingFile=<null>(default), checksumDataForNewFile=<null>(default)]
15:23:39.543 WARN  o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@1ed575e9[origDateTime=2017-02-18T15:23:39.543+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@16210825[correlationID=5b0faacb-647d-4358-8482-b801ce66d805, collectionID=TwoPillarCollection, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationWrongDestructiveChecksum-cibuild01-contributor, from=Pillar-badCaseOperationWrongDestructiveChecksum, to=<null>(default), version=30, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@1ed575e9[origDateTime=2017-02-18T15:23:39.543+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@7af92277[correlationID=4387e862-371e-4713-b14c-973e9ea9c441, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseIdentification-cibuild01-contributor, from=Pillar-goodCaseIdentification, to=goodCaseIdentification, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@75751baf[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], fileID=DefaultFile, pillarID=Pillar-goodCaseIdentification, pillarChecksumSpec=<null>(default), timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@505014a7[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@53d5e209[correlationID=8d8b1dec-61cf-4f38-ab47-11a3dd5d29e7, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperation-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperation-cibuild01-contributor, from=Pillar-goodCaseOperation, to=goodCaseOperation, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@4b7bbcd5[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Performing the ReplaceFileRequest for file 'DefaultFile' at 'TwoPillarCollection'.], pillarID=Pillar-goodCaseOperation, pillarChecksumSpec=<null>(default), fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt]
          Result: Received message on TEST-TOPIC-goodCaseOperation-cibuild01 : org.bitrepository.bitrepositorymessages.ReplaceFileFinalResponse@6d362079[correlationID=8d8b1dec-61cf-4f38-ab47-11a3dd5d29e7, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperation-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperation-cibuild01-contributor, from=Pillar-goodCaseOperation, to=goodCaseOperation, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@118f427c[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], pillarID=Pillar-goodCaseOperation, pillarChecksumSpec=<null>(default), fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForExistingFile=<null>(default), checksumDataForNewFile=<null>(default)]
        Step: Retrieve the ProgressResponse for the GetFileIDs request
        Step: Retrieve the FinalResponse for the ReplaceFile request
      Test success: goodCaseOperation
        Added fixture: Initialize a new Pillar.
      Test starting: goodCaseOperationWithChecksumsReturn
        Description: Tests the ReplaceFile operation on the pillar for the success scenario, when requesting both the cheksums of the file returned.
        Step: Set up constants and variables.
        Step: Setup for already having the file and delivering pillar id
        Step: Create and send the identify request message.
          Result: Received message on TEST-TOPIC-goodCaseOperationWithChecksumsReturn-cibuild01 : org.bitrepository.bitrepositorymessages.ReplaceFileProgressResponse@28019d67[correlationID=39777f66-f9ed-40b5-a214-b7f9a98eb494, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationWithChecksumsReturn-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationWithChecksumsReturn-cibuild01-contributor, from=Pillar-goodCaseOperationWithChecksumsReturn, to=goodCaseOperationWithChecksumsReturn, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@2e191007[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Performing the ReplaceFileRequest for file 'DefaultFile' at 'TwoPillarCollection'.], pillarID=Pillar-goodCaseOperationWithChecksumsReturn, pillarChecksumSpec=<null>(default), fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt]
          Result: Received message on TEST-TOPIC-goodCaseOperationWithChecksumsReturn-cibuild01 : org.bitrepository.bitrepositorymessages.ReplaceFileFinalResponse@7e6a2cb5[correlationID=39777f66-f9ed-40b5-a214-b7f9a98eb494, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationWithChecksumsReturn-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationWithChecksumsReturn-cibuild01-contributor, from=Pillar-goodCaseOperationWithChecksumsReturn, to=goodCaseOperationWithChecksumsReturn, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@79016b60[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], pillarID=Pillar-goodCaseOperationWithChecksumsReturn, pillarChecksumSpec=<null>(default), fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@5d4f3b82[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@3b308104[checksumType=HMAC_SHA512, checksumSalt={97,98}, otherChecksumType=<null>(default)], checksumValue={18,52,-52,-52,-52,-52,67,34}, calculationTimestamp=2017-02-18T15:23:42.043+01:00], checksumDataForNewFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@14101d53[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@66b83eda[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2017-02-18T15:23:42.044+01:00]]
        Step: Retrieve the ProgressResponse for the GetFileIDs request
        Step: Retrieve the FinalResponse for the ReplaceFile request
      Test success: goodCaseOperationWithChecksumsReturn
    Starting testcase GetFileTest
        Added fixture: Initialize a new Pillar.
      Test starting: badCaseIdentification
        Description: Tests the identification for a GetFile operation on the checksum pillar for the failure scenario, when the file is missing.
        Step: Set up constants and variables.
        Step: Setup for throwing an exception when asked to verify file existence
        Step: Create and send the identify request message.
          Result: Received message on TEST-TOPIC-badCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileResponse@684e436b[correlationID=e73b711d-73c5-4c5a-9435-bdb367ff6efb, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseIdentification-cibuild01-contributor, from=Pillar-badCaseIdentification, to=badCaseIdentification, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@277c87e5[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], fileID=DefaultFilebadCaseIdentification, pillarID=Pillar-badCaseIdentification, timeToDeliver=<null>(default)]
        Step: Retrieve and validate the response getPillarID() the pillar.
      Test success: badCaseIdentification
        Added fixture: Initialize a new Pillar.
      Test starting: goodCaseIdentification
        Description: Tests the identification for a GetFile operation on the pillar for the successful scenario.
        Step: Set up constants and variables.
        Step: Setup for having the file and delivering pillar id
        Step: Create and send the identify request message.
          Result: Received message on TEST-TOPIC-goodCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileResponse@422b1292[correlationID=03735212-d5f5-4242-8219-ddd69bbfbbad, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseIdentification-cibuild01-contributor, from=Pillar-goodCaseIdentification, to=goodCaseIdentification, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@60135b59[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], fileID=DefaultFilegoodCaseIdentification, pillarID=Pillar-goodCaseIdentification, timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@6c9696c5[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.
15:23:46.483 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
      Finished testcase
  Finished suite
Finished project
Tests run: 64, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 63.182 sec - in TestSuite

Results :

Tests run: 64, Failures: 0, Errors: 0, Skipped: 0

[JENKINS] Recording test results
[INFO] 
[INFO] --- jacoco-maven-plugin:0.7.5.201505241946:report (report) @ bitrepository-reference-pillar ---
[INFO] Analyzed bundle 'Bitrepository Reference Pillar' with 43 classes
[INFO] 
[INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ bitrepository-reference-pillar ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.9-SNAPSHOT.jar
[INFO] 
[INFO] --- maven-jar-plugin:2.4:test-jar (default) @ bitrepository-reference-pillar ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.9-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-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.9-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] Downloading: https://sbforge.org/nexus/content/groups/public/org/bitrepository/reference/bitrepository-client/1.9-SNAPSHOT/bitrepository-client-1.9-20170218.141808-7.pom
[INFO] Downloaded: https://sbforge.org/nexus/content/groups/public/org/bitrepository/reference/bitrepository-client/1.9-SNAPSHOT/bitrepository-client-1.9-20170218.141808-7.pom (2 KB at 48.8 KB/sec)
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.9-SNAPSHOT-distribution.tar.gz
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.9-SNAPSHOT-acceptance-test.tar.gz
[WARNING] Entry: bitrepository-reference-pillar-1.9-SNAPSHOT/lib/bitrepository-reference-pillar-1.9-SNAPSHOT-tests.jar longer than 100 characters.
[WARNING] Resulting tar file can only be processed successfully by GNU compatible tar commands
[WARNING] Entry: bitrepository-reference-pillar-1.9-SNAPSHOT/lib/bitrepository-client-1.9-20170218.141808-7-tests.jar longer than 100 characters.
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.9-SNAPSHOT-deploy.tar.gz
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.9-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-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.9-SNAPSHOT.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/bitrepository-reference-pillar-1.9-SNAPSHOT.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/bitrepository-reference-pillar-1.9-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.9-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/bitrepository-reference-pillar-1.9-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.9-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/bitrepository-reference-pillar-1.9-SNAPSHOT-sources.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.9-SNAPSHOT-distribution.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/bitrepository-reference-pillar-1.9-SNAPSHOT-distribution.tar.gz
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.9-SNAPSHOT-acceptance-test.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/bitrepository-reference-pillar-1.9-SNAPSHOT-acceptance-test.tar.gz
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.9-SNAPSHOT-deploy.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/bitrepository-reference-pillar-1.9-SNAPSHOT-deploy.tar.gz
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.9-SNAPSHOT-acceptance-test-deploy.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/bitrepository-reference-pillar-1.9-SNAPSHOT-acceptance-test-deploy.tar.gz
[INFO] 
[INFO] --- maven-deploy-plugin:2.8.1:deploy (default-deploy) @ bitrepository-reference-pillar ---
[INFO] Downloading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/maven-metadata.xml (3 KB at 68.7 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/bitrepository-reference-pillar-1.9-20170218.142352-7.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/bitrepository-reference-pillar-1.9-20170218.142352-7.jar (128 KB at 1766.7 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/bitrepository-reference-pillar-1.9-20170218.142352-7.pom
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/bitrepository-reference-pillar-1.9-20170218.142352-7.pom (8 KB at 316.6 KB/sec)
[INFO] Downloading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/maven-metadata.xml (455 B at 27.8 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/maven-metadata.xml (3 KB at 64.4 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/maven-metadata.xml (455 B at 13.1 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/bitrepository-reference-pillar-1.9-20170218.142352-7-tests.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/bitrepository-reference-pillar-1.9-20170218.142352-7-tests.jar (238 KB at 2304.4 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/maven-metadata.xml (3 KB at 76.3 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/bitrepository-reference-pillar-1.9-20170218.142352-7-sources.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/bitrepository-reference-pillar-1.9-20170218.142352-7-sources.jar (104 KB at 1723.9 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/maven-metadata.xml (3 KB at 73.6 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/bitrepository-reference-pillar-1.9-20170218.142352-7-distribution.tar.gz
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/bitrepository-reference-pillar-1.9-20170218.142352-7-distribution.tar.gz (13313 KB at 1833.2 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/maven-metadata.xml (3 KB at 79.3 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/bitrepository-reference-pillar-1.9-20170218.142352-7-acceptance-test.tar.gz
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/bitrepository-reference-pillar-1.9-20170218.142352-7-acceptance-test.tar.gz (12946 KB at 1506.7 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/maven-metadata.xml (3 KB at 85.9 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/bitrepository-reference-pillar-1.9-20170218.142352-7-deploy.tar.gz
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/bitrepository-reference-pillar-1.9-20170218.142352-7-deploy.tar.gz (4 KB at 140.4 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/maven-metadata.xml (3 KB at 82.4 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/bitrepository-reference-pillar-1.9-20170218.142352-7-acceptance-test-deploy.tar.gz
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/bitrepository-reference-pillar-1.9-20170218.142352-7-acceptance-test-deploy.tar.gz (4 KB at 125.5 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/maven-metadata.xml (3 KB at 71.1 KB/sec)
[JENKINS] Archiving disabled
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Monitoring Service 1.9-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-monitoring-service ---
[INFO] Deleting /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/target
[INFO] 
[INFO] --- jacoco-maven-plugin:0.7.5.201505241946:prepare-agent (default) @ bitrepository-monitoring-service ---
[INFO] argLine set to -javaagent:/home/cibuild01/.m2/repository/org/jacoco/org.jacoco.agent/0.7.5.201505241946/org.jacoco.agent-0.7.5.201505241946-runtime.jar=destfile=/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/target/jacoco.exec
[INFO] 
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ bitrepository-monitoring-service ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/src/main/resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ bitrepository-monitoring-service ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 14 source files to /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/target/classes
[INFO] 
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ bitrepository-monitoring-service ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/src/test/resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ bitrepository-monitoring-service ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 7 source files to /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/target/test-classes
[INFO] 
[INFO] --- maven-surefire-plugin:2.17:test (default-test) @ bitrepository-monitoring-service ---
[INFO] Surefire report directory: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/target/surefire-reports

-------------------------------------------------------
 T E S T S
-------------------------------------------------------
Running TestSuite
Configuring TestNG with: TestNG652Configurator
Starting test project Core module test
  Suite: Surefire suite
    Starting testcase StatusCollectorTest
      Test starting: testStatusCollector
        Description: Tests the status collector.
        Step: Setup
        Step: Create the collector
        Step: Start the collector
        Step: wait 2 * the interval
        Step: wait the interval + delay again
      Test success: testStatusCollector
    Starting testcase StatusEventHandlerTest
      Test starting: testStatusEventHandler
        Description: Test the GetStatusEventHandler handling of events
        Step: Setup
        Step: Validate initial calls to the mocks
        Step: Test an unhandled event.
        Step: Test the Complete event
        Step: Test the Failed event
        Step: Test the component complete status
      Test success: testStatusEventHandler
    Starting testcase ComponentStatusStoreTest
      Test starting: testComponentStatus
        Description: Tests the compontent status
        Step: Setup
        Step: Validate the initial content
        Step: Update the replay counts and validate 
        Step: Test what happens when an invalid component id attempted to be updated.
15:24:18.335 WARN  o.b.m.status.ComponentStatusStore - Got status from an unexpected component: BAD-COMPONENT-ID
        Step: Try giving it a positive status
      Test success: testComponentStatus
    Starting testcase MonitorAlerterTest
      Test starting: testMonitorAlerter
        Description: Tests the org.bitrepository.monitoringservice.alarm.BasicMonitoringServiceAlerter
        Step: Setup
        Step: Create the alerter, but ignore the part of actually sending the alarms. Just log it.
        Step: Check statuses with an empty map.
        Step: Check the status when a positive entry exists.
        Step: Check the status when a negative entry exists.
15:24:20.807 WARN  o.b.m.a.BasicMonitoringServiceAlerter - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@7bb4ed71[origDateTime=2017-02-18T15:24:20.766+01:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MonitorAlerterUnderTest, alarmText=The following components have become unresponsive: [TestMonitorService], fileID=<null>(default), collectionID=<null>(default)]
          Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@6cd45b6c[correlationID=41db66d3-0f57-4293-9780-16219e8202e8, collectionID=<null>(default), destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-MonitorAlerterUnderTest-cibuild01-contributor, from=MonitorAlerterUnderTest, to=<null>(default), version=30, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@7bb4ed71[origDateTime=2017-02-18T15:24:20.766+01:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MonitorAlerterUnderTest, alarmText=The following components have become unresponsive: [TestMonitorService], fileID=<null>(default), collectionID=<null>(default)]]
      Test success: testMonitorAlerter
      Finished testcase
  Finished suite
Finished project
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 9.087 sec - in TestSuite

Results :

Tests run: 4, Failures: 0, Errors: 0, Skipped: 0

[JENKINS] Recording test results
[INFO] 
[INFO] --- jacoco-maven-plugin:0.7.5.201505241946:report (report) @ bitrepository-monitoring-service ---
[INFO] Analyzed bundle 'Bitrepository Monitoring Service' with 14 classes
[INFO] 
[INFO] --- maven-war-plugin:2.4:war (default-war) @ bitrepository-monitoring-service ---
[INFO] Packaging webapp
[INFO] Assembling webapp [bitrepository-monitoring-service] in [/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.9-SNAPSHOT]
[INFO] Processing war project
[INFO] Copying webapp resources [/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/src/main/webapp]
[INFO] Webapp assembled in [78 msecs]
[INFO] Building war: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.9-SNAPSHOT.war
[INFO] 
[INFO] --- maven-jar-plugin:2.4:test-jar (default) @ bitrepository-monitoring-service ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.9-SNAPSHOT-tests.jar
[INFO] 
[INFO] --- maven-source-plugin:2.2.1:jar-no-fork (attach-sources-no-fork) @ bitrepository-monitoring-service ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.9-SNAPSHOT-sources.jar
[INFO] 
[INFO] --- maven-assembly-plugin:2.4:single (distribution) @ bitrepository-monitoring-service ---
[INFO] Reading assembly descriptor: src/main/assembly/assembly.xml
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.9-SNAPSHOT-distribution.tar.gz
[INFO] 
[INFO] --- maven-install-plugin:2.5.1:install (default-install) @ bitrepository-monitoring-service ---
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.9-SNAPSHOT.war to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-monitoring-service/1.9-SNAPSHOT/bitrepository-monitoring-service-1.9-SNAPSHOT.war
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-monitoring-service/1.9-SNAPSHOT/bitrepository-monitoring-service-1.9-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.9-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-monitoring-service/1.9-SNAPSHOT/bitrepository-monitoring-service-1.9-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.9-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-monitoring-service/1.9-SNAPSHOT/bitrepository-monitoring-service-1.9-SNAPSHOT-sources.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.9-SNAPSHOT-distribution.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-monitoring-service/1.9-SNAPSHOT/bitrepository-monitoring-service-1.9-SNAPSHOT-distribution.tar.gz
[INFO] 
[INFO] --- maven-deploy-plugin:2.8.1:deploy (default-deploy) @ bitrepository-monitoring-service ---
[INFO] Downloading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.9-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.9-SNAPSHOT/maven-metadata.xml (2 KB at 22.8 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.9-SNAPSHOT/bitrepository-monitoring-service-1.9-20170218.142424-7.war
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.9-SNAPSHOT/bitrepository-monitoring-service-1.9-20170218.142424-7.war (18062 KB at 3087.4 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.9-SNAPSHOT/bitrepository-monitoring-service-1.9-20170218.142424-7.pom
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.9-SNAPSHOT/bitrepository-monitoring-service-1.9-20170218.142424-7.pom (4 KB at 121.7 KB/sec)
[INFO] Downloading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/maven-metadata.xml (457 B at 7.8 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.9-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.9-SNAPSHOT/maven-metadata.xml (2 KB at 47.0 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/maven-metadata.xml (457 B at 12.1 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.9-SNAPSHOT/bitrepository-monitoring-service-1.9-20170218.142424-7-tests.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.9-SNAPSHOT/bitrepository-monitoring-service-1.9-20170218.142424-7-tests.jar (15 KB at 383.4 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.9-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.9-SNAPSHOT/maven-metadata.xml (2 KB at 32.1 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.9-SNAPSHOT/bitrepository-monitoring-service-1.9-20170218.142424-7-sources.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.9-SNAPSHOT/bitrepository-monitoring-service-1.9-20170218.142424-7-sources.jar (19 KB at 279.3 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.9-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.9-SNAPSHOT/maven-metadata.xml (2 KB at 9.9 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.9-SNAPSHOT/bitrepository-monitoring-service-1.9-20170218.142424-7-distribution.tar.gz
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.9-SNAPSHOT/bitrepository-monitoring-service-1.9-20170218.142424-7-distribution.tar.gz (18060 KB at 3073.4 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.9-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.9-SNAPSHOT/maven-metadata.xml (2 KB at 29.4 KB/sec)
[JENKINS] Archiving disabled
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Webclient 1.9-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-webclient ---
[INFO] Deleting /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/target
[INFO] 
[INFO] --- jacoco-maven-plugin:0.7.5.201505241946:prepare-agent (default) @ bitrepository-webclient ---
[INFO] argLine set to -javaagent:/home/cibuild01/.m2/repository/org/jacoco/org.jacoco.agent/0.7.5.201505241946/org.jacoco.agent-0.7.5.201505241946-runtime.jar=destfile=/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/target/jacoco.exec
[INFO] 
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ bitrepository-webclient ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ bitrepository-webclient ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 12 source files to /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/target/classes
[INFO] 
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ bitrepository-webclient ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/src/test/resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ bitrepository-webclient ---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-surefire-plugin:2.17:test (default-test) @ bitrepository-webclient ---
[INFO] No tests to run.
[JENKINS] Recording test results[INFO] 
[INFO] --- jacoco-maven-plugin:0.7.5.201505241946:report (report) @ bitrepository-webclient ---

[INFO] Skipping JaCoCo execution due to missing execution data file:/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/target/jacoco.exec
[INFO] 
[INFO] --- maven-war-plugin:2.4:war (default-war) @ bitrepository-webclient ---
[INFO] Packaging webapp
[INFO] Assembling webapp [bitrepository-webclient] in [/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/target/bitrepository-webclient-1.9-SNAPSHOT]
[INFO] Processing war project
[INFO] Copying webapp webResources [/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/src/main/webapp] to [/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/target/bitrepository-webclient-1.9-SNAPSHOT]
[INFO] Copying webapp resources [/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/src/main/webapp]
[INFO] Webapp assembled in [481 msecs]
[INFO] Building war: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/target/bitrepository-webclient-1.9-SNAPSHOT.war
[INFO] 
[INFO] --- maven-jar-plugin:2.4:test-jar (default) @ bitrepository-webclient ---
[WARNING] JAR will be empty - no content was marked for inclusion!
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/target/bitrepository-webclient-1.9-SNAPSHOT-tests.jar
[INFO] 
[INFO] --- maven-source-plugin:2.2.1:jar-no-fork (attach-sources-no-fork) @ bitrepository-webclient ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/target/bitrepository-webclient-1.9-SNAPSHOT-sources.jar
[INFO] 
[INFO] --- maven-assembly-plugin:2.4:single (distribution) @ bitrepository-webclient ---
[INFO] Reading assembly descriptor: src/main/assembly/assembly.xml
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/target/bitrepository-webclient-1.9-SNAPSHOT-distribution.tar.gz
[INFO] 
[INFO] --- maven-install-plugin:2.5.1:install (default-install) @ bitrepository-webclient ---
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/target/bitrepository-webclient-1.9-SNAPSHOT.war to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-webclient/1.9-SNAPSHOT/bitrepository-webclient-1.9-SNAPSHOT.war
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-webclient/1.9-SNAPSHOT/bitrepository-webclient-1.9-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/target/bitrepository-webclient-1.9-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-webclient/1.9-SNAPSHOT/bitrepository-webclient-1.9-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/target/bitrepository-webclient-1.9-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-webclient/1.9-SNAPSHOT/bitrepository-webclient-1.9-SNAPSHOT-sources.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/target/bitrepository-webclient-1.9-SNAPSHOT-distribution.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-webclient/1.9-SNAPSHOT/bitrepository-webclient-1.9-SNAPSHOT-distribution.tar.gz
[INFO] 
[INFO] --- maven-deploy-plugin:2.8.1:deploy (default-deploy) @ bitrepository-webclient ---
[INFO] Downloading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.9-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.9-SNAPSHOT/maven-metadata.xml (2 KB at 42.5 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.9-SNAPSHOT/bitrepository-webclient-1.9-20170218.142440-7.war
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.9-SNAPSHOT/bitrepository-webclient-1.9-20170218.142440-7.war (12467 KB at 3060.0 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.9-SNAPSHOT/bitrepository-webclient-1.9-20170218.142440-7.pom
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.9-SNAPSHOT/bitrepository-webclient-1.9-20170218.142440-7.pom (3 KB at 33.7 KB/sec)
[INFO] Downloading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/maven-metadata.xml (448 B at 31.2 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.9-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.9-SNAPSHOT/maven-metadata.xml (2 KB at 50.1 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/maven-metadata.xml (448 B at 16.8 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.9-SNAPSHOT/bitrepository-webclient-1.9-20170218.142440-7-tests.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.9-SNAPSHOT/bitrepository-webclient-1.9-20170218.142440-7-tests.jar (3 KB at 13.1 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.9-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.9-SNAPSHOT/maven-metadata.xml (2 KB at 45.2 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.9-SNAPSHOT/bitrepository-webclient-1.9-20170218.142440-7-sources.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.9-SNAPSHOT/bitrepository-webclient-1.9-20170218.142440-7-sources.jar (17 KB at 246.2 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.9-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.9-SNAPSHOT/maven-metadata.xml (2 KB at 34.2 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.9-SNAPSHOT/bitrepository-webclient-1.9-20170218.142440-7-distribution.tar.gz
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.9-SNAPSHOT/bitrepository-webclient-1.9-20170218.142440-7-distribution.tar.gz (12462 KB at 2787.8 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.9-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.9-SNAPSHOT/maven-metadata.xml (2 KB at 58.4 KB/sec)
[JENKINS] Archiving disabled
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Integration 1.9-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] Downloading: https://sbforge.org/nexus/content/groups/public/org/bitrepository/reference/bitrepository-client/1.9-SNAPSHOT/bitrepository-client-1.9-20170218.141808-7-distribution.tar.gz
[INFO] Downloaded: https://sbforge.org/nexus/content/groups/public/org/bitrepository/reference/bitrepository-client/1.9-SNAPSHOT/bitrepository-client-1.9-20170218.141808-7-distribution.tar.gz (7824 KB at 3049.9 KB/sec)
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-integration ---
[INFO] Deleting /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/target
[INFO] 
[INFO] --- jacoco-maven-plugin:0.7.5.201505241946:prepare-agent (default) @ bitrepository-integration ---
[INFO] argLine set to -javaagent:/home/cibuild01/.m2/repository/org/jacoco/org.jacoco.agent/0.7.5.201505241946/org.jacoco.agent-0.7.5.201505241946-runtime.jar=destfile=/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/target/jacoco.exec
[INFO] 
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ bitrepository-integration ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 33 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ bitrepository-integration ---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ bitrepository-integration ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ bitrepository-integration ---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-surefire-plugin:2.17:test (default-test) @ bitrepository-integration ---
[JENKINS] Recording test results[INFO] 
[INFO] --- jacoco-maven-plugin:0.7.5.201505241946:report (report) @ bitrepository-integration ---
[INFO] Skipping JaCoCo execution due to missing execution data file:/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/target/jacoco.exec

[INFO] 
[INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ bitrepository-integration ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/target/bitrepository-integration-1.9-SNAPSHOT.jar
[INFO] 
[INFO] --- maven-jar-plugin:2.4:test-jar (default) @ bitrepository-integration ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/target/bitrepository-integration-1.9-SNAPSHOT-tests.jar
[INFO] 
[INFO] --- maven-source-plugin:2.2.1:jar-no-fork (attach-sources-no-fork) @ bitrepository-integration ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/target/bitrepository-integration-1.9-SNAPSHOT-sources.jar
[INFO] 
[INFO] --- maven-assembly-plugin:2.4:single (make-assembly) @ bitrepository-integration ---
[INFO] Reading assembly descriptor: src/main/assembly/assembly.xml
[INFO] Reading assembly descriptor: src/main/assembly/tools-assembly.xml
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/target/bitrepository-integration-1.9-SNAPSHOT-quickstart.tar.gz
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/target/bitrepository-integration-1.9-SNAPSHOT-tools.tar.gz
[WARNING] Entry: bitrepository-integration-1.9-SNAPSHOT/lib/bitrepository-reference-pillar-1.9-SNAPSHOT-distribution.tar.gz longer than 100 characters.
[WARNING] Resulting tar file can only be processed successfully by GNU compatible tar commands
[WARNING] Entry: bitrepository-integration-1.9-SNAPSHOT/lib/bitrepository-client-1.9-20170218.141808-7-distribution.tar.gz longer than 100 characters.
[INFO] 
[INFO] --- maven-install-plugin:2.5.1:install (default-install) @ bitrepository-integration ---
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/target/bitrepository-integration-1.9-SNAPSHOT.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integration/1.9-SNAPSHOT/bitrepository-integration-1.9-SNAPSHOT.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integration/1.9-SNAPSHOT/bitrepository-integration-1.9-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/target/bitrepository-integration-1.9-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integration/1.9-SNAPSHOT/bitrepository-integration-1.9-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/target/bitrepository-integration-1.9-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integration/1.9-SNAPSHOT/bitrepository-integration-1.9-SNAPSHOT-sources.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/target/bitrepository-integration-1.9-SNAPSHOT-quickstart.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integration/1.9-SNAPSHOT/bitrepository-integration-1.9-SNAPSHOT-quickstart.tar.gz
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/target/bitrepository-integration-1.9-SNAPSHOT-tools.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integration/1.9-SNAPSHOT/bitrepository-integration-1.9-SNAPSHOT-tools.tar.gz
[INFO] 
[INFO] --- maven-deploy-plugin:2.8.1:deploy (default-deploy) @ bitrepository-integration ---
[INFO] Downloading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.9-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.9-SNAPSHOT/maven-metadata.xml (2 KB at 36.6 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.9-SNAPSHOT/bitrepository-integration-1.9-20170218.142513-7.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.9-SNAPSHOT/bitrepository-integration-1.9-20170218.142513-7.jar (33 KB at 498.0 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.9-SNAPSHOT/bitrepository-integration-1.9-20170218.142513-7.pom
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.9-SNAPSHOT/bitrepository-integration-1.9-20170218.142513-7.pom (4 KB at 64.9 KB/sec)
[INFO] Downloading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/maven-metadata.xml (450 B at 14.2 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.9-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.9-SNAPSHOT/maven-metadata.xml (2 KB at 47.4 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/maven-metadata.xml (450 B at 14.2 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.9-SNAPSHOT/bitrepository-integration-1.9-20170218.142513-7-tests.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.9-SNAPSHOT/bitrepository-integration-1.9-20170218.142513-7-tests.jar (3 KB at 14.8 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.9-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.9-SNAPSHOT/maven-metadata.xml (2 KB at 51.9 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.9-SNAPSHOT/bitrepository-integration-1.9-20170218.142513-7-sources.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.9-SNAPSHOT/bitrepository-integration-1.9-20170218.142513-7-sources.jar (31 KB at 460.3 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.9-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.9-SNAPSHOT/maven-metadata.xml (2 KB at 73.2 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.9-SNAPSHOT/bitrepository-integration-1.9-20170218.142513-7-quickstart.tar.gz
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.9-SNAPSHOT/bitrepository-integration-1.9-20170218.142513-7-quickstart.tar.gz (106360 KB at 3110.0 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.9-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.9-SNAPSHOT/maven-metadata.xml (2 KB at 64.4 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.9-SNAPSHOT/bitrepository-integration-1.9-20170218.142513-7-tools.tar.gz
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.9-SNAPSHOT/bitrepository-integration-1.9-20170218.142513-7-tools.tar.gz (119616 KB at 2969.8 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.9-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.9-SNAPSHOT/maven-metadata.xml (2 KB at 70.0 KB/sec)
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO] 
[INFO] Bitrepository ..................................... SUCCESS [ 11.163 s]
[INFO] Bitrepository Reference Settings .................. SUCCESS [  7.940 s]
[INFO] Bitrepository Core ................................ SUCCESS [ 58.514 s]
[INFO] Bitrepository Client .............................. SUCCESS [01:16 min]
[INFO] Bitrepository Service ............................. SUCCESS [ 27.089 s]
[INFO] Bitrepository Integrity Service ................... SUCCESS [02:20 min]
[INFO] Bitrepository Alarm Service ....................... SUCCESS [ 37.346 s]
[INFO] Bitrepository Audit Trail Service ................. SUCCESS [ 55.433 s]
[INFO] Bitrepository Reference Pillar .................... SUCCESS [01:36 min]
[INFO] Bitrepository Monitoring Service .................. SUCCESS [ 27.295 s]
[INFO] Bitrepository Webclient ........................... SUCCESS [ 12.685 s]
[INFO] Bitrepository Integration ......................... SUCCESS [01:38 min]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 10:57 min
[INFO] Finished at: 2017-02-18T15:26:34+01:00
[INFO] Final Memory: 44M/170M
[INFO] ------------------------------------------------------------------------
channel stopped
Started indexing related Jira issue keys
Successfully indexed related Jira issue keys
Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered
Triggering a new build of Bitrepository-deploy-ci-test
Finished: SUCCESS