-------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-audit-trail-service ---
[INFO] Deleting /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-audit-trail-service/target
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ bitrepository-audit-trail-service ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 9 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ bitrepository-audit-trail-service ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 23 source files to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-audit-trail-service/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 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:21:40.821 WARN o.b.service.database.DatabaseUtils - Migrating AuditServiceDB from version 2 to 3.
02:21:41.181 WARN o.b.service.database.DatabaseUtils - Migrating AuditServiceDB from version 3 to 4.
02:21:41.309 WARN o.b.service.database.DatabaseUtils - Migrating AuditServiceDB from version 4 to 5.
Test success: testMigratingAuditServiceDatabase
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:21:41.720 WARN o.b.a.collector.IncrementalCollector - Received bad collection id! Expected 'dummy-collection', but got 'FalseCollection1447982501453'.
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:21:41.830 WARN o.b.a.collector.IncrementalCollector - Event: null: null: COMPONENT_FAILED: ContributorID Contributor1 ResponseCode: REQUEST_NOT_SUPPORTED
02:21:41.832 WARN o.b.a.collector.IncrementalCollector - Event: null: null: FAILED: ,
02:21:41.837 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:61) ~[bitrepository-client-1.6-SNAPSHOT.jar:1.6-SNAPSHOT]
at org.bitrepository.audittrails.collector.IncrementalCollector.collect(IncrementalCollector.java:135) [classes/:na]
at org.bitrepository.audittrails.collector.IncrementalCollector.performCollection(IncrementalCollector.java:112) [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 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 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 AuditCollectorTest
Test starting: auditCollectorIntervalTest
Description: Test that the collector calls the AuditClient at the correct intervals.
02:21:44.272 WARN o.b.a.collector.IncrementalCollector - Received bad collection id! Expected 'TwoPillarCollection', but got 'dummy-collection'.
02:21:45.281 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: 23.771 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.6-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 [93 msecs]
[INFO] Building war: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-audit-trail-service/target/bitrepository-audit-trail-service-1.6-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.6-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.6-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.6-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.6-SNAPSHOT.war to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-audit-trail-service/1.6-SNAPSHOT/bitrepository-audit-trail-service-1.6-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.6-SNAPSHOT/bitrepository-audit-trail-service-1.6-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-audit-trail-service/target/bitrepository-audit-trail-service-1.6-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-audit-trail-service/1.6-SNAPSHOT/bitrepository-audit-trail-service-1.6-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-audit-trail-service/target/bitrepository-audit-trail-service-1.6-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-audit-trail-service/1.6-SNAPSHOT/bitrepository-audit-trail-service-1.6-SNAPSHOT-sources.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-audit-trail-service/target/bitrepository-audit-trail-service-1.6-SNAPSHOT-distribution.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-audit-trail-service/1.6-SNAPSHOT/bitrepository-audit-trail-service-1.6-SNAPSHOT-distribution.tar.gz
[JENKINS] Archiving disabled
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Reference Pillar 1.6-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-reference-pillar ---
[INFO] Deleting /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target
[INFO]
[INFO] --- maven-dependency-plugin:2.8:unpack-dependencies (unpack-shared-sqlscripts) @ bitrepository-reference-pillar ---
[INFO] Unpacking /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-service/target/bitrepository-service-1.6-SNAPSHOT.jar to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/classes with includes "**/*.sql" and excludes ""
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ bitrepository-reference-pillar ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 10 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ bitrepository-reference-pillar ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 44 source files to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/classes
[INFO]
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ bitrepository-reference-pillar ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 12 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ bitrepository-reference-pillar ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 70 source files to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/test-classes
[INFO]
[INFO] --- maven-surefire-plugin:2.17:test (default-test) @ bitrepository-reference-pillar ---
[INFO] Surefire report directory: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/surefire-reports
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running TestSuite
Configuring TestNG with: TestNG652Configurator
Starting test project Reference Pillar Test
Suite: Surefire suite
Starting testcase 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 GeneralMessageHandlingTest
Added fixture: Initialize a new Pillar.
Test starting: testPillarMessageHandler
Description: Test the handling of the PillarMessageHandler super-class.
Step: Setup
Step: Test the pillar ID
Test success: testPillarMessageHandler
Starting testcase GetChecksumsTest
Added fixture: Initialize a new Pillar.
Test starting: badCaseIdentification
Description: Tests the identification for a GetChecksums operation on the pillar for the failure scenario, when the file is missing.
Step: Set up constants and variables.
Step: Setup for delivering pillar id and not having the file
Step: Create and send the identify request message.
Result: Received message on TEST-TOPIC-badCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsResponse@6f1b8544[correlationID=5dff1e46-1b0d-4896-8694-0c4346036a1f, 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@51dae791[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@688a2c09[fileID=DefaultFilebadCaseIdentification, allFileIDs=<null>], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@5de5e95[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:22:14.214 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@6723610b[correlationID=fb1c388c-272b-42c5-9384-631f793e496f, 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@5ba03c82[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@60df7989[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], resultingChecksums=<null>, partialResult=<null>]
Step: Retrieve the FinalResponse for the GetChecksums request
Test success: badCaseOperationNoFile
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@58a84a12[correlationID=b51a2bf6-1f08-4b85-a275-1c86528edc4d, 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@e700eba[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@6436e181[fileID=DefaultFilegoodCaseIdentification, allFileIDs=<null>], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7186b202[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], pillarID=Pillar-goodCaseIdentification, pillarChecksumSpec=<null>, timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@6b649efa[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@1e3f0aea[correlationID=21a55a38-d30f-4620-932f-dd400f35b2f4, 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@48268eec[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to calculate checksums.], pillarID=Pillar-goodCaseOperationAllFiles, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@69a024a0[fileID=<null>, allFileIDs=true], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@4bf80c29[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], resultAddress=<null>]
Result: Received message on TEST-TOPIC-goodCaseOperationAllFiles-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@32a4ecbe[correlationID=21a55a38-d30f-4620-932f-dd400f35b2f4, 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@2e71240b[responseCode=OPERATION_COMPLETED, responseText=<null>], pillarID=Pillar-goodCaseOperationAllFiles, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@4bf80c29[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], resultingChecksums=org.bitrepository.bitrepositoryelements.ResultingChecksums@23cd5d42[resultAddress=<null>, checksumDataItems={org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@2b44d6d0[fileID=DefaultFile, checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2015-11-20T02:22:17.310+01:00],org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@3e900e1a[fileID=goodCaseOperationAllFiles-cibuild01--Test-File-1447982537305, 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@457a5b2d[correlationID=2826f083-6cc0-4c99-b0ea-6b436fdc0ec4, 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@79d7035[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to calculate checksums.], pillarID=Pillar-goodCaseOperationSingleFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@372461a9[fileID=DefaultFilegoodCaseOperationSingleFile, allFileIDs=<null>], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@5fffb692[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], resultAddress=<null>]
Result: Received message on TEST-TOPIC-goodCaseOperationSingleFile-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@48cb2d73[correlationID=2826f083-6cc0-4c99-b0ea-6b436fdc0ec4, 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@243bf087[responseCode=OPERATION_COMPLETED, responseText=<null>], pillarID=Pillar-goodCaseOperationSingleFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@5fffb692[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], resultingChecksums=org.bitrepository.bitrepositoryelements.ResultingChecksums@3086f480[resultAddress=<null>, checksumDataItems={org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@126f8f24[fileID=DefaultFilegoodCaseOperationSingleFile, checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2015-11-20T02:22:17.515+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@3d104c9b[correlationID=a11d0d52-a1e2-4e99-a9ab-d28e9b8e5b7b, 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@6544899b[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to calculate checksums.], pillarID=Pillar-testRestrictions, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@6da54910[fileID=<null>, allFileIDs=true], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1bd8afc8[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], resultAddress=<null>]
Result: Received message on TEST-TOPIC-testRestrictions-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@24134cbc[correlationID=a11d0d52-a1e2-4e99-a9ab-d28e9b8e5b7b, 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@65da01f4[responseCode=OPERATION_COMPLETED, responseText=<null>], pillarID=Pillar-testRestrictions, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1bd8afc8[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], resultingChecksums=org.bitrepository.bitrepositoryelements.ResultingChecksums@22f02996[resultAddress=<null>, checksumDataItems={org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@7c8874ef[fileID=DefaultFile, checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2015-11-20T02:22:17.788+01:00]}], partialResult=false]
Step: Retrieve the ProgressResponse for the GetChecksums request
Step: Retrieve the FinalResponse for the GetChecksums request
Test success: testRestrictions
Starting testcase GetFileIDsTest
Added fixture: Initialize a new Pillar.
Test starting: badCaseIdentification
Description: Tests the identification for a GetFileIDs operation on the pillar for the failure scenario, when the file is missing.
Step: Set up constants and variables.
Step: Setup for delivering pillar id and not having the file
Step: Create and send the identify request message.
02:22:17.949 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@72c4a3aa[correlationID=c95eb3e5-ac1b-4bf2-b485-aafd8f6dc06c, 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@1e495414[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseIdentification, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@3711c71c[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:19.389 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@6d6039df[correlationID=d80dad1c-0b8e-43d2-acb6-ee739e23aae6, 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@611c3eae[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@13e00016[fileID=DefaultFilebadCaseOperationNoFile, allFileIDs=<null>], resultingFileIDs=<null>, partialResult=<null>]
02:22:19.392 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@17176b18[correlationID=d80dad1c-0b8e-43d2-acb6-ee739e23aae6, 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@4e4395c[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@13e00016[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@17176b18[correlationID=d80dad1c-0b8e-43d2-acb6-ee739e23aae6, 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@4e4395c[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@13e00016[fileID=DefaultFilebadCaseOperationNoFile, allFileIDs=<null>], resultingFileIDs=<null>, partialResult=<null>]
02:22:20.408 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.GetFileIDsFinalResponse@17176b18[correlationID=d80dad1c-0b8e-43d2-acb6-ee739e23aae6, 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@4e4395c[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@13e00016[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@5e98032e[correlationID=4c291b13-4eb6-4a83-82aa-84fb50ed65ba, 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@4fe8f2ae[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], pillarID=Pillar-goodCaseIdentification, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@591be8aa[fileID=DefaultFilegoodCaseIdentification, allFileIDs=<null>], timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@61808ecd[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@300bb303[correlationID=2dd7e49e-2d6f-4936-8699-b744e1403c3d, 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@4243341e[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@47c96f2c[correlationID=b62d5330-87b0-445f-9687-32222f758108, 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@210a26b[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], fileID=DefaultFilegoodCaseIdentification, pillarID=Pillar-goodCaseIdentification, timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@2dc21583[timeMeasureUnit=MILLISECONDS, timeMeasureValue=1000]]
Step: Retrieve and validate the response getPillarID() the pillar.
Test success: goodCaseIdentification
Starting testcase MediatorTest
Test starting: testMediatorRuntimeExceptionHandling
Description: Tests the handling of a runtime exception
Step: Setup create and start the mediator.
Step: Send a request to the mediator.
02:22:26.428 WARN o.b.pillar.MediatorTest$TestMediator - Unexpected exception caught.
java.lang.RuntimeException: I am supposed to throw a RuntimeException
at org.bitrepository.pillar.MediatorTest$ErroneousRequestHandler.processRequest(MediatorTest.java:122) ~[test-classes/:na]
at org.bitrepository.pillar.MediatorTest$ErroneousRequestHandler.processRequest(MediatorTest.java:113) ~[test-classes/:na]
at org.bitrepository.pillar.messagehandler.PillarMediator.handleRequest(PillarMediator.java:76) ~[classes/:na]
at org.bitrepository.service.contributor.AbstractContributorMediator$GeneralRequestHandler.onMessage(AbstractContributorMediator.java:101) [bitrepository-service-1.6-SNAPSHOT.jar:1.6-SNAPSHOT]
at org.bitrepository.protocol.messagebus.SimpleMessageBus.lambda$sendMessage$0(SimpleMessageBus.java:48) [bitrepository-core-1.6-SNAPSHOT.jar:1.6-SNAPSHOT]
at org.bitrepository.protocol.messagebus.SimpleMessageBus$$Lambda$1/1789376127.accept(Unknown Source) [bitrepository-core-1.6-SNAPSHOT.jar:1.6-SNAPSHOT]
at java.lang.Iterable.forEach(Iterable.java:75) [na:1.8.0_11]
at org.bitrepository.protocol.messagebus.SimpleMessageBus.sendMessage(SimpleMessageBus.java:48) [bitrepository-core-1.6-SNAPSHOT.jar:1.6-SNAPSHOT]
at org.bitrepository.pillar.MediatorTest.testMediatorRuntimeExceptionHandling(MediatorTest.java:84) [test-classes/:na]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_11]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_11]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_11]
at java.lang.reflect.Method.invoke(Method.java:483) ~[na:1.8.0_11]
at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84) [testng-6.8.8.jar:na]
at org.testng.internal.Invoker.invokeMethod(Invoker.java:714) [testng-6.8.8.jar:na]
at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901) [testng-6.8.8.jar:na]
at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231) [testng-6.8.8.jar:na]
at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127) [testng-6.8.8.jar:na]
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111) [testng-6.8.8.jar:na]
at org.testng.TestRunner.privateRun(TestRunner.java:767) [testng-6.8.8.jar:na]
at org.testng.TestRunner.run(TestRunner.java:617) [testng-6.8.8.jar:na]
at org.testng.SuiteRunner.runTest(SuiteRunner.java:348) [testng-6.8.8.jar:na]
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:343) [testng-6.8.8.jar:na]
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:305) [testng-6.8.8.jar:na]
at org.testng.SuiteRunner.run(SuiteRunner.java:254) [testng-6.8.8.jar:na]
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) [testng-6.8.8.jar:na]
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) [testng-6.8.8.jar:na]
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1224) [testng-6.8.8.jar:na]
at org.testng.TestNG.runSuitesLocally(TestNG.java:1149) [testng-6.8.8.jar:na]
at org.testng.TestNG.run(TestNG.java:1057) [testng-6.8.8.jar:na]
at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:115) [surefire-testng-2.17.jar:2.17]
at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:204) [surefire-testng-2.17.jar:2.17]
at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:107) [surefire-testng-2.17.jar:2.17]
at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:112) [surefire-testng-2.17.jar:2.17]
at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) [surefire-booter-2.17.jar:2.17]
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) [surefire-booter-2.17.jar:2.17]
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) [surefire-booter-2.17.jar:2.17]
Result: Received message on TEST-TOPIC-testMediatorRuntimeExceptionHandling-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetStatusResponse@f10d055[correlationID=51916e5d-ddab-4caf-9c04-64b3ba05dfc7, 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@542ff147[responseCode=FAILURE, responseText=java.lang.RuntimeException: I am supposed to throw a RuntimeException], contributor=TEST-TOPIC-cibuild01, timeToDeliver=<null>]
02:22:26.446 WARN o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@b9b97ad[origDateTime=2015-11-20T02:22:26.444+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@2807cf3[correlationID=4cae019e-7305-42ed-89cc-71f90254cca4, 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@b9b97ad[origDateTime=2015-11-20T02:22:26.444+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
Test starting: componentIDTest
Test success: componentIDTest
Starting testcase PutFileTest
Added fixture: Initialize a new Pillar.
Test starting: badCaseIdentification
Description: Tests the identification for a PutFile operation on the pillar for the failure scenario, when the file already exists.
Step: Set up constants and variables.
Step: Setup for already having the file and delivering pillar id
Step: Create and send the identify request message.
Result: Received message on TEST-TOPIC-badCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileResponse@3ca278bc[correlationID=cc4a463e-562e-4255-83fe-d58a28e2d3b7, 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@283e1759[responseCode=DUPLICATE_FILE_FAILURE, responseText=<null>], pillarID=Pillar-badCaseIdentification, fileID=DefaultFilebadCaseIdentification, pillarChecksumSpec=<null>, checksumDataForExistingFile=<null>, timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@2acb1264[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@3e5ebdfe[correlationID=6c3556b8-7177-401d-bb33-f291702db3f2, 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@71668a67[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@67a38[correlationID=905ad909-a161-4287-b3a7-d11d3d854cea, 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@7ef4aceb[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:31.128 WARN o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@31b650e9[origDateTime=2015-11-20T02:22:31.128+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@683fe7b5[correlationID=9a465e31-82b3-4905-a64f-9c5d408dd09f, 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@31b650e9[origDateTime=2015-11-20T02:22:31.128+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@45832b85[correlationID=dc4277d2-18f3-41a3-b3ce-9a32fbe132c1, 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@103478b8[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], pillarID=Pillar-goodCaseIdentification, fileID=DefaultFilegoodCaseIdentification, pillarChecksumSpec=<null>, checksumDataForExistingFile=<null>, timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@270f7b4d[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@701c482e[correlationID=63883df5-7936-488d-82f1-af696bf670b4, 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@4738131e[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@795eddda[correlationID=63883df5-7936-488d-82f1-af696bf670b4, 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@c6bf8d9[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@44392e64[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@e18d2a2[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2015-11-20T02:22:32.732+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
Test starting: getPillarCollectionsTest
Test success: getPillarCollectionsTest
Starting testcase ArchiveDirectoryTest
Test starting: testArchiveDirectoryExistingFile
Description: Test the ArchiveDirectory when the file exists
Step: Setup
Step: Validate the existence of the file
Step: Delete the file.
Test success: testArchiveDirectoryExistingFile
Test starting: testArchiveDirectoryMissingFile
Description: Test the ArchiveDirectory when the file is missing.
Step: Setup
Step: Validate the existence of the file
Step: Delete the file.
Test success: testArchiveDirectoryMissingFile
Test starting: testArchiveDirectoryMoveFileToArchive
Description: Testing the error scenarios when moving a file from tmp to archive for the ArchiveDirectory.
Step: Setup
Step: Moving file from tmp to archive
Step: Create file in both tmp and archive.
Step: Moving file from tmp to archive
Step: Remove the file from archive and try again
Test success: testArchiveDirectoryMoveFileToArchive
Test starting: testArchiveDirectoryNewFile
Description: Testing the ArchiveDirectory handling of a new file.
Step: Setup
Step: Retrieve tmp file
Step: Request a new file for the tmp dir
Step: Retrieve tmp file
Step: Request another new file with the same name
Step: Move the file from tmp to archive
Test success: testArchiveDirectoryNewFile
Test starting: testArchiveDirectoryRemoveFile
Description: Testing the error scenarios when removing files from the archive.
Step: Setup
Step: Remove nonexisting file from archive
Step: Remove nonexisting file from tmp
Step: Create file in both tmp, archive and retain directories.
Step: Remove the file from archive and tmp
Test success: testArchiveDirectoryRemoveFile
Starting testcase 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:22:34.689 WARN o.b.service.database.DatabaseUtils - Migrating the checksums table from version 1 to 2 in the ChecksumDatabase.
02:22:34.765 WARN o.b.service.database.DatabaseUtils - Migrating ChecksumDB from version 2 to 3.
Step: Validate the entry
Test success: testMigratingDatabaseChecksumsTable
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@2b06681c[correlationID=8d39354c-7b7b-4628-9714-7c0dedfa4ace, 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@20f6b6e0[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@2ea4e762[correlationID=8e9abf3a-f7cf-4792-af52-462e80bf5bdf, 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@444c0f9a[responseCode=EXISTING_FILE_CHECKSUM_FAILURE, responseText=No mandatory checksum for destructive operation was supplied.], pillarID=Pillar-badCaseOperationMissingVerification, fileID=DefaultFilebadCaseOperationMissingVerification, checksumDataForExistingFile=<null>]
02:22:36.227 WARN o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@74919649[origDateTime=2015-11-20T02:22:36.226+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@7d07e04e[correlationID=f37d4f7f-d65f-4566-9567-15a5cd1201fd, 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@74919649[origDateTime=2015-11-20T02:22:36.226+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@7b92ea9d[correlationID=45895016-610c-49cd-958e-de7c1d4c0229, 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@6b3bc1f6[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileID=DefaultFilebadCaseOperationNoFile, checksumDataForExistingFile=<null>]
Result: Received message on TEST-TOPIC-badCaseOperationNoFile-cibuild01 : org.bitrepository.bitrepositorymessages.DeleteFileFinalResponse@3050d479[correlationID=45895016-610c-49cd-958e-de7c1d4c0229, 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@5c7a06ec[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileID=DefaultFilebadCaseOperationNoFile, checksumDataForExistingFile=<null>]
Result: Received message on TEST-TOPIC-badCaseOperationNoFile-cibuild01 : org.bitrepository.bitrepositorymessages.DeleteFileFinalResponse@137d04d8[correlationID=45895016-610c-49cd-958e-de7c1d4c0229, 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@25b8f9d2[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
Result: The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.DeleteFileFinalResponse@3050d479[correlationID=45895016-610c-49cd-958e-de7c1d4c0229, 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@5c7a06ec[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileID=DefaultFilebadCaseOperationNoFile, checksumDataForExistingFile=<null>]
org.bitrepository.bitrepositorymessages.DeleteFileFinalResponse@137d04d8[correlationID=45895016-610c-49cd-958e-de7c1d4c0229, 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@25b8f9d2[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileID=DefaultFilebadCaseOperationNoFile, checksumDataForExistingFile=<null>]
02:22:37.461 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.DeleteFileFinalResponse@3050d479[correlationID=45895016-610c-49cd-958e-de7c1d4c0229, 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@5c7a06ec[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileID=DefaultFilebadCaseOperationNoFile, checksumDataForExistingFile=<null>]
org.bitrepository.bitrepositorymessages.DeleteFileFinalResponse@137d04d8[correlationID=45895016-610c-49cd-958e-de7c1d4c0229, 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@25b8f9d2[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileID=DefaultFilebadCaseOperationNoFile, checksumDataForExistingFile=<null>]
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@43cc7951[correlationID=ce0fda9f-ebb6-4b10-914b-39d37009116d, 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@758311ed[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], fileID=DefaultFilegoodCaseIdentification, pillarID=Pillar-goodCaseIdentification, pillarChecksumSpec=<null>, timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@7533923b[timeMeasureUnit=MILLISECONDS, timeMeasureValue=1000]]
Step: Retrieve and validate the response getPillarID() the pillar.
Test success: goodCaseIdentification
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@e2498a3[correlationID=ec3e998d-7cb9-4b59-8ffa-8fb4189943f7, 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@26c2f767[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@aade5a2[correlationID=ec3e998d-7cb9-4b59-8ffa-8fb4189943f7, 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@51f009ef[responseCode=OPERATION_COMPLETED, responseText=<null>], contributor=Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@59c00722[resultAddress=<null>, auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@6c96346b[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@9734cae[sequenceNumber=1, fileID=fileId1447982558814, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=CHECKSUM_CALCULATED, actionDateTime=2015-11-20T02:22:38.814+01:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@589d831e[sequenceNumber=2, fileID=fileId1447982558814, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=DELETE_FILE, actionDateTime=2015-11-20T02:22:38.814+01:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@1bd6638[sequenceNumber=3, fileID=fileId1447982558814, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=FAILURE, actionDateTime=2015-11-20T02:22:38.814+01:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@5c552f08[sequenceNumber=4, fileID=fileId1447982558814, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=FILE_MOVED, actionDateTime=2015-11-20T02:22:38.814+01:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@4fd00e10[sequenceNumber=5, fileID=fileId1447982558814, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=GET_CHECKSUMS, actionDateTime=2015-11-20T02:22:38.814+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@45f6181a[correlationID=8e46e08d-be81-46db-9c43-2952498ba379, 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@19d0d1ab[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@5114c8a1[correlationID=8e46e08d-be81-46db-9c43-2952498ba379, 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@24d73c51[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@3b95fce9[correlationID=8e46e08d-be81-46db-9c43-2952498ba379, 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@f26cd76[responseCode=OPERATION_COMPLETED, responseText=<null>], contributor=Pillar-checksumPillarGetAuditTrailsSpecificRequests, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@78805df3[resultAddress=<null>, auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@65a8c306[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@71ce19ee[sequenceNumber=1, fileID=fileId1447982558986, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=OTHER, actionDateTime=2015-11-20T02:22:38.986+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@48ba37dc[correlationID=8e46e08d-be81-46db-9c43-2952498ba379, 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@322f84fd[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@113cc14d[correlationID=8e46e08d-be81-46db-9c43-2952498ba379, 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@10bcbbed[responseCode=OPERATION_COMPLETED, responseText=<null>], contributor=Pillar-checksumPillarGetAuditTrailsSpecificRequests, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@9a16af1[resultAddress=<null>, auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@47e70f54[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@71ce19ee[sequenceNumber=1, fileID=fileId1447982558986, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=OTHER, actionDateTime=2015-11-20T02:22:38.986+01:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@30a6984c[sequenceNumber=2, fileID=notThisFile, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=UnknownActor, actionOnFile=FAILURE, actionDateTime=2015-11-20T02:22:38.987+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@8a11a19[correlationID=7973e783-c4f6-4177-a3b0-5d2156bc4499, 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@47393345[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@5b16e486[correlationID=7973e783-c4f6-4177-a3b0-5d2156bc4499, 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@2b85edc7[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@2bf45b7c[correlationID=7973e783-c4f6-4177-a3b0-5d2156bc4499, 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@2559f65c[responseCode=OPERATION_COMPLETED, responseText=<null>], contributor=Pillar-checksumPillarGetAuditTrailsSuccessful, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@490704a5[resultAddress=<null>, auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@4d682397[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@444ebefd[sequenceNumber=1, fileID=fileid, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=actor, actionOnFile=OTHER, actionDateTime=2015-11-20T02:22:39.143+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 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@6600d07d[correlationID=64bdffed-b25f-452c-b92b-62ea14c25f2f, 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@44103266[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@4df54c1[correlationID=a11a427a-7f05-4c1e-b83e-89de7b4a0b45, 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@785477e5[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@3aac31b7[correlationID=aac80613-364f-4f95-a1c2-85ea8d02f355, 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@57def953[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:22:42.250 WARN o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@1bf4a79b[origDateTime=2015-11-20T02:22:42.249+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@a1be5cb[correlationID=f13450b2-6038-47fd-930e-d6ec8d16eda0, 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@1bf4a79b[origDateTime=2015-11-20T02:22:42.249+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@67e37d25[correlationID=b6558344-2f6b-42e6-b374-5fdf8bc75c43, 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@78d49939[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:22:42.462 WARN o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@21f27bb5[origDateTime=2015-11-20T02:22:42.461+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@2e2a2b07[correlationID=cce3a466-84cb-493d-b3e1-d78bb7dd6905, 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@21f27bb5[origDateTime=2015-11-20T02:22:42.461+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:22:42.662 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@359903b6[correlationID=e4a410b9-73aa-4219-92a5-95fbce4a2dda, 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@1071f3ad[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:22:42.664 WARN o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@6aaed880[origDateTime=2015-11-20T02:22:42.663+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@9bd477c[correlationID=2d324e08-ef1f-4586-aa19-945a16d26a50, 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@6aaed880[origDateTime=2015-11-20T02:22:42.663+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@9742012[correlationID=98f093e9-c5e3-43b7-a160-892fc8051a5c, 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@118d7e0e[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], fileID=DefaultFile, pillarID=Pillar-goodCaseIdentification, pillarChecksumSpec=<null>, timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@39ff4421[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@30b2d267[correlationID=bf1b2109-8f6c-464c-8676-90dfa7cc41e5, 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@5a740449[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@33ac7934[correlationID=bf1b2109-8f6c-464c-8676-90dfa7cc41e5, 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@152bb4cc[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@258ff54a[correlationID=dcf88eac-82aa-49af-a8a5-0b58cfba626c, 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@50c462b8[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@77d03738[correlationID=dcf88eac-82aa-49af-a8a5-0b58cfba626c, 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@566dc0c3[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@c925ae1[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7fb02869[checksumType=HMAC_SHA512, checksumSalt={97,98}, otherChecksumType=<null>], checksumValue={18,52,-52,-52,-52,-52,67,34}, calculationTimestamp=2015-11-20T02:22:45.167+01:00], checksumDataForNewFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@92fa950[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@31fc1b6e[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2015-11-20T02:22:45.168+01:00]]
Step: Retrieve the ProgressResponse for the GetFileIDs request
Step: Retrieve the FinalResponse for the ReplaceFile request
Test success: goodCaseOperationWithChecksumsReturn
Starting testcase ChecksumEntryTest
Test starting: testExtendedTestCase
Description: Test the ChecksumEntry
Step: Create a ChecksumEntry
Step: Change the value of the checksum
Step: Change the value of the calculation date
Test success: testExtendedTestCase
Starting testcase ChecksumPillarModelTest
Test starting: testPillarModelBasicFunctionality
Description: Test the basic functions of the full reference pillar model.
Step: Check the pillar id in the pillar model
Step: Ask whether it can handle a file of size 0
Step: Ask whether it can handle a file of maximum size
Step: Check the ChecksumPillarSpec
Step: Checkum whether the checksum pillar should download
Test success: testPillarModelBasicFunctionality
Test starting: testPillarModelHasFile
Description: Test that the file exists, when placed in the archive and cache
Step: Setup
Step: Check whether file exists and retrieve it.
Step: Check whether file exists.
Step: Ask for the checksum data for the file with different checksum specs
Step: Ask for the checksum entry for the file with different checksum specs
Step: Ask for the checksum for the file with different checksum specs
Step: Check extraction of checksum result set
Step: Check retrieval of non-default checksum
Step: Check retrieval of non-default checksum result set
Step: Test retrieval of single checksum result set
Test success: testPillarModelHasFile
Test starting: testPillarModelNoFile
Description: Test that the file exists, when placed in the archive and cache
Step: Setup
Step: Check whether file exists and try to retrieve it.
Step: Verify that anexceptions are thrown when verifying file existance.
Test success: testPillarModelNoFile
Starting testcase 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:22:47.568 WARN o.b.pillar.store.FileStorageModel - The file 'DefaultFile' has been requested, but we do not have that file in collection 'TwoPillarCollection'!
Test success: testPillarModelNoFile
Finished testcase
Finished suite
Finished project
Tests run: 57, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 54.319 sec - in TestSuite
Results :
Tests run: 57, Failures: 0, Errors: 0, Skipped: 0
[JENKINS] Recording test results
[INFO]
[INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ bitrepository-reference-pillar ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.6-SNAPSHOT.jar
[INFO]
[INFO] --- maven-jar-plugin:2.4:test-jar (default) @ bitrepository-reference-pillar ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.6-SNAPSHOT-tests.jar
[INFO]
[INFO] --- maven-source-plugin:2.2.1:jar-no-fork (attach-sources-no-fork) @ bitrepository-reference-pillar ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.6-SNAPSHOT-sources.jar
[INFO]
[INFO] --- maven-assembly-plugin:2.4:single (distribution) @ bitrepository-reference-pillar ---
[INFO] Reading assembly descriptor: src/main/assembly/assembly.xml
[INFO] Reading assembly descriptor: src/test/assembly/assembly.xml
[INFO] Reading assembly descriptor: src/main/assembly/deploy-assembly.xml
[INFO] Reading assembly descriptor: src/test/assembly/test-deploy-assembly.xml
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.6-SNAPSHOT-distribution.tar.gz
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.6-SNAPSHOT-acceptance-test.tar.gz
[WARNING] Entry: bitrepository-reference-pillar-1.6-SNAPSHOT/lib/bitrepository-reference-pillar-1.6-SNAPSHOT-tests.jar longer than 100 characters.
[WARNING] Resulting tar file can only be processed successfully by GNU compatible tar commands
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.6-SNAPSHOT-deploy.tar.gz
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.6-SNAPSHOT-acceptance-test-deploy.tar.gz
[INFO]
[INFO] --- maven-install-plugin:2.5.1:install (default-install) @ bitrepository-reference-pillar ---
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.6-SNAPSHOT.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.6-SNAPSHOT/bitrepository-reference-pillar-1.6-SNAPSHOT.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.6-SNAPSHOT/bitrepository-reference-pillar-1.6-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.6-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.6-SNAPSHOT/bitrepository-reference-pillar-1.6-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.6-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.6-SNAPSHOT/bitrepository-reference-pillar-1.6-SNAPSHOT-sources.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.6-SNAPSHOT-distribution.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.6-SNAPSHOT/bitrepository-reference-pillar-1.6-SNAPSHOT-distribution.tar.gz
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.6-SNAPSHOT-acceptance-test.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.6-SNAPSHOT/bitrepository-reference-pillar-1.6-SNAPSHOT-acceptance-test.tar.gz
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.6-SNAPSHOT-deploy.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.6-SNAPSHOT/bitrepository-reference-pillar-1.6-SNAPSHOT-deploy.tar.gz
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.6-SNAPSHOT-acceptance-test-deploy.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.6-SNAPSHOT/bitrepository-reference-pillar-1.6-SNAPSHOT-acceptance-test-deploy.tar.gz
[JENKINS] Archiving disabled
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Monitoring Service 1.6-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 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:22:56.597 WARN o.b.m.status.ComponentStatusStore - Got status from an unexpected component: BAD-COMPONENT-ID
Step: Try giving it a positive status
Test success: testComponentStatus
Starting testcase MonitorAlerterTest
Test starting: testMonitorAlerter
Description: Tests the org.bitrepository.monitoringservice.alarm.BasicMonitoringServiceAlerter
Step: Setup
Step: Create the alerter, but ignore the part of actually sending the alarms. Just log it.
Step: Check statuses with an empty map.
Step: Check the status when a positive entry exists.
Step: Check the status when a negative entry exists.
02:22:59.286 WARN o.b.m.a.BasicMonitoringServiceAlerter - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@1f9e9475[origDateTime=2015-11-20T02:22:59.282+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@6cc4cdb9[correlationID=be0562f9-3b7f-4405-9cc2-5e6a75a12e71, 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@1f9e9475[origDateTime=2015-11-20T02:22:59.282+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
Finished testcase
Finished suite
Finished project
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 8.335 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.6-SNAPSHOT]
[INFO] Processing war project
[INFO] Copying webapp resources [/home/cibuild01/workspace/Bitrepository-sonar/bitrepository-monitoring-service/src/main/webapp]
[INFO] Webapp assembled in [111 msecs]
[INFO] Building war: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.6-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.6-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.6-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.6-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.6-SNAPSHOT.war to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-monitoring-service/1.6-SNAPSHOT/bitrepository-monitoring-service-1.6-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.6-SNAPSHOT/bitrepository-monitoring-service-1.6-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.6-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-monitoring-service/1.6-SNAPSHOT/bitrepository-monitoring-service-1.6-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.6-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-monitoring-service/1.6-SNAPSHOT/bitrepository-monitoring-service-1.6-SNAPSHOT-sources.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.6-SNAPSHOT-distribution.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-monitoring-service/1.6-SNAPSHOT/bitrepository-monitoring-service-1.6-SNAPSHOT-distribution.tar.gz
[JENKINS] Archiving disabled
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Webclient 1.6-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.6-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.6-SNAPSHOT]
[INFO] Copying webapp resources [/home/cibuild01/workspace/Bitrepository-sonar/bitrepository-webclient/src/main/webapp]
[INFO] Webapp assembled in [637 msecs]
[INFO] Building war: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-webclient/target/bitrepository-webclient-1.6-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.6-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.6-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.6-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.6-SNAPSHOT.war to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-webclient/1.6-SNAPSHOT/bitrepository-webclient-1.6-SNAPSHOT.war
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-webclient/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-webclient/1.6-SNAPSHOT/bitrepository-webclient-1.6-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-webclient/target/bitrepository-webclient-1.6-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-webclient/1.6-SNAPSHOT/bitrepository-webclient-1.6-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-webclient/target/bitrepository-webclient-1.6-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-webclient/1.6-SNAPSHOT/bitrepository-webclient-1.6-SNAPSHOT-sources.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-webclient/target/bitrepository-webclient-1.6-SNAPSHOT-distribution.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-webclient/1.6-SNAPSHOT/bitrepository-webclient-1.6-SNAPSHOT-distribution.tar.gz
[JENKINS] Archiving disabled
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Integration 1.6-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.6-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.6-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.6-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.6-SNAPSHOT-quickstart.tar.gz
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integration/target/bitrepository-integration-1.6-SNAPSHOT-tools.tar.gz
[WARNING] Entry: bitrepository-integration-1.6-SNAPSHOT/lib/bitrepository-reference-pillar-1.6-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.6-SNAPSHOT.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integration/1.6-SNAPSHOT/bitrepository-integration-1.6-SNAPSHOT.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integration/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integration/1.6-SNAPSHOT/bitrepository-integration-1.6-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integration/target/bitrepository-integration-1.6-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integration/1.6-SNAPSHOT/bitrepository-integration-1.6-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integration/target/bitrepository-integration-1.6-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integration/1.6-SNAPSHOT/bitrepository-integration-1.6-SNAPSHOT-sources.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integration/target/bitrepository-integration-1.6-SNAPSHOT-quickstart.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integration/1.6-SNAPSHOT/bitrepository-integration-1.6-SNAPSHOT-quickstart.tar.gz
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integration/target/bitrepository-integration-1.6-SNAPSHOT-tools.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integration/1.6-SNAPSHOT/bitrepository-integration-1.6-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.005 s]
[INFO] Bitrepository Reference Settings .................. SUCCESS [ 11.950 s]
[INFO] Bitrepository Core ................................ SUCCESS [ 42.276 s]
[INFO] Bitrepository Client .............................. SUCCESS [01:07 min]
[INFO] Bitrepository Service ............................. SUCCESS [ 9.621 s]
[INFO] Bitrepository Integrity Service ................... SUCCESS [01:21 min]
[INFO] Bitrepository Alarm Service ....................... SUCCESS [ 13.318 s]
[INFO] Bitrepository Audit Trail Service ................. SUCCESS [ 29.692 s]
[INFO] Bitrepository Reference Pillar .................... SUCCESS [01:03 min]
[INFO] Bitrepository Monitoring Service .................. SUCCESS [ 13.032 s]
[INFO] Bitrepository Webclient ........................... SUCCESS [ 4.380 s]
[INFO] Bitrepository Integration ......................... SUCCESS [ 14.984 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 06:05 min
[INFO] Finished at: 2015-11-20T02:23:28+01:00
[INFO] Final Memory: 51M/123M
[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/codehaus/mojo/maven-metadata.xml
[INFO] Downloading: https://sbforge.org/nexus/content/groups/public/org/apache/maven/plugins/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/groups/public/org/apache/maven/plugins/maven-metadata.xml (14 KB at 7.5 KB/sec)
[INFO] Downloaded: https://sbforge.org/nexus/content/groups/public/org/codehaus/mojo/maven-metadata.xml (23 KB at 11.3 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.9 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.6-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:23:46.063] Load global settings
[INFO] [02:23:46.450] User cache: /home/cibuild01/.sonar/cache
[INFO] [02:23:46.477] Install plugins
[INFO] [02:23:47.467] Install JDBC driver
[INFO] [02:23:47.509] Create JDBC datasource for jdbc:postgresql://leda/sonar
[INFO] [02:23:47.820] Initializing Hibernate
[ERROR] [02:23:56.927] Invalid value of sonar.sources for org.bitrepository.reference:bitrepository-reference-settings
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Bitrepository ..................................... FAILURE [ 17.292 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: 24.504 s
[INFO] Finished at: 2015-11-20T02:23:56+01:00
[INFO] Final Memory: 27M/69M
[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/MojoExecutionExceptionSonarQube 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
Finished: FAILURE