SuccessConsole Output

Skipping 556 KB.. Full Log
MigratingChecksumDatabaseFromV3ToV4
    Starting testcase ChecksumEntryTest
      Test starting: testExtendedTestCase
        Description: Test the ChecksumEntry
        Step: Create a ChecksumEntry
      Test success: testExtendedTestCase
    Starting testcase ChecksumPillarModelTest
      Test starting: testPillarModelBasicFunctionality
        Description: Test the basic functions of the full reference pillar model.
        Step: Check the pillar id in the pillar model
        Step: Ask whether it can handle a file of size 0
        Step: Ask whether it can handle a file of maximum size
        Step: Check the ChecksumPillarSpec
        Step: Checkum whether the checksum pillar should download
      Test success: testPillarModelBasicFunctionality
      Test starting: testPillarModelHasFile
        Description: Test that the file exists, when placed in the archive and cache
        Step: Setup
        Step: Check whether file exists and retrieve it.
        Step: Check whether file exists.
        Step: Ask for the checksum data for the file with different checksum specs
        Step: Ask for the checksum entry for the file with different checksum specs
        Step: Ask for the checksum for the file with different checksum specs
        Step: Check extraction of checksum result set
        Step: Check retrieval of non-default checksum
        Step: Check retrieval of non-default checksum result set
        Step: Test retrieval of single checksum result set
      Test success: testPillarModelHasFile
      Test starting: testPillarModelNoFile
        Description: Test that the file exists, when placed in the archive and cache
        Step: Setup
        Step: Check whether file exists and try to retrieve it.
        Step: Verify that anexceptions are thrown when verifying file existance.
      Test success: testPillarModelNoFile
    Starting testcase DeleteFileTest
        Added fixture: Initialize a new Pillar.
      Test starting: badCaseIdentification
        Description: Tests the identification for a DeleteFile operation on the checksum pillar for the failure scenario, when the file is missing.
        Step: Set up constants and variables.
        Step: Setup for delivering pillar id and not having the file 
        Step: Create and send the identify request message.
          Result: Received message on TEST-TOPIC-badCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileResponse@66ac3957[correlationID=68accb5b-acb5-4b6a-8ed2-933029f50863, 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@8da0e54[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@1c07b091[correlationID=9443e34b-05f4-43c7-b35d-4a2a309b1732, 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@1a8251ba[responseCode=EXISTING_FILE_CHECKSUM_FAILURE, responseText=No mandatory checksum for destructive operation was supplied.], pillarID=Pillar-badCaseOperationMissingVerification, fileID=DefaultFilebadCaseOperationMissingVerification, checksumDataForExistingFile=<null>(default)]
11:09:07.157 WARN  o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@3d2887e0[origDateTime=2017-06-08T11:09:07.157+02:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCaseOperationMissingVerification, alarmText=No mandatory checksum for destructive operation was supplied., fileID=DefaultFilebadCaseOperationMissingVerification, collectionID=TwoPillarCollection]
          Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@1c8a2bec[correlationID=5d86ffa3-2dae-4a90-adbd-6066a9fc8a43, 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@3d2887e0[origDateTime=2017-06-08T11:09:07.157+02:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCaseOperationMissingVerification, alarmText=No mandatory checksum for destructive operation was supplied., fileID=DefaultFilebadCaseOperationMissingVerification, collectionID=TwoPillarCollection]]
        Step: Retrieve the FinalResponse for the DeleteFile request
        Step: Pillar should have sent an alarm
      Test success: badCaseOperationMissingVerification
        Added fixture: Initialize a new Pillar.
      Test starting: badCaseOperationNoFile
        Description: Tests the DeleteFile functionality of the pillar for the failure scenario, where it does not have the file.
        Step: Set up constants and variables.
        Step: Setup for delivering pillar id and not having the file 
        Step: Create and send the actual DeleteFile message to the pillar.
          Result: Received message on TEST-TOPIC-badCaseOperationNoFile-cibuild01 : org.bitrepository.bitrepositorymessages.DeleteFileFinalResponse@550d3cd7[correlationID=60ab8adb-a0aa-46ff-a515-69c1fb584cf7, 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@4e3931[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@3c9788c[correlationID=bea6da5e-ab03-4e26-a010-123b7d855c8b, 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@6873c7e6[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], fileID=DefaultFilegoodCaseIdentification, pillarID=Pillar-goodCaseIdentification, pillarChecksumSpec=<null>(default), timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@4c2ff77[timeMeasureUnit=MILLISECONDS, timeMeasureValue=1000]]
        Step: Retrieve and validate the response getPillarID() the pillar.
      Test success: goodCaseIdentification
    Starting testcase GeneralMessageHandlingTest
        Added fixture: Initialize a new Pillar.
      Test starting: testPillarMessageHandler
        Description: Test the handling of the PillarMessageHandler super-class.
        Step: Setup
        Step: Test the pillar ID
      Test success: testPillarMessageHandler
        Added fixture: Initialize a new Pillar.
      Test starting: testPillarMessageHandlerValidateFileIDFormatDefaultFileId
        Description: Test the validation of file id formats of the PillarMessageHandler super-class on the default file id
      Test success: testPillarMessageHandlerValidateFileIDFormatDefaultFileId
        Added fixture: Initialize a new Pillar.
      Test starting: testPillarMessageHandlerValidateFileIDFormatEnvHomePathFileId
        Description: Test the validation of file id formats of the PillarMessageHandler super-class on a file id containing path relative paths from the environment variable home folder
      Test success: testPillarMessageHandlerValidateFileIDFormatEnvHomePathFileId
        Added fixture: Initialize a new Pillar.
      Test starting: testPillarMessageHandlerValidateFileIDFormatFolderFileId
        Description: Test the validation of file id formats of the PillarMessageHandler super-class on a file id with directory path
      Test success: testPillarMessageHandlerValidateFileIDFormatFolderFileId
        Added fixture: Initialize a new Pillar.
      Test starting: testPillarMessageHandlerValidateFileIDFormatParentFolderFileId
        Description: Test the validation of file id formats of the PillarMessageHandler super-class on a file id containing path to a parent directory
      Test success: testPillarMessageHandlerValidateFileIDFormatParentFolderFileId
        Added fixture: Initialize a new Pillar.
      Test starting: testPillarMessageHandlerValidateFileIDFormatRootPathFileId
        Description: Test the validation of file id formats of the PillarMessageHandler super-class on a file id containing path from the root folder
      Test success: testPillarMessageHandlerValidateFileIDFormatRootPathFileId
        Added fixture: Initialize a new Pillar.
      Test starting: testPillarMessageHandlerValidateFileIDFormatSubFolderToParentFolderFileId
        Description: Test the validation of file id formats of the PillarMessageHandler super-class on a file id containing path to a parent directory, but starting with a sub-folder
      Test success: testPillarMessageHandlerValidateFileIDFormatSubFolderToParentFolderFileId
        Added fixture: Initialize a new Pillar.
      Test starting: testPillarMessageHandlerValidateFileIDFormatTildeHomePathFileId
        Description: Test the validation of file id formats of the PillarMessageHandler super-class on a file id containing path relative paths from the tilde home folder
      Test success: testPillarMessageHandlerValidateFileIDFormatTildeHomePathFileId
        Added fixture: Initialize a new Pillar.
      Test starting: testPillarMessageHandlerValidateFileIDFormatTooLong
        Description: Test the validation of file id formats of the PillarMessageHandler super-class on a file id which has more characters than required
      Test success: testPillarMessageHandlerValidateFileIDFormatTooLong
    Starting testcase 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@3a8a823c[correlationID=36cf7b41-a0e1-454a-84f5-eed83692b974, 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@1235d778[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@65a5458b[fileID=DefaultFilebadCaseIdentification, allFileIDs=<null>(default)], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@a04462d[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.
11:09:13.934 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@4a9f02f4[correlationID=57019232-d73c-409e-87b3-1a31a8d96e4c, 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@5d5984aa[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@34d4aea7[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultingChecksums=<null>(default), partialResult=<null>(default)]
11:09:13.942 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@10b21a2b[correlationID=57019232-d73c-409e-87b3-1a31a8d96e4c, 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@15fa043[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@34d4aea7[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@10b21a2b[correlationID=57019232-d73c-409e-87b3-1a31a8d96e4c, 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@15fa043[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@34d4aea7[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultingChecksums=<null>(default), partialResult=<null>(default)]
11:09:14.947 WARN  o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: 
org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@10b21a2b[correlationID=57019232-d73c-409e-87b3-1a31a8d96e4c, 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@15fa043[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@34d4aea7[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@34c73992[correlationID=52007aeb-3ae8-44b7-be8d-c1abecd2c0c1, 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@322733e[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@269c3cc3[fileID=DefaultFilegoodCaseIdentification, allFileIDs=<null>(default)], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@5b092600[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], pillarID=Pillar-goodCaseIdentification, pillarChecksumSpec=<null>(default), timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@568f8f5a[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@2090ae74[correlationID=79a07cfa-2b15-4732-b6bf-f3ff7d9e2a1e, 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@50150196[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to calculate checksums.], pillarID=Pillar-goodCaseOperationAllFiles, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@7424796c[fileID=<null>(default), allFileIDs=true], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2d8c51c9[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultAddress=<null>(default)]
          Result: Received message on TEST-TOPIC-goodCaseOperationAllFiles-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@521090f1[correlationID=79a07cfa-2b15-4732-b6bf-f3ff7d9e2a1e, 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@54db2ab9[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], pillarID=Pillar-goodCaseOperationAllFiles, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2d8c51c9[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultingChecksums=org.bitrepository.bitrepositoryelements.ResultingChecksums@2c630bff[resultAddress=<null>(default), checksumDataItems={org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@3447c3ed[fileID=DefaultFile, checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2017-06-08T11:09:16.496+02:00],org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@62065a8c[fileID=goodCaseOperationAllFiles-cibuild01--Test-File-1496912956481, 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@505b5ddc[correlationID=44a01071-417e-4521-89e1-5368187f8f9f, 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@44243d32[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to calculate checksums.], pillarID=Pillar-goodCaseOperationSingleFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@6af761ba[fileID=DefaultFilegoodCaseOperationSingleFile, allFileIDs=<null>(default)], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@3ea10f3[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultAddress=<null>(default)]
          Result: Received message on TEST-TOPIC-goodCaseOperationSingleFile-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@9d518ef[correlationID=44a01071-417e-4521-89e1-5368187f8f9f, 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@6cfd694a[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], pillarID=Pillar-goodCaseOperationSingleFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@3ea10f3[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultingChecksums=org.bitrepository.bitrepositoryelements.ResultingChecksums@3d562fde[resultAddress=<null>(default), checksumDataItems={org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@6e68cd0f[fileID=DefaultFilegoodCaseOperationSingleFile, checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2017-06-08T11:09:16.831+02:00]}], partialResult=false]
        Step: Retrieve the ProgressResponse for the GetChecksums request
        Step: Retrieve the FinalResponse for the GetChecksums request
      Test success: goodCaseOperationSingleFile
        Added fixture: Initialize a new Pillar.
      Test starting: testRestrictions
        Description: Tests that the restrictions are correctly passed on to the cache.
        Step: Set up constants and variables.
        Step: Setup for only delivering result-set when the correct restrictions are given.
        Step: Create and send the actual GetChecksums message to the pillar.
          Result: Received message on TEST-TOPIC-testRestrictions-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsProgressResponse@486c3088[correlationID=5a13dcfe-0b59-4e91-bc22-7c77a449308d, 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@62e53557[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to calculate checksums.], pillarID=Pillar-testRestrictions, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@54b7bfbe[fileID=<null>(default), allFileIDs=true], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@70b14988[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultAddress=<null>(default)]
          Result: Received message on TEST-TOPIC-testRestrictions-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@59f0cf66[correlationID=5a13dcfe-0b59-4e91-bc22-7c77a449308d, 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@12f40682[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], pillarID=Pillar-testRestrictions, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@70b14988[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultingChecksums=org.bitrepository.bitrepositoryelements.ResultingChecksums@7bd7012d[resultAddress=<null>(default), checksumDataItems={org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@150fad6[fileID=DefaultFile, checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2017-06-08T11:09:17.125+02:00]}], partialResult=false]
        Step: Retrieve the ProgressResponse for the GetChecksums request
        Step: Retrieve the FinalResponse for the GetChecksums request
      Test success: testRestrictions
    Starting testcase GetFileIDsTest
        Added fixture: Initialize a new Pillar.
      Test starting: badCaseIdentification
        Description: Tests the identification for a GetFileIDs operation on the pillar for the failure scenario, when the file is missing.
        Step: Set up constants and variables.
        Step: Setup for delivering pillar id and not having the file 
        Step: Create and send the identify request message.
11:09:17.442 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@5982f78[correlationID=9ddc8a8e-726c-4091-90d5-680b45206ae1, 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@2a0b4810[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseIdentification, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@5aecf9b5[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.
11:09:18.742 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@1748e38e[correlationID=abeeba1c-9833-4ee9-957a-6ca3a56ff2fd, 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@43cd2f26[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@7d12e459[fileID=DefaultFilebadCaseOperationNoFile, allFileIDs=<null>(default)], resultingFileIDs=<null>(default), partialResult=<null>(default)]
11:09:18.754 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@47daff53[correlationID=abeeba1c-9833-4ee9-957a-6ca3a56ff2fd, 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@6d445c91[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@7d12e459[fileID=DefaultFilebadCaseOperationNoFile, allFileIDs=<null>(default)], resultingFileIDs=<null>(default), partialResult=<null>(default)]
11:09:18.768 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@57ba286d[correlationID=abeeba1c-9833-4ee9-957a-6ca3a56ff2fd, 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@470a65ae[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@7d12e459[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@47daff53[correlationID=abeeba1c-9833-4ee9-957a-6ca3a56ff2fd, 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@6d445c91[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@7d12e459[fileID=DefaultFilebadCaseOperationNoFile, allFileIDs=<null>(default)], resultingFileIDs=<null>(default), partialResult=<null>(default)]
org.bitrepository.bitrepositorymessages.GetFileIDsFinalResponse@57ba286d[correlationID=abeeba1c-9833-4ee9-957a-6ca3a56ff2fd, 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@470a65ae[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@7d12e459[fileID=DefaultFilebadCaseOperationNoFile, allFileIDs=<null>(default)], resultingFileIDs=<null>(default), partialResult=<null>(default)]
11:09:19.774 WARN  o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: 
org.bitrepository.bitrepositorymessages.GetFileIDsFinalResponse@47daff53[correlationID=abeeba1c-9833-4ee9-957a-6ca3a56ff2fd, 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@6d445c91[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@7d12e459[fileID=DefaultFilebadCaseOperationNoFile, allFileIDs=<null>(default)], resultingFileIDs=<null>(default), partialResult=<null>(default)]
org.bitrepository.bitrepositorymessages.GetFileIDsFinalResponse@57ba286d[correlationID=abeeba1c-9833-4ee9-957a-6ca3a56ff2fd, 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@470a65ae[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@7d12e459[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@12c448c[correlationID=92822951-0758-4596-8fba-6821dbd8d97f, 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@48214788[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], pillarID=Pillar-goodCaseIdentification, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@728ce413[fileID=DefaultFilegoodCaseIdentification, allFileIDs=<null>(default)], timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@7d143e6e[timeMeasureUnit=MILLISECONDS, timeMeasureValue=1000]]
        Step: Retrieve and validate the response getPillarID() the pillar.
      Test success: goodCaseIdentification
      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 ChecksumDatabaseTest
      Test starting: testChecksumDatabaseExtraction
        Description: Test the extraction of data from the checksum database.
        Step: Check whether the default entry exists.
        Step: Extract calculation date
        Step: Extract the checksum
        Step: Extract the whole entry
        Step: Extract all entries
      Test success: testChecksumDatabaseExtraction
      Test starting: testDeletion
        Description: Test that data can be deleted from the database.
        Step: Check whether the default entry exists.
        Step: Remove the default entry
      Test success: testDeletion
      Test starting: testExtractionOfMissingData
        Description: Test the handling of bad arguments.
        Step: Try to get the date of a wrong file id.
        Step: Try to get the date of a wrong file id.
        Step: Try to remove a bad file id
      Test success: testExtractionOfMissingData
      Test starting: testGetChecksumResult
        Description: Tests the restrictions on the GetChecksumResult call to the database.
        Step: Instantiate database with appropriate data.
        Step: Test with no time restrictions
        Step: Test with time restrictions from epoc to now
        Step: Test with very strict time restrictions around the default date
        Step: Test with too new a lower limit
        Step: Test with exact date as both upper and lower limit
        Step: Test with date limit from 1 millis before as lower and exact date a upper limit
        Step: Test with date limit from exact date as lower and 1 millis after date a upper limit
        Step: Test with too old an upper limit
      Test success: testGetChecksumResult
      Test starting: testGetFileIDsRestrictions
        Description: Tests the restrictions on the GetFileIDs call to the database.
        Step: Instantiate database with appropriate data.
        Step: Test with no time restrictions and 10000 max_results
        Step: Test with minimum-date earlier than first file
        Step: Test with maximum-date earlier than first file
        Step: Test with minimum-date set to later than second file.
        Step: Test with maximum-date set to later than second file.
        Step: Test with minimum-date set to middle date.
        Step: Test with maximum-date set to middle date.
        Step: Test with both minimum-date and maximum-date set to middle date.
        Step: Test the first file-id, with no other restrictions
        Step: Test the second file-id, with no other restrictions
        Step: Test the date for the first file-id, while requesting the second file-id
      Test success: testGetFileIDsRestrictions
      Test starting: testGetFileIDsWithOldChecksums
        Description: Tests the restrictions on the GetFileIDsWithOldChecksums call to the database.
        Step: Instantiate database with appropriate data.
        Step: Extract all entries with checksum date older than now
        Step: Extract all entries with checksum date older than epoch
        Step: Extract all entries with checksum date older than middle date
      Test success: testGetFileIDsWithOldChecksums
      Test starting: testReplacingExistingEntry
        Description: Test that an entry can be replaced by another in the database.
        Step: Check whether the default entry exists.
        Step: Replace the checksum and date
      Test success: testReplacingExistingEntry
      Test starting: testSpecifiedEntryExtraction
        Description: Test that specific entries can be extracted. Has two entries in the database: one for the current timestamp and one for the epoch.
        Step: Instantiate database with appropriate data.
        Step: Extract with out restrictions
        Step: Extract with a maximum of 1 entry
        Step: Extract all dates older than this tests instantiation
        Step: Extract all dates newer than this tests instantiation
        Step: Extract all dates older than the newest instance
        Step: Extract all dates newer than the oldest instantiation
      Test success: testSpecifiedEntryExtraction
    Starting testcase FullPillarModelTest
      Test starting: testPillarModelBasicFunctionality
        Description: Test the basic functions of the full reference pillar model.
        Step: Check the pillar id in the pillar model
        Step: Ask whether it can handle a file of size 0
        Step: Ask whether it can handle a file of maximum size
        Step: Check the ChecksumPillarSpec
      Test success: testPillarModelBasicFunctionality
      Test starting: testPillarModelHasFile
        Description: Test that the file exists, when placed in the archive and cache
        Step: Setup
        Step: Check whether file exists and retrieve it.
        Step: Verify that no exceptions are thrown when verifying file existance.
        Step: Check retrieval of non-default checksum
      Test success: testPillarModelHasFile
      Test starting: testPillarModelNoFile
        Description: Test that the file exists, when placed in the archive and cache
        Step: Setup
        Step: Check whether file exists and try to retrieve it.
        Step: Verify that anexceptions are thrown when verifying file existance.
11:09:43.534 WARN  o.b.pillar.store.FileStorageModel - The file 'DefaultFile' has been requested, but we do not have that file in collection 'TwoPillarCollection'!
      Test success: testPillarModelNoFile
    Starting testcase GetAuditTrailsTest
        Added fixture: Initialize a new Pillar.
      Test starting: checksumPillarGetAuditTrailsMaximumNumberOfResults
        Description: Tests the GetAuditTrails functionality of the pillar for the successful scenario, where a limited number of audit trails are requested.
        Step: Set up constants and variables.
        Step: Send the request for the limited amount of audit trails to the pillar.
          Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsMaximumNumberOfResults-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsProgressResponse@3d411475[correlationID=23240503-4bde-448e-b7e9-c74b16e5a9ed, 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@32850adc[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@1c3b884[correlationID=23240503-4bde-448e-b7e9-c74b16e5a9ed, 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@1eaa9f9b[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], contributor=Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@5e635533[resultAddress=<null>(default), auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@709e3f6a[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@6c05ae65[sequenceNumber=1, fileID=fileID1496912983801, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=CHECKSUM_CALCULATED, actionDateTime=2017-06-08T11:09:43.808+02:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@2619a239[sequenceNumber=2, fileID=fileID1496912983801, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=DELETE_FILE, actionDateTime=2017-06-08T11:09:43.809+02:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@6297b104[sequenceNumber=3, fileID=fileID1496912983801, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=FAILURE, actionDateTime=2017-06-08T11:09:43.809+02:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@6373a753[sequenceNumber=4, fileID=fileID1496912983801, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=FILE_MOVED, actionDateTime=2017-06-08T11:09:43.809+02:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@22c45bde[sequenceNumber=5, fileID=fileID1496912983801, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=GET_CHECKSUMS, actionDateTime=2017-06-08T11:09:43.809+02:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails]}]], partialResult=true]
        Step: Validate the final response
      Test success: checksumPillarGetAuditTrailsMaximumNumberOfResults
        Added fixture: Initialize a new Pillar.
      Test starting: checksumPillarGetAuditTrailsSpecificRequests
        Description: Tests the GetAuditTrails functionality of the pillar for the successful scenario, where a specific audit trail are requested.
        Step: Set up constants and variables.
        Step: Send the identification request
          Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsResponse@3d4fb16e[correlationID=810cd37a-1193-4536-903b-9285ea80868b, 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@7dff5404[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@fc56cf9[correlationID=810cd37a-1193-4536-903b-9285ea80868b, 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@4fc178ae[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@48195a26[correlationID=810cd37a-1193-4536-903b-9285ea80868b, 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@69159c72[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], contributor=Pillar-checksumPillarGetAuditTrailsSpecificRequests, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@4d13970d[resultAddress=<null>(default), auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@9538209[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@b99316f[sequenceNumber=1, fileID=fileID1496912984135, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=OTHER, actionDateTime=2017-06-08T11:09:44.137+02:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails]}]], partialResult=false]
        Step: Receive and validate the progress response.
        Step: Receive and validate the final response
        Step: Make another request, where both ingested audit trails is requested
          Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsProgressResponse@4eaada62[correlationID=810cd37a-1193-4536-903b-9285ea80868b, 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@1f508745[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@a060d6c[correlationID=810cd37a-1193-4536-903b-9285ea80868b, 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@4856570a[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], contributor=Pillar-checksumPillarGetAuditTrailsSpecificRequests, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@5037eda8[resultAddress=<null>(default), auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@4bc62244[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@b99316f[sequenceNumber=1, fileID=fileID1496912984135, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=OTHER, actionDateTime=2017-06-08T11:09:44.137+02:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@71913b3d[sequenceNumber=2, fileID=notThisFile, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=UnknownActor, actionOnFile=FAILURE, actionDateTime=2017-06-08T11:09:44.137+02:00, info=badInfo, operationID=operationID, certificateID=certificateid, auditTrailInformation=WrongAuditTrail]}]], partialResult=false]
        Step: Receive and validate the progress response.
        Step: Receive and validate the final response
      Test success: checksumPillarGetAuditTrailsSpecificRequests
        Added fixture: Initialize a new Pillar.
      Test starting: checksumPillarGetAuditTrailsSuccessful
        Description: Tests the GetAuditTrails functionality of the pillar for the successful scenario, where all audit trails are requested.
        Step: Set up constants and variables.
        Step: Send the identification request
          Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSuccessful-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsResponse@40c6afcf[correlationID=dcf2edc6-a31b-4bc3-8a87-055cd58d8472, 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@294d2e39[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@23f7d9fe[correlationID=dcf2edc6-a31b-4bc3-8a87-055cd58d8472, 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@557f5cb4[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@20b23903[correlationID=dcf2edc6-a31b-4bc3-8a87-055cd58d8472, 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@60cee7ca[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], contributor=Pillar-checksumPillarGetAuditTrailsSuccessful, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@7debfa04[resultAddress=<null>(default), auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@52de93f1[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@6315d288[sequenceNumber=1, fileID=fileid, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=actor, actionOnFile=OTHER, actionDateTime=2017-06-08T11:09:44.414+02:00, info=info, operationID=operationID, certificateID=certificateID, auditTrailInformation=auditTrail]}]], partialResult=false]
        Step: Receive and validate the progress response.
        Step: Receive and validate the final response
      Test success: checksumPillarGetAuditTrailsSuccessful
    Starting testcase 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@332c8e2c[correlationID=a73cc27d-a042-47dd-a096-42a32216d244, 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@2f98755d[responseCode=DUPLICATE_FILE_FAILURE, responseText=<null>(default)], pillarID=Pillar-badCaseIdentification, fileID=DefaultFilebadCaseIdentification, pillarChecksumSpec=<null>(default), checksumDataForExistingFile=<null>(default), timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@43a99a43[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@3e476882[correlationID=d322cc0e-271e-4755-aa34-bb73a1937f71, 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@76d5040d[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@c8080e6[correlationID=e446919a-5f9f-494e-9410-c68795aea17e, 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@30315a1c[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)]
11:09:47.334 WARN  o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@2b065bdb[origDateTime=2017-06-08T11:09:47.333+02:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCasePutOperationNoValidationChecksum, alarmText=A checksum is required for the PutFile operation to be performed., fileID=DefaultFilebadCasePutOperationNoValidationChecksum, collectionID=TwoPillarCollection]
          Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@21b48fb7[correlationID=2a9aabd6-7d7e-4686-b6fb-31f22dbe43cc, 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@2b065bdb[origDateTime=2017-06-08T11:09:47.333+02:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCasePutOperationNoValidationChecksum, alarmText=A checksum is required for the PutFile operation to be performed., fileID=DefaultFilebadCasePutOperationNoValidationChecksum, collectionID=TwoPillarCollection]]
        Step: Retrieve the FinalResponse for the PutFile request
        Step: Pillar should have sent an alarm
      Test success: badCasePutOperationNoValidationChecksum
        Added fixture: Initialize a new Pillar.
      Test starting: goodCaseIdentification
        Description: Tests the identification for a PutFile operation on the pillar for the successful scenario.
        Step: Set up constants and variables.
        Step: Setup for not already having the file and delivering pillar id
        Step: Create and send the identify request message.
          Result: Received message on TEST-TOPIC-goodCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileResponse@5cddf9cd[correlationID=758796c2-28a6-44c2-bf8e-0de5b606d919, 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@5570d921[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], pillarID=Pillar-goodCaseIdentification, fileID=DefaultFilegoodCaseIdentification, pillarChecksumSpec=<null>(default), checksumDataForExistingFile=<null>(default), timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@45ebde80[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@32cf3e7b[correlationID=59c83fd9-792c-4aa7-a63d-60c59758637c, 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@7bd43ad7[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@26928e2b[correlationID=59c83fd9-792c-4aa7-a63d-60c59758637c, 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@6d654064[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@373dcd9d[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@341ba2e0[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2017-06-08T11:09:48.895+02:00], checksumDataForExistingFile=<null>(default)]
        Step: Retrieve the ProgressResponse for the GetFileIDs request
        Step: Retrieve the FinalResponse for the PutFile request
      Test success: goodCaseOperationWithChecksumReturn
      Test starting: getPillarCollectionsTest
      Test success: getPillarCollectionsTest
    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@7490c78f[correlationID=650115c6-6f24-4723-b957-4bd9ab2def0f, 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@6c4647d2[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@51ece47a[correlationID=c0f36b1a-9f58-4eb6-b2d8-14b6849f688b, 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@7b8b0c78[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], fileID=DefaultFilegoodCaseIdentification, pillarID=Pillar-goodCaseIdentification, timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@65993c30[timeMeasureUnit=MILLISECONDS, timeMeasureValue=1000]]
        Step: Retrieve and validate the response getPillarID() the pillar.
      Test success: goodCaseIdentification
    Starting testcase MediatorTest
      Test starting: testMediatorRuntimeExceptionHandling
        Description: Tests the handling of a runtime exception
        Step: Setup create and start the mediator.
        Step: Send a request to the mediator.
11:09:53.764 WARN  o.b.pillar.MediatorTest$TestMediator - Unexpected exception caught.
java.lang.RuntimeException: I am supposed to throw a RuntimeException
	at org.bitrepository.pillar.MediatorTest$ErroneousRequestHandler.processRequest(MediatorTest.java:122)
	at org.bitrepository.pillar.MediatorTest$ErroneousRequestHandler.processRequest(MediatorTest.java:113)
	at org.bitrepository.pillar.messagehandler.PillarMediator.handleRequest(PillarMediator.java:80)
	at org.bitrepository.service.contributor.AbstractContributorMediator$GeneralRequestHandler.onMessage(AbstractContributorMediator.java:101)
	at org.bitrepository.protocol.messagebus.SimpleMessageBus.lambda$sendMessage$0(SimpleMessageBus.java:73)
	at java.lang.Iterable.forEach(Iterable.java:75)
	at org.bitrepository.protocol.messagebus.SimpleMessageBus.sendMessage(SimpleMessageBus.java:73)
	at org.bitrepository.pillar.MediatorTest.testMediatorRuntimeExceptionHandling(MediatorTest.java:84)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java: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@36fa9ebd[correlationID=a60fb4d3-203d-45f1-849f-1101e61bc0d3, 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@7a5dff85[responseCode=FAILURE, responseText=java.lang.RuntimeException: I am supposed to throw a RuntimeException], contributor=TEST-TOPIC-cibuild01, timeToDeliver=<null>(default)]
11:09:53.767 WARN  o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@d583496[origDateTime=2017-06-08T11:09:53.766+02:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MediatorUnderTest, alarmText=java.lang.RuntimeException: I am supposed to throw a RuntimeException, fileID=<null>(default), collectionID=<null>(default)]
          Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@6f354cf6[correlationID=7d679c2e-dc7b-4bc8-99ea-073dba89e0bc, 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@d583496[origDateTime=2017-06-08T11:09:53.766+02:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MediatorUnderTest, alarmText=java.lang.RuntimeException: I am supposed to throw a RuntimeException, fileID=<null>(default), collectionID=<null>(default)]]
      Test success: testMediatorRuntimeExceptionHandling
    Starting testcase ReferenceArchiveTest
        Added fixture: Initialize the Reference pillar cache with an empty file in default collection TwoPillarCollection
      Test starting: testReferenceArchive
        Description: Test the ReferenceArchive.
        Step: Setup
        Step: test 'hasFile'
        Step: Test 'getFile'
        Step: Test getAllFileIDs
        Step: Test 'getFileAsInputstream'
        Step: Delete, recreate and delete again
        Step: Try to delete missing file.
        Step: Replace a file, which does not exist in the filedir.
        Step: Copy a file into the tmpDir and then use replace.
        Step: Try performing the replace, when the file in the tempdir has been removed.
      Test success: testReferenceArchive
    Starting testcase ReplaceFileTest
        Added fixture: Initialize a new Pillar.
      Test starting: badCaseIdentification
        Description: Tests the identification for a ReplaceFile operation on the pillar for the failure scenario, when the file does not exist.
        Step: Set up constants and variables.
        Step: Setup for not having the file and delivering pillar id
        Step: Create and send the identify request message.
          Result: Received message on TEST-TOPIC-badCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileResponse@3451f8ff[correlationID=0ee61941-2119-4ac7-b78c-65572a96a8ef, 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@1169382d[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@5460c665[correlationID=6e0b3e62-0605-41e2-bd09-6ed9f24debe9, 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@319f6039[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@55f591c2[correlationID=82f6cda0-aa5f-4ff7-a3e0-d79626a5d47f, 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@581fa170[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)]
11:09:56.890 WARN  o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@7a95ed24[origDateTime=2017-06-08T11:09:56.889+02:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCaseOperationNoDestructiveChecksum, alarmText=According to the contract a checksum for file to be deleted during the replacing operation is required., fileID=DefaultFile, collectionID=TwoPillarCollection]
          Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@3e8712b0[correlationID=e6dd24c3-a667-423c-89e6-36ea80a10ef4, 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@7a95ed24[origDateTime=2017-06-08T11:09:56.889+02:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCaseOperationNoDestructiveChecksum, alarmText=According to the contract a checksum for file to be deleted during the replacing operation is required., fileID=DefaultFile, collectionID=TwoPillarCollection]]
        Step: Retrieve the FinalResponse for the ReplaceFile request
        Step: Pillar should have sent an alarm
      Test success: badCaseOperationNoDestructiveChecksum
        Added fixture: Initialize a new Pillar.
      Test starting: badCaseOperationNoValidationChecksum
        Description: Tests the ReplaceFile operation on the pillar for the failure scenario, when no validation checksum is given for the new file, but though is required.
        Step: Set up constants and variables.
        Step: Setup for having the file and delivering pillar id
        Step: Create and send the identify request message.
          Result: Received message on TEST-TOPIC-badCaseOperationNoValidationChecksum-cibuild01 : org.bitrepository.bitrepositorymessages.ReplaceFileFinalResponse@40955466[correlationID=c27e8be2-f1a1-43d2-9c7f-b2823db570a4, 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@19e90def[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)]
11:09:57.177 WARN  o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@5f4098bd[origDateTime=2017-06-08T11:09:57.177+02:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCaseOperationNoValidationChecksum, alarmText=According to the contract a checksum for new file in the replacing operation is required., fileID=DefaultFile, collectionID=TwoPillarCollection]
          Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@5c38ce9a[correlationID=2037b0ee-3945-469f-9678-e9bca8020dee, 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@5f4098bd[origDateTime=2017-06-08T11:09:57.177+02:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCaseOperationNoValidationChecksum, alarmText=According to the contract a checksum for new file in the replacing operation is required., fileID=DefaultFile, collectionID=TwoPillarCollection]]
        Step: Retrieve the FinalResponse for the ReplaceFile request
        Step: Pillar should have sent an alarm
      Test success: badCaseOperationNoValidationChecksum
        Added fixture: Initialize a new Pillar.
      Test starting: badCaseOperationWrongDestructiveChecksum
        Description: Tests the ReplaceFile operation on the pillar for the failure scenario, when the checksum for the destructive action is different from the one in the cache.
        Step: Set up constants and variables.
        Step: Setup for having the file and delivering pillar id
        Step: Create and send the identify request message.
11:09:57.542 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@3fd8e5a4[correlationID=53243646-4660-4a5d-ac56-381066e3f603, 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@3613bc0b[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)]
11:09:57.551 WARN  o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@de353ad[origDateTime=2017-06-08T11:09:57.548+02:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCaseOperationWrongDestructiveChecksum, alarmText=Requested to replace the file 'DefaultFile' with checksum '1234cccccccc4321', but our file had a different checksum., fileID=DefaultFile, collectionID=TwoPillarCollection]
          Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@24694bd9[correlationID=ec9161c3-d270-49d6-9f64-d451c7e59565, 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@de353ad[origDateTime=2017-06-08T11:09:57.548+02:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCaseOperationWrongDestructiveChecksum, alarmText=Requested to replace the file 'DefaultFile' with checksum '1234cccccccc4321', but our file had a different checksum., fileID=DefaultFile, collectionID=TwoPillarCollection]]
        Step: Retrieve the FinalResponse for the ReplaceFile request
        Step: Pillar should have sent an alarm
      Test success: badCaseOperationWrongDestructiveChecksum
        Added fixture: Initialize a new Pillar.
      Test starting: goodCaseIdentification
        Description: Tests the identification for a ReplaceFile operation on the pillar for the successful scenario.
        Step: Set up constants and variables.
        Step: Setup for having the file and delivering pillar id
        Step: Create and send the identify request message.
          Result: Received message on TEST-TOPIC-goodCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileResponse@4e3617fe[correlationID=8ba35fb8-f2a1-4b4f-b941-ff55c6f9689e, 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@51ffdbc9[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], fileID=DefaultFile, pillarID=Pillar-goodCaseIdentification, pillarChecksumSpec=<null>(default), timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@4ab50d80[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@19acd913[correlationID=fbdf4c05-e3d1-4f93-9eac-d3c43bec5e81, 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@1c23ef5e[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@49035687[correlationID=fbdf4c05-e3d1-4f93-9eac-d3c43bec5e81, 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@36987af5[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@6a093719[correlationID=506d7945-5441-4435-b1cc-89855990f691, 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@6aabf6f5[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@33006891[correlationID=506d7945-5441-4435-b1cc-89855990f691, 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@130646f9[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@30141a7f[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@5bd5ed6[checksumType=HMAC_SHA512, checksumSalt={97,98}, otherChecksumType=<null>(default)], checksumValue={18,52,-52,-52,-52,-52,67,34}, calculationTimestamp=2017-06-08T11:10:00.205+02:00], checksumDataForNewFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@3549ea10[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@14d953ce[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2017-06-08T11:10:00.206+02:00]]
        Step: Retrieve the ProgressResponse for the GetFileIDs request
        Step: Retrieve the FinalResponse for the ReplaceFile request
      Test success: goodCaseOperationWithChecksumsReturn
      Finished testcase
  Finished suite
Finished project
Tests run: 72, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 70.155 sec - in TestSuite

Results :

Tests run: 72, 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.10-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.10-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.10-SNAPSHOT-sources.jar
[INFO] 
[INFO] --- maven-assembly-plugin:2.4:single (distribution) @ bitrepository-reference-pillar ---
[INFO] Reading assembly descriptor: src/main/assembly/assembly.xml
[INFO] Reading assembly descriptor: src/test/assembly/assembly.xml
[INFO] Reading assembly descriptor: src/main/assembly/deploy-assembly.xml
[INFO] Reading assembly descriptor: src/test/assembly/test-deploy-assembly.xml
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.10-SNAPSHOT-distribution.tar.gz
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.10-SNAPSHOT-acceptance-test.tar.gz
[WARNING] Entry: bitrepository-reference-pillar-1.10-SNAPSHOT/lib/bitrepository-reference-pillar-1.10-SNAPSHOT-tests.jar longer than 100 characters.
[WARNING] Resulting tar file can only be processed successfully by GNU compatible tar commands
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.10-SNAPSHOT-deploy.tar.gz
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.10-SNAPSHOT-acceptance-test-deploy.tar.gz
[INFO] 
[INFO] --- maven-install-plugin: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.10-SNAPSHOT.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-SNAPSHOT.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.10-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.10-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-SNAPSHOT-sources.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.10-SNAPSHOT-distribution.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-SNAPSHOT-distribution.tar.gz
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.10-SNAPSHOT-acceptance-test.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-SNAPSHOT-acceptance-test.tar.gz
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.10-SNAPSHOT-deploy.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-SNAPSHOT-deploy.tar.gz
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.10-SNAPSHOT-acceptance-test-deploy.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-SNAPSHOT-acceptance-test-deploy.tar.gz
[INFO] 
[INFO] --- maven-deploy-plugin: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.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/maven-metadata.xml (3 KB at 22.7 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20170608.091006-4.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20170608.091006-4.jar (128 KB at 1722.1 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20170608.091006-4.pom
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20170608.091006-4.pom (8 KB at 251.1 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 (457 B at 17.9 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/maven-metadata.xml (3 KB at 53.1 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 (457 B at 12.1 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20170608.091006-4-tests.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20170608.091006-4-tests.jar (238 KB at 4856.4 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/maven-metadata.xml (3 KB at 44.0 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20170608.091006-4-sources.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20170608.091006-4-sources.jar (104 KB at 1785.3 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/maven-metadata.xml (3 KB at 45.0 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20170608.091006-4-distribution.tar.gz
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20170608.091006-4-distribution.tar.gz (13314 KB at 21647.4 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/maven-metadata.xml (3 KB at 86.2 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20170608.091006-4-acceptance-test.tar.gz
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20170608.091006-4-acceptance-test.tar.gz (12951 KB at 25343.1 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/maven-metadata.xml (3 KB at 66.8 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20170608.091006-4-deploy.tar.gz
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20170608.091006-4-deploy.tar.gz (4 KB at 106.8 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/maven-metadata.xml (3 KB at 79.6 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20170608.091006-4-acceptance-test-deploy.tar.gz
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20170608.091006-4-acceptance-test-deploy.tar.gz (4 KB at 130.3 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/maven-metadata.xml (3 KB at 53.1 KB/sec)
[JENKINS] Archiving disabled
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Monitoring Service 1.10-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-monitoring-service ---
[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 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.
11:10:14.317 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.
11:10:16.903 WARN  o.b.m.a.BasicMonitoringServiceAlerter - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@4cc26df[origDateTime=2017-06-08T11:10:16.882+02: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@3d6778d5[correlationID=2b19f215-0192-4419-ae19-65d620aa9939, 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@4cc26df[origDateTime=2017-06-08T11:10:16.882+02:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MonitorAlerterUnderTest, alarmText=The following components have become unresponsive: [TestMonitorService], fileID=<null>(default), collectionID=<null>(default)]]
      Test success: testMonitorAlerter
    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 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
      Finished testcase
  Finished suite
Finished project
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 9.141 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.10-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 [148 msecs]
[INFO] Building war: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.10-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.10-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.10-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.10-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.10-SNAPSHOT.war to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/bitrepository-monitoring-service-1.10-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.10-SNAPSHOT/bitrepository-monitoring-service-1.10-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.10-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/bitrepository-monitoring-service-1.10-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.10-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/bitrepository-monitoring-service-1.10-SNAPSHOT-sources.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.10-SNAPSHOT-distribution.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/bitrepository-monitoring-service-1.10-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.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 14.2 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/bitrepository-monitoring-service-1.10-20170608.091023-4.war
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/bitrepository-monitoring-service-1.10-20170608.091023-4.war (18064 KB at 21684.8 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/bitrepository-monitoring-service-1.10-20170608.091023-4.pom
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/bitrepository-monitoring-service-1.10-20170608.091023-4.pom (4 KB at 75.1 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 (459 B at 17.2 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 37.3 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 (459 B at 10.9 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/bitrepository-monitoring-service-1.10-20170608.091023-4-tests.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/bitrepository-monitoring-service-1.10-20170608.091023-4-tests.jar (15 KB at 373.3 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 44.3 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/bitrepository-monitoring-service-1.10-20170608.091023-4-sources.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/bitrepository-monitoring-service-1.10-20170608.091023-4-sources.jar (19 KB at 505.9 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 56.7 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/bitrepository-monitoring-service-1.10-20170608.091023-4-distribution.tar.gz
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/bitrepository-monitoring-service-1.10-20170608.091023-4-distribution.tar.gz (18062 KB at 21682.1 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 44.3 KB/sec)
[JENKINS] Archiving disabled
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Webclient 1.10-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-webclient ---
[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.10-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.10-SNAPSHOT]
[INFO] Copying webapp resources [/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/src/main/webapp]
[INFO] Webapp assembled in [436 msecs]
[INFO] Building war: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/target/bitrepository-webclient-1.10-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.10-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.10-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.10-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.10-SNAPSHOT.war to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/bitrepository-webclient-1.10-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.10-SNAPSHOT/bitrepository-webclient-1.10-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/target/bitrepository-webclient-1.10-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/bitrepository-webclient-1.10-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/target/bitrepository-webclient-1.10-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/bitrepository-webclient-1.10-SNAPSHOT-sources.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/target/bitrepository-webclient-1.10-SNAPSHOT-distribution.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/bitrepository-webclient-1.10-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.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 18.5 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/bitrepository-webclient-1.10-20170608.091029-4.war
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/bitrepository-webclient-1.10-20170608.091029-4.war (12468 KB at 23088.7 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/bitrepository-webclient-1.10-20170608.091029-4.pom
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/bitrepository-webclient-1.10-20170608.091029-4.pom (3 KB at 104.8 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 (450 B at 24.4 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 37.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 (450 B at 16.9 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/bitrepository-webclient-1.10-20170608.091029-4-tests.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/bitrepository-webclient-1.10-20170608.091029-4-tests.jar (3 KB at 74.7 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 54.2 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/bitrepository-webclient-1.10-20170608.091029-4-sources.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/bitrepository-webclient-1.10-20170608.091029-4-sources.jar (17 KB at 558.0 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 38.1 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/bitrepository-webclient-1.10-20170608.091029-4-distribution.tar.gz
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/bitrepository-webclient-1.10-20170608.091029-4-distribution.tar.gz (12463 KB at 22215.3 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 54.2 KB/sec)
[JENKINS] Archiving disabled
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Integration 1.10-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-integration ---
[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.10-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.10-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.10-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.10-SNAPSHOT-quickstart.tar.gz
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/target/bitrepository-integration-1.10-SNAPSHOT-tools.tar.gz
[WARNING] Entry: bitrepository-integration-1.10-SNAPSHOT/lib/bitrepository-reference-pillar-1.10-SNAPSHOT-distribution.tar.gz longer than 100 characters.
[WARNING] Resulting tar file can only be processed successfully by GNU compatible tar commands
[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.10-SNAPSHOT.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-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.10-SNAPSHOT/bitrepository-integration-1.10-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/target/bitrepository-integration-1.10-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/target/bitrepository-integration-1.10-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-SNAPSHOT-sources.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/target/bitrepository-integration-1.10-SNAPSHOT-quickstart.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-SNAPSHOT-quickstart.tar.gz
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/target/bitrepository-integration-1.10-SNAPSHOT-tools.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-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.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 4.8 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-20170608.091049-4.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-20170608.091049-4.jar (33 KB at 647.3 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-20170608.091049-4.pom
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-20170608.091049-4.pom (4 KB at 132.0 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 (452 B at 11.3 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 57.8 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 (452 B at 12.3 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-20170608.091049-4-tests.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-20170608.091049-4-tests.jar (3 KB at 74.8 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 44.9 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-20170608.091049-4-sources.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-20170608.091049-4-sources.jar (31 KB at 759.2 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 62.2 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-20170608.091049-4-quickstart.tar.gz
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-20170608.091049-4-quickstart.tar.gz (106370 KB at 23817.7 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 64.7 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-20170608.091049-4-tools.tar.gz
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-20170608.091049-4-tools.tar.gz (119629 KB at 24007.3 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 57.8 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 [  8.726 s]
[INFO] Bitrepository Reference Settings ................... SUCCESS [ 13.351 s]
[INFO] Bitrepository Core ................................. SUCCESS [ 53.492 s]
[INFO] Bitrepository Client ............................... SUCCESS [01:21 min]
[INFO] Bitrepository Service .............................. SUCCESS [ 27.634 s]
[INFO] Bitrepository Integrity Service .................... SUCCESS [02:03 min]
[INFO] Bitrepository Alarm Service ........................ SUCCESS [ 24.168 s]
[INFO] Bitrepository Audit Trail Service .................. SUCCESS [ 47.485 s]
[INFO] Bitrepository Reference Pillar ..................... SUCCESS [01:23 min]
[INFO] Bitrepository Monitoring Service ................... SUCCESS [ 16.491 s]
[INFO] Bitrepository Webclient ............................ SUCCESS [  5.181 s]
[INFO] Bitrepository Integration .......................... SUCCESS [ 28.097 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 08:42 min
[INFO] Finished at: 2017-06-08T11:11:04+02:00
[INFO] Final Memory: 58M/147M
[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