FailedConsole Output

Skipping 427 KB.. Full Log
ice/target/classes
[INFO] 
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ bitrepository-audit-trail-service ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ bitrepository-audit-trail-service ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 11 source files to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-audit-trail-service/target/test-classes
[INFO] 
[INFO] --- maven-surefire-plugin:2.17:test (default-test) @ bitrepository-audit-trail-service ---
[INFO] Surefire report directory: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-audit-trail-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 AuditPreservationEventHandlerTest
      Test starting: auditPreservationEventHandlerTest
        Description: Test the handling of the audit trail event handler.
        Step: Setup
        Step: Test the handling of another complete event.
      Test success: auditPreservationEventHandlerTest
    Starting testcase IncrementalCollectorTest
      Test starting: collectionIDFailureTest
        Description: Tests what happens when a wrong collection id is received.
        Step: 
        Step: Start a collection with two contributors
        Step: Send an auditTrail result from contributor 1 with a wrong collection id.
02:22:00.533 WARN  o.b.a.collector.IncrementalCollector - Received bad collection id! Expected 'dummy-collection', but got 'FalseCollection1450488120257'.
      Test success: collectionIDFailureTest
      Test starting: contributorFailureTest
        Description: Tests that the collector is able to collect from the remaining contributors if a contributor fails.
        Step: 
        Step: Start a collection with two contributors
        Step: Send a audit trail result from contributor 2 with the PartialResults boolean set to true and a failed event from contributor 1
02:22:00.654 WARN  o.b.a.collector.IncrementalCollector - Event: null: null: COMPONENT_FAILED: ContributorID Contributor1 ResponseCode: REQUEST_NOT_SUPPORTED
02:22:00.660 WARN  o.b.a.collector.IncrementalCollector - Event: null: null: FAILED: , 
02:22:00.676 ERROR o.b.a.collector.IncrementalCollector - Problem in collecting audittrails, collection will not be complete for collection 'dummy-collection'
org.bitrepository.client.exceptions.NegativeResponseException: 
	at org.bitrepository.access.getaudittrails.BlockingAuditTrailClient.getAuditTrails(BlockingAuditTrailClient.java:65) ~[bitrepository-client-1.7-SNAPSHOT.jar:1.7-SNAPSHOT]
	at org.bitrepository.audittrails.collector.IncrementalCollector.collect(IncrementalCollector.java:137) [classes/:na]
	at org.bitrepository.audittrails.collector.IncrementalCollector.performCollection(IncrementalCollector.java:114) [classes/:na]
	at org.bitrepository.audittrails.collector.IncrementalCollectorTest$CollectionRunner.run(IncrementalCollectorTest.java:288) [test-classes/:na]
	at java.lang.Thread.run(Thread.java:745) [na:1.8.0_11]
        Step: Send another audit trail result from contributor 2 with PartialResults set to false
      Test success: contributorFailureTest
      Test starting: multipleIncrementTest
        Description: Verifies the behaviour in the case where the adit trails needs to be reteived in multiple requests because of MaxNumberOfResults limits.
        Step: Start a collection with two contributors
        Step: Send a audit trail result from contributor 1 and 2 with the PartialResults boolean set to true
        Step: Send another audit trail result from the contributors, now with PartialResults set to false
      Test success: multipleIncrementTest
      Test starting: singleIncrementTest
        Description: Verifies the behaviour in the simplest case with just one result set 
        Step: Start a collection with two contributors
        Step: Send a audit trail result from contributor 1
        Step: Send a audit trail result from contributor 2
      Test success: singleIncrementTest
    Starting testcase AuditDatabaseTest
      Test starting: AuditDatabaseExtractionTest
        Description: Testing the connection to the audit trail service database especially with regards to extracting the data from it.
        Step: Setup the variables and constants.
        Step: Adds the variables to the settings and instantaites the database cache
        Step: Validate that the database is empty and then populate it.
        Step: Extract the audit trails
        Step: Test the extraction of FileID
        Step: Test the extraction of CollectionID
        Step: Perform extraction based on the component id.
        Step: Perform extraction based on the sequence number restriction
        Step: Perform extraction based on actor id restriction.
        Step: Perform extraction based on operation restriction.
        Step: Perform extraction based on date restriction.
        Step: Perform extraction based on fingerprint restriction.
        Step: Perform extraction based on operationID restriction.
      Test success: AuditDatabaseExtractionTest
      Test starting: AuditDatabaseGoodIngestTest
        Description: Testing good case ingest of audittrails into the database
        Step: Adds the variables to the settings and instantaites the database cache
        Step: Build test data
      Test success: AuditDatabaseGoodIngestTest
      Test starting: AuditDatabaseIngestTest
        Description: Testing ingest of audittrails into the database
        Step: Adds the variables to the settings and instantaites the database cache
        Step: Test ingesting with all data
        Step: Test ingesting with no timestamp
        Step: Test ingesting with no file action
        Step: Test ingesting with no actor
        Step: Test ingesting with no audit info
        Step: Test ingesting with no file id
        Step: Test ingesting with no info
        Step: Test ingesting with no component id
        Step: Test ingesting with no sequence number
        Step: Test ingest with very long auditInfo (255+)
        Step: Test ingest with very long info (255+)
      Test success: AuditDatabaseIngestTest
      Test starting: AuditDatabasePreservationTest
        Description: Tests the functions related to the preservation of the database.
        Step: Adds the variables to the settings and instantaites the database cache
        Step: Validate the preservation sequence number
        Step: Validate the insertion of the preservation sequence number
      Test success: AuditDatabasePreservationTest
    Starting testcase AuditServiceDatabaseMigrationTest
      Test starting: testMigratingAuditServiceDatabase
        Description: Tests that the database can be migrated to latest version with the provided scripts.
        Step: Validate setup
        Step: Perform migration
02:22:17.586 WARN  o.b.service.database.DatabaseUtils - Migrating AuditServiceDB from version 2 to 3.
02:22:18.000 WARN  o.b.service.database.DatabaseUtils - Migrating AuditServiceDB from version 3 to 4.
02:22:18.116 WARN  o.b.service.database.DatabaseUtils - Migrating AuditServiceDB from version 4 to 5.
      Test success: testMigratingAuditServiceDatabase
    Starting testcase LocalAuditPreservationTest
      Test starting: auditPreservationIngestTest
        Description: Tests the ingest of the audit trail preservation.
        Step: Setup variables and settings for the test
        Step: Create the preserver and populate the store
        Step: Call the preservation of audit trails now.
      Test success: auditPreservationIngestTest
    Starting testcase AuditCollectorTest
      Test starting: auditCollectorIntervalTest
        Description: Test that the collector calls the AuditClient at the correct intervals.
02:22:20.199 WARN  o.b.a.collector.IncrementalCollector - Received bad collection id! Expected 'TwoPillarCollection', but got 'dummy-collection'.
02:22:21.218 WARN  o.b.a.collector.IncrementalCollector - Received bad collection id! Expected 'TwoPillarCollection', but got 'dummy-collection'.
      Test success: auditCollectorIntervalTest
      Finished testcase
  Finished suite
Finished project
Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 22.391 sec - in TestSuite

Results :

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

[JENKINS] Recording test results
[INFO] 
[INFO] --- maven-war-plugin:2.4:war (default-war) @ bitrepository-audit-trail-service ---
[INFO] Packaging webapp
[INFO] Assembling webapp [bitrepository-audit-trail-service] in [/home/cibuild01/workspace/Bitrepository-sonar/bitrepository-audit-trail-service/target/bitrepository-audit-trail-service-1.7-SNAPSHOT]
[INFO] Processing war project
[INFO] Copying webapp resources [/home/cibuild01/workspace/Bitrepository-sonar/bitrepository-audit-trail-service/src/main/webapp]
[INFO] Webapp assembled in [102 msecs]
[INFO] Building war: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-audit-trail-service/target/bitrepository-audit-trail-service-1.7-SNAPSHOT.war
[INFO] 
[INFO] --- maven-jar-plugin:2.4:test-jar (default) @ bitrepository-audit-trail-service ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-audit-trail-service/target/bitrepository-audit-trail-service-1.7-SNAPSHOT-tests.jar
[INFO] 
[INFO] --- maven-source-plugin:2.2.1:jar-no-fork (attach-sources-no-fork) @ bitrepository-audit-trail-service ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-audit-trail-service/target/bitrepository-audit-trail-service-1.7-SNAPSHOT-sources.jar
[INFO] 
[INFO] --- maven-assembly-plugin:2.4:single (distribution) @ bitrepository-audit-trail-service ---
[INFO] Reading assembly descriptor: src/main/assembly/assembly.xml
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-audit-trail-service/target/bitrepository-audit-trail-service-1.7-SNAPSHOT-distribution.tar.gz
[INFO] 
[INFO] --- maven-install-plugin:2.5.1:install (default-install) @ bitrepository-audit-trail-service ---
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-audit-trail-service/target/bitrepository-audit-trail-service-1.7-SNAPSHOT.war to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-audit-trail-service/1.7-SNAPSHOT/bitrepository-audit-trail-service-1.7-SNAPSHOT.war
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-audit-trail-service/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-audit-trail-service/1.7-SNAPSHOT/bitrepository-audit-trail-service-1.7-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-audit-trail-service/target/bitrepository-audit-trail-service-1.7-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-audit-trail-service/1.7-SNAPSHOT/bitrepository-audit-trail-service-1.7-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-audit-trail-service/target/bitrepository-audit-trail-service-1.7-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-audit-trail-service/1.7-SNAPSHOT/bitrepository-audit-trail-service-1.7-SNAPSHOT-sources.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-audit-trail-service/target/bitrepository-audit-trail-service-1.7-SNAPSHOT-distribution.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-audit-trail-service/1.7-SNAPSHOT/bitrepository-audit-trail-service-1.7-SNAPSHOT-distribution.tar.gz
[JENKINS] Archiving disabled
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Reference Pillar 1.7-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-reference-pillar ---
[INFO] Deleting /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target
[INFO] 
[INFO] --- maven-dependency-plugin:2.8:unpack-dependencies (unpack-shared-sqlscripts) @ bitrepository-reference-pillar ---
[INFO] Unpacking /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-service/target/bitrepository-service-1.7-SNAPSHOT.jar to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/classes with includes "**/*.sql" and excludes ""
[INFO] 
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ bitrepository-reference-pillar ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 10 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ bitrepository-reference-pillar ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 44 source files to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/classes
[INFO] 
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ bitrepository-reference-pillar ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 12 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ bitrepository-reference-pillar ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 70 source files to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/test-classes
[INFO] 
[INFO] --- maven-surefire-plugin:2.17:test (default-test) @ bitrepository-reference-pillar ---
[INFO] Surefire report directory: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/surefire-reports

-------------------------------------------------------
 T E S T S
-------------------------------------------------------
Running TestSuite
Configuring TestNG with: TestNG652Configurator
Starting test project Reference Pillar Test
  Suite: Surefire suite
    Starting testcase ArchiveDirectoryTest
      Test starting: testArchiveDirectoryExistingFile
        Description: Test the ArchiveDirectory when the file exists
        Step: Setup
        Step: Validate the existence of the file
        Step: Delete the file.
      Test success: testArchiveDirectoryExistingFile
      Test starting: testArchiveDirectoryMissingFile
        Description: Test the ArchiveDirectory when the file is missing.
        Step: Setup
        Step: Validate the existence of the file
        Step: Delete the file.
      Test success: testArchiveDirectoryMissingFile
      Test starting: testArchiveDirectoryMoveFileToArchive
        Description: Testing the error scenarios when moving a file from tmp to archive for the ArchiveDirectory.
        Step: Setup
        Step: Moving file from tmp to archive
        Step: Create file in both tmp and archive.
        Step: Moving file from tmp to archive
        Step: Remove the file from archive and try again
      Test success: testArchiveDirectoryMoveFileToArchive
      Test starting: testArchiveDirectoryNewFile
        Description: Testing the ArchiveDirectory handling of a new file.
        Step: Setup
        Step: Retrieve tmp file
        Step: Request a new file for the tmp dir
        Step: Retrieve tmp file
        Step: Request another new file with the same name
        Step: Move the file from tmp to archive
      Test success: testArchiveDirectoryNewFile
      Test starting: testArchiveDirectoryRemoveFile
        Description: Testing the error scenarios when removing files from the archive.
        Step: Setup
        Step: Remove nonexisting file from archive
        Step: Remove nonexisting file from tmp
        Step: Create file in both tmp, archive and retain directories.
        Step: Remove the file from archive and tmp
      Test success: testArchiveDirectoryRemoveFile
    Starting testcase 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@841e575[correlationID=a1456d3b-7d14-41c6-9466-f639ccc26c78, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseIdentification-cibuild01-contributor, from=Pillar-badCaseIdentification, to=badCaseIdentification, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@27a5328c[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], fileID=DefaultFilebadCaseIdentification, pillarID=Pillar-badCaseIdentification, pillarChecksumSpec=<null>, timeToDeliver=<null>]
        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@20312893[correlationID=b6946531-68e9-455a-92bb-459e1792d787, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationMissingVerification-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationMissingVerification-cibuild01-contributor, from=Pillar-badCaseOperationMissingVerification, to=badCaseOperationMissingVerification, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@70eecdc2[responseCode=EXISTING_FILE_CHECKSUM_FAILURE, responseText=No mandatory checksum for destructive operation was supplied.], pillarID=Pillar-badCaseOperationMissingVerification, fileID=DefaultFilebadCaseOperationMissingVerification, checksumDataForExistingFile=<null>]
02:22:38.965 WARN  o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@7db0565c[origDateTime=2015-12-19T02:22:38.964+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCaseOperationMissingVerification, alarmText=No mandatory checksum for destructive operation was supplied., fileID=DefaultFilebadCaseOperationMissingVerification, collectionID=TwoPillarCollection]
          Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@54ec8cc9[correlationID=dbbc65f7-ddd6-446d-af97-9fc864b8cb8b, collectionID=TwoPillarCollection, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationMissingVerification-cibuild01-contributor, from=Pillar-badCaseOperationMissingVerification, to=<null>, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@7db0565c[origDateTime=2015-12-19T02:22:38.964+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCaseOperationMissingVerification, alarmText=No mandatory checksum for destructive operation was supplied., fileID=DefaultFilebadCaseOperationMissingVerification, collectionID=TwoPillarCollection]]
        Step: Retrieve the FinalResponse for the DeleteFile request
        Step: Pillar should have sent an alarm
      Test success: badCaseOperationMissingVerification
        Added fixture: Initialize a new Pillar.
      Test starting: badCaseOperationNoFile
        Description: Tests the DeleteFile functionality of the pillar for the failure scenario, where it does not have the file.
        Step: Set up constants and variables.
        Step: Setup for delivering pillar id and not having the file 
        Step: Create and send the actual DeleteFile message to the pillar.
          Result: Received message on TEST-TOPIC-badCaseOperationNoFile-cibuild01 : org.bitrepository.bitrepositorymessages.DeleteFileFinalResponse@3163987e[correlationID=34a60b97-1d5a-4b85-9629-50ad10075b2f, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@6c000e0c[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileID=DefaultFilebadCaseOperationNoFile, checksumDataForExistingFile=<null>]
        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@1ded7b14[correlationID=a71574b7-c5dc-4501-af91-e056bdee76f3, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseIdentification-cibuild01-contributor, from=Pillar-goodCaseIdentification, to=goodCaseIdentification, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@29be7749[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], fileID=DefaultFilegoodCaseIdentification, pillarID=Pillar-goodCaseIdentification, pillarChecksumSpec=<null>, timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@5f84abe8[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
    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@5e8c34a0[correlationID=2d90a27c-257f-4533-9d3c-1ed6868fd61f, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsMaximumNumberOfResults-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults, to=Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@7c1c5936[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to extract the requested audit trails.], contributor=Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults, resultAddress=<null>]
          Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsMaximumNumberOfResults-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsFinalResponse@ce9b9a9[correlationID=2d90a27c-257f-4533-9d3c-1ed6868fd61f, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsMaximumNumberOfResults-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults, to=Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@4ad3d266[responseCode=OPERATION_COMPLETED, responseText=<null>], contributor=Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@3533df16[resultAddress=<null>, auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@15d0849[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@4038cd3a[sequenceNumber=1, fileID=fileID1450488163299, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=CHECKSUM_CALCULATED, actionDateTime=2015-12-19T02:22:43.300+01:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@14ac77b9[sequenceNumber=2, fileID=fileID1450488163299, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=DELETE_FILE, actionDateTime=2015-12-19T02:22:43.301+01:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@3f4cd155[sequenceNumber=3, fileID=fileID1450488163299, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=FAILURE, actionDateTime=2015-12-19T02:22:43.301+01:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@563a89b5[sequenceNumber=4, fileID=fileID1450488163299, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=FILE_MOVED, actionDateTime=2015-12-19T02:22:43.301+01:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@506dcf55[sequenceNumber=5, fileID=fileID1450488163299, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=GET_CHECKSUMS, actionDateTime=2015-12-19T02:22:43.301+01:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails]}]], partialResult=true]
        Step: Validate the final response
      Test success: checksumPillarGetAuditTrailsMaximumNumberOfResults
        Added fixture: Initialize a new Pillar.
      Test starting: checksumPillarGetAuditTrailsSpecificRequests
        Description: Tests the GetAuditTrails functionality of the pillar for the successful scenario, where a specific audit trail are requested.
        Step: Set up constants and variables.
        Step: Send the identification request
          Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsResponse@61f39bb[correlationID=f1f3d0c4-4b44-47c5-a69e-c77365aed76e, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSpecificRequests-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSpecificRequests, to=Pillar-checksumPillarGetAuditTrailsSpecificRequests, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@249e0271[responseCode=IDENTIFICATION_POSITIVE, responseText=<null>]]
        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@53a665ad[correlationID=f1f3d0c4-4b44-47c5-a69e-c77365aed76e, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSpecificRequests-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSpecificRequests, to=Pillar-checksumPillarGetAuditTrailsSpecificRequests, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@2c0b4c83[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to extract the requested audit trails.], contributor=Pillar-checksumPillarGetAuditTrailsSpecificRequests, resultAddress=<null>]
          Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsFinalResponse@78525ef9[correlationID=f1f3d0c4-4b44-47c5-a69e-c77365aed76e, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSpecificRequests-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSpecificRequests, to=Pillar-checksumPillarGetAuditTrailsSpecificRequests, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@2d0ecb24[responseCode=OPERATION_COMPLETED, responseText=<null>], contributor=Pillar-checksumPillarGetAuditTrailsSpecificRequests, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@4d654825[resultAddress=<null>, auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@3bfc6a5e[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@51b35e4e[sequenceNumber=1, fileID=fileID1450488163856, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=OTHER, actionDateTime=2015-12-19T02:22:43.856+01:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails]}]], partialResult=false]
        Step: Receive and validate the progress response.
        Step: Receive and validate the final response
        Step: Make another request, where both ingested audit trails is requested
          Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsProgressResponse@abff8b7[correlationID=f1f3d0c4-4b44-47c5-a69e-c77365aed76e, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSpecificRequests-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSpecificRequests, to=Pillar-checksumPillarGetAuditTrailsSpecificRequests, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@6d7cada5[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to extract the requested audit trails.], contributor=Pillar-checksumPillarGetAuditTrailsSpecificRequests, resultAddress=<null>]
          Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsFinalResponse@350a94ce[correlationID=f1f3d0c4-4b44-47c5-a69e-c77365aed76e, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSpecificRequests-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSpecificRequests, to=Pillar-checksumPillarGetAuditTrailsSpecificRequests, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@7e00ed0f[responseCode=OPERATION_COMPLETED, responseText=<null>], contributor=Pillar-checksumPillarGetAuditTrailsSpecificRequests, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@b0fc838[resultAddress=<null>, auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@3964d79[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@51b35e4e[sequenceNumber=1, fileID=fileID1450488163856, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=OTHER, actionDateTime=2015-12-19T02:22:43.856+01:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@62db0521[sequenceNumber=2, fileID=notThisFile, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=UnknownActor, actionOnFile=FAILURE, actionDateTime=2015-12-19T02:22:43.856+01:00, info=badInfo, operationID=operationID, certificateID=certificateid, auditTrailInformation=WrongAuditTrail]}]], partialResult=false]
        Step: Receive and validate the progress response.
        Step: Receive and validate the final response
      Test success: checksumPillarGetAuditTrailsSpecificRequests
        Added fixture: Initialize a new Pillar.
      Test starting: checksumPillarGetAuditTrailsSuccessful
        Description: Tests the GetAuditTrails functionality of the pillar for the successful scenario, where all audit trails are requested.
        Step: Set up constants and variables.
        Step: Send the identification request
          Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSuccessful-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsResponse@44b18fe4[correlationID=5a434dc1-7f12-42cd-aa4a-7b162dab37f6, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSuccessful-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSuccessful-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSuccessful, to=Pillar-checksumPillarGetAuditTrailsSuccessful, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@2ba5aa7a[responseCode=IDENTIFICATION_POSITIVE, responseText=<null>]]
        Step: Make and send the request for the actual GetAuditTrails operation
          Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSuccessful-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsProgressResponse@4d3ca6c7[correlationID=5a434dc1-7f12-42cd-aa4a-7b162dab37f6, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSuccessful-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSuccessful-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSuccessful, to=Pillar-checksumPillarGetAuditTrailsSuccessful, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@22e5f96e[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to extract the requested audit trails.], contributor=Pillar-checksumPillarGetAuditTrailsSuccessful, resultAddress=<null>]
          Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSuccessful-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsFinalResponse@6a638c79[correlationID=5a434dc1-7f12-42cd-aa4a-7b162dab37f6, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSuccessful-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSuccessful-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSuccessful, to=Pillar-checksumPillarGetAuditTrailsSuccessful, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@6c931d35[responseCode=OPERATION_COMPLETED, responseText=<null>], contributor=Pillar-checksumPillarGetAuditTrailsSuccessful, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@44b194fe[resultAddress=<null>, auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@49122b8f[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@3fe46690[sequenceNumber=1, fileID=fileid, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=actor, actionOnFile=OTHER, actionDateTime=2015-12-19T02:22:44.227+01:00, info=info, operationID=operationID, certificateID=certificateID, auditTrailInformation=auditTrail]}]], partialResult=false]
        Step: Receive and validate the progress response.
        Step: Receive and validate the final response
      Test success: checksumPillarGetAuditTrailsSuccessful
    Starting testcase GetFileIDsTest
        Added fixture: Initialize a new Pillar.
      Test starting: badCaseIdentification
        Description: Tests the identification for a GetFileIDs operation on the pillar for the failure scenario, when the file is missing.
        Step: Set up constants and variables.
        Step: Setup for delivering pillar id and not having the file 
        Step: Create and send the identify request message.
02:22:44.560 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@2370ac7a[correlationID=95088878-3eda-48a2-be81-172cfcff3caa, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseIdentification-cibuild01-contributor, from=Pillar-badCaseIdentification, to=badCaseIdentification, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@534180a2[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseIdentification, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@6cf0a747[fileID=DefaultFilebadCaseIdentification, allFileIDs=<null>], timeToDeliver=<null>]
        Step: Retrieve and validate the response getPillarID() the pillar.
      Test success: badCaseIdentification
        Added fixture: Initialize a new Pillar.
      Test starting: badCaseOperationNoFile
        Description: Tests the GetFileIDs functionality of the pillar for the failure scenario, where it does not have the file.
        Step: Set up constants and variables.
        Step: Setup for not having the file
        Step: Create and send the actual GetFileIDs message to the pillar.
02:22:46.403 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@76464795[correlationID=bd75bf67-926f-40bd-8595-25b1f094a248, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@b34832b[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@48f4713c[fileID=DefaultFilebadCaseOperationNoFile, allFileIDs=<null>], resultingFileIDs=<null>, partialResult=<null>]
02:22:46.407 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@642413d4[correlationID=bd75bf67-926f-40bd-8595-25b1f094a248, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@fb2e3fd[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@48f4713c[fileID=DefaultFilebadCaseOperationNoFile, allFileIDs=<null>], resultingFileIDs=<null>, partialResult=<null>]
        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@642413d4[correlationID=bd75bf67-926f-40bd-8595-25b1f094a248, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@fb2e3fd[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@48f4713c[fileID=DefaultFilebadCaseOperationNoFile, allFileIDs=<null>], resultingFileIDs=<null>, partialResult=<null>]
02:22:47.419 WARN  o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: 
org.bitrepository.bitrepositorymessages.GetFileIDsFinalResponse@642413d4[correlationID=bd75bf67-926f-40bd-8595-25b1f094a248, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@fb2e3fd[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@48f4713c[fileID=DefaultFilebadCaseOperationNoFile, allFileIDs=<null>], resultingFileIDs=<null>, partialResult=<null>]
        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@717d7587[correlationID=ddad211e-adbc-46c9-a27d-799b060aeadf, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseIdentification-cibuild01-contributor, from=Pillar-goodCaseIdentification, to=goodCaseIdentification, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@3e906375[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], pillarID=Pillar-goodCaseIdentification, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@40230eb9[fileID=DefaultFilegoodCaseIdentification, allFileIDs=<null>], timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@5b7aa898[timeMeasureUnit=MILLISECONDS, timeMeasureValue=1000]]
        Step: Retrieve and validate the response getPillarID() the pillar.
      Test success: goodCaseIdentification
    Starting testcase GetFileTest
        Added fixture: Initialize a new Pillar.
      Test starting: badCaseIdentification
        Description: Tests the identification for a GetFile operation on the checksum pillar for the failure scenario, when the file is missing.
        Step: Set up constants and variables.
        Step: Setup for throwing an exception when asked to verify file existence
        Step: Create and send the identify request message.
          Result: Received message on TEST-TOPIC-badCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileResponse@68e02f33[correlationID=9bd350df-a622-4db8-8993-8560c510fa12, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseIdentification-cibuild01-contributor, from=Pillar-badCaseIdentification, to=badCaseIdentification, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@64942607[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], fileID=DefaultFilebadCaseIdentification, pillarID=Pillar-badCaseIdentification, timeToDeliver=<null>]
        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@b9d018b[correlationID=bfaa2a8c-d220-4dec-bf7b-5d90c36b0806, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseIdentification-cibuild01-contributor, from=Pillar-goodCaseIdentification, to=goodCaseIdentification, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@429aeac1[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], fileID=DefaultFilegoodCaseIdentification, pillarID=Pillar-goodCaseIdentification, timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@79eeff87[timeMeasureUnit=MILLISECONDS, timeMeasureValue=1000]]
        Step: Retrieve and validate the response getPillarID() the pillar.
      Test success: goodCaseIdentification
    Starting testcase PutFileTest
        Added fixture: Initialize a new Pillar.
      Test starting: badCaseIdentification
        Description: Tests the identification for a PutFile operation on the pillar for the failure scenario, when the file already exists.
        Step: Set up constants and variables.
        Step: Setup for already having the file and delivering pillar id
        Step: Create and send the identify request message.
          Result: Received message on TEST-TOPIC-badCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileResponse@3ad8717d[correlationID=c2da7233-911e-41c7-acc5-2f2dbeff5630, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseIdentification-cibuild01-contributor, from=Pillar-badCaseIdentification, to=badCaseIdentification, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@4293e066[responseCode=DUPLICATE_FILE_FAILURE, responseText=<null>], pillarID=Pillar-badCaseIdentification, fileID=DefaultFilebadCaseIdentification, pillarChecksumSpec=<null>, checksumDataForExistingFile=<null>, timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@d13960e[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@4b325930[correlationID=83d6f9ca-7a5e-4335-b6a9-137fccc1751b, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationFileAlreadyExists-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationFileAlreadyExists-cibuild01-contributor, from=Pillar-badCaseOperationFileAlreadyExists, to=badCaseOperationFileAlreadyExists, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@267f9765[responseCode=DUPLICATE_FILE_FAILURE, responseText=We already have the file], pillarID=Pillar-badCaseOperationFileAlreadyExists, pillarChecksumSpec=<null>, fileID=DefaultFilebadCaseOperationFileAlreadyExists, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForNewFile=<null>, checksumDataForExistingFile=<null>]
        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@626b639e[correlationID=7944870e-359d-4a4d-be34-fea403ee5dbb, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCasePutOperationNoValidationChecksum-cibuild01, replyTo=TEST-TOPIC-Pillar-badCasePutOperationNoValidationChecksum-cibuild01-contributor, from=Pillar-badCasePutOperationNoValidationChecksum, to=badCasePutOperationNoValidationChecksum, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@273fa9e[responseCode=NEW_FILE_CHECKSUM_FAILURE, responseText=A checksum is required for the PutFile operation to be performed.], pillarID=Pillar-badCasePutOperationNoValidationChecksum, pillarChecksumSpec=<null>, fileID=DefaultFilebadCasePutOperationNoValidationChecksum, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForNewFile=<null>, checksumDataForExistingFile=<null>]
02:22:56.334 WARN  o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@527a8665[origDateTime=2015-12-19T02:22:56.333+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCasePutOperationNoValidationChecksum, alarmText=A checksum is required for the PutFile operation to be performed., fileID=DefaultFilebadCasePutOperationNoValidationChecksum, collectionID=TwoPillarCollection]
          Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@7ab2a07e[correlationID=ccedddce-649d-4744-8caa-eac6a847da56, collectionID=TwoPillarCollection, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-Pillar-badCasePutOperationNoValidationChecksum-cibuild01-contributor, from=Pillar-badCasePutOperationNoValidationChecksum, to=<null>, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@527a8665[origDateTime=2015-12-19T02:22:56.333+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCasePutOperationNoValidationChecksum, alarmText=A checksum is required for the PutFile operation to be performed., fileID=DefaultFilebadCasePutOperationNoValidationChecksum, collectionID=TwoPillarCollection]]
        Step: Retrieve the FinalResponse for the PutFile request
        Step: Pillar should have sent an alarm
      Test success: badCasePutOperationNoValidationChecksum
        Added fixture: Initialize a new Pillar.
      Test starting: goodCaseIdentification
        Description: Tests the identification for a PutFile operation on the pillar for the successful scenario.
        Step: Set up constants and variables.
        Step: Setup for not already having the file and delivering pillar id
        Step: Create and send the identify request message.
          Result: Received message on TEST-TOPIC-goodCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileResponse@7a66c35a[correlationID=c35dcc66-ad16-4744-af8d-c3027d2499a8, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseIdentification-cibuild01-contributor, from=Pillar-goodCaseIdentification, to=goodCaseIdentification, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@7994a0d1[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], pillarID=Pillar-goodCaseIdentification, fileID=DefaultFilegoodCaseIdentification, pillarChecksumSpec=<null>, checksumDataForExistingFile=<null>, timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@73e4387[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@21002393[correlationID=b0e6918f-4525-445c-91de-61d5dfd716e4, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationWithChecksumReturn-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationWithChecksumReturn-cibuild01-contributor, from=Pillar-goodCaseOperationWithChecksumReturn, to=goodCaseOperationWithChecksumReturn, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@718989fa[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Started to receive data.], pillarID=Pillar-goodCaseOperationWithChecksumReturn, pillarChecksumSpec=<null>, 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@6568f998[correlationID=b0e6918f-4525-445c-91de-61d5dfd716e4, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationWithChecksumReturn-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationWithChecksumReturn-cibuild01-contributor, from=Pillar-goodCaseOperationWithChecksumReturn, to=goodCaseOperationWithChecksumReturn, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@45d4421d[responseCode=OPERATION_COMPLETED, responseText=<null>], pillarID=Pillar-goodCaseOperationWithChecksumReturn, pillarChecksumSpec=<null>, fileID=DefaultFilegoodCaseOperationWithChecksumReturn, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForNewFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@782fd504[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1537c744[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2015-12-19T02:22:57.829+01:00], checksumDataForExistingFile=<null>]
        Step: Retrieve the ProgressResponse for the GetFileIDs request
        Step: Retrieve the FinalResponse for the PutFile request
      Test success: goodCaseOperationWithChecksumReturn
    Starting testcase ReferenceArchiveTest
        Added fixture: Initialize the Reference pillar cache with an empty file in default collection TwoPillarCollection
      Test starting: testReferenceArchive
        Description: Test the ReferenceArchive.
        Step: Setup
        Step: test 'hasFile'
        Step: Test 'getFile'
        Step: Test getAllFileIDs
        Step: Test 'getFileAsInputstream'
        Step: Delete, recreate and delete again
        Step: Try to delete missing file.
        Step: Replace a file, which does not exist in the filedir.
        Step: Copy a file into the tmpDir and then use replace.
        Step: Try performing the replace, when the file in the tempdir has been removed.
      Test success: testReferenceArchive
    Starting testcase ChecksumDatabaseMigrationTest
      Test starting: testMigratingDatabaseChecksumsTable
        Description: Tests that the checksums table can be migrated from version 1 to 2, e.g. getting the column collectionid, which should be set to the default in settings.
        Step: Validate setup
        Step: Ingest a entry to the database without the collection id
        Step: Perform migration
02:23:01.272 WARN  o.b.service.database.DatabaseUtils - Migrating the checksums table from version 1 to 2 in the ChecksumDatabase.
02:23:01.473 WARN  o.b.service.database.DatabaseUtils - Migrating ChecksumDB from version 2 to 3.
        Step: Validate the entry
      Test success: testMigratingDatabaseChecksumsTable
    Starting testcase ChecksumDatabaseTest
      Test starting: testChecksumDatabaseExtraction
        Description: Test the extraction of data from the checksum database.
        Step: Check whether the default entry exists.
        Step: Extract calculation date
        Step: Extract the checksum
        Step: Extract the whole entry
        Step: Extract all entries
      Test success: testChecksumDatabaseExtraction
      Test starting: testDeletion
        Description: Test that data can be deleted from the database.
        Step: Check whether the default entry exists.
        Step: Remove the default entry
      Test success: testDeletion
      Test starting: testExtractionOfMissingData
        Description: Test the handling of bad arguments.
        Step: Try to get the date of a wrong file id.
        Step: Try to get the date of a wrong file id.
        Step: Try to remove a bad file id
      Test success: testExtractionOfMissingData
      Test starting: testGetFileIDsRestrictions
        Description: Tests the restrictions on the GetFileIDs call to the database.
        Step: Instantiate database with appropriate data.
        Step: Test with no time restrictions and 10000 max_results
        Step: Test with minimum-date earlier than first file
        Step: Test with maximum-date earlier than first file
        Step: Test with minimum-date set to later than second file.
        Step: Test with maximum-date set to later than second file.
        Step: Test with minimum-date set to middle date.
        Step: Test with maximum-date set to middle date.
        Step: Test with both minimum-date and maximum-date set to middle date.
        Step: Test the first file-id, with no other restrictions
        Step: Test the second file-id, with no other restrictions
        Step: Test the date for the first file-id, while requesting the second file-id
      Test success: testGetFileIDsRestrictions
      Test starting: testReplacingExistingEntry
        Description: Test that an entry can be replaced by another in the database.
        Step: Check whether the default entry exists.
        Step: Replace the checksum and date
      Test success: testReplacingExistingEntry
      Test starting: testSpecifiedEntryExtraction
        Description: Test that specific entries can be extracted. Has two entries in the database: one for the current timestamp and one for the epoch.
        Step: Instantiate database with appropriate data.
        Step: Extract with out restrictions
        Step: Extract with a maximum of 1 entry
        Step: Extract all dates older than this tests instantiation
        Step: Extract all dates newer than this tests instantiation
        Step: Extract all dates older than the newest instance
        Step: Extract all dates newer than the oldest instantiation
      Test success: testSpecifiedEntryExtraction
    Starting testcase FullPillarModelTest
      Test starting: testPillarModelBasicFunctionality
        Description: Test the basic functions of the full reference pillar model.
        Step: Check the pillar id in the pillar model
        Step: Ask whether it can handle a file of size 0
        Step: Ask whether it can handle a file of maximum size
        Step: Check the ChecksumPillarSpec
      Test success: testPillarModelBasicFunctionality
      Test starting: testPillarModelHasFile
        Description: Test that the file exists, when placed in the archive and cache
        Step: Setup
        Step: Check whether file exists and retrieve it.
        Step: Verify that no exceptions are thrown when verifying file existance.
        Step: Check retrieval of non-default checksum
      Test success: testPillarModelHasFile
      Test starting: testPillarModelNoFile
        Description: Test that the file exists, when placed in the archive and cache
        Step: Setup
        Step: Check whether file exists and try to retrieve it.
        Step: Verify that anexceptions are thrown when verifying file existance.
02:23:14.322 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 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@52463255[correlationID=fc62ed82-296c-4890-994b-96a054b8e8af, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseIdentification-cibuild01-contributor, from=Pillar-badCaseIdentification, to=badCaseIdentification, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@66f5770e[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@16024b49[fileID=DefaultFilebadCaseIdentification, allFileIDs=<null>], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@53f94afe[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], pillarID=Pillar-badCaseIdentification, pillarChecksumSpec=<null>, timeToDeliver=<null>]
        Step: Retrieve and validate the response getPillarID() the pillar.
      Test success: badCaseIdentification
        Added fixture: Initialize a new Pillar.
      Test starting: badCaseOperationNoFile
        Description: Tests the GetChecksums functionality of the pillar for the failure scenario, where it does not have the file.
        Step: Set up constants and variables.
        Step: Setup for not having the file
        Step: Create and send the actual GetChecksums message to the pillar.
02:23:15.652 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@7da6d695[correlationID=54d25b62-1ffc-4ed5-97ab-3be7e063b897, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@74a991cf[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6097f225[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], resultingChecksums=<null>, partialResult=<null>]
02:23:15.665 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@26c1f3eb[correlationID=54d25b62-1ffc-4ed5-97ab-3be7e063b897, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@79982bcc[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6097f225[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], resultingChecksums=<null>, partialResult=<null>]
02:23:15.667 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@79f3f34c[correlationID=54d25b62-1ffc-4ed5-97ab-3be7e063b897, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@50841932[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6097f225[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], resultingChecksums=<null>, partialResult=<null>]
        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@26c1f3eb[correlationID=54d25b62-1ffc-4ed5-97ab-3be7e063b897, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@79982bcc[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6097f225[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], resultingChecksums=<null>, partialResult=<null>]
org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@79f3f34c[correlationID=54d25b62-1ffc-4ed5-97ab-3be7e063b897, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@50841932[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6097f225[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], resultingChecksums=<null>, partialResult=<null>]
02:23:16.680 WARN  o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: 
org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@26c1f3eb[correlationID=54d25b62-1ffc-4ed5-97ab-3be7e063b897, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@79982bcc[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6097f225[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], resultingChecksums=<null>, partialResult=<null>]
org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@79f3f34c[correlationID=54d25b62-1ffc-4ed5-97ab-3be7e063b897, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@50841932[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6097f225[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], resultingChecksums=<null>, partialResult=<null>]
        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@7dcc0296[correlationID=5a25d2e9-9e6c-428e-86e3-51cf1fc12ce1, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseIdentification-cibuild01-contributor, from=Pillar-goodCaseIdentification, to=goodCaseIdentification, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@6b8f87dc[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@4c25201[fileID=DefaultFilegoodCaseIdentification, allFileIDs=<null>], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@4faaff61[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], pillarID=Pillar-goodCaseIdentification, pillarChecksumSpec=<null>, timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@526f8cb0[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@470866d1[correlationID=5596f2d8-046a-43fc-89e8-0cf87662c1b4, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationAllFiles-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationAllFiles-cibuild01-contributor, from=Pillar-goodCaseOperationAllFiles, to=goodCaseOperationAllFiles, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@11267e87[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to calculate checksums.], pillarID=Pillar-goodCaseOperationAllFiles, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@118c1faa[fileID=<null>, allFileIDs=true], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@da5b46f[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], resultAddress=<null>]
          Result: Received message on TEST-TOPIC-goodCaseOperationAllFiles-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@7a491a60[correlationID=5596f2d8-046a-43fc-89e8-0cf87662c1b4, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationAllFiles-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationAllFiles-cibuild01-contributor, from=Pillar-goodCaseOperationAllFiles, to=goodCaseOperationAllFiles, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@80b6098[responseCode=OPERATION_COMPLETED, responseText=<null>], pillarID=Pillar-goodCaseOperationAllFiles, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@da5b46f[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], resultingChecksums=org.bitrepository.bitrepositoryelements.ResultingChecksums@5c30decf[resultAddress=<null>, checksumDataItems={org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@7827cdfc[fileID=DefaultFile, checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2015-12-19T02:23:17.958+01:00],org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@4a0f4282[fileID=goodCaseOperationAllFiles-cibuild01--Test-File-1450488197955, 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@318a81a0[correlationID=575f8962-3c93-474d-8825-4c246cf5a102, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationSingleFile-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationSingleFile-cibuild01-contributor, from=Pillar-goodCaseOperationSingleFile, to=goodCaseOperationSingleFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@f73a7cf[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to calculate checksums.], pillarID=Pillar-goodCaseOperationSingleFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@4198921f[fileID=DefaultFilegoodCaseOperationSingleFile, allFileIDs=<null>], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@44181746[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], resultAddress=<null>]
          Result: Received message on TEST-TOPIC-goodCaseOperationSingleFile-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@21fa19e4[correlationID=575f8962-3c93-474d-8825-4c246cf5a102, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationSingleFile-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationSingleFile-cibuild01-contributor, from=Pillar-goodCaseOperationSingleFile, to=goodCaseOperationSingleFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@33a58fcb[responseCode=OPERATION_COMPLETED, responseText=<null>], pillarID=Pillar-goodCaseOperationSingleFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@44181746[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], resultingChecksums=org.bitrepository.bitrepositoryelements.ResultingChecksums@36a8ebca[resultAddress=<null>, checksumDataItems={org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@328e687e[fileID=DefaultFilegoodCaseOperationSingleFile, checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2015-12-19T02:23:18.182+01:00]}], partialResult=false]
        Step: Retrieve the ProgressResponse for the GetChecksums request
        Step: Retrieve the FinalResponse for the GetChecksums request
      Test success: goodCaseOperationSingleFile
        Added fixture: Initialize a new Pillar.
      Test starting: testRestrictions
        Description: Tests that the restrictions are correctly passed on to the cache.
        Step: Set up constants and variables.
        Step: Setup for only delivering result-set when the correct restrictions are given.
        Step: Create and send the actual GetChecksums message to the pillar.
          Result: Received message on TEST-TOPIC-testRestrictions-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsProgressResponse@eef6e[correlationID=e9e761b4-b1b5-409a-9669-ab2db33413cb, collectionID=TwoPillarCollection, destination=TEST-TOPIC-testRestrictions-cibuild01, replyTo=TEST-TOPIC-Pillar-testRestrictions-cibuild01-contributor, from=Pillar-testRestrictions, to=testRestrictions, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@56b66cc6[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to calculate checksums.], pillarID=Pillar-testRestrictions, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@6f076c53[fileID=<null>, allFileIDs=true], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@3c39c739[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], resultAddress=<null>]
          Result: Received message on TEST-TOPIC-testRestrictions-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@4b3b2a4f[correlationID=e9e761b4-b1b5-409a-9669-ab2db33413cb, collectionID=TwoPillarCollection, destination=TEST-TOPIC-testRestrictions-cibuild01, replyTo=TEST-TOPIC-Pillar-testRestrictions-cibuild01-contributor, from=Pillar-testRestrictions, to=testRestrictions, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@2e8eafb2[responseCode=OPERATION_COMPLETED, responseText=<null>], pillarID=Pillar-testRestrictions, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@3c39c739[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], resultingChecksums=org.bitrepository.bitrepositoryelements.ResultingChecksums@7a3f3bc4[resultAddress=<null>, checksumDataItems={org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@8cd2bb5[fileID=DefaultFile, checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2015-12-19T02:23:18.360+01:00]}], partialResult=false]
        Step: Retrieve the ProgressResponse for the GetChecksums request
        Step: Retrieve the FinalResponse for the GetChecksums request
      Test success: testRestrictions
      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 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@145ce025[correlationID=28aec643-1900-4424-ae84-9746b4544f4f, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseIdentification-cibuild01-contributor, from=Pillar-badCaseIdentification, to=badCaseIdentification, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@1deca369[responseCode=FILE_NOT_FOUND_FAILURE, responseText=Could not find the requested file to delete.], fileID=DefaultFile, pillarID=Pillar-badCaseIdentification, pillarChecksumSpec=<null>, timeToDeliver=<null>]
        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@29ec5005[correlationID=9ecadbad-2e7d-492b-9a31-05a114fce6bf, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationMissingFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationMissingFile-cibuild01-contributor, from=Pillar-badCaseOperationMissingFile, to=badCaseOperationMissingFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@42ceb67f[responseCode=FILE_NOT_FOUND_FAILURE, responseText=The file 'DefaultFile' has been requested, but we do not have that file!], pillarID=Pillar-badCaseOperationMissingFile, pillarChecksumSpec=<null>, fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForExistingFile=<null>, checksumDataForNewFile=<null>]
        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@755057c7[correlationID=1150a096-647d-4d3f-9963-ea9b78a0a7ec, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoDestructiveChecksum-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoDestructiveChecksum-cibuild01-contributor, from=Pillar-badCaseOperationNoDestructiveChecksum, to=badCaseOperationNoDestructiveChecksum, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@4d62bb8b[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>, fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForExistingFile=<null>, checksumDataForNewFile=<null>]
02:23:21.493 WARN  o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@70f37190[origDateTime=2015-12-19T02:23:21.492+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCaseOperationNoDestructiveChecksum, alarmText=According to the contract a checksum for file to be deleted during the replacing operation is required., fileID=DefaultFile, collectionID=TwoPillarCollection]
          Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@1d642682[correlationID=807ca42b-7936-4877-822f-732047385028, collectionID=TwoPillarCollection, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoDestructiveChecksum-cibuild01-contributor, from=Pillar-badCaseOperationNoDestructiveChecksum, to=<null>, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@70f37190[origDateTime=2015-12-19T02:23:21.492+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCaseOperationNoDestructiveChecksum, alarmText=According to the contract a checksum for file to be deleted during the replacing operation is required., fileID=DefaultFile, collectionID=TwoPillarCollection]]
        Step: Retrieve the FinalResponse for the ReplaceFile request
        Step: Pillar should have sent an alarm
      Test success: badCaseOperationNoDestructiveChecksum
        Added fixture: Initialize a new Pillar.
      Test starting: badCaseOperationNoValidationChecksum
        Description: Tests the ReplaceFile operation on the pillar for the failure scenario, when no validation checksum is given for the new file, but though is required.
        Step: Set up constants and variables.
        Step: Setup for having the file and delivering pillar id
        Step: Create and send the identify request message.
          Result: Received message on TEST-TOPIC-badCaseOperationNoValidationChecksum-cibuild01 : org.bitrepository.bitrepositorymessages.ReplaceFileFinalResponse@8616368[correlationID=61ee37bd-5668-499d-86ff-da8200e21405, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoValidationChecksum-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoValidationChecksum-cibuild01-contributor, from=Pillar-badCaseOperationNoValidationChecksum, to=badCaseOperationNoValidationChecksum, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@c4fc610[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>, fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForExistingFile=<null>, checksumDataForNewFile=<null>]
02:23:21.697 WARN  o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@2c8469fe[origDateTime=2015-12-19T02:23:21.697+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCaseOperationNoValidationChecksum, alarmText=According to the contract a checksum for new file in the replacing operation is required., fileID=DefaultFile, collectionID=TwoPillarCollection]
          Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@78626209[correlationID=3c5fe0ce-9aed-459b-bd87-d449b5741d77, collectionID=TwoPillarCollection, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoValidationChecksum-cibuild01-contributor, from=Pillar-badCaseOperationNoValidationChecksum, to=<null>, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@2c8469fe[origDateTime=2015-12-19T02:23:21.697+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCaseOperationNoValidationChecksum, alarmText=According to the contract a checksum for new file in the replacing operation is required., fileID=DefaultFile, collectionID=TwoPillarCollection]]
        Step: Retrieve the FinalResponse for the ReplaceFile request
        Step: Pillar should have sent an alarm
      Test success: badCaseOperationNoValidationChecksum
        Added fixture: Initialize a new Pillar.
      Test starting: badCaseOperationWrongDestructiveChecksum
        Description: Tests the ReplaceFile operation on the pillar for the failure scenario, when the checksum for the destructive action is different from the one in the cache.
        Step: Set up constants and variables.
        Step: Setup for having the file and delivering pillar id
        Step: Create and send the identify request message.
02:23:21.895 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@18f493d7[correlationID=cd5c450b-a546-41b4-9bc5-7602e21f247b, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationWrongDestructiveChecksum-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationWrongDestructiveChecksum-cibuild01-contributor, from=Pillar-badCaseOperationWrongDestructiveChecksum, to=badCaseOperationWrongDestructiveChecksum, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@2d036335[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>, fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForExistingFile=<null>, checksumDataForNewFile=<null>]
02:23:21.896 WARN  o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@4a3e1b5d[origDateTime=2015-12-19T02:23:21.895+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCaseOperationWrongDestructiveChecksum, alarmText=Requested to replace the file 'DefaultFile' with checksum '1234cccccccc4321', but our file had a different checksum., fileID=DefaultFile, collectionID=TwoPillarCollection]
          Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@587df3e4[correlationID=9a893243-4e09-4f11-886c-457a8c8bf258, collectionID=TwoPillarCollection, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationWrongDestructiveChecksum-cibuild01-contributor, from=Pillar-badCaseOperationWrongDestructiveChecksum, to=<null>, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@4a3e1b5d[origDateTime=2015-12-19T02:23:21.895+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCaseOperationWrongDestructiveChecksum, alarmText=Requested to replace the file 'DefaultFile' with checksum '1234cccccccc4321', but our file had a different checksum., fileID=DefaultFile, collectionID=TwoPillarCollection]]
        Step: Retrieve the FinalResponse for the ReplaceFile request
        Step: Pillar should have sent an alarm
      Test success: badCaseOperationWrongDestructiveChecksum
        Added fixture: Initialize a new Pillar.
      Test starting: goodCaseIdentification
        Description: Tests the identification for a ReplaceFile operation on the pillar for the successful scenario.
        Step: Set up constants and variables.
        Step: Setup for having the file and delivering pillar id
        Step: Create and send the identify request message.
          Result: Received message on TEST-TOPIC-goodCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileResponse@181a6784[correlationID=5b21057a-8d80-45a1-bfd7-1f8c4fb77d10, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseIdentification-cibuild01-contributor, from=Pillar-goodCaseIdentification, to=goodCaseIdentification, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@a589070[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], fileID=DefaultFile, pillarID=Pillar-goodCaseIdentification, pillarChecksumSpec=<null>, timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@747216b6[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@140e003e[correlationID=ce56a355-dabc-4e39-b423-de13448c4ca2, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperation-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperation-cibuild01-contributor, from=Pillar-goodCaseOperation, to=goodCaseOperation, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@2197990b[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Performing the ReplaceFileRequest for file 'DefaultFile' at 'TwoPillarCollection'.], pillarID=Pillar-goodCaseOperation, pillarChecksumSpec=<null>, 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@63b0aeb1[correlationID=ce56a355-dabc-4e39-b423-de13448c4ca2, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperation-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperation-cibuild01-contributor, from=Pillar-goodCaseOperation, to=goodCaseOperation, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@75b5d09[responseCode=OPERATION_COMPLETED, responseText=<null>], pillarID=Pillar-goodCaseOperation, pillarChecksumSpec=<null>, fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForExistingFile=<null>, checksumDataForNewFile=<null>]
        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@1435feb6[correlationID=b612213e-3569-4e98-bb41-4c71cb543925, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationWithChecksumsReturn-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationWithChecksumsReturn-cibuild01-contributor, from=Pillar-goodCaseOperationWithChecksumsReturn, to=goodCaseOperationWithChecksumsReturn, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@34fe89a5[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Performing the ReplaceFileRequest for file 'DefaultFile' at 'TwoPillarCollection'.], pillarID=Pillar-goodCaseOperationWithChecksumsReturn, pillarChecksumSpec=<null>, 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@71acf065[correlationID=b612213e-3569-4e98-bb41-4c71cb543925, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationWithChecksumsReturn-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationWithChecksumsReturn-cibuild01-contributor, from=Pillar-goodCaseOperationWithChecksumsReturn, to=goodCaseOperationWithChecksumsReturn, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@3705e3fb[responseCode=OPERATION_COMPLETED, responseText=<null>], pillarID=Pillar-goodCaseOperationWithChecksumsReturn, pillarChecksumSpec=<null>, fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@cfe7be3[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@4c0d7878[checksumType=HMAC_SHA512, checksumSalt={97,98}, otherChecksumType=<null>], checksumValue={18,52,-52,-52,-52,-52,67,34}, calculationTimestamp=2015-12-19T02:23:24.407+01:00], checksumDataForNewFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@5a349644[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@42b6acc2[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2015-12-19T02:23:24.407+01:00]]
        Step: Retrieve the ProgressResponse for the GetFileIDs request
        Step: Retrieve the FinalResponse for the ReplaceFile request
      Test success: goodCaseOperationWithChecksumsReturn
      Test starting: getPillarCollectionsTest
      Test success: getPillarCollectionsTest
    Starting testcase ChecksumEntryTest
      Test starting: testExtendedTestCase
        Description: Test the ChecksumEntry
        Step: Create a ChecksumEntry
        Step: Change the value of the checksum
        Step: Change the value of the calculation date
      Test success: testExtendedTestCase
    Starting testcase MediatorTest
      Test starting: testMediatorRuntimeExceptionHandling
        Description: Tests the handling of a runtime exception
        Step: Setup create and start the mediator.
        Step: Send a request to the mediator.
02:23:26.543 WARN  o.b.pillar.MediatorTest$TestMediator - Unexpected exception caught.
java.lang.RuntimeException: I am supposed to throw a RuntimeException
	at org.bitrepository.pillar.MediatorTest$ErroneousRequestHandler.processRequest(MediatorTest.java:122) ~[test-classes/:na]
	at org.bitrepository.pillar.MediatorTest$ErroneousRequestHandler.processRequest(MediatorTest.java:113) ~[test-classes/:na]
	at org.bitrepository.pillar.messagehandler.PillarMediator.handleRequest(PillarMediator.java:80) ~[classes/:na]
	at org.bitrepository.service.contributor.AbstractContributorMediator$GeneralRequestHandler.onMessage(AbstractContributorMediator.java:101) [bitrepository-service-1.7-SNAPSHOT.jar:1.7-SNAPSHOT]
	at org.bitrepository.protocol.messagebus.SimpleMessageBus.lambda$sendMessage$0(SimpleMessageBus.java:73) [bitrepository-core-1.7-SNAPSHOT.jar:1.7-SNAPSHOT]
	at org.bitrepository.protocol.messagebus.SimpleMessageBus$$Lambda$1/144699438.accept(Unknown Source) [bitrepository-core-1.7-SNAPSHOT.jar:1.7-SNAPSHOT]
	at java.lang.Iterable.forEach(Iterable.java:75) [na:1.8.0_11]
	at org.bitrepository.protocol.messagebus.SimpleMessageBus.sendMessage(SimpleMessageBus.java:73) [bitrepository-core-1.7-SNAPSHOT.jar:1.7-SNAPSHOT]
	at org.bitrepository.pillar.MediatorTest.testMediatorRuntimeExceptionHandling(MediatorTest.java:84) [test-classes/:na]
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_11]
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_11]
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_11]
	at java.lang.reflect.Method.invoke(Method.java:483) ~[na:1.8.0_11]
	at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84) [testng-6.8.8.jar:na]
	at org.testng.internal.Invoker.invokeMethod(Invoker.java:714) [testng-6.8.8.jar:na]
	at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901) [testng-6.8.8.jar:na]
	at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231) [testng-6.8.8.jar:na]
	at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127) [testng-6.8.8.jar:na]
	at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111) [testng-6.8.8.jar:na]
	at org.testng.TestRunner.privateRun(TestRunner.java:767) [testng-6.8.8.jar:na]
	at org.testng.TestRunner.run(TestRunner.java:617) [testng-6.8.8.jar:na]
	at org.testng.SuiteRunner.runTest(SuiteRunner.java:348) [testng-6.8.8.jar:na]
	at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:343) [testng-6.8.8.jar:na]
	at org.testng.SuiteRunner.privateRun(SuiteRunner.java:305) [testng-6.8.8.jar:na]
	at org.testng.SuiteRunner.run(SuiteRunner.java:254) [testng-6.8.8.jar:na]
	at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) [testng-6.8.8.jar:na]
	at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) [testng-6.8.8.jar:na]
	at org.testng.TestNG.runSuitesSequentially(TestNG.java:1224) [testng-6.8.8.jar:na]
	at org.testng.TestNG.runSuitesLocally(TestNG.java:1149) [testng-6.8.8.jar:na]
	at org.testng.TestNG.run(TestNG.java:1057) [testng-6.8.8.jar:na]
	at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:115) [surefire-testng-2.17.jar:2.17]
	at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:204) [surefire-testng-2.17.jar:2.17]
	at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:107) [surefire-testng-2.17.jar:2.17]
	at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:112) [surefire-testng-2.17.jar:2.17]
	at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) [surefire-booter-2.17.jar:2.17]
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) [surefire-booter-2.17.jar:2.17]
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) [surefire-booter-2.17.jar:2.17]
          Result: Received message on TEST-TOPIC-testMediatorRuntimeExceptionHandling-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetStatusResponse@340ef431[correlationID=089c1cd6-d9a9-4705-8962-7ff91081e2ce, collectionID=TwoPillarCollection, destination=TEST-TOPIC-testMediatorRuntimeExceptionHandling-cibuild01, replyTo=TEST-TOPIC-MediatorUnderTest-cibuild01-contributor, from=MediatorUnderTest, to=MediatorUnderTest, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@50d02417[responseCode=FAILURE, responseText=java.lang.RuntimeException: I am supposed to throw a RuntimeException], contributor=TEST-TOPIC-cibuild01, timeToDeliver=<null>]
02:23:26.544 WARN  o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@314e240c[origDateTime=2015-12-19T02:23:26.544+01:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MediatorUnderTest, alarmText=java.lang.RuntimeException: I am supposed to throw a RuntimeException, fileID=<null>, collectionID=<null>]
          Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@7222e168[correlationID=84e1e706-0002-495c-96a7-732bec70b784, collectionID=<null>, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-MediatorUnderTest-cibuild01-contributor, from=MediatorUnderTest, to=<null>, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@314e240c[origDateTime=2015-12-19T02:23:26.544+01:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MediatorUnderTest, alarmText=java.lang.RuntimeException: I am supposed to throw a RuntimeException, fileID=<null>, collectionID=<null>]]
      Test success: testMediatorRuntimeExceptionHandling
      Finished testcase
  Finished suite
Finished project
Tests run: 57, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 58.541 sec - in TestSuite

Results :

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

[JENKINS] Recording test results
[INFO] 
[INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ bitrepository-reference-pillar ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.7-SNAPSHOT.jar
[INFO] 
[INFO] --- maven-jar-plugin:2.4:test-jar (default) @ bitrepository-reference-pillar ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.7-SNAPSHOT-tests.jar
[INFO] 
[INFO] --- maven-source-plugin:2.2.1:jar-no-fork (attach-sources-no-fork) @ bitrepository-reference-pillar ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.7-SNAPSHOT-sources.jar
[INFO] 
[INFO] --- maven-assembly-plugin:2.4:single (distribution) @ bitrepository-reference-pillar ---
[INFO] Reading assembly descriptor: src/main/assembly/assembly.xml
[INFO] Reading assembly descriptor: src/test/assembly/assembly.xml
[INFO] Reading assembly descriptor: src/main/assembly/deploy-assembly.xml
[INFO] Reading assembly descriptor: src/test/assembly/test-deploy-assembly.xml
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.7-SNAPSHOT-distribution.tar.gz
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.7-SNAPSHOT-acceptance-test.tar.gz
[WARNING] Entry: bitrepository-reference-pillar-1.7-SNAPSHOT/lib/bitrepository-reference-pillar-1.7-SNAPSHOT-tests.jar longer than 100 characters.
[WARNING] Resulting tar file can only be processed successfully by GNU compatible tar commands
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.7-SNAPSHOT-deploy.tar.gz
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.7-SNAPSHOT-acceptance-test-deploy.tar.gz
[INFO] 
[INFO] --- maven-install-plugin:2.5.1:install (default-install) @ bitrepository-reference-pillar ---
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.7-SNAPSHOT.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.7-SNAPSHOT/bitrepository-reference-pillar-1.7-SNAPSHOT.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.7-SNAPSHOT/bitrepository-reference-pillar-1.7-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.7-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.7-SNAPSHOT/bitrepository-reference-pillar-1.7-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.7-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.7-SNAPSHOT/bitrepository-reference-pillar-1.7-SNAPSHOT-sources.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.7-SNAPSHOT-distribution.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.7-SNAPSHOT/bitrepository-reference-pillar-1.7-SNAPSHOT-distribution.tar.gz
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.7-SNAPSHOT-acceptance-test.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.7-SNAPSHOT/bitrepository-reference-pillar-1.7-SNAPSHOT-acceptance-test.tar.gz
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.7-SNAPSHOT-deploy.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.7-SNAPSHOT/bitrepository-reference-pillar-1.7-SNAPSHOT-deploy.tar.gz
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.7-SNAPSHOT-acceptance-test-deploy.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.7-SNAPSHOT/bitrepository-reference-pillar-1.7-SNAPSHOT-acceptance-test-deploy.tar.gz
[JENKINS] Archiving disabled
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Monitoring Service 1.7-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-monitoring-service ---
[INFO] Deleting /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-monitoring-service/target
[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-sonar/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-sonar/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-sonar/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-sonar/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-sonar/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 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.
02:23:39.492 WARN  o.b.m.a.BasicMonitoringServiceAlerter - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@7ef82753[origDateTime=2015-12-19T02:23:39.488+01:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MonitorAlerterUnderTest, alarmText=The following components have become unresponsive: [TestMonitorService], fileID=<null>, collectionID=<null>]
          Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@4d1c005e[correlationID=88f5c085-7b28-49fd-a409-467571067027, collectionID=<null>, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-MonitorAlerterUnderTest-cibuild01-contributor, from=MonitorAlerterUnderTest, to=<null>, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@7ef82753[origDateTime=2015-12-19T02:23:39.488+01:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MonitorAlerterUnderTest, alarmText=The following components have become unresponsive: [TestMonitorService], fileID=<null>, collectionID=<null>]]
      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
    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.
02:23:42.403 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
      Finished testcase
  Finished suite
Finished project
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 8.627 sec - in TestSuite

Results :

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

[JENKINS] Recording test results
[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-sonar/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.7-SNAPSHOT]
[INFO] Processing war project
[INFO] Copying webapp resources [/home/cibuild01/workspace/Bitrepository-sonar/bitrepository-monitoring-service/src/main/webapp]
[INFO] Webapp assembled in [102 msecs]
[INFO] Building war: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.7-SNAPSHOT.war
[INFO] 
[INFO] --- maven-jar-plugin:2.4:test-jar (default) @ bitrepository-monitoring-service ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.7-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-sonar/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.7-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-sonar/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.7-SNAPSHOT-distribution.tar.gz
[INFO] 
[INFO] --- maven-install-plugin:2.5.1:install (default-install) @ bitrepository-monitoring-service ---
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.7-SNAPSHOT.war to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-monitoring-service/1.7-SNAPSHOT/bitrepository-monitoring-service-1.7-SNAPSHOT.war
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-monitoring-service/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-monitoring-service/1.7-SNAPSHOT/bitrepository-monitoring-service-1.7-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.7-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-monitoring-service/1.7-SNAPSHOT/bitrepository-monitoring-service-1.7-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.7-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-monitoring-service/1.7-SNAPSHOT/bitrepository-monitoring-service-1.7-SNAPSHOT-sources.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.7-SNAPSHOT-distribution.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-monitoring-service/1.7-SNAPSHOT/bitrepository-monitoring-service-1.7-SNAPSHOT-distribution.tar.gz
[JENKINS] Archiving disabled
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Webclient 1.7-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-webclient ---
[INFO] Deleting /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-webclient/target
[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-sonar/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-sonar/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] --- maven-war-plugin:2.4:war (default-war) @ bitrepository-webclient ---
[INFO] Packaging webapp
[INFO] Assembling webapp [bitrepository-webclient] in [/home/cibuild01/workspace/Bitrepository-sonar/bitrepository-webclient/target/bitrepository-webclient-1.7-SNAPSHOT]
[INFO] Processing war project
[INFO] Copying webapp webResources [/home/cibuild01/workspace/Bitrepository-sonar/bitrepository-webclient/src/main/webapp] to [/home/cibuild01/workspace/Bitrepository-sonar/bitrepository-webclient/target/bitrepository-webclient-1.7-SNAPSHOT]
[INFO] Copying webapp resources [/home/cibuild01/workspace/Bitrepository-sonar/bitrepository-webclient/src/main/webapp]
[INFO] Webapp assembled in [1367 msecs]
[INFO] Building war: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-webclient/target/bitrepository-webclient-1.7-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-sonar/bitrepository-webclient/target/bitrepository-webclient-1.7-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-sonar/bitrepository-webclient/target/bitrepository-webclient-1.7-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-sonar/bitrepository-webclient/target/bitrepository-webclient-1.7-SNAPSHOT-distribution.tar.gz
[INFO] 
[INFO] --- maven-install-plugin:2.5.1:install (default-install) @ bitrepository-webclient ---
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-webclient/target/bitrepository-webclient-1.7-SNAPSHOT.war to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-webclient/1.7-SNAPSHOT/bitrepository-webclient-1.7-SNAPSHOT.war
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-webclient/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-webclient/1.7-SNAPSHOT/bitrepository-webclient-1.7-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-webclient/target/bitrepository-webclient-1.7-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-webclient/1.7-SNAPSHOT/bitrepository-webclient-1.7-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-webclient/target/bitrepository-webclient-1.7-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-webclient/1.7-SNAPSHOT/bitrepository-webclient-1.7-SNAPSHOT-sources.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-webclient/target/bitrepository-webclient-1.7-SNAPSHOT-distribution.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-webclient/1.7-SNAPSHOT/bitrepository-webclient-1.7-SNAPSHOT-distribution.tar.gz
[JENKINS] Archiving disabled
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Integration 1.7-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-integration ---
[INFO] Deleting /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integration/target
[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] --- maven-jar-plugin:2.4:jar (default-jar) @ bitrepository-integration ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integration/target/bitrepository-integration-1.7-SNAPSHOT.jar
[INFO] 
[INFO] --- maven-jar-plugin:2.4:test-jar (default) @ bitrepository-integration ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integration/target/bitrepository-integration-1.7-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-sonar/bitrepository-integration/target/bitrepository-integration-1.7-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-sonar/bitrepository-integration/target/bitrepository-integration-1.7-SNAPSHOT-quickstart.tar.gz
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integration/target/bitrepository-integration-1.7-SNAPSHOT-tools.tar.gz
[WARNING] Entry: bitrepository-integration-1.7-SNAPSHOT/lib/bitrepository-reference-pillar-1.7-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-sonar/bitrepository-integration/target/bitrepository-integration-1.7-SNAPSHOT.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integration/1.7-SNAPSHOT/bitrepository-integration-1.7-SNAPSHOT.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integration/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integration/1.7-SNAPSHOT/bitrepository-integration-1.7-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integration/target/bitrepository-integration-1.7-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integration/1.7-SNAPSHOT/bitrepository-integration-1.7-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integration/target/bitrepository-integration-1.7-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integration/1.7-SNAPSHOT/bitrepository-integration-1.7-SNAPSHOT-sources.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integration/target/bitrepository-integration-1.7-SNAPSHOT-quickstart.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integration/1.7-SNAPSHOT/bitrepository-integration-1.7-SNAPSHOT-quickstart.tar.gz
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integration/target/bitrepository-integration-1.7-SNAPSHOT-tools.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integration/1.7-SNAPSHOT/bitrepository-integration-1.7-SNAPSHOT-tools.tar.gz
[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 [  5.027 s]
[INFO] Bitrepository Reference Settings .................. SUCCESS [ 11.630 s]
[INFO] Bitrepository Core ................................ SUCCESS [ 47.447 s]
[INFO] Bitrepository Client .............................. SUCCESS [01:07 min]
[INFO] Bitrepository Service ............................. SUCCESS [ 14.932 s]
[INFO] Bitrepository Integrity Service ................... SUCCESS [01:31 min]
[INFO] Bitrepository Alarm Service ....................... SUCCESS [ 21.964 s]
[INFO] Bitrepository Audit Trail Service ................. SUCCESS [ 29.033 s]
[INFO] Bitrepository Reference Pillar .................... SUCCESS [01:06 min]
[INFO] Bitrepository Monitoring Service .................. SUCCESS [ 13.658 s]
[INFO] Bitrepository Webclient ........................... SUCCESS [  4.675 s]
[INFO] Bitrepository Integration ......................... SUCCESS [ 16.424 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 06:41 min
[INFO] Finished at: 2015-12-19T02:24:12+01:00
[INFO] Final Memory: 48M/117M
[INFO] ------------------------------------------------------------------------
channel stopped
[Bitrepository-sonar] $ /home/cibuild01/tools/hudson.tasks.Maven_MavenInstallation/Maven3.2/bin/mvn -f /home/cibuild01/workspace/Bitrepository-sonar/pom.xml -e -B sonar:sonar -Dsonar.jdbc.url=jdbc:postgresql://leda/sonar ******** ******** -Dsonar.host.url=https://sbforge.org/sonar
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=128m; support was removed in 8.0
[INFO] Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO] 
[INFO] Bitrepository
[INFO] Bitrepository Reference Settings
[INFO] Bitrepository Core
[INFO] Bitrepository Client
[INFO] Bitrepository Service
[INFO] Bitrepository Integrity Service
[INFO] Bitrepository Alarm Service
[INFO] Bitrepository Audit Trail Service
[INFO] Bitrepository Reference Pillar
[INFO] Bitrepository Monitoring Service
[INFO] Bitrepository Webclient
[INFO] Bitrepository Integration
[INFO] Downloading: https://sbforge.org/nexus/content/groups/public/org/apache/maven/plugins/maven-metadata.xml
[INFO] Downloading: https://sbforge.org/nexus/content/groups/public/org/codehaus/mojo/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/groups/public/org/apache/maven/plugins/maven-metadata.xml (14 KB at 6.5 KB/sec)
[INFO] Downloaded: https://sbforge.org/nexus/content/groups/public/org/codehaus/mojo/maven-metadata.xml (24 KB at 9.1 KB/sec)
[INFO] Downloading: https://sbforge.org/nexus/content/groups/public/org/codehaus/mojo/sonar-maven-plugin/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/groups/public/org/codehaus/mojo/sonar-maven-plugin/maven-metadata.xml (892 B at 0.8 KB/sec)
[INFO] 
[INFO] Using the builder org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder with a thread count of 1
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository 1.7-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] 
[INFO] --- sonar-maven-plugin:2.7.1:sonar (default-cli) @ bitrepository-parent ---
[INFO] User cache: /home/cibuild01/.sonar/cache
[INFO] SonarQube version: 4.4
[INFO] Default locale: "en_US", source code encoding: "UTF-8"
[INFO] [02:24:36.442] Load global settings
[INFO] [02:24:36.640] User cache: /home/cibuild01/.sonar/cache
[INFO] [02:24:36.663] Install plugins
[INFO] [02:24:37.600] Install JDBC driver
[INFO] [02:24:37.658] Create JDBC datasource for jdbc:postgresql://leda/sonar
[INFO] [02:24:37.915] Initializing Hibernate
[ERROR] [02:24:42.405] Invalid value of sonar.sources for org.bitrepository.reference:bitrepository-reference-settings
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO] 
[INFO] Bitrepository ..................................... FAILURE [ 16.637 s]
[INFO] Bitrepository Reference Settings .................. SKIPPED
[INFO] Bitrepository Core ................................ SKIPPED
[INFO] Bitrepository Client .............................. SKIPPED
[INFO] Bitrepository Service ............................. SKIPPED
[INFO] Bitrepository Integrity Service ................... SKIPPED
[INFO] Bitrepository Alarm Service ....................... SKIPPED
[INFO] Bitrepository Audit Trail Service ................. SKIPPED
[INFO] Bitrepository Reference Pillar .................... SKIPPED
[INFO] Bitrepository Monitoring Service .................. SKIPPED
[INFO] Bitrepository Webclient ........................... SKIPPED
[INFO] Bitrepository Integration ......................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 25.575 s
[INFO] Finished at: 2015-12-19T02:24:42+01:00
[INFO] Final Memory: 27M/68M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.codehaus.mojo:sonar-maven-plugin:2.7.1:sonar (default-cli) on project bitrepository-parent: The folder '/home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-settings/pom.xml' does not exist for 'org.bitrepository.reference:bitrepository-reference-settings' (base directory = /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-settings) -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.codehaus.mojo:sonar-maven-plugin:2.7.1:sonar (default-cli) on project bitrepository-parent: The folder '/home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-settings/pom.xml' does not exist for 'org.bitrepository.reference:bitrepository-reference-settings' (base directory = /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-settings)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:108)
	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:76)
	at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
	at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:116)
	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:361)
	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
	at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
	at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:213)
	at org.apache.maven.cli.MavenCli.main(MavenCli.java:157)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:483)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
	at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
	at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.apache.maven.plugin.MojoExecutionException: The folder '/home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-settings/pom.xml' does not exist for 'org.bitrepository.reference:bitrepository-reference-settings' (base directory = /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-settings)
	at org.codehaus.mojo.sonar.bootstrap.ExceptionHandling.handle(ExceptionHandling.java:41)
	at org.codehaus.mojo.sonar.bootstrap.RunnerBootstrapper.execute(RunnerBootstrapper.java:104)
	at org.codehaus.mojo.sonar.SonarMojo.execute(SonarMojo.java:135)
	at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:133)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
	... 19 more
Caused by: java.lang.IllegalStateException: The folder '/home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-settings/pom.xml' does not exist for 'org.bitrepository.reference:bitrepository-reference-settings' (base directory = /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-settings)
	at org.sonar.batch.scan.ProjectReactorBuilder.checkExistenceOfDirectories(ProjectReactorBuilder.java:423)
	at org.sonar.batch.scan.ProjectReactorBuilder.cleanAndCheckModuleProperties(ProjectReactorBuilder.java:336)
	at org.sonar.batch.scan.ProjectReactorBuilder.cleanAndCheckProjectDefinitions(ProjectReactorBuilder.java:319)
	at org.sonar.batch.scan.ProjectReactorBuilder.cleanAndCheckProjectDefinitions(ProjectReactorBuilder.java:325)
	at org.sonar.batch.scan.ProjectReactorBuilder.execute(ProjectReactorBuilder.java:117)
	at org.sonar.batch.scan.ProjectScanContainer.projectBootstrap(ProjectScanContainer.java:114)
	at org.sonar.batch.scan.ProjectScanContainer.doBeforeStart(ProjectScanContainer.java:92)
	at org.sonar.api.platform.ComponentContainer.startComponents(ComponentContainer.java:90)
	at org.sonar.api.platform.ComponentContainer.execute(ComponentContainer.java:77)
	at org.sonar.batch.scan.ScanTask.scan(ScanTask.java:64)
	at org.sonar.batch.scan.ScanTask.execute(ScanTask.java:51)
	at org.sonar.batch.bootstrap.TaskContainer.doAfterStart(TaskContainer.java:110)
	at org.sonar.api.platform.ComponentContainer.startComponents(ComponentContainer.java:92)
	at org.sonar.api.platform.ComponentContainer.execute(ComponentContainer.java:77)
	at org.sonar.batch.bootstrap.BootstrapContainer.executeTask(BootstrapContainer.java:185)
	at org.sonar.batch.bootstrapper.Batch.executeTask(Batch.java:95)
	at org.sonar.batch.bootstrapper.Batch.execute(Batch.java:67)
	at org.sonar.runner.batch.BatchIsolatedLauncher.executeOldVersion(BatchIsolatedLauncher.java:92)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:483)
	at org.sonar.runner.impl.IsolatedLauncherProxy.invoke(IsolatedLauncherProxy.java:61)
	at com.sun.proxy.$Proxy21.executeOldVersion(Unknown Source)
	at org.sonar.runner.api.EmbeddedRunner.doExecute(EmbeddedRunner.java:284)
	at org.sonar.runner.api.EmbeddedRunner.runAnalysis(EmbeddedRunner.java:166)
	at org.sonar.runner.api.EmbeddedRunner.runAnalysis(EmbeddedRunner.java:153)
	at org.codehaus.mojo.sonar.bootstrap.RunnerBootstrapper.execute(RunnerBootstrapper.java:99)
	... 22 more
[ERROR] 
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
SonarQube analysis completed: FAILURE
Build step 'SonarQube' changed build result to FAILURE
Build step 'SonarQube' marked build as failure
Sending e-mails to: ktc@statsbiblioteket.dk abr@statsbiblioteket.dk jolf@kb.dk thorbjoern@gmail.com tra@statsbiblioteket.dk
Finished: FAILURE