Started by an SCM change
Building remotely on Local activeMQ in workspace /home/cibuild01/workspace/Bitrepository-sonar
Cloning the remote Git repository
Cloning repository https://github.com/bitrepository/reference.git
> git init /home/cibuild01/workspace/Bitrepository-sonar # timeout=10
Fetching upstream changes from https://github.com/bitrepository/reference.git
> git --version # timeout=10
> git -c core.askpass=true fetch --tags --progress https://github.com/bitrepository/reference.git +refs/heads/*:refs/remotes/origin/*
> git config remote.origin.url https://github.com/bitrepository/reference.git # timeout=10
> git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
> git config remote.origin.url https://github.com/bitrepository/reference.git # timeout=10
Fetching upstream changes from https://github.com/bitrepository/reference.git
> git -c core.askpass=true fetch --tags --progress https://github.com/bitrepository/reference.git +refs/heads/master:refs/remotes/origin/master
> git rev-parse refs/remotes/origin/master^{commit} # timeout=10
> git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision 67ea1ce287009eb39546a1bd2d28242f9be39e8f (refs/remotes/origin/master)
> git config core.sparsecheckout # timeout=10
> git checkout -f 67ea1ce287009eb39546a1bd2d28242f9be39e8f
> git rev-list 7ff825844cbcbe9825e10bc9e50537795afb5a60 # timeout=10
> git tag -a -f -m Jenkins Build #77 jenkins-Bitrepository-sonar-77 # timeout=10
Parsing POMs
Modules changed, recalculating dependency graph
Established TCP socket on 50462
maven32-agent.jar already up to date
maven32-interceptor.jar already up to date
maven3-interceptor-commons.jar already up to date
[Bitrepository-sonar] $ /usr/java/java-1.8.0-oracle-1.8.0.11.x86_64/bin/java -Xmx512m -XX:MaxPermSize=128m -cp /home/cibuild01/maven32-agent.jar:/home/cibuild01/tools/hudson.tasks.Maven_MavenInstallation/Maven3.2/boot/plexus-classworlds-2.5.1.jar:/home/cibuild01/tools/hudson.tasks.Maven_MavenInstallation/Maven3.2/conf/logging jenkins.maven3.agent.Maven32Main /home/cibuild01/tools/hudson.tasks.Maven_MavenInstallation/Maven3.2 /home/cibuild01/slave.jar /home/cibuild01/maven32-interceptor.jar /home/cibuild01/maven3-interceptor-commons.jar 50462
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=128m; support was removed in 8.0
<===[JENKINS REMOTING CAPACITY]===> channel started
Executing Maven: -B -f /home/cibuild01/workspace/Bitrepository-sonar/pom.xml clean install
[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]
[INFO] Using the builder org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder with a thread count of 1
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository 1.7-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-parent ---
[INFO]
[INFO] --- maven-jar-plugin:2.4:test-jar (default) @ bitrepository-parent ---
[WARNING] JAR will be empty - no content was marked for inclusion!
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/target/bitrepository-parent-1.7-SNAPSHOT-tests.jar
[INFO]
[INFO] --- maven-source-plugin:2.2.1:jar-no-fork (attach-sources-no-fork) @ bitrepository-parent ---
[INFO]
[INFO] --- maven-install-plugin:2.5.1:install (default-install) @ bitrepository-parent ---
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-parent/1.7-SNAPSHOT/bitrepository-parent-1.7-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/target/bitrepository-parent-1.7-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-parent/1.7-SNAPSHOT/bitrepository-parent-1.7-SNAPSHOT-tests.jar
[JENKINS] Archiving disabled
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Reference Settings 1.7-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-reference-settings ---
[INFO]
[INFO] --- maven-resources-plugin:2.6:copy-resources (copy-resources) @ bitrepository-reference-settings ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO]
[INFO] --- maven-jaxb2-plugin:0.11.0:generate (generate-classes-from-xsds) @ bitrepository-reference-settings ---
[INFO] Sources are not up-to-date, XJC will be executed.
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ bitrepository-reference-settings ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO] Copying 1 resource
[INFO] Copying 1 resource
[INFO]
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ bitrepository-reference-settings ---
[JENKINS] Recording test results
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 38 source files to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-settings/target/classes
[INFO]
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ bitrepository-reference-settings ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-settings/src/test/resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ bitrepository-reference-settings ---
[INFO] No sources to compile
[INFO]
[INFO] --- maven-surefire-plugin:2.17:test (default-test) @ bitrepository-reference-settings ---
[INFO] No tests to run.
[INFO]
[INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ bitrepository-reference-settings ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-settings/target/bitrepository-reference-settings-1.7-SNAPSHOT.jar
[INFO]
[INFO] --- maven-jar-plugin:2.4:test-jar (default) @ bitrepository-reference-settings ---
[WARNING] JAR will be empty - no content was marked for inclusion!
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-settings/target/bitrepository-reference-settings-1.7-SNAPSHOT-tests.jar
[INFO]
[INFO] --- maven-source-plugin:2.2.1:jar-no-fork (attach-sources-no-fork) @ bitrepository-reference-settings ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-settings/target/bitrepository-reference-settings-1.7-SNAPSHOT-sources.jar
[INFO]
[INFO] --- maven-install-plugin:2.5.1:install (default-install) @ bitrepository-reference-settings ---
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-settings/target/bitrepository-reference-settings-1.7-SNAPSHOT.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-settings/1.7-SNAPSHOT/bitrepository-reference-settings-1.7-SNAPSHOT.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-settings/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-settings/1.7-SNAPSHOT/bitrepository-reference-settings-1.7-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-settings/target/bitrepository-reference-settings-1.7-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-settings/1.7-SNAPSHOT/bitrepository-reference-settings-1.7-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-settings/target/bitrepository-reference-settings-1.7-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-settings/1.7-SNAPSHOT/bitrepository-reference-settings-1.7-SNAPSHOT-sources.jar
[JENKINS] Archiving disabled
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Core 1.7-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-core ---
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ bitrepository-core ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ bitrepository-core ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 89 source files to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-core/target/classes
[INFO]
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ bitrepository-core ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 11 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ bitrepository-core ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 62 source files to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-core/target/test-classes
[INFO]
[INFO] --- maven-surefire-plugin:2.17:test (default-test) @ bitrepository-core ---
[INFO] Surefire report directory: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-core/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 CertificateIDTest
Test starting: equalTest
Description: Tests the equality of CertificateIDs
Step: Setup
Step: Validate the content of the certificateID
Step: Test whether it equals it self
Step: Test with a null as argument
Step: Test with another class
Step: Test with same issuer but no serial
Step: Test with same serial but no issuer
Step: Test the positive case, with both the issuer and serial
Step: Setup an empty certificate
Step: Test empty certificate against issuer but no serial
Step: Test empty certificate against serial but no issuer
Step: Test empty certificate against serial and issuer
Step: Test the positive case, with neither issuer nor serial
Step: Check the hash codes for the two certificate
Test success: equalTest
Test starting: negativeCertificateIdentificationTest
Description: Tests that a certificate is not identified based on a incorrect signature.
Step: Create CertificateID object based on a certificate not used for signing the data
Step: Create CertificateID object based on signature
Step: Assert that the two CertificateID objects are equal
Test success: negativeCertificateIdentificationTest
Test starting: positiveCertificateIdentificationTest
Description: Tests that a certificate can be identified based on the correct signature.
Step: Create CertificateID object based on the certificate used to sign the data
Step: Create CertificateID object based on signature
Step: Assert that the two CertificateID objects are equal
Test success: positiveCertificateIdentificationTest
Starting testcase ChecksumUtilsTest
Test starting: calculateDigestChecksums
Description: Tests whether the utility class for calculating checksums with MessageDigest is able to correctly calculate the checksums.
Step: Setup variables.
Step: Test with no text and no key for MD5, SHA1, and SHA256
Step: Test with text
Step: add a salt to the checksum
Test success: calculateDigestChecksums
Test starting: calculateHmacChecksums
Description: Tests whether the utility class for calculating checksums with HMAC is able to correctly calculate predefined examples from : http://en.wikipedia.org/wiki/HMAC#Examples_of_HMAC_.28MD5.2C_SHA1.2C_SHA256_.29
Step: Setup variables.
Step: Test with no text and no key for HMAC_MD5, HMAC_SHA1, and HMAC_SHA256
Step: Test with the text 'The quick brown fox jumps over the lazy dog' and key 'key' for MD5, SHA1, and SHA256
Step: Try calculating HMAC with a null salt
Test success: calculateHmacChecksums
Test starting: testChecksumAlgorithmValidation
Description: Test the algorithm validation for every single possible checksum algorithm.
Step: Test 'MD5'
Step: Test 'SHA1'
Step: Test 'SHA256'
Step: Test 'SHA384'
Step: Test 'SHA512'
Step: Test 'HMAC_MD5'
Step: Test 'HMAC_SHA1'
Step: Test 'HMAC_SHA256'
Step: Test 'HMAC_SHA384'
Step: Test 'HMAC_SHA512'
Step: Test 'OTHER'
Test success: testChecksumAlgorithmValidation
Test starting: testChecksumOnFile
Description: Test the checksum calculation on a file
Step: Setup
Step: Calculate the checksum of the file with the different ways of defining the MD5 without salt
Test success: testChecksumOnFile
Test starting: testDefaultChecksum
Description: Test the extraction of the default checksum from settings.
Step: Setup the settings
Step: Use utils to extract default checksum spec
Test success: testDefaultChecksum
Test starting: utilityTester
Description: Test that the utility class is a proper utility class.
Test success: utilityTester
Starting testcase ConfigLoaderTest
Test starting: testLoadingConfig
Description: Test the loading of a configuration file for the config loader.
Step: Setup variables
Step: Test with a invalid file path
Step: Test when the file is unreadable
Step: success case
Test success: testLoadingConfig
Starting testcase MessageAuthenticationExceptionTest
Test starting: testMessageAuthenticationException
Description: Test the instantiation of the exception
Step: Setup
Step: Try to throw such an exception
Step: Throw the exception with an embedded exception
Test success: testMessageAuthenticationException
Starting testcase PermissionStoreExceptionTest
Test starting: testPermissionStoreException
Description: Test the instantiation of the exception
Step: Setup
Step: Try to throw such an exception
Step: Throw the exception with an embedded exception
Test success: testPermissionStoreException
Starting testcase ResponseInfoUtilsTest
Test starting: responseInfoTester
Description: Test the response info.
Step: Validate the positive identification response
Step: Validate the Progress response
Test success: responseInfoTester
Test starting: utilityTester
Description: Test that the utility class is a proper utility class.
Test success: utilityTester
Test starting: componentIDTest
Test success: componentIDTest
Test starting: reloadTest
Test success: reloadTest
Starting testcase StreamUtilsTest
Test starting: streamTester
Description: Tests the SteamUtils class.
Step: Setup variables
Step: Test with null arguments
Step: Test copying the input stream to the output stream.
Test success: streamTester
Test starting: utilityTester
Description: Test that the utility class is a proper utility class.
Test success: utilityTester
Starting testcase XMLFileSettingsLoaderTest
Test starting: testCollectionSettingsLoading
Test success: testCollectionSettingsLoading
Starting testcase Base16UtilsTest
Test starting: badArgumentTest
Description: Test bad arguments
Step: Test with a odd number of characters.
Test success: badArgumentTest
Test starting: decodeChecksum
Description: Validating the decoding of the checksums.
Step: Decode the checksum and validate.
Test success: decodeChecksum
Test starting: encodeChecksum
Description: Validating the encoding of the checksums.
Step: Encode the checksum and validate
Test success: encodeChecksum
Test starting: utilityTester
Description: Test that the utility class is a proper utility class.
Test success: utilityTester
Starting testcase FileIDUtilsTest
Test starting: fileIDsTest
Description: Test the utility class for generating FileIDs
Step: Test 'all file ids'
Step: Test a specific file id
Test success: fileIDsTest
Test starting: utilityTester
Description: Test that the utility class is a proper utility class.
Test success: utilityTester
Starting testcase FileIDValidatorTest
Test starting: badRegexTest
Description: Tests the FileIDValidator handling of bad file id pattern.
Step: Give the validator a 'null' as allowed file id pattern
Step: Give the validator an empty string as allowed file id pattern
Test success: badRegexTest
Test starting: validatorDefaultTest
Description: Tests the FileIDValidator class default restrictions. Only the length should fail.
Step: Setup the validator, where all file ids are allowed at default.
Step: Test a null as argument
Step: Test a valid fileID
Step: Test odd characters
Step: Test invalid length
Step: Test too short
Test success: validatorDefaultTest
Test starting: validatorTest
Description: Tests the FileIDValidator class for the input handling based on a given regex.
Step: Setup the validator
Step: Test a null as argument
Step: Test a valid fileID
Step: Test invalid characters
Step: Test invalid length
Step: Test too short
Test success: validatorTest
Starting testcase MessageCreationTest
Test starting: messageCreationTest
Description: Tests if we are able to create message objects from xml. The input XML is the example code defined in the message-xml, thereby also testing whether this is valid.
Step: Creating IdentifyPillarsForGetFileRequest message
Step: Creating IdentifyPillarsForGetFileResponse message
Step: Creating GetFileRequest message
Step: Creating GetFileProgressResponse message
Step: Creating GetFileFinalResponse message
Step: Creating IdentifyPillarsForPutFileRequest message
Step: Creating IdentifyPillarsForPutFileResponse message
Step: Creating PutFileRequest message
Step: Creating PutFileProgressResponse message
Step: Creating PutFileFinalResponse message
Step: Creating IdentifyPillarsForDeleteFileRequest message
Step: Creating IdentifyPillarsForDeleteFileResponse message
Step: Creating DeleteFileRequest message
Step: Creating DeleteFileProgressResponse message
Step: Creating DeleteFileFinalResponse message
Step: Creating IdentifyPillarsForReplaceFileRequest message
Step: Creating IdentifyPillarsForReplaceFileResponse message
Step: Creating ReplaceFileRequest message
Step: Creating ReplaceFileProgressResponse message
Step: Creating ReplaceFileFinalResponse message
Step: Creating IdentifyPillarsForGetChecksumsRequest message
Step: Creating IdentifyPillarsForGetChecksumsResponse message
Step: Creating GetChecksumsRequest message
Step: Creating GetChecksumsProgressResponse message
Step: Creating GetChecksumsFinalResponse message
Step: Creating IdentifyPillarsForGetFileIDsRequest message
Step: Creating IdentifyPillarsForGetFileIDsResponse message
Step: Creating GetFileIDsRequest message
Step: Creating GetFileIDsProgressResponse message
Step: Creating GetFileIDsFinalResponse message
Step: Creating IdentifyContributorsForGetStatusRequest message
Step: Creating IdentifyContributorsForGetStatusResponse message
Step: Creating GetStatusRequest message
Step: Creating GetStatusProgressResponse message
Step: Creating GetStatusFinalResponse message
Step: Creating IdentifyContributorsForGetAuditTrailsRequest message
Step: Creating IdentifyContributorsForGetAuditTrailsResponse message
Step: Creating GetAuditTrailsRequest message
Step: Creating GetAuditTrailsProgressResponse message
Step: Creating GetAuditTrailsFinalResponse message
Step: Creating AlarmMessage message
Test success: messageCreationTest
Starting testcase ReceivedMessageHandlerTest
Test starting: manyMessageDispatch
Description: Tests that many (50) messages can be handled in parallel in the default pool configuration.
Added fixture: Create a ReceivedMessageHandler with a null configuration. This should create a ReceivedMessageHandler with a single CachedThreadPool.
Step: Dispatch messages to 49 listeners, where the first 49 are blocking.
Step: Unblock the blocked listeners
Test success: manyMessageDispatch
Test starting: parallelMessageDispatch
Description: Tests that two messages can be handled in parallel in the default pool configuration.
Added fixture: Create a ReceivedMessageHandler with a null configuration. This should create a ReceivedMessageHandler with a single CachedThreadPool.
Step: Dispatch messages to two listeners, the first blocking.
Step: Unblock the first listener
Test success: parallelMessageDispatch
Test starting: singleMessageDispatch
Description: Tests that a single message is dispatched correctly
Test success: singleMessageDispatch
Test starting: singleThreadMessageDispatch
Description: Tests that two messages will be handled in sequence if a singleThreaded pool is configured.
Added fixture: Create a ReceivedMessageHandler with a single pool of size 1.
Step: Dispatch messages to two listeners, the first blocking.
Step: Unblock the first listener
Test success: singleThreadMessageDispatch
Test starting: specificCollectionPoolAndDefaultPool
Description: Tests it is possible to specify a pool for a specific collection, with a default pool for the remainder.
Added fixture: Create a ReceivedMessageHandler with a one specific pool for Collection1. The Collection1 pool should be limited to 1 thread.
Step: Dispatch two messages for collection1, blocking on the processing of the first message.
Step: Dispatch a message for the other collection.
Step: Dispatch a message with no collectionID.
Step: Unblock the blocked collection1 listener
Test success: specificCollectionPoolAndDefaultPool
Test starting: specificCollectionPoolWithSpecificMessageTypePool
Description: Tests it is possible to specify a pool for a specific collection for only a specificmessage type.
Added fixture: Create a ReceivedMessageHandler with a one specific pool for Collection1 and PutFileRequests. The pool should be limited to 1 thread.
Step: Dispatch two putFileRequests for collection1, blocking on the processing of the first message.
Step: Dispatch a putFile request for the other collection.
Step: Dispatch a status request for collection1.
Step: Unblock the blocked collection1 listener
Test success: specificCollectionPoolWithSpecificMessageTypePool
Test starting: specificMessageCategoryPoolAndDefaultPool
Description: Tests it is possible to specify a pool for a specific message category, with a default pool for the remainder.
Added fixture: Create a ReceivedMessageHandler with a one specific pool for slow requests. The put file pool should be limited to 1 thread.
Step: Dispatch two put messages, blocking on the processing of the first message.
Step: Dispatch a status request message.
Step: Unblock the blocked put listener
Test success: specificMessageCategoryPoolAndDefaultPool
Test starting: specificMessageNamePoolAndDefaultPool
Description: Tests it is possible to specify a pool for a specific message type, with a default pool for the remainder.
Added fixture: Create a ReceivedMessageHandler with a one specific pool for put requests. The put file pool should be limited to 1 thread.
Step: Dispatch two put messages, blocking on the processing of the first message.
Step: Dispatch a status request message.
Step: Unblock the blocked put listener
Test success: specificMessageNamePoolAndDefaultPool
Test starting: specificMessagePools
Description: Tests that different message types can be handled by different executors.
Added fixture: Create a ReceivedMessageHandler with a two pools, one for status requests and one for put requests. The put file pool should be limited to 1 thread.
Step: Dispatch two put messages, blocking on the processing of the first message.
Step: Dispatch a status request message.
Step: Unblock the blocked put listener
Test success: specificMessagePools
Starting testcase SecurityExceptionTest
Test starting: testSecurityException
Description: Test the instantiation of the exception
Step: Setup
Step: Try to throw such an exception
Step: Throw the exception with an embedded exception
Test success: testSecurityException
Starting testcase TimeMeasurementUtilsTest
Test starting: testCompareMilliSeconds
Description: Test the comparison between TimeMeasure units.
Test success: testCompareMilliSeconds
Test starting: testCompareMilliSecondsToHours
Description: Test the comparison between milliseconds and hours.
Test success: testCompareMilliSecondsToHours
Test starting: testMaxValue
Description: Test the Maximum value
Test success: testMaxValue
Test starting: utilityTester
Description: Test that the utility class is a proper utility class.
Test success: utilityTester
Starting testcase ArgumentValidatorTest
Test starting: testArgumentValidatorArrays
Description: Test the argument validator for arguments for arrays
Step: Check against null or empty arrays
Test success: testArgumentValidatorArrays
Test starting: testArgumentValidatorBoolean
Description: Test the argument validator for arguments for booleans
Step: validate checkTrue
Test success: testArgumentValidatorBoolean
Test starting: testArgumentValidatorCollection
Description: Test the argument validator for arguments for collections
Step: Check against null or empty collection
Test success: testArgumentValidatorCollection
Test starting: testArgumentValidatorInteger
Description: Test the argument validator for arguments for integers
Step: Test not negative
Step: Test positive
Test success: testArgumentValidatorInteger
Test starting: testArgumentValidatorLong
Description: Test the argument validator for arguments for longs
Step: Test not negative
Step: Test positive
Test success: testArgumentValidatorLong
Test starting: testArgumentValidatorObject
Description: Test the argument validator for arguments not null
Step: Test not null
Test success: testArgumentValidatorObject
Test starting: testArgumentValidatorString
Description: Test the argument validator for arguments for strings
Step: Test empty string
Test success: testArgumentValidatorString
Test starting: utilityTester
Description: Test that the utility class is a proper utility class.
Test success: utilityTester
Starting testcase HttpFileExchangeTest
Test starting: checkUrlEncodingOfFilenamesTest
Description: Tests that the filename is url-encoded correctly for a configured webdav server
Step: Check plain filename (a filename that does not see any changes due to urlencoding
Step: Check that + is encoded as expected
Test success: checkUrlEncodingOfFilenamesTest
Starting testcase MessageSignerExceptionTest
Test starting: testMessageSigningException
Description: Test the instantiation of the exception
Step: Setup
Step: Try to throw such an exception
Step: Throw the exception with an embedded exception
Test success: testMessageSigningException
Starting testcase OperationAuthorizationExceptionTest
Test starting: testOperationAuthorizationException
Description: Test the instantiation of the exception
Step: Setup
Step: Try to throw such an exception
Step: Throw the exception with an embedded exception
Test success: testOperationAuthorizationException
Starting testcase PermissionStoreTest
Test starting: certificateFingerprintTest
Description: Tests that a certificate fingerprint can correctly be retrived for a signer.
Added fixture: Create signer to lookup fingerprint
Step: Lookup fingerprint based on signerId
Test success: certificateFingerprintTest
Test starting: negativeCertificateRetrievalTest
Description: Tests that a certificate cannot be retrieved based on the wrong signerId.
Step: Create signer and modify its ID so lookup will fail
Step: Lookup certificate based on signerId
Test success: negativeCertificateRetrievalTest
Test starting: positiveCertificateRetrievalTest
Description: Tests that a certificate can be retrieved based on the correct signerId.
Step: Create signer to lookup certificate
Step: Lookup certificate based on signerId
Test success: positiveCertificateRetrievalTest
Starting testcase ActiveMQMessageBusTest
02:18:52.995 WARN o.a.activemq.broker.BrokerService - Memory Usage for the Broker (1024 mb) is more than the maximum available for the JVM: 487 mb - resetting to 70% of maximum available: 341 mb
02:18:53.014 WARN o.a.activemq.broker.BrokerService - Temporary Store limit is 51200 mb (current store usage is 0 mb). The data directory: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-core/target only has 7444 mb of usable space - resetting to maximum available disk space: 7444 mb
Test starting: collectionFilterTest
Description: Test that message bus filters identify requests to other collection, eg. ignores these.
Step: Send an identify request with a undefined 'Collection' header property, eg. this identify requests should be handled by everybody.
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@25ed2787[correlationID=12345, collectionID=MyCollection, destination=topic://collectionTopic, replyTo=topic://clientTopic, from=ClientPillar, to=<null>, version=28, minVersion=24, auditTrailInformation=User: Name, Institution: Place, fileID=MyDataID]
Step: Send an identify request with the 'Collection' header property set to my collection
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@2b2add4a[correlationID=12345, collectionID=MyCollection, destination=topic://collectionTopic, replyTo=topic://clientTopic, from=ClientPillar, to=<null>, version=28, minVersion=24, auditTrailInformation=User: Name, Institution: Place, fileID=MyDataID]
Step: Send an invalid message with the 'Receiver' header property set to another specific component
Test success: collectionFilterTest
Test starting: sendMessageToSpecificComponentTest
Description: Test that message bus correct uses the 'to' header property to indicated that the message is meant for a specific component
Step: Send a message with the 'Recipient' parameter set to at specific component
Stimuli: Sending message: org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@69356aca[correlationID=12345, collectionID=MySla, destination=TEST-TOPIC-cibuild01, replyTo=topic://clientTopic, from=ClientPillar, to=specificReceiver, version=28, minVersion=24, auditTrailInformation=User: Name, Institution: Place, fileID=MyDataID]
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@2f154cf7[correlationID=12345, collectionID=MySla, destination=TEST-TOPIC-cibuild01, replyTo=topic://clientTopic, from=ClientPillar, to=specificReceiver, version=28, minVersion=24, auditTrailInformation=User: Name, Institution: Place, fileID=MyDataID]
Test success: sendMessageToSpecificComponentTest
Result: The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@2f154cf7[correlationID=12345, collectionID=MySla, destination=TEST-TOPIC-cibuild01, replyTo=topic://clientTopic, from=ClientPillar, to=specificReceiver, version=28, minVersion=24, auditTrailInformation=User: Name, Institution: Place, fileID=MyDataID]
02:18:59.648 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@2f154cf7[correlationID=12345, collectionID=MySla, destination=TEST-TOPIC-cibuild01, replyTo=topic://clientTopic, from=ClientPillar, to=specificReceiver, version=28, minVersion=24, auditTrailInformation=User: Name, Institution: Place, fileID=MyDataID]
Test starting: toFilterTest
Description: Test that message bus filters identify requests to other components, eg. ignores these.
Step: Send an identify request with a undefined 'To' header property, eg. this identify requests should be handled by all components.
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@6a17d771[correlationID=12345, collectionID=MySla, destination=TEST-TOPIC-cibuild01, replyTo=topic://clientTopic, from=ClientPillar, to=<null>, version=28, minVersion=24, auditTrailInformation=User: Name, Institution: Place, fileID=MyDataID]
Step: Send an identify request with the 'To' header property set to this component
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@268a04ab[correlationID=12345, collectionID=MySla, destination=TEST-TOPIC-cibuild01, replyTo=topic://clientTopic, from=ClientPillar, to=<null>, version=28, minVersion=24, auditTrailInformation=User: Name, Institution: Place, fileID=MyDataID]
Step: Send an invalid identify request with the 'To' header property set to another specific component
Step: Send an identify response with the 'To' header property set to another component
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileResponse@5bb75dbd[correlationID=12345, collectionID=MySla, destination=topic://collectionTopic, replyTo=topic://clientTopic, from=MyPillar, to=<null>, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@5ec0d0c8[responseCode=IDENTIFICATION_POSITIVE, responseText=Ready to delete file 'MyDataID'.], fileID=MyDataID, pillarID=MyPillar, pillarChecksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@a38283e[checksumType=MD5, checksumSalt={-85,-51}, otherChecksumType=<null>], timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@7c61da8e[timeMeasureUnit=MILLISECONDS, timeMeasureValue=1000]]
Step: Send an non-identify request with the 'To' header property set to another component
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.DeleteFileRequest@1dda2a0a[correlationID=12345, collectionID=MySla, destination=TEST-TOPIC-cibuild01, replyTo=topic://clientTopic, from=ClientPillar, to=<null>, version=28, minVersion=24, auditTrailInformation=User: Name, Institution: Place, pillarID=MyPillar, fileID=MyDataID, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@20fbd09e[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7e93b686[checksumType=MD5, checksumSalt={-85,-85}, otherChecksumType=<null>], checksumValue={19,95,33,86}, calculationTimestamp=2011-02-17T09:47:00], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@40914923[checksumType=MD5, checksumSalt={-85,-51}, otherChecksumType=<null>]]
Test success: toFilterTest
Starting testcase CalendarUtilsTest
Test starting: calendarTester
Description: Test the calendar utility class
Step: Test the convertion of a date
Step: Test that a 'null' date is equivalent to epoch
Step: Test epoch
Step: Test that a given time in millis is extractable in millis
Step: Test the 'getNow' function
Step: Test the reverse conversion, from XMLCalendar to Date
Test success: calendarTester
Test starting: utilityTester
Description: Test that the utility class is a proper utility class.
Test success: utilityTester
Test starting: busActivityTest
Description: Tests whether it is possible to create a message listener, and then set it to listen to the topic. Then puts a messageon the topic for the message listener to find, andtests whether it finds the correct message.
Step: Send a message to the topic
Stimuli: Sending message: org.bitrepository.bitrepositorymessages.AlarmMessage@64096a41[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@33de9d85[origDateTime=2011-05-03T11:18:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>]]
Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@45c4ffe9[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@4752d85e[origDateTime=2011-05-03T11:18:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>]]
Step: Make sure both listeners received the message
Test success: busActivityTest
Test starting: twoListenersForTopicTest
Description: Verifies that two listeners on the same topic both receive the message
Step: Make a connection to the message bus and add two listeners
Step: Send a message to the topic
Stimuli: Sending message: org.bitrepository.bitrepositorymessages.AlarmMessage@21dbd651[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@5f63a6f2[origDateTime=2011-05-03T11:18:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>]]
Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@e7656b7[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@130d9ed1[origDateTime=2011-05-03T11:18:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>]]
Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@7c31585d[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@4e55884c[origDateTime=2011-05-03T11:18:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>]]
Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@3077a7ab[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@27aeb957[origDateTime=2011-05-03T11:18:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>]]
Step: Make sure both listeners received the message
Test success: twoListenersForTopicTest
Result: The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.AlarmMessage@e7656b7[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@130d9ed1[origDateTime=2011-05-03T11:18:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>]]
02:19:03.648 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.AlarmMessage@e7656b7[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@130d9ed1[origDateTime=2011-05-03T11:18:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>]]
Test starting: utilityTester
Description: Test that the utility class is a proper utility class.
Test success: utilityTester
Starting testcase SecurityManagerTest
Test starting: certificateAuthorizationBehaviourTest
Description: Tests that a certificate is only allowed by registered users (component).
Step: Check that the registered component is allowed.
Step: Check that an unregistered component is not allowed.
Test success: certificateAuthorizationBehaviourTest
Test starting: negativeSigningAuthenticationRoundtripBadDataTest
Description: Tests that a roundtrip of signing a request and afterwards authenticating it fails due to bad data
Description: Tests that a roundtrip of signing a request and afterwards authenticating is succedes.
Step: Sign a chunck of data.
Step: Check signature matches the data
Test success: negativeSigningAuthenticationRoundtripBadDataTest
Test starting: negativeSigningAuthenticationRoundtripUnkonwnCertificateTest
Description: Tests that a roundtrip of signing a request and afterwards authenticating it fails due to a unknown certificate.
Step: Sign a chunck of data.
Step: Check signature matches the data
Test success: negativeSigningAuthenticationRoundtripUnkonwnCertificateTest
Test starting: operationAuthorizationBehaviourTest
Description: Tests that a signature only allows the correct requests.
Step: Check that GET_FILE is allowed.
Test success: operationAuthorizationBehaviourTest
Test starting: positiveSigningAuthenticationRoundtripTest
Description: Tests that a roundtrip of signing a request and afterwards authenticating is succedes.
Step: Sign a chunck of data.
Step: Check signature matches the data
Test success: positiveSigningAuthenticationRoundtripTest
Starting testcase UnregisteredPermissionTest
Test starting: testUnregisteredPermissionException
Description: Test the instantiation of the exception
Step: Setup
Step: Try to throw such an exception
Step: Throw the exception with an embedded exception
Test success: testUnregisteredPermissionException
Starting testcase CertificateUseExceptionTest
Test starting: testCertificateUseException
Description: Test the instantiation of the exception
Step: Setup
Step: Try to throw such an exception
Step: Throw the exception with an embedded exception
Test success: testCertificateUseException
Starting testcase MultiThreadedMessageBusTest
Test starting: manyTheadsBeforeFinish
Description: Tests whether it is possible to start the handling of many threads simultaneously.
Step: Send one message for each listener
Stimuli: Sending message: org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileRequest@2e2a42ba[correlationID=12345, collectionID=MySla, destination=BusActivityTest, replyTo=topic://clientTopic, from=ClientPillar, to=<null>, version=28, minVersion=24, auditTrailInformation=User: Name, Institution: Place, fileID=MyDataID]
Stimuli: Sending message: org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileRequest@2e2a42ba[correlationID=12345, collectionID=MySla, destination=BusActivityTest, replyTo=topic://clientTopic, from=ClientPillar, to=<null>, version=28, minVersion=24, auditTrailInformation=User: Name, Institution: Place, fileID=MyDataID]
Stimuli: Sending message: org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileRequest@2e2a42ba[correlationID=12345, collectionID=MySla, destination=BusActivityTest, replyTo=topic://clientTopic, from=ClientPillar, to=<null>, version=28, minVersion=24, auditTrailInformation=User: Name, Institution: Place, fileID=MyDataID]
Test success: manyTheadsBeforeFinish
Starting testcase FileUtilsTest
Test starting: createDeleteDirectoryTester
Description: Test the ability to delete directories.
Step: Test deleting a directory with file and subdirectory
Test success: createDeleteDirectoryTester
Test starting: createDirectoryTester
Description: Test the ability to create directories.
Step: Test the ability to create a directory
Step: Test error scenarios, when the directory path is a file
Test success: createDirectoryTester
Test starting: createSubDirectoryTester
Description: Test the ability to create sub directories.
Step: Test the ability to create sub-directories
Step: Test that it fails if the 'directory' is actually a file
Step: Test that it fails, if the parent directory does not allow writing
Test success: createSubDirectoryTester
Test starting: deprecateFileTester
Description: Test the deprecation of a file.
Step: Setup
Step: Deprecate the file
Test success: deprecateFileTester
Test starting: moveFileTester
Description: Test the moving of a file.
Step: Setup
Step: Move the file
Test success: moveFileTester
Test starting: unzipFileTester
Description: Test unzipping a file.
Step: Setup
Step: Unzip the zipfile to the directory
Test success: unzipFileTester
Test starting: utilityTester
Description: Test that the utility class is a proper utility class.
Test success: utilityTester
Test starting: writeInputstreamTester
Description: Test writing an inputstream to a file.
Step: Setup
Step: Write the input stream to the file
Test success: writeInputstreamTester
Starting testcase TimeUtilsTest
Test starting: shortDateTest
Test success: shortDateTest
Test starting: timeTester
Description: Tests the TimeUtils. Pi days = 271433605 milliseconds
Step: Test that milliseconds can be converted into human readable seconds
Step: Test that milliseconds can be converted into human readable minutes.
Step: Test that milliseconds can be converted into human readable hours.
Step: Test that milliseconds can be converted into human readable minutes.
Step: Test the human readable output.
Test success: timeTester
Test starting: utilityTester
Description: Test that the utility class is a proper utility class.
Test success: utilityTester
Test starting: zeroIntervalTest
Description: Verifies that a 0 ms interval is represented correctly
Step: Call the millisecondsToHuman with 0 ms
Test success: zeroIntervalTest
Starting testcase MessageUtilsTest
Test starting: testIdentificationResponse
Description: Tests isIdentifyResponse method in the message utility class.
Step: validate that it can see a identify response
Test success: testIdentificationResponse
Test starting: testPositiveIdentification
Description: Tests isPositiveIdentifyResponse method in the message utility class.
Step: validate that it can see a positive identify response
Test success: testPositiveIdentification
Test starting: testProgressResponse
Description: Tests isPositiveProgressResponse method in the message utility class.
Step: validate progress response
Test success: testProgressResponse
Test starting: validateUtilityClass
Description: Validating that the utility class is actually an utility class.
Test success: validateUtilityClass
Starting testcase UnableToFinishExceptionTest
Test starting: testUnableToFinish
Description: Test the instantiation of the exception
Step: Setup
Step: Try to throw such an exception
Step: Throw the exception with an embedded exception
Test success: testUnableToFinish
Starting testcase GeneralMessageBusTest
Test starting: busActivityTest
Description: Tests whether it is possible to create a message listener, and then set it to listen to the topic. Then puts a messageon the topic for the message listener to find, andtests whether it finds the correct message.
Step: Send a message to the topic
Stimuli: Sending message: org.bitrepository.bitrepositorymessages.AlarmMessage@3aa8ebf9[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@2ff84e42[origDateTime=2011-05-03T11:18:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>]]
Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@2cdc94ad[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@4cf9929a[origDateTime=2011-05-03T11:18:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>]]
Step: Make sure both listeners received the message
Test success: busActivityTest
Test starting: twoListenersForTopicTest
Description: Verifies that two listeners on the same topic both receive the message
Step: Make a connection to the message bus and add two listeners
Step: Send a message to the topic
Stimuli: Sending message: org.bitrepository.bitrepositorymessages.AlarmMessage@2ac4079f[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@72aa6a00[origDateTime=2011-05-03T11:18:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>]]
Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@221b6f46[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@4db56a42[origDateTime=2011-05-03T11:18:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>]]
Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@2624ffdd[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@39b523c7[origDateTime=2011-05-03T11:18:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>]]
Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@6326657d[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@5727c0a7[origDateTime=2011-05-03T11:18:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>]]
Step: Make sure both listeners received the message
Test success: twoListenersForTopicTest
Result: The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.AlarmMessage@221b6f46[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@4db56a42[origDateTime=2011-05-03T11:18:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>]]
02:19:11.251 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.AlarmMessage@221b6f46[correlationID=12345, collectionID=MySla, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=queue://MyQueueOrTopic, from=MyPillar, to=<null>, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@4db56a42[origDateTime=2011-05-03T11:18:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MyPillar, alarmText=Component failure, fileID=MydataId1, collectionID=<null>]]
Test starting: utilityTester
Description: Test that the utility class is a proper utility class.
Test success: utilityTester
Starting testcase SettingsLoaderTest
Test starting: testDevelopmentCollectionSettingsLoading
Test success: testDevelopmentCollectionSettingsLoading
Test starting: testExampleSettingsLoading
Test success: testExampleSettingsLoading
Finished testcase
02:19:11.588 ERROR o.b.protocol.bus.RawMessagebus - JMSException caught:
javax.jms.JMSException: java.io.EOFException
at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:54) ~[activemq-client-5.13.0.jar:5.13.0]
at org.apache.activemq.ActiveMQConnection.onAsyncException(ActiveMQConnection.java:1966) ~[activemq-client-5.13.0.jar:5.13.0]
at org.apache.activemq.ActiveMQConnection.onException(ActiveMQConnection.java:1985) ~[activemq-client-5.13.0.jar:5.13.0]
at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:101) ~[activemq-client-5.13.0.jar:5.13.0]
at org.apache.activemq.transport.ResponseCorrelator.onException(ResponseCorrelator.java:126) ~[activemq-client-5.13.0.jar:5.13.0]
at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:101) ~[activemq-client-5.13.0.jar:5.13.0]
at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:101) ~[activemq-client-5.13.0.jar:5.13.0]
at org.apache.activemq.transport.WireFormatNegotiator.onException(WireFormatNegotiator.java:173) ~[activemq-client-5.13.0.jar:5.13.0]
at org.apache.activemq.transport.AbstractInactivityMonitor.onException(AbstractInactivityMonitor.java:344) ~[activemq-client-5.13.0.jar:5.13.0]
at org.apache.activemq.transport.TransportSupport.onException(TransportSupport.java:96) ~[activemq-client-5.13.0.jar:5.13.0]
at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:219) ~[activemq-client-5.13.0.jar:5.13.0]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_11]
Caused by: java.io.EOFException: null
at java.io.DataInputStream.readInt(DataInputStream.java:392) ~[na:1.8.0_11]
at org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:267) ~[activemq-client-5.13.0.jar:5.13.0]
at org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:240) ~[activemq-client-5.13.0.jar:5.13.0]
at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:232) ~[activemq-client-5.13.0.jar:5.13.0]
at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:215) ~[activemq-client-5.13.0.jar:5.13.0]
... 1 common frames omitted
02:19:11.607 ERROR o.b.protocol.bus.RawMessagebus - JMSException caught:
javax.jms.JMSException: java.io.EOFException
at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:54) ~[activemq-client-5.13.0.jar:5.13.0]
at org.apache.activemq.ActiveMQConnection.onAsyncException(ActiveMQConnection.java:1966) ~[activemq-client-5.13.0.jar:5.13.0]
at org.apache.activemq.ActiveMQConnection.onException(ActiveMQConnection.java:1985) ~[activemq-client-5.13.0.jar:5.13.0]
at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:101) ~[activemq-client-5.13.0.jar:5.13.0]
at org.apache.activemq.transport.ResponseCorrelator.onException(ResponseCorrelator.java:126) ~[activemq-client-5.13.0.jar:5.13.0]
at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:101) ~[activemq-client-5.13.0.jar:5.13.0]
at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:101) ~[activemq-client-5.13.0.jar:5.13.0]
at org.apache.activemq.transport.WireFormatNegotiator.onException(WireFormatNegotiator.java:173) ~[activemq-client-5.13.0.jar:5.13.0]
at org.apache.activemq.transport.AbstractInactivityMonitor.onException(AbstractInactivityMonitor.java:344) ~[activemq-client-5.13.0.jar:5.13.0]
at org.apache.activemq.transport.TransportSupport.onException(TransportSupport.java:96) ~[activemq-client-5.13.0.jar:5.13.0]
at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:219) ~[activemq-client-5.13.0.jar:5.13.0]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_11]
Caused by: java.io.EOFException: null
at java.io.DataInputStream.readInt(DataInputStream.java:392) ~[na:1.8.0_11]
at org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:267) ~[activemq-client-5.13.0.jar:5.13.0]
at org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:240) ~[activemq-client-5.13.0.jar:5.13.0]
at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:232) ~[activemq-client-5.13.0.jar:5.13.0]
at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:215) ~[activemq-client-5.13.0.jar:5.13.0]
... 1 common frames omitted
02:19:11.613 ERROR o.b.protocol.bus.RawMessagebus - JMSException caught:
javax.jms.JMSException: java.io.EOFException
at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:54) ~[activemq-client-5.13.0.jar:5.13.0]
at org.apache.activemq.ActiveMQConnection.onAsyncException(ActiveMQConnection.java:1966) ~[activemq-client-5.13.0.jar:5.13.0]
at org.apache.activemq.ActiveMQConnection.onException(ActiveMQConnection.java:1985) ~[activemq-client-5.13.0.jar:5.13.0]
at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:101) ~[activemq-client-5.13.0.jar:5.13.0]
at org.apache.activemq.transport.ResponseCorrelator.onException(ResponseCorrelator.java:126) ~[activemq-client-5.13.0.jar:5.13.0]
at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:101) ~[activemq-client-5.13.0.jar:5.13.0]
at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:101) ~[activemq-client-5.13.0.jar:5.13.0]
at org.apache.activemq.transport.WireFormatNegotiator.onException(WireFormatNegotiator.java:173) ~[activemq-client-5.13.0.jar:5.13.0]
at org.apache.activemq.transport.AbstractInactivityMonitor.onException(AbstractInactivityMonitor.java:344) ~[activemq-client-5.13.0.jar:5.13.0]
at org.apache.activemq.transport.TransportSupport.onException(TransportSupport.java:96) ~[activemq-client-5.13.0.jar:5.13.0]
at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:219) ~[activemq-client-5.13.0.jar:5.13.0]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_11]
Caused by: java.io.EOFException: null
at java.io.DataInputStream.readInt(DataInputStream.java:392) ~[na:1.8.0_11]
at org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:267) ~[activemq-client-5.13.0.jar:5.13.0]
at org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:240) ~[activemq-client-5.13.0.jar:5.13.0]
at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:232) ~[activemq-client-5.13.0.jar:5.13.0]
at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:215) ~[activemq-client-5.13.0.jar:5.13.0]
... 1 common frames omitted
Finished suite
Finished project
Tests run: 95, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 45.271 sec - in TestSuite
Results :
Tests run: 95, Failures: 0, Errors: 0, Skipped: 0
[JENKINS] Recording test results
log4j:WARN No appenders could be found for logger (org.apache.commons.beanutils.converters.BooleanConverter).
log4j:WARN Please initialize the log4j system properly.
[INFO]
[INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ bitrepository-core ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-core/target/bitrepository-core-1.7-SNAPSHOT.jar
[INFO]
[INFO] --- maven-jar-plugin:2.4:test-jar (default) @ bitrepository-core ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-core/target/bitrepository-core-1.7-SNAPSHOT-tests.jar
[INFO]
[INFO] --- maven-source-plugin:2.2.1:jar-no-fork (attach-sources-no-fork) @ bitrepository-core ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-core/target/bitrepository-core-1.7-SNAPSHOT-sources.jar
[INFO]
[INFO] --- maven-install-plugin:2.5.1:install (default-install) @ bitrepository-core ---
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-core/target/bitrepository-core-1.7-SNAPSHOT.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-core/1.7-SNAPSHOT/bitrepository-core-1.7-SNAPSHOT.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-core/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-core/1.7-SNAPSHOT/bitrepository-core-1.7-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-core/target/bitrepository-core-1.7-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-core/1.7-SNAPSHOT/bitrepository-core-1.7-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-core/target/bitrepository-core-1.7-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-core/1.7-SNAPSHOT/bitrepository-core-1.7-SNAPSHOT-sources.jar
[JENKINS] Archiving disabled
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Client 1.7-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-client ---
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ bitrepository-client ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 4 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ bitrepository-client ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 130 source files to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/target/classes
[WARNING] /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/src/main/java/org/bitrepository/commandline/utils/CommandLineArgumentsHandler.java: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/src/main/java/org/bitrepository/commandline/utils/CommandLineArgumentsHandler.java uses or overrides a deprecated API.
[WARNING] /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/src/main/java/org/bitrepository/commandline/utils/CommandLineArgumentsHandler.java: Recompile with -Xlint:deprecation for details.
[INFO]
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ bitrepository-client ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/src/test/resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ bitrepository-client ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 41 source files to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/target/test-classes
[INFO]
[INFO] --- maven-surefire-plugin:2.17:test (default-test) @ bitrepository-client ---
[INFO] Surefire report directory: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/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 AuditTrailClientComponentTest
Test starting: getAllAuditTrailsTest
Description: Tests the simplest case of getting all audit trail event for all contributers.
Step: Create a AuditTrailClient.
Step: Retrieve all audit trails from the collection by calling with a null componentQueries array
Stimuli: Calling getAuditTrails(null, default-test-file.txt, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@51bf5add[correlationID=9116c293-bc1b-46a4-8ed2-9d241d8c4759, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=getAllAuditTrailsTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
Result: Received event: 9116c293: GET_AUDIT_TRAILS for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
Step: Send a identifyResponse from each pillar
Result: Received event: 9116c293: GET_AUDIT_TRAILS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 9116c293: GET_AUDIT_TRAILS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 9116c293: GET_AUDIT_TRAILS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2, Pillar1]
Result: Received event: 9116c293: GET_AUDIT_TRAILS for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for audit trails
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@1b410b60[correlationID=9116c293-bc1b-46a4-8ed2-9d241d8c4759, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=getAllAuditTrailsTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar1, fileID=default-test-file.txt, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@19b843ba[correlationID=9116c293-bc1b-46a4-8ed2-9d241d8c4759, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=getAllAuditTrailsTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar2, fileID=default-test-file.txt, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
Step: Send a final response from pillar 1
Result: Received event: 9116c293: GET_AUDIT_TRAILS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, NumberOfAuditTrailEvents=2, PartialResult=false
Step: Send a final response from pillar 2
Result: Received event: 9116c293: GET_AUDIT_TRAILS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2, NumberOfAuditTrailEvents=2, PartialResult=false
Result: Received event: 9116c293: GET_AUDIT_TRAILS for file default-test-file.txt: COMPLETE:
Test success: getAllAuditTrailsTest
Test starting: getSomeAuditTrailsTest
Description: Tests the client maps a AuditTrail query correctly to a GetAuditTrail request.
Step: Request audit trails from pillar 1 with both min and max sequence number set.
Stimuli: Calling getAuditTrails([AuditTrailQuery{componentID='Pillar1, minTimestamp=null, maxTimestamp=null, maxNumberOfResults=10000}minSequenceNumber=1, maxSequenceNumber=3}], null, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@5ba88be8[correlationID=a1222bbe-48de-4a5f-bf58-557bd5c3b93a, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=getSomeAuditTrailsTest, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>]
Result: Received event: a1222bbe: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
Step: Send a identifyResponse from pillar1
Result: Received event: a1222bbe: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: a1222bbe: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: a1222bbe: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1], Sending request for audit trails
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@3899782c[correlationID=a1222bbe-48de-4a5f-bf58-557bd5c3b93a, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=getSomeAuditTrailsTest, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar1, fileID=<null>, minSequenceNumber=1, maxSequenceNumber=3, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=10000, resultAddress=<null>]
Step: Verify no request is sent to pillar2
Step: Send a final response from pillar 1
Result: Received event: a1222bbe: GET_AUDIT_TRAILS: COMPONENT_COMPLETE: ContributorID Pillar1, NumberOfAuditTrailEvents=2, PartialResult=false
Result: Received event: a1222bbe: GET_AUDIT_TRAILS: COMPLETE:
Test success: getSomeAuditTrailsTest
Test starting: incompleteSetOfFinalResponsesTest
Description: Verify that the GetAuditTrail client works correct without receiving responses from all contributers.
Step: Configure 500 ms second timeout for the operation itself. The default 2 contributers collection is used
Stimuli: Calling getAuditTrails(null, null, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@3668d4[correlationID=a032a1e0-69fa-45a7-941e-e350e0563836, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=incompleteSetOfFinalResponsesTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
Result: Received event: a032a1e0: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
Step: Send a identifyResponse from each of the two pillars
Result: Received event: a032a1e0: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: a032a1e0: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: a032a1e0: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2, Pillar1]
Result: Received event: a032a1e0: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for audit trails
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@7f6f61c8[correlationID=a032a1e0-69fa-45a7-941e-e350e0563836, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=incompleteSetOfFinalResponsesTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar1, fileID=<null>, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@4c2cc639[correlationID=a032a1e0-69fa-45a7-941e-e350e0563836, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=incompleteSetOfFinalResponsesTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar2, fileID=<null>, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
Test success: incompleteSetOfFinalResponsesTest
Result: The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@4c2cc639[correlationID=a032a1e0-69fa-45a7-941e-e350e0563836, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=incompleteSetOfFinalResponsesTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar2, fileID=<null>, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
02:19:29.016 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@4c2cc639[correlationID=a032a1e0-69fa-45a7-941e-e350e0563836, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=incompleteSetOfFinalResponsesTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar2, fileID=<null>, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
Test starting: negativeGetAuditTrailsResponseTest
Description: Verify that the GetAuditTrail client works correct when receiving a negative GetAuditTrails response from one contributers.
Step: Create a AuditTrailClient.
Step: Retrieve all audit trails from the collection by calling with a null componentQueries array
Stimuli: Calling getAuditTrails(null, null, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@7e3060d8[correlationID=53243cd4-4bec-40c5-9005-dc85c51470c6, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=negativeGetAuditTrailsResponseTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
Result: Received event: 53243cd4: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
Step: Send a identifyResponse from each of the two pillars
Result: Received event: 53243cd4: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 53243cd4: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 53243cd4: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2]
Result: Received event: 53243cd4: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for audit trails
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@7b64240d[correlationID=53243cd4-4bec-40c5-9005-dc85c51470c6, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=negativeGetAuditTrailsResponseTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar1, fileID=<null>, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@62fad19[correlationID=53243cd4-4bec-40c5-9005-dc85c51470c6, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=negativeGetAuditTrailsResponseTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar2, fileID=<null>, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
Step: Send a failed response from pillar 1
Result: Received event: 53243cd4: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE, GetAuditTrails failed
Step: Send a final response from pillar 2
Result: Received event: 53243cd4: GET_AUDIT_TRAILS: COMPONENT_COMPLETE: ContributorID Pillar2, NumberOfAuditTrailEvents=2, PartialResult=false
Result: Received event: 53243cd4: GET_AUDIT_TRAILS: FAILED: , Failed operation. Cause(s):
[53243cd4: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE, GetAuditTrails failed]
Test success: negativeGetAuditTrailsResponseTest
Result: Received event: a032a1e0: GET_AUDIT_TRAILS: FAILED: , Failed to receive responses from all contributors before timeout(500ms). Missing contributors [Pillar1, Pillar2]
Test starting: noFinalResponsesTest
Description: Tests the the AuditTrailClient handles lack of Final Responses gracefully
Step: Set a 100 ms timeout for the operation.
Step: Make the client ask for all audit trails.
Stimuli: Calling getAuditTrails(null, null, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@2c4ca0f9[correlationID=afc79b2b-2c7c-4f11-9300-97cf83727f95, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noFinalResponsesTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
Result: Received event: afc79b2b: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
Step: Send a identifyResponse from each of the two pillars
Result: Received event: afc79b2b: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: afc79b2b: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: afc79b2b: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2]
Result: Received event: afc79b2b: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for audit trails
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@6e57e95e[correlationID=afc79b2b-2c7c-4f11-9300-97cf83727f95, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noFinalResponsesTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar1, fileID=<null>, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@2755d705[correlationID=afc79b2b-2c7c-4f11-9300-97cf83727f95, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noFinalResponsesTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar2, fileID=<null>, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
Step: Wait for 1 second
Result: Received event: afc79b2b: GET_AUDIT_TRAILS: FAILED: , Failed to receive responses from all contributors before timeout(100ms). Missing contributors [Pillar1, Pillar2]
Test success: noFinalResponsesTest
Result: The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@6e57e95e[correlationID=afc79b2b-2c7c-4f11-9300-97cf83727f95, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noFinalResponsesTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar1, fileID=<null>, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
02:19:29.786 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@6e57e95e[correlationID=afc79b2b-2c7c-4f11-9300-97cf83727f95, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noFinalResponsesTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar1, fileID=<null>, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
Result: The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@2755d705[correlationID=afc79b2b-2c7c-4f11-9300-97cf83727f95, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noFinalResponsesTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar2, fileID=<null>, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
02:19:29.786 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@2755d705[correlationID=afc79b2b-2c7c-4f11-9300-97cf83727f95, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noFinalResponsesTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar2, fileID=<null>, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
Test starting: progressEventsTest
Description: Tests that progress events are handled correctly.
Step: Create a AuditTrailClient.
Step: Retrieve all audit trails from the collection by calling with a null componentQueries array
Stimuli: Calling getAuditTrails(null, null, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@3d829787[correlationID=038a1591-5e89-4f7a-85b8-caf41cf2924e, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=progressEventsTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
Result: Received event: 038a1591: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
Step: Send a identifyResponse from each of the two pillars
Result: Received event: 038a1591: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 038a1591: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 038a1591: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2, Pillar1]
Result: Received event: 038a1591: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for audit trails
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@60b85ba1[correlationID=038a1591-5e89-4f7a-85b8-caf41cf2924e, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=progressEventsTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar1, fileID=<null>, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@492fc69e[correlationID=038a1591-5e89-4f7a-85b8-caf41cf2924e, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=progressEventsTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar2, fileID=<null>, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
Step: Send a progress accepted response from pillar 1
Result: Received event: 038a1591: GET_AUDIT_TRAILS: PROGRESS: ContributorID Pillar1, GetAuditTrails request accepted
Step: Send a general progress response from pillar 2
Result: Received event: 038a1591: GET_AUDIT_TRAILS: PROGRESS: ContributorID Pillar2, Still progressing
Test success: progressEventsTest
Test starting: verifyAuditTrailClientFromFactory
Test success: verifyAuditTrailClientFromFactory
Starting testcase AuditTrailQueryTest
Test starting: testBothSequenceNumberFailure
Description: Test the creation of a AuditTrailQuery with both SequenceNumber, where max is smalle than min.
Test success: testBothSequenceNumberFailure
Test starting: testBothSequenceNumberSuccess
Description: Test the creation of a AuditTrailQuery with both SequenceNumber, where max is larger than min.
Test success: testBothSequenceNumberSuccess
Test starting: testNoSequenceNumbers
Description: Test that a AuditTrailQuery can be created without any sequence numbers.
Test success: testNoSequenceNumbers
Test starting: testOnlyMinSequenceNumber
Description: Test the creation of a AuditTrailQuery with only the minSequenceNumber
Test success: testOnlyMinSequenceNumber
Starting testcase ChecksumExtractionUtilsTest
Test starting: testDefaultChecksumSpec
Description: Test that the default checksum is retrieved when no arguments are given.
Test success: testDefaultChecksumSpec
Test starting: testDefaultChecksumSpecWithSaltArgument
Description: Test that the HMAC version of default checksum is retrieved when the salt arguments are given.
Test success: testDefaultChecksumSpecWithSaltArgument
Test starting: testNonSaltChecksumSpecWithSaltArgument
Description: Test that a salt checksum type is retrieved even though a non-salt checksum algorithm it is given as argument, but a salt argument also is given.
Test success: testNonSaltChecksumSpecWithSaltArgument
Test starting: testNonSaltChecksumSpecWithoutSaltArgument
Description: Test that a non-salt checksum type is retrieved when it is given as argument, and no salt arguments are given.
Test success: testNonSaltChecksumSpecWithoutSaltArgument
Test starting: testSaltChecksumSpecWithSaltArgument
Description: Test that a salt checksum type is retrieved when the salt checksum algorithm it is given as argument, and a salt argument also is given.
Test success: testSaltChecksumSpecWithSaltArgument
Test starting: testSaltChecksumSpecWithoutSaltArgument
Description: Test that a non-salt checksum type is retrieved even though a salt checksum algorithm it is given as argument, but no salt argument also is given.
Test success: testSaltChecksumSpecWithoutSaltArgument
Test starting: collectionIDIncludedInEventsTest
Description: Tests the the client provides collectionID in events.
Step: Set a 0.5 second operation timeout.
Step: Start the operation
Stimuli: Calling getAuditTrails(null, null, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@42cc183e[correlationID=ddd294c0-dc4c-4760-8622-0c92174d4226, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=collectionIDIncludedInEventsTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
Result: Received event: ddd294c0: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
Step: Send positive responses from the pillar1 and a negative response from pillar2
Result: Received event: ddd294c0: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: ddd294c0: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE
Result: Received event: ddd294c0: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: ddd294c0: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1], Sending request for audit trails
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@6a1d6ef2[correlationID=ddd294c0-dc4c-4760-8622-0c92174d4226, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=collectionIDIncludedInEventsTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar1, fileID=<null>, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
Step: Wait for 1 second
Result: Received event: ddd294c0: GET_AUDIT_TRAILS: FAILED: , Failed to receive responses from all contributors before timeout(500ms). Missing contributors [Pillar1]
Test success: collectionIDIncludedInEventsTest
Starting testcase GetChecksumsClientComponentTest
Test starting: collectionIDIncludedInEventsTest
Description: Tests the the client provides collectionID in events.
Step: Set a 0.5 second operation timeout.
Step: Start the operation
Stimuli: Calling getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@25a7fedf, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@79696332[correlationID=91480e39-888f-444e-bfd0-7dc882797f55, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=collectionIDIncludedInEventsTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@ed2f2f6[fileID=<null>, allFileIDs=true], checksumRequestForExistingFile=<null>]
Result: Received event: 91480e39: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums
Step: Send positive responses from the pillar1 and a negative response from pillar2
Result: Received event: 91480e39: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 91480e39: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE
Result: Received event: 91480e39: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 91480e39: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar1], Sending GetFileIDsRequest's
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@7c281eb8[correlationID=91480e39-888f-444e-bfd0-7dc882797f55, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=collectionIDIncludedInEventsTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@65f40689[fileID=<null>, allFileIDs=true], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, checksumRequestForExistingFile=<null>, resultAddress=<null>]
Step: Wait for 1 second
Result: Received event: 91480e39: GET_CHECKSUMS: FAILED: , Failed to receive responses from all contributors before timeout(500ms). Missing contributors [Pillar1]
Test success: collectionIDIncludedInEventsTest
Test starting: conversationTimeoutTest
Description: Tests the the client handles lack of IdentifyPillarResponses gracefully
Step: Set a 100 ms ConversationTimeout.
Step: Start the operation
Stimuli: Calling getAuditTrails(null, null, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@20c812c8[correlationID=360a3c2e-06ad-4370-9167-0c40649f55b4, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=conversationTimeoutTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
Result: Received event: 360a3c2e: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
02:19:35.055 WARN o.b.c.c.m.CollectionBasedConversationMediator - Failing timed out conversation 360a3c2e-06ad-4370-9167-0c40649f55b4 (Age 1008ms)
Result: Received event: 360a3c2e: GET_AUDIT_TRAILS: FAILED: , Failing timed out conversation 360a3c2e-06ad-4370-9167-0c40649f55b4
Test success: conversationTimeoutTest
Test starting: conversationTimeoutTest
Description: Tests the the client handles lack of IdentifyPillarResponses gracefully
Step: Set a 100 ms ConversationTimeout.
Step: Start the operation
Stimuli: Calling getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@25a7fedf, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@68b7d0ef[correlationID=7e296dc3-d518-4d87-8a4e-a44ef30c9410, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=conversationTimeoutTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@7069f076[fileID=<null>, allFileIDs=true], checksumRequestForExistingFile=<null>]
Result: Received event: 7e296dc3: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums
02:19:36.660 WARN o.b.c.c.m.CollectionBasedConversationMediator - Failing timed out conversation 7e296dc3-d518-4d87-8a4e-a44ef30c9410 (Age 1014ms)
Result: Received event: 7e296dc3: GET_CHECKSUMS: FAILED: , Failing timed out conversation 7e296dc3-d518-4d87-8a4e-a44ef30c9410
Test success: conversationTimeoutTest
Test starting: identificationFailureTest
Description: Verify that the client works correctly when a contributor sends a failure response.
Step: Start the operation.
Stimuli: Calling getAuditTrails(null, null, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@1a21f43f[correlationID=52f85df7-efe9-4d1c-8749-f59d501c3989, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=identificationFailureTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
Result: Received event: 52f85df7: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
Step: Send a identification response from contributor1 with a FAILURE response code.
Result: Received event: 52f85df7: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE
Step: Send a identification response from contributor2 with a IDENTIFICATION_POSITIVE response code .
Result: Received event: 52f85df7: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 52f85df7: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: 52f85df7: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar2], Sending request for audit trails
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@241fbec[correlationID=52f85df7-efe9-4d1c-8749-f59d501c3989, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=identificationFailureTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar2, fileID=<null>, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
Step: Verify that the client continues to the performing phase.
Step: Send a final response message from contributor2
Result: Received event: 52f85df7: GET_AUDIT_TRAILS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false
Result: Received event: 52f85df7: GET_AUDIT_TRAILS: FAILED: , Failed operation. Cause(s):
[52f85df7: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE]
Test success: identificationFailureTest
Test starting: identificationFailureTest
Description: Verify that the client works correctly when a contributor sends a failure response.
Step: Start the operation.
Stimuli: Calling getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@25a7fedf, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@482c351d[correlationID=6b4e4124-d205-408e-85cb-7d4e6f876c74, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=identificationFailureTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@75eaba95[fileID=<null>, allFileIDs=true], checksumRequestForExistingFile=<null>]
Result: Received event: 6b4e4124: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums
Step: Send a identification response from contributor1 with a FAILURE response code.
Result: Received event: 6b4e4124: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE
Step: Send a identification response from contributor2 with a IDENTIFICATION_POSITIVE response code .
Result: Received event: 6b4e4124: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 6b4e4124: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: 6b4e4124: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar2], Sending GetFileIDsRequest's
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@435e416c[correlationID=6b4e4124-d205-408e-85cb-7d4e6f876c74, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=identificationFailureTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@6af310c7[fileID=<null>, allFileIDs=true], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, checksumRequestForExistingFile=<null>, resultAddress=<null>]
Step: Verify that the client continues to the performing phase.
Step: Send a final response message from contributor2
Result: Received event: 6b4e4124: GET_CHECKSUMS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false
Result: Received event: 6b4e4124: GET_CHECKSUMS: FAILED: , Failed operation. Cause(s):
[6b4e4124: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE]
Test success: identificationFailureTest
Test starting: identificationNegativeTest
Description: Verify that the client works correctly when a contributor sends a negative response.
Step: Start the operation.
Stimuli: Calling getAuditTrails(null, null, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@325162e9[correlationID=b02c07c9-862c-4c94-ba1e-c7f96d92e19a, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=identificationNegativeTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
Result: Received event: b02c07c9: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
Step: Send a identification response from contributor1 with a IDENTIFICATION_NEGATIVE response code .
Result: Received event: b02c07c9: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: IDENTIFICATION_NEGATIVE
Step: Send a identification response from contributor2 with a IDENTIFICATION_POSITIVE response code .
Result: Received event: b02c07c9: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: b02c07c9: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: b02c07c9: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar2], Sending request for audit trails
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@5c448ef[correlationID=b02c07c9-862c-4c94-ba1e-c7f96d92e19a, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=identificationNegativeTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar2, fileID=<null>, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
Step: Verify that the client continues to the performing phase.
Step: Send a final response message from contributor2
Result: Received event: b02c07c9: GET_AUDIT_TRAILS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false
Result: Received event: b02c07c9: GET_AUDIT_TRAILS: FAILED: , Failed operation. Cause(s):
[b02c07c9: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: IDENTIFICATION_NEGATIVE]
Test success: identificationNegativeTest
Test starting: identificationNegativeTest
Description: Verify that the client works correctly when a contributor sends a negative response.
Step: Start the operation.
Stimuli: Calling getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@25a7fedf, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@514377fc[correlationID=94f4ce28-cf97-44b0-baf0-8f0a5ec1192f, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=identificationNegativeTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@2e4eda17[fileID=<null>, allFileIDs=true], checksumRequestForExistingFile=<null>]
Result: Received event: 94f4ce28: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums
Step: Send a identification response from contributor1 with a IDENTIFICATION_NEGATIVE response code .
Result: Received event: 94f4ce28: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: IDENTIFICATION_NEGATIVE
Step: Send a identification response from contributor2 with a IDENTIFICATION_POSITIVE response code .
Result: Received event: 94f4ce28: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 94f4ce28: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: 94f4ce28: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar2], Sending GetFileIDsRequest's
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@6befbb12[correlationID=94f4ce28-cf97-44b0-baf0-8f0a5ec1192f, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=identificationNegativeTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@21d9cd04[fileID=<null>, allFileIDs=true], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, checksumRequestForExistingFile=<null>, resultAddress=<null>]
Step: Verify that the client continues to the performing phase.
Step: Send a final response message from contributor2
Result: Received event: 94f4ce28: GET_CHECKSUMS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false
Result: Received event: 94f4ce28: GET_CHECKSUMS: FAILED: , Failed operation. Cause(s):
[94f4ce28: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: IDENTIFICATION_NEGATIVE]
Test success: identificationNegativeTest
Test starting: noContributorsRespondingTest
Description: Tests the the client handles lack of a IdentifyResponse gracefully. More concrete this means that the occurrence of a identification timeout should be handled correctly
Step: Set a 100 ms timeout for identifying contributors.
Step: Start the operation.
Stimuli: Calling getAuditTrails(null, null, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@11bfffb3[correlationID=6c0a1e98-be94-46ce-8016-bd103e61ba59, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noContributorsRespondingTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
Result: Received event: 6c0a1e98: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
Step: Wait for 1 second
Result: Received event: 6c0a1e98: GET_AUDIT_TRAILS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar1, Pillar2]
Result: Received event: 6c0a1e98: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor
Result: Received event: 6c0a1e98: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
Result: Received event: 6c0a1e98: GET_AUDIT_TRAILS: FAILED: , Unable to continue operation, contributors unavailable.
Test success: noContributorsRespondingTest
Result: The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@11bfffb3[correlationID=6c0a1e98-be94-46ce-8016-bd103e61ba59, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noContributorsRespondingTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
02:19:43.770 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@11bfffb3[correlationID=6c0a1e98-be94-46ce-8016-bd103e61ba59, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=noContributorsRespondingTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
Test starting: noContributorsRespondingTest
Description: Tests the the client handles lack of a IdentifyResponse gracefully. More concrete this means that the occurrence of a identification timeout should be handled correctly
Step: Set a 100 ms timeout for identifying contributors.
Step: Start the operation.
Stimuli: Calling getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@25a7fedf, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@7afbf2a0[correlationID=8464d8dd-1a83-445d-b694-06da52107254, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=noContributorsRespondingTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@2a6fb62f[fileID=<null>, allFileIDs=true], checksumRequestForExistingFile=<null>]
Result: Received event: 8464d8dd: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums
Step: Wait for 1 second
Result: Received event: 8464d8dd: GET_CHECKSUMS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar1, Pillar2]
Result: Received event: 8464d8dd: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor
Result: Received event: 8464d8dd: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
Result: Received event: 8464d8dd: GET_CHECKSUMS: FAILED: , Unable to continue operation, contributors unavailable.
Test success: noContributorsRespondingTest
Result: The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@7afbf2a0[correlationID=8464d8dd-1a83-445d-b694-06da52107254, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=noContributorsRespondingTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@2a6fb62f[fileID=<null>, allFileIDs=true], checksumRequestForExistingFile=<null>]
02:19:44.305 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@7afbf2a0[correlationID=8464d8dd-1a83-445d-b694-06da52107254, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=noContributorsRespondingTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@2a6fb62f[fileID=<null>, allFileIDs=true], checksumRequestForExistingFile=<null>]
Test starting: oneContributorNotRespondingTest
Description: Verify that the client works correct without receiving identification responses from all contributors.
Added fixture: Set the a identification timeout to 100 ms.
Step: Start the operation.
Stimuli: Calling getAuditTrails(null, null, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@7956f93a[correlationID=6b6b49b3-ddca-4adc-8bdf-30c208b0961e, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=oneContributorNotRespondingTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
Result: Received event: 6b6b49b3: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
Step: Send a identification response from contributor1.
Result: Received event: 6b6b49b3: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Step: Wait 1 second.
Result: Received event: 6b6b49b3: GET_AUDIT_TRAILS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar2]
Result: Received event: 6b6b49b3: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
Result: Received event: 6b6b49b3: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 6b6b49b3: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1], Sending request for audit trails
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@5915a9b4[correlationID=6b6b49b3-ddca-4adc-8bdf-30c208b0961e, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=oneContributorNotRespondingTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar1, fileID=<null>, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
Step: Verify that the client continues to the performing phase.
Step: Send a final response upload message
Result: Received event: 6b6b49b3: GET_AUDIT_TRAILS: COMPONENT_COMPLETE: ContributorID Pillar1, PartialResult=false
Result: Received event: 6b6b49b3: GET_AUDIT_TRAILS: FAILED: , Failed operation. Cause(s):
[6b6b49b3: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor]
Test success: oneContributorNotRespondingTest
Test starting: oneContributorNotRespondingTest
Description: Verify that the client works correct without receiving identification responses from all contributors.
Added fixture: Set the a identification timeout to 100 ms.
Step: Start the operation.
Stimuli: Calling getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@25a7fedf, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@68f776ee[correlationID=2af14d6b-865a-41d3-bddf-b83318432d1c, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=oneContributorNotRespondingTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@5a6195b8[fileID=<null>, allFileIDs=true], checksumRequestForExistingFile=<null>]
Result: Received event: 2af14d6b: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums
Step: Send a identification response from contributor1.
Result: Received event: 2af14d6b: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Step: Wait 1 second.
Result: Received event: 2af14d6b: GET_CHECKSUMS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar2]
Result: Received event: 2af14d6b: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
Result: Received event: 2af14d6b: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 2af14d6b: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar1], Sending GetFileIDsRequest's
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@57d24ce6[correlationID=2af14d6b-865a-41d3-bddf-b83318432d1c, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=oneContributorNotRespondingTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@53edc2c4[fileID=<null>, allFileIDs=true], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, checksumRequestForExistingFile=<null>, resultAddress=<null>]
Step: Verify that the client continues to the performing phase.
Step: Send a final response upload message
Result: Received event: 2af14d6b: GET_CHECKSUMS: COMPONENT_COMPLETE: ContributorID Pillar1, PartialResult=false
Result: Received event: 2af14d6b: GET_CHECKSUMS: FAILED: , Failed operation. Cause(s):
[2af14d6b: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor]
Test success: oneContributorNotRespondingTest
Test starting: operationTimeoutTest
Description: Tests the the client handles lack of final responses gracefully.
Step: Set a 100 ms operation timeout.
Step: Start the operation
Stimuli: Calling getAuditTrails(null, null, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsRequest@7db162f2[correlationID=d4a91146-933f-4acc-85e0-419ce205373e, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=operationTimeoutTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>]
Result: Received event: d4a91146: GET_AUDIT_TRAILS: IDENTIFY_REQUEST_SENT: , Identifying contributers for audit trails
Step: Send positive responses from the pillar1 and a negative response from pillar2
Result: Received event: d4a91146: GET_AUDIT_TRAILS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: d4a91146: GET_AUDIT_TRAILS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE
Result: Received event: d4a91146: GET_AUDIT_TRAILS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: d4a91146: GET_AUDIT_TRAILS: REQUEST_SENT: ContributorID [Pillar1], Sending request for audit trails
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsRequest@39e3ea78[correlationID=d4a91146-933f-4acc-85e0-419ce205373e, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-AuditTrailClientUnderTest-cibuild01, from=operationTimeoutTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, contributor=Pillar1, fileID=<null>, minSequenceNumber=<null>, maxSequenceNumber=<null>, minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
Step: Wait for 1 second
Result: Received event: d4a91146: GET_AUDIT_TRAILS: FAILED: , Failed to receive responses from all contributors before timeout(100ms). Missing contributors [Pillar1]
Test success: operationTimeoutTest
Test starting: operationTimeoutTest
Description: Tests the the client handles lack of final responses gracefully.
Step: Set a 100 ms operation timeout.
Step: Start the operation
Stimuli: Calling getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@25a7fedf, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@5950054d[correlationID=caebaef8-0f47-4b81-b865-1ee753a2ebee, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=operationTimeoutTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@24018c8b[fileID=<null>, allFileIDs=true], checksumRequestForExistingFile=<null>]
Result: Received event: caebaef8: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums
Step: Send positive responses from the pillar1 and a negative response from pillar2
Result: Received event: caebaef8: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: caebaef8: GET_CHECKSUMS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE
Result: Received event: caebaef8: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: caebaef8: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar1], Sending GetFileIDsRequest's
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@3dc55719[correlationID=caebaef8-0f47-4b81-b865-1ee753a2ebee, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=operationTimeoutTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@64665781[fileID=<null>, allFileIDs=true], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, checksumRequestForExistingFile=<null>, resultAddress=<null>]
Step: Wait for 1 second
Result: Received event: caebaef8: GET_CHECKSUMS: FAILED: , Failed to receive responses from all contributors before timeout(100ms). Missing contributors [Pillar1]
Test success: operationTimeoutTest
Starting testcase DeleteFileCmdTest
Test starting: checksumArgumentNonSaltAlgorithmWitoutSaltTest
Description: Test MD5 checksum without salt -> no failure
Test success: checksumArgumentNonSaltAlgorithmWitoutSaltTest
Test starting: checksumArgumentSaltAlgorithmWithSaltTest
Description: Test HMAC_SHA256 checksum with salt -> No failure
Test success: checksumArgumentSaltAlgorithmWithSaltTest
Test starting: defaultSuccessScenarioTest
Description: Tests simplest arguments for running the CmdLineClient
Test success: defaultSuccessScenarioTest
Test starting: missingCollectionArgumentTest
Description: Tests the scenario, where the collection arguments is missing.
Takes the following arguments:
-s The path to the directory with the settings files for the client
-k The path to the file containing the private key.
-v Makes the client more verbose
-c The id for the collection to perform the operation on.
-i The id for the file to perform the operation on.
-p [OPTIONAL] The id of the pillar where the should be performed. If undefined the operations is performed on all pillars.
-C [OPTIONAL] The checksum of the file to be delete.
-R [OPTIONAL] The algorithm of checksum to request in the response from the pillars.
-S [OPTIONAL] The salt of checksum to request in the response. Requires the ChecksumType argument.
Missing argument: Missing required option: c
Test success: missingCollectionArgumentTest
Test starting: missingFileIDArgumentTest
Description: Tests the scenario, where no arguments for file id argument is given.
Takes the following arguments:
-s The path to the directory with the settings files for the client
-k The path to the file containing the private key.
-v Makes the client more verbose
-c The id for the collection to perform the operation on.
-i The id for the file to perform the operation on.
-p [OPTIONAL] The id of the pillar where the should be performed. If undefined the operations is performed on all pillars.
-C [OPTIONAL] The checksum of the file to be delete.
-R [OPTIONAL] The algorithm of checksum to request in the response from the pillars.
-S [OPTIONAL] The salt of checksum to request in the response. Requires the ChecksumType argument.
Missing argument: Missing required option: i
Test success: missingFileIDArgumentTest
Test starting: missingPillarArgumentTest
Description: Tests the different scenarios, with the pillar argument.
Invalid argument: The pillar argument -p must defined for the delete operation, only single pillar deletes are allowed
Test success: missingPillarArgumentTest
Test starting: unknownPillarArgumentTest
Step: Testing against a non-existing pillar id
Invalid argument: Random1454030388873pillar is not a valid pillar for collection TwoPillarCollection
The collection contains the following pillars: [Pillar1, Pillar2]
Test success: unknownPillarArgumentTest
Test starting: getChecksumsDeliveredAtUrl
Description: Tests the delivery of checksums from all pillars at a given URL.
Step: Ensure the delivery file isn't already present on the http server
Step: Request the delivery of the checksum of a file from all pillars.
Stimuli: Calling getChecksums(null, default-test-file.txt, null, file:../bitrepository-core/src/test/resources/test-files//TEST-CHECKSUM-DELIVERY.xml, org.bitrepository.client.TestEventHandler@912a644, TEST-AUDIT)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@478cc5f1[correlationID=64af4b5a-1b96-4b39-bc2b-4c8a3202ba8b, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=getChecksumsDeliveredAtUrl, to=<null>, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@245b0bd7[fileID=default-test-file.txt, allFileIDs=<null>], checksumRequestForExistingFile=<null>]
Result: Received event: 64af4b5a: GET_CHECKSUMS for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums
Step: The pillar sends a response to the identify message.
Result: Received event: 64af4b5a: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 64af4b5a: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 64af4b5a: GET_CHECKSUMS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2]
Result: Received event: 64af4b5a: GET_CHECKSUMS for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending GetFileIDsRequest's
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@64a4739[correlationID=64af4b5a-1b96-4b39-bc2b-4c8a3202ba8b, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=getChecksumsDeliveredAtUrl, to=<null>, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@7ab3f194[fileID=default-test-file.txt, allFileIDs=<null>], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, checksumRequestForExistingFile=<null>, resultAddress=file:../bitrepository-core/src/test/resources/test-files//TEST-CHECKSUM-DELIVERY.xml-Pillar1]
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@613a608e[correlationID=64af4b5a-1b96-4b39-bc2b-4c8a3202ba8b, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=getChecksumsDeliveredAtUrl, to=<null>, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT, pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@37b1218[fileID=default-test-file.txt, allFileIDs=<null>], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, checksumRequestForExistingFile=<null>, resultAddress=file:../bitrepository-core/src/test/resources/test-files//TEST-CHECKSUM-DELIVERY.xml-Pillar2]
Step: Sends a final response from each pillar
Result: Received event: 64af4b5a: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, NumberOfChecksums=0, PartialResult=false
Result: Received event: 64af4b5a: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2, NumberOfChecksums=0, PartialResult=false
Result: Received event: 64af4b5a: GET_CHECKSUMS for file default-test-file.txt: COMPLETE:
Test success: getChecksumsDeliveredAtUrl
Result: The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.GetChecksumsRequest@613a608e[correlationID=64af4b5a-1b96-4b39-bc2b-4c8a3202ba8b, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=getChecksumsDeliveredAtUrl, to=<null>, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT, pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@37b1218[fileID=default-test-file.txt, allFileIDs=<null>], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, checksumRequestForExistingFile=<null>, resultAddress=file:../bitrepository-core/src/test/resources/test-files//TEST-CHECKSUM-DELIVERY.xml-Pillar2]
02:19:49.258 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.GetChecksumsRequest@613a608e[correlationID=64af4b5a-1b96-4b39-bc2b-4c8a3202ba8b, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=getChecksumsDeliveredAtUrl, to=<null>, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT, pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@37b1218[fileID=default-test-file.txt, allFileIDs=<null>], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, checksumRequestForExistingFile=<null>, resultAddress=file:../bitrepository-core/src/test/resources/test-files//TEST-CHECKSUM-DELIVERY.xml-Pillar2]
Test starting: getChecksumsFromOtherCollection
Description: Tests the getChecksums client will correctly try to get from a second collection if required
Added fixture: Configure collection1 to contain both pillars and collection 2 to only contain pillar2
Step: Request the putting of a file through the PutClient for collection2
Stimuli: Calling getChecksums(null, null, null, null, org.bitrepository.client.TestEventHandler@3606eee9, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@1e34840f[correlationID=08b9aa76-1703-4030-8507-15dacb84fa80, collectionID=SinglePillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=getChecksumsFromOtherCollection, to=Pillar2, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@6792f2c6[fileID=<null>, allFileIDs=true], checksumRequestForExistingFile=<null>]
Result: Received event: 08b9aa76: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums
Step: Send an identification response from pillar2.
Result: Received event: 08b9aa76: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 08b9aa76: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: 08b9aa76: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar2], Sending GetFileIDsRequest's
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@530e08a7[correlationID=08b9aa76-1703-4030-8507-15dacb84fa80, collectionID=SinglePillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=getChecksumsFromOtherCollection, to=Pillar2, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@6920fa35[fileID=<null>, allFileIDs=true], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, checksumRequestForExistingFile=<null>, resultAddress=<null>]
Step: Send a complete event from the pillar
Result: Received event: 08b9aa76: GET_CHECKSUMS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false
Result: Received event: 08b9aa76: GET_CHECKSUMS: COMPLETE:
Test success: getChecksumsFromOtherCollection
Test starting: getChecksumsFromSinglePillar
Description: Tests that the client can retrieve checksums from a single pillar.
Step: Request the delivery of the checksum of a file from pillar1.
Stimuli: Calling getChecksums([ContributorQuery{componentID='Pillar1, minTimestamp=null, maxTimestamp=null, maxNumberOfResults=null}], default-test-file.txt, org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@4adc3951[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], null, org.bitrepository.client.TestEventHandler@52b49891, TEST-AUDIT)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@75973f7a[correlationID=64797a89-bb67-40b1-a12c-64a44a5ab58b, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=getChecksumsFromSinglePillar, to=Pillar1, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@7940b729[fileID=default-test-file.txt, allFileIDs=<null>], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@4adc3951[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>]]
Result: Received event: 64797a89: GET_CHECKSUMS for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums
Step: Sends a response from pillar2.
Step: Sends a response from pillar1.
Result: Received event: 64797a89: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 64797a89: GET_CHECKSUMS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 64797a89: GET_CHECKSUMS for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending GetFileIDsRequest's
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@24fb752f[correlationID=64797a89-bb67-40b1-a12c-64a44a5ab58b, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=getChecksumsFromSinglePillar, to=Pillar1, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@68dbe225[fileID=default-test-file.txt, allFileIDs=<null>], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@4adc3951[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], resultAddress=<null>]
Step: Send a GetChecksumsFinalResponse to the client from pillar1
Result: Received event: 64797a89: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, NumberOfChecksums=0, PartialResult=false
Result: Received event: 64797a89: GET_CHECKSUMS for file default-test-file.txt: COMPLETE:
Test success: getChecksumsFromSinglePillar
Test starting: testNoSuchFile
Description: Testing how a request for a non-existing file is handled.
Step: Setting up variables and such.
Step: Request the delivery of the checksum of a file from the pillar(s). A callback listener should be supplied.
Stimuli: Calling getChecksums(null, default-test-file.txt, null, null, org.bitrepository.client.TestEventHandler@689eab53, TEST-AUDIT)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@1c24639e[correlationID=fc724802-684b-4185-a1dd-13b7f6b6ed09, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=testNoSuchFile, to=Pillar1, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@5c9168c3[fileID=default-test-file.txt, allFileIDs=<null>], checksumRequestForExistingFile=<null>]
Result: Received event: fc724802: GET_CHECKSUMS for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums
Step: The pillar sends a response to the identify message.
Result: Received event: fc724802: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: fc724802: GET_CHECKSUMS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: fc724802: GET_CHECKSUMS for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending GetFileIDsRequest's
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@571903ff[correlationID=fc724802-684b-4185-a1dd-13b7f6b6ed09, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=testNoSuchFile, to=Pillar1, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@689ea211[fileID=default-test-file.txt, allFileIDs=<null>], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, checksumRequestForExistingFile=<null>, resultAddress=<null>]
Step: Send a error that the file cannot be found.
Result: Received event: fc724802: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FILE_NOT_FOUND_FAILURE, No such file.
Result: Received event: fc724802: GET_CHECKSUMS for file default-test-file.txt: FAILED: , Failed operation. Cause(s):
[fc724802: GET_CHECKSUMS for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FILE_NOT_FOUND_FAILURE, No such file.]
Test success: testNoSuchFile
Test starting: testPaging
Description: Tests the GetChecksums client correctly handles functionality for limiting results, either by timestamp or result count.
Step: Request checksums from with MinTimestamp, MaxTimestamp, MaxNumberOfResults set for both pillars .
Stimuli: Calling getChecksums([ContributorQuery{componentID='Pillar1, minTimestamp=Fri Jan 29 02:19:50 CET 2016, maxTimestamp=Fri Jan 29 02:19:51 CET 2016, maxNumberOfResults=1}, ContributorQuery{componentID='Pillar2, minTimestamp=Fri Jan 29 02:19:51 CET 2016, maxTimestamp=Fri Jan 29 02:19:51 CET 2016, maxNumberOfResults=2}], null, null, null, org.bitrepository.client.TestEventHandler@25a7fedf, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsRequest@57a0aeb8[correlationID=5dd575dd-03a8-438f-803f-1786c0c4b1f3, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=testPaging, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@45f70f68[fileID=<null>, allFileIDs=true], checksumRequestForExistingFile=<null>]
Result: Received event: 5dd575dd: GET_CHECKSUMS: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetChecksums
Step: Send a IdentifyPillarsForGetChecksumsResponse from both pillars.
Result: Received event: 5dd575dd: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 5dd575dd: GET_CHECKSUMS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 5dd575dd: GET_CHECKSUMS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2]
Result: Received event: 5dd575dd: GET_CHECKSUMS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending GetFileIDsRequest's
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@56017274[correlationID=5dd575dd-03a8-438f-803f-1786c0c4b1f3, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=testPaging, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@2bf0bb93[fileID=<null>, allFileIDs=true], minTimestamp=2016-01-29T02:19:50.483+01:00, maxTimestamp=2016-01-29T02:19:51.383+01:00, maxNumberOfResults=1, checksumRequestForExistingFile=<null>, resultAddress=<null>]
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsRequest@23adbd6b[correlationID=5dd575dd-03a8-438f-803f-1786c0c4b1f3, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetChecksumsClientComponentTest-cibuild01, from=testPaging, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@11d0bff5[fileID=<null>, allFileIDs=true], minTimestamp=2016-01-29T02:19:51.383+01:00, maxTimestamp=2016-01-29T02:19:51.483+01:00, maxNumberOfResults=2, checksumRequestForExistingFile=<null>, resultAddress=<null>]
Test success: testPaging
Test starting: verifyGetChecksumsClientFromFactory
Test success: verifyGetChecksumsClientFromFactory
Starting testcase GetFileCmdTest
Test starting: defaultSuccessScenarioTest
Description: Tests simplest arguments for running the CmdLineClient
Test success: defaultSuccessScenarioTest
Test starting: missingCollectionArgumentTest
Description: Tests the scenario, where the collection arguments is missing.
Takes the following arguments:
-s The path to the directory with the settings files for the client
-k The path to the file containing the private key.
-v Makes the client more verbose
-c The id for the collection to perform the operation on.
-i The id for the file to perform the operation on.
-p [OPTIONAL] The id of the pillar where the should be performed. If undefined the operations is performed on all pillars.
-l [OPTIONAL] The location where the file should be placed (either total path or directory). If no argument, then in the directory where the script is located.
Missing argument: Missing required option: c
Test success: missingCollectionArgumentTest
Test starting: missingFileIDArgumentTest
Description: Tests the scenario, where no arguments for file id argument is given.
Takes the following arguments:
-s The path to the directory with the settings files for the client
-k The path to the file containing the private key.
-v Makes the client more verbose
-c The id for the collection to perform the operation on.
-i The id for the file to perform the operation on.
-p [OPTIONAL] The id of the pillar where the should be performed. If undefined the operations is performed on all pillars.
-l [OPTIONAL] The location where the file should be placed (either total path or directory). If no argument, then in the directory where the script is located.
Missing argument: Missing required option: i
Test success: missingFileIDArgumentTest
Test starting: specificPillarArgumentTest
Description: Test argument for a specific pillar
Test success: specificPillarArgumentTest
Test starting: unknownPillarArgumentTest
Description: Testing against a non-existing pillar id -> Should fail
Invalid argument: Random1454030392949pillar is not a valid pillar for collection TwoPillarCollection
The collection contains the following pillars: [Pillar1, Pillar2]
Test success: unknownPillarArgumentTest
Starting testcase GetFileIDsCmdTest
Test starting: defaultSuccessScenarioTest
Description: Tests simplest arguments for running the CmdLineClient
Test success: defaultSuccessScenarioTest
Test starting: fileArgumentTest
Description: Tests the argument for a specific file.
Test success: fileArgumentTest
Test starting: missingCollectionArgumentTest
Description: Tests the scenario, where the collection arguments is missing.
Takes the following arguments:
-s The path to the directory with the settings files for the client
-k The path to the file containing the private key.
-v Makes the client more verbose
-c The id for the collection to perform the operation on.
-i The id for the file to perform the operation on.
-p [OPTIONAL] The id of the pillar where the should be performed. If undefined the operations is performed on all pillars.
Missing argument: Missing required option: c
Test success: missingCollectionArgumentTest
Test starting: specificPillarArgumentTest
Description: Test argument for a specific pillar
Test success: specificPillarArgumentTest
Test starting: unknownPillarArgumentTest
Description: Testing against a non-existing pillar id -> Should fail
Invalid argument: Random1454030394377pillar is not a valid pillar for collection TwoPillarCollection
The collection contains the following pillars: [Pillar1, Pillar2]
Test success: unknownPillarArgumentTest
Starting testcase NegativeResponseExceptionTest
Test starting: testNegativeResponse
Description: Test the instantiation of the exception
Step: Setup
Step: Try to throw such an exception with the response code
Test success: testNegativeResponse
Starting testcase PutFileClientComponentTest
Test starting: defaultReturnChecksumsWithChecksumPillar
Description: Tests that PutClient handles the presence of a ChecksumPillar correctly, when a return checksum of default type is requested (which a checksum pillar can provide).
Step: Call putFile while requesting a salted checksum to be returned.
Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7bb3cbb4[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], org.bitrepository.client.TestEventHandler@3fcc58f8, TEST-AUDIT-TRAIL)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@51f714d1[correlationID=01635ecc-1928-4f8b-b0d9-0aae018363eb, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=defaultReturnChecksumsWithChecksumPillar, to=<null>, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, fileID=default-test-file.txt, fileSize=0]
Result: Received event: 01635ecc: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file
Step: Send an identification response with a PillarChecksumSpec element set, indicating that this is a checksum pillar.
Result: Received event: 01635ecc: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Step: Send an normal identification response from pillar2.
Result: Received event: 01635ecc: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 01635ecc: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2, Pillar1]
Result: Received event: 01635ecc: PUT_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for put file
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@260d878a[correlationID=01635ecc-1928-4f8b-b0d9-0aae018363eb, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=defaultReturnChecksumsWithChecksumPillar, to=<null>, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>, checksumRequestForNewFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7bb3cbb4[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>]]
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@1f664881[correlationID=01635ecc-1928-4f8b-b0d9-0aae018363eb, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=defaultReturnChecksumsWithChecksumPillar, to=<null>, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, pillarID=Pillar2, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>, checksumRequestForNewFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7bb3cbb4[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>]]
Test success: defaultReturnChecksumsWithChecksumPillar
Test starting: fileExistsOnPillarChecksumFromPillarNoClientChecksum
Description: Tests that PutClient handles the presence of a file correctly, when the pillar returns a checksum but the putFile was called without a checksum.
Step: Call putFile.
Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, null, org.bitrepository.client.TestEventHandler@6b6dce39, TEST-AUDIT-TRAIL)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@3e272f0[correlationID=20160258-b3a3-430e-a093-f8d6d748721c, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=fileExistsOnPillarChecksumFromPillarNoClientChecksum, to=<null>, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, fileID=default-test-file.txt, fileSize=0]
Result: Received event: 20160258: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file
Step: Send a DUPLICATE_FILE_FAILURE response with a random checksum.
Result: Received event: 20160258: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: DUPLICATE_FILE_FAILURE, Received negative response from component Pillar1: org.bitrepository.bitrepositoryelements.ResponseInfo@5f33123[responseCode=DUPLICATE_FILE_FAILURE, responseText=Testing the handling of 'DUPLICATE FILE' identification.] (existing file checksum does not match)
Result: Received event: 20160258: PUT_FILE for file default-test-file.txt: FAILED: , Can not put file default-test-file.txt, as an different file already exists on pillar Pillar1
Test success: fileExistsOnPillarChecksumFromPillarNoClientChecksum
Test starting: fileExistsOnPillarDifferentChecksumFromPillar
Description: Tests that PutClient handles the presence of a file correctly, when the pillar returns a checksum different from the file being put.
Step: Call putFile.
Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@65c040c9[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@11736ebc[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={-70}, calculationTimestamp=2016-01-29T02:19:54.959+01:00], null, org.bitrepository.client.TestEventHandler@4a03c4bc, TEST-AUDIT-TRAIL)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@3d0c88f4[correlationID=9cc5289b-39da-40a2-b5ee-2d144cafeaef, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=fileExistsOnPillarDifferentChecksumFromPillar, to=<null>, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, fileID=default-test-file.txt, fileSize=0]
Result: Received event: 9cc5289b: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file
Step: Send a DUPLICATE_FILE_FAILURE response with a random checksum.
Result: Received event: 9cc5289b: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: DUPLICATE_FILE_FAILURE, Received negative response from component Pillar1: org.bitrepository.bitrepositoryelements.ResponseInfo@453ca7f[responseCode=DUPLICATE_FILE_FAILURE, responseText=Testing the handling of 'DUPLICATE FILE' identification.] (existing file checksum does not match)
Result: Received event: 9cc5289b: PUT_FILE for file default-test-file.txt: FAILED: , Can not put file default-test-file.txt, as an different file already exists on pillar Pillar1
Test success: fileExistsOnPillarDifferentChecksumFromPillar
Test starting: fileExistsOnPillarNoChecksumFromPillar
Description: Tests that PutClient handles the presence of a file correctly, when the pillar doesn't return a checksum in the identification response.
Step: Call putFile.
Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, null, org.bitrepository.client.TestEventHandler@7ae736a8, TEST-AUDIT-TRAIL)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@7b3b763d[correlationID=1885c997-4a7d-4175-b2d1-ee9d4266ac25, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=fileExistsOnPillarNoChecksumFromPillar, to=<null>, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, fileID=default-test-file.txt, fileSize=0]
Result: Received event: 1885c997: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file
Step: Send a DUPLICATE_FILE_FAILURE response without a checksum.
Result: Received event: 1885c997: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: DUPLICATE_FILE_FAILURE, Received negative response from component Pillar1: org.bitrepository.bitrepositoryelements.ResponseInfo@34ceefb5[responseCode=DUPLICATE_FILE_FAILURE, responseText=Testing the handling of 'DUPLICATE FILE' identification.]
Result: Received event: 1885c997: PUT_FILE for file default-test-file.txt: FAILED: , Can not put file default-test-file.txt, as an file already exists on pillar Pillar1
Test success: fileExistsOnPillarNoChecksumFromPillar
Test starting: noPillarsResponding
Description: Tests the handling of missing identification responses from all pillar
Added fixture: Sets the identification timeout to 100 ms.
Step: Request the putting of a file through the PutClient
Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, null, org.bitrepository.client.TestEventHandler@6921e251, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@724d4c0a[correlationID=61b3aef6-1bc5-4e25-a016-32e275acf096, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=noPillarsResponding, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt, fileSize=0]
Result: Received event: 61b3aef6: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file
Step: Do not respond. Just await the timeout.
Result: Received event: 61b3aef6: PUT_FILE for file default-test-file.txt: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar1, Pillar2]
Result: Received event: 61b3aef6: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor
Result: Received event: 61b3aef6: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
Result: Received event: 61b3aef6: PUT_FILE for file default-test-file.txt: FAILED: , Unable to continue operation, contributors unavailable.
Test success: noPillarsResponding
Test starting: noReturnChecksumsWithChecksumPillar
Description: Tests that PutClient handles the presence of a ChecksumPillar correctly, when no return checksum is requested.
Step: Call putFile while requesting a salted checksum to be returned.
Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, null, org.bitrepository.client.TestEventHandler@52f9a620, TEST-AUDIT-TRAIL)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@6d575cd8[correlationID=983aad4a-1d84-4ff7-989b-b46b1d81b214, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=noReturnChecksumsWithChecksumPillar, to=<null>, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, fileID=default-test-file.txt, fileSize=0]
Result: Received event: 983aad4a: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file
Step: Send an identification response with a PillarChecksumSpec element set, indicating that this is a checksum pillar.
Result: Received event: 983aad4a: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Step: Send an normal identification response from pillar2.
Result: Received event: 983aad4a: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 983aad4a: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2]
Result: Received event: 983aad4a: PUT_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for put file
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@63100783[correlationID=983aad4a-1d84-4ff7-989b-b46b1d81b214, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=noReturnChecksumsWithChecksumPillar, to=<null>, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>, checksumRequestForNewFile=<null>]
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@34f636a5[correlationID=983aad4a-1d84-4ff7-989b-b46b1d81b214, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=noReturnChecksumsWithChecksumPillar, to=<null>, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, pillarID=Pillar2, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>, checksumRequestForNewFile=<null>]
Test success: noReturnChecksumsWithChecksumPillar
Test starting: normalPutFile
Description: Tests the PutClient. Makes a whole conversation for the put client for a 'good' scenario.
Added fixture: Initialise the number of pillars to one
Step: Ensure that the test-file is placed on the HTTP server.
Step: Request the delivery of a file from a specific pillar. A callback listener should be supplied.
Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, null, org.bitrepository.client.TestEventHandler@74cf108b, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@56c72fff[correlationID=5da8cf58-1228-4a3d-a99e-d0cf6dbb5823, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=normalPutFile, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt, fileSize=0]
Result: Received event: 5da8cf58: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file
Step: Make response for the pillar.
Result: Received event: 5da8cf58: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 5da8cf58: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 5da8cf58: PUT_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for put file
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@60f10f6a[correlationID=5da8cf58-1228-4a3d-a99e-d0cf6dbb5823, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=normalPutFile, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>, checksumRequestForNewFile=<null>]
Step: Validate the steps of the PutClient by going through the events.
Step: The pillar sends a progress response to the PutClient.
Result: Received event: 5da8cf58: PUT_FILE for file default-test-file.txt: PROGRESS: ContributorID Pillar1, First test progress response message
Step: Send a final response message to the PutClient.
Result: Received event: 5da8cf58: PUT_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, requestedChecksumResult=null
Result: Received event: 5da8cf58: PUT_FILE for file default-test-file.txt: COMPLETE:
Test success: normalPutFile
Test starting: onePillarPutRetryFailure
Reference: <a href=https://sbforge.org/jira/browse/BITMAG-810>BITMAG-810 Reference client should be able to retry failed file transfers</a>
Description: Tests that a putfile attempt failing due to FILE_TRANSFER_FAILURE is only attempted the maximum allowed attempts
Added fixture: Sets the identification timeout to 3 sec, allow two retries and only register one pillar.
Step: Request the putting of a file through the PutClient
Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, null, org.bitrepository.client.TestEventHandler@7c3b7d7c, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@579e8a7[correlationID=e4d88a70-7c1a-4538-8e4b-abc10c5eb504, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarPutRetryFailure, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt, fileSize=0]
Result: Received event: e4d88a70: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file
Step: Send an identification response from the one pillar.
Result: Received event: e4d88a70: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: e4d88a70: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: e4d88a70: PUT_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for put file
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@61906bb1[correlationID=e4d88a70-7c1a-4538-8e4b-abc10c5eb504, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarPutRetryFailure, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>, checksumRequestForNewFile=<null>]
Step: The client should proceed to send a putFileOperation request to the responding pillar.
Step: Send a PutFileFinalResponse indicating a FILE_TRANSFER_FAILURE
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@46672a62[correlationID=e4d88a70-7c1a-4538-8e4b-abc10c5eb504, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarPutRetryFailure, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>, checksumRequestForNewFile=<null>]
Result: Received event: e4d88a70: PUT_FILE for file default-test-file.txt: WARNING: ContributorID Pillar1, Retrying putfile (attempt number 2)
Step: Send a PutFileFinalResponse indicating a FILE_TRANSFER_FAILURE for the second put attempt
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@c91ced9[correlationID=e4d88a70-7c1a-4538-8e4b-abc10c5eb504, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarPutRetryFailure, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>, checksumRequestForNewFile=<null>]
Result: Received event: e4d88a70: PUT_FILE for file default-test-file.txt: WARNING: ContributorID Pillar1, Retrying putfile (attempt number 3)
Step: Send a PutFileFinalResponse indicating a FILE_TRANSFER_FAILURE for the third put attempt
Result: Received event: e4d88a70: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FILE_TRANSFER_FAILURE
Result: Received event: e4d88a70: PUT_FILE for file default-test-file.txt: FAILED: , Failed operation. Cause(s):
[e4d88a70: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FILE_TRANSFER_FAILURE]
Test success: onePillarPutRetryFailure
Test starting: onePillarPutRetrySuccess
Reference: <a href=https://sbforge.org/jira/browse/BITMAG-810>BITMAG-810 Reference client should be able to retry failed file transfers</a>
Description: Tests the handling of a failed transmission when retry is allowed
Added fixture: Sets the identification timeout to 3 sec, allow two retries and only register one pillar.
Step: Request the putting of a file through the PutClient
Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, null, org.bitrepository.client.TestEventHandler@1de7c0ad, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@37445c57[correlationID=f74777d9-73d0-4ee7-afb2-c39da52d1658, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarPutRetrySuccess, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt, fileSize=0]
Result: Received event: f74777d9: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file
Step: Send an identification response from the one pillar.
Result: Received event: f74777d9: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: f74777d9: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: f74777d9: PUT_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for put file
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@3d97b0a[correlationID=f74777d9-73d0-4ee7-afb2-c39da52d1658, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarPutRetrySuccess, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>, checksumRequestForNewFile=<null>]
Step: The client should proceed to send a putFileOperation request to the responding pillar.
Step: Send a PutFileFinalResponse indicating a FILE_TRANSFER_FAILURE
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@20983174[correlationID=f74777d9-73d0-4ee7-afb2-c39da52d1658, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarPutRetrySuccess, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>, checksumRequestForNewFile=<null>]
Result: Received event: f74777d9: PUT_FILE for file default-test-file.txt: WARNING: ContributorID Pillar1, Retrying putfile (attempt number 2)
Step: A new PutFileRequest is send, pillar responds with success
Result: Received event: f74777d9: PUT_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, requestedChecksumResult=null
Result: Received event: f74777d9: PUT_FILE for file default-test-file.txt: COMPLETE:
Test success: onePillarPutRetrySuccess
Test starting: onePillarRespondingWithPartialPutAllowed
Reference: <a href=https://sbforge.org/jira/browse/BITMAG-598>BITMAG-598 It should be possible to putFiles, even though only a subset of the pillars are available</a>
Description: Tests the handling of missing identification responses from one pillar, when partial put are allowed
Added fixture: Sets the identification timeout to 100 ms and allow partial puts.
Step: Request the putting of a file through the PutClient
Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, null, org.bitrepository.client.TestEventHandler@200cdb37, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@523d6b45[correlationID=e3f2e9a2-0eba-4325-b9b4-cdf321f02f48, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarRespondingWithPartialPutAllowed, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt, fileSize=0]
Result: Received event: e3f2e9a2: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file
Step: Only send an identification response from one pillar.
Result: Received event: e3f2e9a2: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Step: Await the timeout.
Result: Received event: e3f2e9a2: PUT_FILE for file default-test-file.txt: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar2]
Result: Received event: e3f2e9a2: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
Result: Received event: e3f2e9a2: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: e3f2e9a2: PUT_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for put file
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@16ef46dd[correlationID=e3f2e9a2-0eba-4325-b9b4-cdf321f02f48, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarRespondingWithPartialPutAllowed, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>, checksumRequestForNewFile=<null>]
Step: The client should proceed to send a putFileOperation request to the responding pillar.
Step: Send a pillar complete event
Result: Received event: e3f2e9a2: PUT_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, requestedChecksumResult=null
Result: Received event: e3f2e9a2: PUT_FILE for file default-test-file.txt: FAILED: , Failed operation. Cause(s):
[e3f2e9a2: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor]
Test success: onePillarRespondingWithPartialPutAllowed
Test starting: onePillarRespondingWithPartialPutDisallowed
Description: Tests the handling of missing identification responses from one pillar, when partial put are allowed
Added fixture: Sets the identification timeout to 100 ms and disallow partial puts.
Step: Request the putting of a file through the PutClient
Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, null, org.bitrepository.client.TestEventHandler@1727d525, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@1f7b7ac4[correlationID=9bf856fd-9e9f-46b8-9e67-649ac405df9a, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=onePillarRespondingWithPartialPutDisallowed, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt, fileSize=0]
Result: Received event: 9bf856fd: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file
Step: Only send an identification response from one pillar.
Result: Received event: 9bf856fd: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Step: Await the timeout.
Result: Received event: 9bf856fd: PUT_FILE for file default-test-file.txt: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar2]
Result: Received event: 9bf856fd: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
Result: Received event: 9bf856fd: PUT_FILE for file default-test-file.txt: FAILED: , Unable to continue operation, contributors unavailable.
Test success: onePillarRespondingWithPartialPutDisallowed
Test starting: putClientOperationTimeout
Description: Tests the handling of a failed operation for the PutClient
Step: Initialise the number of pillars and the PutClient. Sets the operation timeout to 100 ms.
Step: Request the putting of a file through the PutClient
Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, null, org.bitrepository.client.TestEventHandler@cf97391, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@65d5de1a[correlationID=caec98af-333a-477c-bfde-77e383c5bcda, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=putClientOperationTimeout, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt, fileSize=0]
Result: Received event: caec98af: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file
Step: Make response for the pillar.
Result: Received event: caec98af: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: caec98af: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: caec98af: PUT_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for put file
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@44d51c85[correlationID=caec98af-333a-477c-bfde-77e383c5bcda, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=putClientOperationTimeout, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>, checksumRequestForNewFile=<null>]
Step: Validate the steps of the PutClient by going through the events.
Step: Do not respond. Just await the timeout.
Result: Received event: caec98af: PUT_FILE for file default-test-file.txt: FAILED: , Failed to receive responses from all contributors before timeout(100ms). Missing contributors [Pillar1]
Test success: putClientOperationTimeout
Test starting: putClientPillarOperationFailed
Description: Tests the handling of a operation failure for the PutClient.
Step: Initialise the number of pillars to one
Step: Ensure that the test-file is placed on the HTTP server.
Step: Request the delivery of a file from a specific pillar. A callback listener should be supplied.
Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, null, org.bitrepository.client.TestEventHandler@7cd91400, TEST-AUDIT-TRAIL)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@108817cc[correlationID=3d659e7f-2b0e-47d7-a5a0-ed959b44abb0, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=putClientPillarOperationFailed, to=Pillar1, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, fileID=default-test-file.txt, fileSize=0]
Result: Received event: 3d659e7f: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file
Step: Send pillar response.
Result: Received event: 3d659e7f: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 3d659e7f: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 3d659e7f: PUT_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for put file
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@1f334ce0[correlationID=3d659e7f-2b0e-47d7-a5a0-ed959b44abb0, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=putClientPillarOperationFailed, to=Pillar1, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>, checksumRequestForNewFile=<null>]
Step: Validate the steps of the PutClient by going through the events.
Step: Send a failed response message to the PutClient.
Result: Received event: 3d659e7f: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE, Verifying that a failure can be understood!
Result: Received event: 3d659e7f: PUT_FILE for file default-test-file.txt: FAILED: , Failed operation. Cause(s):
[3d659e7f: PUT_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE, Verifying that a failure can be understood!]
Test success: putClientPillarOperationFailed
Test starting: putToOtherCollection
Reference: <a href=https://sbforge.org/jira/browse/BITMAG-925>BITMAG-925 Client will always try to put to the pillars defined in the first collection</a>
Description: Tests the putFIle client will correctly try to put to a second collection if required
Added fixture: Sets the identification timeout to 3 sec, allow two retries and only register one pillar.
Added fixture: Configure collection1 to contain both pillars and collection 2 to only contain pillar2
Step: Request the putting of a file through the PutClient for collection2
Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, null, org.bitrepository.client.TestEventHandler@39b704f7, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@22a9170c[correlationID=eaf7eace-a949-4be7-b142-2203e6cf29d1, collectionID=SinglePillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=putToOtherCollection, to=Pillar2, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt, fileSize=0]
Result: Received event: eaf7eace: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file
Step: Send an identification response from pillar2.
Result: Received event: eaf7eace: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: eaf7eace: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: eaf7eace: PUT_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar2], Sending request for put file
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@4fa62aed[correlationID=eaf7eace-a949-4be7-b142-2203e6cf29d1, collectionID=SinglePillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=putToOtherCollection, to=Pillar2, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar2, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>, checksumRequestForNewFile=<null>]
Step: Send a put complete event from the pillar
Result: Received event: eaf7eace: PUT_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2, requestedChecksumResult=null
Result: Received event: eaf7eace: PUT_FILE for file default-test-file.txt: COMPLETE:
Test success: putToOtherCollection
Test starting: saltedReturnChecksumsWithChecksumPillar
Description: Tests that PutClient handles the presence of a ChecksumPillar correctly, when a salted return checksum (which a checksum pillar can't provide) is requested.
Reference: <a href="https://sbforge.org/jira/browse/BITMAG-677">BITMAG-677put, replace and delete clients fails if return checksums are requested and a checksumpillar is involved</a>
Step: Call putFile while requesting a salted checksum to be returned.
Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, null, org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2f9f939[checksumType=HMAC_MD5, checksumSalt={-86}, otherChecksumType=<null>], org.bitrepository.client.TestEventHandler@113366e7, TEST-AUDIT-TRAIL)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@32c3102[correlationID=45aac446-b856-429b-b8aa-449ddcddcd70, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=saltedReturnChecksumsWithChecksumPillar, to=<null>, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, fileID=default-test-file.txt, fileSize=0]
Result: Received event: 45aac446: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file
Step: Send an identification response with a PillarChecksumSpec element set, indicating that this is a checksum pillar.
Result: Received event: 45aac446: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Step: Send an normal identification response from pillar2.
Result: Received event: 45aac446: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 45aac446: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2, Pillar1]
Result: Received event: 45aac446: PUT_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for put file
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@4ca87dbe[correlationID=45aac446-b856-429b-b8aa-449ddcddcd70, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=saltedReturnChecksumsWithChecksumPillar, to=<null>, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, pillarID=Pillar1, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>, checksumRequestForNewFile=<null>]
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@2eeee108[correlationID=45aac446-b856-429b-b8aa-449ddcddcd70, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=saltedReturnChecksumsWithChecksumPillar, to=<null>, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, pillarID=Pillar2, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=<null>, checksumRequestForNewFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2f9f939[checksumType=HMAC_MD5, checksumSalt={-86}, otherChecksumType=<null>]]
Test success: saltedReturnChecksumsWithChecksumPillar
Test starting: sameFileExistsOnOnePillar
Description: Tests that PutClient handles the presence of a file correctly, when the pillar returns a checksum equal the file being put (idempotent).
Step: Call putFile.
Stimuli: Calling PutFileWithId(file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, default-test-file.txt, 0, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@5c24a636[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@332e4784[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2016-01-29T02:19:57.807+01:00], null, org.bitrepository.client.TestEventHandler@2f22049d, TEST-AUDIT-TRAIL)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileRequest@60cb3ca9[correlationID=34f4a747-d08d-4a88-b536-3e1677f99646, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=sameFileExistsOnOnePillar, to=<null>, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, fileID=default-test-file.txt, fileSize=0]
Result: Received event: 34f4a747: PUT_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for put file
Step: Send a DUPLICATE_FILE_FAILURE response with a checksum equal to the one supplied to the client.
Result: Received event: 34f4a747: PUT_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, requestedChecksumResult=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@674db438[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@5e5af20c[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2016-01-29T02:19:57.808+01:00], File already existed on Pillar1
Step: Send an identification response from the second pillar.
Result: Received event: 34f4a747: PUT_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 34f4a747: PUT_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: 34f4a747: PUT_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar2], Sending request for put file
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileRequest@4e55d96[correlationID=34f4a747-d08d-4a88-b536-3e1677f99646, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-PutFileClientComponentTest-cibuild01, from=sameFileExistsOnOnePillar, to=<null>, version=28, minVersion=24, auditTrailInformation=TEST-AUDIT-TRAIL, pillarID=Pillar2, fileID=default-test-file.txt, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@5c24a636[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@332e4784[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2016-01-29T02:19:57.807+01:00], checksumRequestForNewFile=<null>]
Step: The client should proceed to send a putFileOperation request to the second pillar.
Step: Send a pillar complete event
Result: Received event: 34f4a747: PUT_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2, requestedChecksumResult=null
Result: Received event: 34f4a747: PUT_FILE for file default-test-file.txt: COMPLETE:
Test success: sameFileExistsOnOnePillar
Test starting: verifyPutClientFromFactory
Description: Testing the initialization through the ModifyComponentFactory.
Step: Use the ModifyComponentFactory to instantiate a PutFileClient.
Test success: verifyPutClientFromFactory
Starting testcase ReplaceFileClientComponentTest
Test starting: replaceClientIdentificationTimeout
Description: Tests the handling of a failed identification for the ReplaceClient
Step: Initialise the number of pillars and the DeleteClient. Sets the identification timeout to 100 ms.
Step: Request a file to be replaced on the default pillar.
Stimuli: replaceFile(default-test-file.txt, Pillar1, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@2bab0d9a[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@5eead9c2[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@21cb02d0[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, 10, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@2e5c842a[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@5eead9c2[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@21cb02d0[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], org.bitrepository.client.TestEventHandler@5d689ba6, null
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileRequest@55446d00[correlationID=16d69188-245e-43a9-8f67-ad44907bfce1, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-ReplaceFileClientComponentTest-cibuild01, from=replaceClientIdentificationTimeout, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt, fileSize=<null>]
Result: Received event: 16d69188: REPLACE_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for replace file
Step: Do not respond. Just await the timeout.
Result: Received event: 16d69188: REPLACE_FILE for file default-test-file.txt: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar1]
Result: Received event: 16d69188: REPLACE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor
Result: Received event: 16d69188: REPLACE_FILE for file default-test-file.txt: FAILED: , Unable to continue operation, contributors unavailable.
Test success: replaceClientIdentificationTimeout
Test starting: replaceClientOperationTimeout
Description: Tests the handling of a failed operation for the ReplaceClient
Step: Initialise the number of pillars and the DeleteClient. Sets the operation timeout to 100 ms.
Step: Request a file to be replaced on the default pillar.
Stimuli: replaceFile(default-test-file.txt, Pillar1, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@13866e67[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1a44d89b[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@5547476c[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, 10, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@26664caa[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1a44d89b[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@5547476c[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], org.bitrepository.client.TestEventHandler@6b3eb57, null
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileRequest@3a0f6b1a[correlationID=6188cf82-3866-4cb5-988d-e8293b16b661, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-ReplaceFileClientComponentTest-cibuild01, from=replaceClientOperationTimeout, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt, fileSize=<null>]
Result: Received event: 6188cf82: REPLACE_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for replace file
Step: Make response for the pillar.
Result: Received event: 6188cf82: REPLACE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 6188cf82: REPLACE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 6188cf82: REPLACE_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for replace file
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.ReplaceFileRequest@418b3215[correlationID=6188cf82-3866-4cb5-988d-e8293b16b661, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-ReplaceFileClientComponentTest-cibuild01, from=replaceClientOperationTimeout, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@13866e67[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1a44d89b[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@5547476c[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=10, checksumDataForNewFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@26664caa[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1a44d89b[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], checksumRequestForNewFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@5547476c[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>]]
Step: Validate the steps of the ReplaceClient by going through the events.
Step: Do not respond. Just await the timeout.
Result: Received event: 6188cf82: REPLACE_FILE for file default-test-file.txt: FAILED: , Failed to receive responses from all contributors before timeout(100ms). Missing contributors [Pillar1]
Test success: replaceClientOperationTimeout
Test starting: replaceClientPillarFailed
Description: Tests the handling of a operation failure for the ReplaceClient.
Step: Initialise the number of pillars to one
Step: Request a file to be replaced on the default pillar.
Stimuli: replaceFile(default-test-file.txt, Pillar1, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@1e3e01b[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6ef99da8[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@12a96a6e[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, 0, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@18e8003a[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6ef99da8[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@12a96a6e[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], org.bitrepository.client.TestEventHandler@695d804, null
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileRequest@24a301a3[correlationID=30b98372-1ebf-4087-80ae-32e2e4469f01, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-ReplaceFileClientComponentTest-cibuild01, from=replaceClientPillarFailed, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt, fileSize=<null>]
Result: Received event: 30b98372: REPLACE_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for replace file
Step: Make response for the pillar.
Result: Received event: 30b98372: REPLACE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 30b98372: REPLACE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 30b98372: REPLACE_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for replace file
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.ReplaceFileRequest@2531c319[correlationID=30b98372-1ebf-4087-80ae-32e2e4469f01, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-ReplaceFileClientComponentTest-cibuild01, from=replaceClientPillarFailed, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@1e3e01b[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6ef99da8[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@12a96a6e[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@18e8003a[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6ef99da8[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], checksumRequestForNewFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@12a96a6e[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>]]
Step: Validate the steps of the ReplaceClient by going through the events.
Step: Send a failed response message to the ReplaceClient.
Result: Received event: 30b98372: REPLACE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE, Verifying that a failure can be understood!
Result: Received event: 30b98372: REPLACE_FILE for file default-test-file.txt: FAILED: , Failed operation. Cause(s):
[30b98372: REPLACE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE, Verifying that a failure can be understood!]
Test success: replaceClientPillarFailed
Test starting: replaceClientTester
Description: Tests the ReplaceFileClient. Makes a whole conversation for the replace client for a 'good' scenario.
Step: Initialise the number of pillars to one
Step: Request a file to be replaced on all pillars (which means only the default pillar).
Stimuli: replaceFile(default-test-file.txt, Pillar1, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@4a281ae0[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@55c445e5[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7144cd51[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, 10, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@28fb3476[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@55c445e5[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7144cd51[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], org.bitrepository.client.TestEventHandler@228ec493, null
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileRequest@5592464a[correlationID=7e1f0d48-42e9-48c6-9175-2c7c376c86a5, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-ReplaceFileClientComponentTest-cibuild01, from=replaceClientTester, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt, fileSize=<null>]
Result: Received event: 7e1f0d48: REPLACE_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for replace file
Step: Make response for the pillar.
Result: Received event: 7e1f0d48: REPLACE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 7e1f0d48: REPLACE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 7e1f0d48: REPLACE_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for replace file
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.ReplaceFileRequest@7342eb53[correlationID=7e1f0d48-42e9-48c6-9175-2c7c376c86a5, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-ReplaceFileClientComponentTest-cibuild01, from=replaceClientTester, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@4a281ae0[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@55c445e5[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7144cd51[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=10, checksumDataForNewFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@28fb3476[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@55c445e5[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], checksumRequestForNewFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7144cd51[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>]]
Step: Validate the steps of the ReplaceClient by going through the events.
Step: The pillar sends a progress response to the ReplaceClient.
Result: Received event: 7e1f0d48: REPLACE_FILE for file default-test-file.txt: PROGRESS: ContributorID Pillar1, First test progress response message
Step: Send a final response message to the ReplaceClient.
Result: Received event: 7e1f0d48: REPLACE_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, checksum for new file: 'org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@28fb3476[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@55c445e5[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00]',checksum for replaced file: 'null'
Result: Received event: 7e1f0d48: REPLACE_FILE for file default-test-file.txt: COMPLETE:
Test success: replaceClientTester
Test starting: saltedReturnChecksumsForNewFileWithChecksumPillar
Description: Tests that the ReplaceClient handles the presence of a ChecksumPillar correctly, when a salted return checksum (which a checksum pillar can't provide) is requested for the new file.
Step: Call replaceFile while requesting a salted checksum to be returned.
Stimuli: replaceFile(default-test-file.txt, Pillar1, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@37994ff[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@755a3ffb[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], null, file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, 0, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@5d642e46[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@755a3ffb[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@62b9757d[checksumType=MD5, checksumSalt={-86}, otherChecksumType=<null>], org.bitrepository.client.TestEventHandler@2da8cbb9, null
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileRequest@9a99c10[correlationID=0d2adc0e-2280-4893-8b0d-147cbd91ab8d, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-ReplaceFileClientComponentTest-cibuild01, from=saltedReturnChecksumsForNewFileWithChecksumPillar, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt, fileSize=<null>]
Result: Received event: 0d2adc0e: REPLACE_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for replace file
Step: Send an identification response with a PillarChecksumSpec element set, indicating that this is a checksum pillar.
Result: Received event: 0d2adc0e: REPLACE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 0d2adc0e: REPLACE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 0d2adc0e: REPLACE_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for replace file
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.ReplaceFileRequest@5c781425[correlationID=0d2adc0e-2280-4893-8b0d-147cbd91ab8d, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-ReplaceFileClientComponentTest-cibuild01, from=saltedReturnChecksumsForNewFileWithChecksumPillar, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@37994ff[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@755a3ffb[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], checksumRequestForExistingFile=<null>, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, fileSize=0, checksumDataForNewFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@5d642e46[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@755a3ffb[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], checksumRequestForNewFile=<null>]
Test success: saltedReturnChecksumsForNewFileWithChecksumPillar
Test starting: verifyReplaceFileClientFromFactory
Description: Testing the initialization through the ModifyComponentFactory.
Step: Use the ModifyComponentFactory to instantiate a ReplaceFileClient.
Test success: verifyReplaceFileClientFromFactory
Starting testcase CommandLineTest
Test starting: argumentsTesterUnknownArgument
Description: Test the handling of arguments by the CommandLineArgumentHandler.
Step: Validate arguments without any options.
Test success: argumentsTesterUnknownArgument
Test starting: argumentsTesterWrongArgument
Description: Test the handling of arguments by the CommandLineArgumentHandler.
Step: Validate the default options
Test success: argumentsTesterWrongArgument
Test starting: newArgumentTester
Description: Test the handling of a new argument.
Step: Test the option
Test success: newArgumentTester
Starting testcase GetFileIDsClientComponentTest
Test starting: collectionIDIncludedInEventsTest
Description: Tests the the client provides collectionID in events.
Step: Set a 0.5 second operation timeout.
Step: Start the operation
Stimuli: Calling getFileIDs(null, null, null, org.bitrepository.client.TestEventHandler@58e48d9)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@7be55279[correlationID=6374dbb8-2869-4590-bd22-9db1a90b9da3, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=collectionIDIncludedInEventsTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@6dd6c64c[fileID=<null>, allFileIDs=true]]
Result: Received event: 6374dbb8: GET_FILE_IDS: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs
Step: Send positive responses from the pillar1 and a negative response from pillar2
Result: Received event: 6374dbb8: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 6374dbb8: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE
Result: Received event: 6374dbb8: GET_FILE_IDS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 6374dbb8: GET_FILE_IDS: REQUEST_SENT: ContributorID [Pillar1], Sending request for get fileIDs
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@203f929[correlationID=6374dbb8-2869-4590-bd22-9db1a90b9da3, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=collectionIDIncludedInEventsTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@59bcab83[fileID=<null>, allFileIDs=true], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
Step: Wait for 1 second
Result: Received event: 6374dbb8: GET_FILE_IDS: FAILED: , Failed to receive responses from all contributors before timeout(500ms). Missing contributors [Pillar1]
Test success: collectionIDIncludedInEventsTest
Test starting: conversationTimeoutTest
Description: Tests the the client handles lack of IdentifyPillarResponses gracefully
Step: Set a 100 ms ConversationTimeout.
Step: Start the operation
Stimuli: Calling getFileIDs(null, null, null, org.bitrepository.client.TestEventHandler@58e48d9)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@59463bab[correlationID=360736da-aa5d-4f94-8a0c-a8c60ef102e3, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=conversationTimeoutTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@4155e85d[fileID=<null>, allFileIDs=true]]
Result: Received event: 360736da: GET_FILE_IDS: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs
02:20:01.145 WARN o.b.c.c.m.CollectionBasedConversationMediator - Failing timed out conversation 360736da-aa5d-4f94-8a0c-a8c60ef102e3 (Age 1017ms)
Result: Received event: 360736da: GET_FILE_IDS: FAILED: , Failing timed out conversation 360736da-aa5d-4f94-8a0c-a8c60ef102e3
Test success: conversationTimeoutTest
Test starting: identificationFailureTest
Description: Verify that the client works correctly when a contributor sends a failure response.
Step: Start the operation.
Stimuli: Calling getFileIDs(null, null, null, org.bitrepository.client.TestEventHandler@58e48d9)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@20ea933f[correlationID=2f86572e-c9b6-423f-80ff-5cc121e9f0be, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=identificationFailureTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@125bfc70[fileID=<null>, allFileIDs=true]]
Result: Received event: 2f86572e: GET_FILE_IDS: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs
Step: Send a identification response from contributor1 with a FAILURE response code.
Result: Received event: 2f86572e: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE
Step: Send a identification response from contributor2 with a IDENTIFICATION_POSITIVE response code .
Result: Received event: 2f86572e: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 2f86572e: GET_FILE_IDS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: 2f86572e: GET_FILE_IDS: REQUEST_SENT: ContributorID [Pillar2], Sending request for get fileIDs
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@245b6b85[correlationID=2f86572e-c9b6-423f-80ff-5cc121e9f0be, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=identificationFailureTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@505c675a[fileID=<null>, allFileIDs=true], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
Step: Verify that the client continues to the performing phase.
Step: Send a final response message from contributor2
Result: Received event: 2f86572e: GET_FILE_IDS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false
Result: Received event: 2f86572e: GET_FILE_IDS: FAILED: , Failed operation. Cause(s):
[2f86572e: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE]
Test success: identificationFailureTest
Test starting: identificationNegativeTest
Description: Verify that the client works correctly when a contributor sends a negative response.
Step: Start the operation.
Stimuli: Calling getFileIDs(null, null, null, org.bitrepository.client.TestEventHandler@58e48d9)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@45f3891c[correlationID=cf7b0368-b0c0-4096-b3bb-96b106e6aba0, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=identificationNegativeTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@13e4acf6[fileID=<null>, allFileIDs=true]]
Result: Received event: cf7b0368: GET_FILE_IDS: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs
Step: Send a identification response from contributor1 with a IDENTIFICATION_NEGATIVE response code .
Result: Received event: cf7b0368: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: IDENTIFICATION_NEGATIVE
Step: Send a identification response from contributor2 with a IDENTIFICATION_POSITIVE response code .
Result: Received event: cf7b0368: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: cf7b0368: GET_FILE_IDS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: cf7b0368: GET_FILE_IDS: REQUEST_SENT: ContributorID [Pillar2], Sending request for get fileIDs
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@5883f0d5[correlationID=cf7b0368-b0c0-4096-b3bb-96b106e6aba0, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=identificationNegativeTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@16139b0[fileID=<null>, allFileIDs=true], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
Step: Verify that the client continues to the performing phase.
Step: Send a final response message from contributor2
Result: Received event: cf7b0368: GET_FILE_IDS: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false
Result: Received event: cf7b0368: GET_FILE_IDS: FAILED: , Failed operation. Cause(s):
[cf7b0368: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: IDENTIFICATION_NEGATIVE]
Test success: identificationNegativeTest
Test starting: noContributorsRespondingTest
Description: Tests the the client handles lack of a IdentifyResponse gracefully. More concrete this means that the occurrence of a identification timeout should be handled correctly
Step: Set a 100 ms timeout for identifying contributors.
Step: Start the operation.
Stimuli: Calling getFileIDs(null, null, null, org.bitrepository.client.TestEventHandler@58e48d9)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@7f487086[correlationID=93627c6e-9a73-4ed1-96ed-058e670c2630, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=noContributorsRespondingTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@4ced03c7[fileID=<null>, allFileIDs=true]]
Result: Received event: 93627c6e: GET_FILE_IDS: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs
Step: Wait for 1 second
Result: Received event: 93627c6e: GET_FILE_IDS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar1, Pillar2]
Result: Received event: 93627c6e: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor
Result: Received event: 93627c6e: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
Result: Received event: 93627c6e: GET_FILE_IDS: FAILED: , Unable to continue operation, contributors unavailable.
Test success: noContributorsRespondingTest
Result: The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@7f487086[correlationID=93627c6e-9a73-4ed1-96ed-058e670c2630, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=noContributorsRespondingTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@4ced03c7[fileID=<null>, allFileIDs=true]]
02:20:04.366 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@7f487086[correlationID=93627c6e-9a73-4ed1-96ed-058e670c2630, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=noContributorsRespondingTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@4ced03c7[fileID=<null>, allFileIDs=true]]
Test starting: oneContributorNotRespondingTest
Description: Verify that the client works correct without receiving identification responses from all contributors.
Added fixture: Set the a identification timeout to 100 ms.
Step: Start the operation.
Stimuli: Calling getFileIDs(null, null, null, org.bitrepository.client.TestEventHandler@58e48d9)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@2a447744[correlationID=57dde0bc-9430-44e8-b789-099388c05164, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=oneContributorNotRespondingTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@69d2cffb[fileID=<null>, allFileIDs=true]]
Result: Received event: 57dde0bc: GET_FILE_IDS: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs
Step: Send a identification response from contributor1.
Result: Received event: 57dde0bc: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Step: Wait 1 second.
Result: Received event: 57dde0bc: GET_FILE_IDS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar2]
Result: Received event: 57dde0bc: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
Result: Received event: 57dde0bc: GET_FILE_IDS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 57dde0bc: GET_FILE_IDS: REQUEST_SENT: ContributorID [Pillar1], Sending request for get fileIDs
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@62c315bd[correlationID=57dde0bc-9430-44e8-b789-099388c05164, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=oneContributorNotRespondingTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@27b3d07f[fileID=<null>, allFileIDs=true], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
Step: Verify that the client continues to the performing phase.
Step: Send a final response upload message
Result: Received event: 57dde0bc: GET_FILE_IDS: COMPONENT_COMPLETE: ContributorID Pillar1, PartialResult=false
Result: Received event: 57dde0bc: GET_FILE_IDS: FAILED: , Failed operation. Cause(s):
[57dde0bc: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor]
Test success: oneContributorNotRespondingTest
Test starting: operationTimeoutTest
Description: Tests the the client handles lack of final responses gracefully.
Step: Set a 100 ms operation timeout.
Step: Start the operation
Stimuli: Calling getFileIDs(null, null, null, org.bitrepository.client.TestEventHandler@58e48d9)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@7a00446[correlationID=6ca35cdc-f0e4-4f37-bf10-7e23cf4320cf, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=operationTimeoutTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@50f77755[fileID=<null>, allFileIDs=true]]
Result: Received event: 6ca35cdc: GET_FILE_IDS: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs
Step: Send positive responses from the pillar1 and a negative response from pillar2
Result: Received event: 6ca35cdc: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 6ca35cdc: GET_FILE_IDS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: IDENTIFICATION_NEGATIVE
Result: Received event: 6ca35cdc: GET_FILE_IDS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 6ca35cdc: GET_FILE_IDS: REQUEST_SENT: ContributorID [Pillar1], Sending request for get fileIDs
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@6cb0ab1e[correlationID=6ca35cdc-f0e4-4f37-bf10-7e23cf4320cf, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=operationTimeoutTest, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@6bb500fa[fileID=<null>, allFileIDs=true], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
Step: Wait for 1 second
Result: Received event: 6ca35cdc: GET_FILE_IDS: FAILED: , Failed to receive responses from all contributors before timeout(100ms). Missing contributors [Pillar1]
Test success: operationTimeoutTest
Starting testcase GetChecksumsCmdTest
Test starting: checksumArgumentNonSaltAlgorithmWitoutSaltTest
Description: Test MD5 checksum without salt -> no failure
Test success: checksumArgumentNonSaltAlgorithmWitoutSaltTest
Test starting: checksumArgumentSaltAlgorithmWithSaltTest
Description: Test HMAC_SHA256 checksum with salt -> No failure
Test success: checksumArgumentSaltAlgorithmWithSaltTest
Test starting: defaultSuccessScenarioTest
Description: Tests simplest arguments for running the CmdLineClient
Test success: defaultSuccessScenarioTest
Test starting: fileArgumentTest
Description: Tests the argument for a specific file.
Test success: fileArgumentTest
Test starting: missingCollectionArgumentTest
Description: Tests the scenario, where the collection arguments is missing.
Takes the following arguments:
-s The path to the directory with the settings files for the client
-k The path to the file containing the private key.
-v Makes the client more verbose
-c The id for the collection to perform the operation on.
-i The id for the file to perform the operation on.
-p [OPTIONAL] The id of the pillar where the should be performed. If undefined the operations is performed on all pillars.
-R [OPTIONAL] The algorithm of checksum to request in the response from the pillars. If no such argument is given, then the default from settings is retrieved.
-S [OPTIONAL] The salt of checksum to request in the response. Requires the ChecksumType argument.
Missing argument: Missing required option: c
Test success: missingCollectionArgumentTest
Test starting: specificPillarArgumentTest
Description: Test argument for a specific pillar
Test success: specificPillarArgumentTest
Test starting: unknownPillarArgumentTest
Description: Testing against a non-existing pillar id -> Should fail
Invalid argument: Random1454030406373pillar is not a valid pillar for collection TwoPillarCollection
The collection contains the following pillars: [Pillar1, Pillar2]
Test success: unknownPillarArgumentTest
Test starting: getFileIDsDeliveredAtUrl
Description: Tests the delivery of fileIDs from a pillar at a given URL.
Step: Initialise the variables for this test.
Step: Request the delivery of the file ids of a file from the pillar(s). A callback listener should be supplied.
Stimuli: Calling getFileIDs(null, default-test-file.txt, file:../bitrepository-core/src/test/resources/test-files//TEST-FILE-IDS-DELIVERY.xml, org.bitrepository.client.TestEventHandler@58e48d9)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@bf154bb[correlationID=a4b42c14-85ef-44ef-a32a-88cd2331c2a1, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=getFileIDsDeliveredAtUrl, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@6d6cd631[fileID=default-test-file.txt, allFileIDs=<null>]]
Result: Received event: a4b42c14: GET_FILE_IDS for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs
Step: The pillar sends a response to the identify message.
Result: Received event: a4b42c14: GET_FILE_IDS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: a4b42c14: GET_FILE_IDS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: a4b42c14: GET_FILE_IDS for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for get fileIDs
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@55cb75bf[correlationID=a4b42c14-85ef-44ef-a32a-88cd2331c2a1, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=getFileIDsDeliveredAtUrl, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@549ea731[fileID=default-test-file.txt, allFileIDs=<null>], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=file:../bitrepository-core/src/test/resources/test-files//TEST-FILE-IDS-DELIVERY.xml-Pillar1]
Step: The pillar sends a getFileIDsProgressResponse to the GetFileIDsClient.
Result: Received event: a4b42c14: GET_FILE_IDS for file default-test-file.txt: PROGRESS: ContributorID Pillar1, First test progress response message
Step: The resulting file is uploaded to the indicated url and the pillar sends a final response upload message
Result: Received event: a4b42c14: GET_FILE_IDS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, PartialResult=false
Result: Received event: a4b42c14: GET_FILE_IDS for file default-test-file.txt: COMPLETE:
Step: Receive and validate event results for the pillar.
Test success: getFileIDsDeliveredAtUrl
Test starting: getFileIDsDeliveredThroughMessage
Description: Tests the delivery of fileIDs from a pillar at a given URL.
Step: Initialise the variables for this test.
Step: Ensure the delivery file isn't already present on the http server
Step: Request the delivery of the file ids of a file from the pillar(s). A callback listener should be supplied.
Stimuli: Calling getFileIDs(null, default-test-file.txt, null, org.bitrepository.client.TestEventHandler@58e48d9)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@44e60564[correlationID=41c5f38c-4235-4c91-a604-1ce86f294ee9, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=getFileIDsDeliveredThroughMessage, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@5b9ad433[fileID=default-test-file.txt, allFileIDs=<null>]]
Result: Received event: 41c5f38c: GET_FILE_IDS for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs
Step: The pillar sends a response to the identify message.
Result: Received event: 41c5f38c: GET_FILE_IDS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 41c5f38c: GET_FILE_IDS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 41c5f38c: GET_FILE_IDS for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for get fileIDs
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@16ad008f[correlationID=41c5f38c-4235-4c91-a604-1ce86f294ee9, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=getFileIDsDeliveredThroughMessage, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@6214ea1b[fileID=default-test-file.txt, allFileIDs=<null>], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
Step: The pillar sends a getFileIDsProgressResponse to the GetFileIDsClient.
Result: Received event: 41c5f38c: GET_FILE_IDS for file default-test-file.txt: PROGRESS: ContributorID Pillar1, First test progress response message
Step: The resulting file is uploaded to the indicated url and the pillar sends a final response upload message
Result: Received event: 41c5f38c: GET_FILE_IDS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, NumberOfFileIDs=1, PartialResult=false
Result: Received event: 41c5f38c: GET_FILE_IDS for file default-test-file.txt: COMPLETE:
Step: Receive and validate event results for the pillar.
Test success: getFileIDsDeliveredThroughMessage
Test starting: getFileIDsFromOtherCollection
Description: Tests the getFileIDs client will correctly try to get from a second collection if required
Added fixture: Configure collection1 to contain both pillars and collection 2 to only contain pillar2
Step: Request the putting of a file through the PutClient for collection2
Stimuli: Calling getFileIDs(null, default-test-file.txt, null, org.bitrepository.client.TestEventHandler@3f1870bc)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@3993c2be[correlationID=7ef22927-aecf-4b95-8df0-3bfcbefb46d4, collectionID=SinglePillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=getFileIDsFromOtherCollection, to=Pillar2, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@55b0c0a6[fileID=default-test-file.txt, allFileIDs=<null>]]
Result: Received event: 7ef22927: GET_FILE_IDS for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs
Step: Send an identification response from pillar2.
Result: Received event: 7ef22927: GET_FILE_IDS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 7ef22927: GET_FILE_IDS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: 7ef22927: GET_FILE_IDS for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar2], Sending request for get fileIDs
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@e0895b3[correlationID=7ef22927-aecf-4b95-8df0-3bfcbefb46d4, collectionID=SinglePillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=getFileIDsFromOtherCollection, to=Pillar2, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@29a920fe[fileID=default-test-file.txt, allFileIDs=<null>], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=<null>]
Step: Send a complete event from the pillar
Result: Received event: 7ef22927: GET_FILE_IDS for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2, PartialResult=false
Result: Received event: 7ef22927: GET_FILE_IDS for file default-test-file.txt: COMPLETE:
Test success: getFileIDsFromOtherCollection
Test starting: testNoSuchFile
Description: Testing how a request for a non-existing file is handled.
Step: Setting up variables and such.
Step: Request the delivery of the file id of a file from the pillar(s). A callback listener should be supplied.
Stimuli: Calling getFileIDs(null, default-test-file.txt, file:../bitrepository-core/src/test/resources/test-files//TEST-FILE-IDS-DELIVERY.xml, org.bitrepository.client.TestEventHandler@58e48d9)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@6dfce79d[correlationID=18c1babb-6035-4038-b88b-362afb0b930e, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=testNoSuchFile, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@5c1c44b9[fileID=default-test-file.txt, allFileIDs=<null>]]
Result: Received event: 18c1babb: GET_FILE_IDS for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs
Step: The pillar sends a response to the identify message.
Result: Received event: 18c1babb: GET_FILE_IDS for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 18c1babb: GET_FILE_IDS for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 18c1babb: GET_FILE_IDS for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for get fileIDs
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@1ae12304[correlationID=18c1babb-6035-4038-b88b-362afb0b930e, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=testNoSuchFile, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@10abffca[fileID=default-test-file.txt, allFileIDs=<null>], minTimestamp=<null>, maxTimestamp=<null>, maxNumberOfResults=<null>, resultAddress=file:../bitrepository-core/src/test/resources/test-files//TEST-FILE-IDS-DELIVERY.xml-Pillar1]
Step: Send a error that the file cannot be found.
Result: Received event: 18c1babb: GET_FILE_IDS for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FILE_NOT_FOUND_FAILURE, No such file.
Result: Received event: 18c1babb: GET_FILE_IDS for file default-test-file.txt: FAILED: , Failed operation. Cause(s):
[18c1babb: GET_FILE_IDS for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FILE_NOT_FOUND_FAILURE, No such file.]
Test success: testNoSuchFile
Test starting: testPaging
Description: Tests the GetFileIDs client correctly handles functionality for limiting results, either by timestamp or result count.
Step: Request fileIDs from with MinTimestamp, MaxTimestamp, MaxNumberOfResults set for both pillars .
Stimuli: Calling getFileIDs([ContributorQuery{componentID='Pillar1, minTimestamp=Fri Jan 29 02:20:06 CET 2016, maxTimestamp=Fri Jan 29 02:20:07 CET 2016, maxNumberOfResults=1}, ContributorQuery{componentID='Pillar2, minTimestamp=Fri Jan 29 02:20:07 CET 2016, maxTimestamp=Fri Jan 29 02:20:07 CET 2016, maxNumberOfResults=2}], null, null, org.bitrepository.client.TestEventHandler@58e48d9)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsRequest@6ee88669[correlationID=0aa52512-9746-4b00-91fb-616ef3be6ad3, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=testPaging, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@4d1bbad3[fileID=<null>, allFileIDs=true]]
Result: Received event: 0aa52512: GET_FILE_IDS: IDENTIFY_REQUEST_SENT: , Identifying contributers for get fileIDs
Step: Send a IdentifyPillarsForGetFileIDsResponse from both pillars.
Result: Received event: 0aa52512: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 0aa52512: GET_FILE_IDS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 0aa52512: GET_FILE_IDS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1, Pillar2]
Result: Received event: 0aa52512: GET_FILE_IDS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending request for get fileIDs
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@1c791c14[correlationID=0aa52512-9746-4b00-91fb-616ef3be6ad3, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=testPaging, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@c24e06a[fileID=<null>, allFileIDs=true], minTimestamp=2016-01-29T02:20:06.160+01:00, maxTimestamp=2016-01-29T02:20:07.060+01:00, maxNumberOfResults=1, resultAddress=<null>]
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsRequest@1926e42e[correlationID=0aa52512-9746-4b00-91fb-616ef3be6ad3, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetFileIDsClientComponentTest-cibuild01, from=testPaging, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar2, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@6fa38b67[fileID=<null>, allFileIDs=true], minTimestamp=2016-01-29T02:20:07.060+01:00, maxTimestamp=2016-01-29T02:20:07.160+01:00, maxNumberOfResults=2, resultAddress=<null>]
Test success: testPaging
Test starting: verifyGetFileIDsClientFromFactory
Test success: verifyGetFileIDsClientFromFactory
Starting testcase GetStatusClientComponentTest
Test starting: getAllStatuses
Description: Tests the simplest case of getting status for all contributers.
Step: Create a GetStatusClient.
Step: Retrieve from all contributors in the collection
Stimuli: Calling getAuditTrails()
Result: Received event: 82f7b070: GET_STATUS: IDENTIFY_REQUEST_SENT: , Identifying contributors for getting status
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetStatusRequest@4436b8b[correlationID=82f7b070-18cb-4ab6-ad1c-0ec85e9e9a7c, collectionID=<null>, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetStatusClientComponentTest-cibuild01, from=getAllStatuses, to=<null>, version=28, minVersion=24, auditTrailInformation=]
Step: Send a identifyResponse from each pillar
Result: Received event: 82f7b070: GET_STATUS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 82f7b070: GET_STATUS: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 82f7b070: GET_STATUS: IDENTIFICATION_COMPLETE: Contributors: [Pillar2, Pillar1]
Result: Received event: 82f7b070: GET_STATUS: REQUEST_SENT: ContributorID [Pillar1, Pillar2], Sending GetStatusRequest
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetStatusRequest@3400f5aa[correlationID=82f7b070-18cb-4ab6-ad1c-0ec85e9e9a7c, collectionID=<null>, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetStatusClientComponentTest-cibuild01, from=getAllStatuses, to=<null>, version=28, minVersion=24, auditTrailInformation=, contributor=Pillar1]
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetStatusRequest@5daf0cb0[correlationID=82f7b070-18cb-4ab6-ad1c-0ec85e9e9a7c, collectionID=<null>, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetStatusClientComponentTest-cibuild01, from=getAllStatuses, to=<null>, version=28, minVersion=24, auditTrailInformation=, contributor=Pillar2]
Step: Send a final response from pillar 1
Result: Received event: 82f7b070: GET_STATUS: COMPONENT_COMPLETE: ContributorID Pillar1, resulting status: org.bitrepository.bitrepositoryelements.ResultingStatus@1a714d1[statusInfo=org.bitrepository.bitrepositoryelements.StatusInfo@3f13f033[statusCode=OK, statusText=Everythings fine..], statusTimestamp=2016-01-29T02:20:07.463+01:00]
Step: Send a final response from pillar 2
Result: Received event: 82f7b070: GET_STATUS: COMPONENT_COMPLETE: ContributorID Pillar2, resulting status: org.bitrepository.bitrepositoryelements.ResultingStatus@6e432c80[statusInfo=org.bitrepository.bitrepositoryelements.StatusInfo@60cb502a[statusCode=OK, statusText=Everythings fine..], statusTimestamp=2016-01-29T02:20:07.463+01:00]
Result: Received event: 82f7b070: GET_STATUS: COMPLETE:
Test success: getAllStatuses
Test starting: incompleteSetOfIdendifyResponses
Description: Verify that the GetStatus client works correct without receiving responses from all contributers.
Step: Configure 1 second timeout for identifying contributers. The default 2 contributers collection is used
Stimuli: Calling getAuditTrails()
Result: Received event: 0f851b47: GET_STATUS: IDENTIFY_REQUEST_SENT: , Identifying contributors for getting status
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetStatusRequest@5f3e12fc[correlationID=0f851b47-da9d-49d7-8521-61f29aa77fbe, collectionID=<null>, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetStatusClientComponentTest-cibuild01, from=incompleteSetOfIdendifyResponses, to=<null>, version=28, minVersion=24, auditTrailInformation=]
Step: Send a identifyResponse from pillar 1
Result: Received event: 0f851b47: GET_STATUS: COMPONENT_IDENTIFIED: ContributorID Pillar1
Step: Wait for timeout event
Result: Received event: 0f851b47: GET_STATUS: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar2]
Result: Received event: 0f851b47: GET_STATUS: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
Result: Received event: 0f851b47: GET_STATUS: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 0f851b47: GET_STATUS: REQUEST_SENT: ContributorID [Pillar1], Sending GetStatusRequest
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetStatusRequest@1a75ddaf[correlationID=0f851b47-da9d-49d7-8521-61f29aa77fbe, collectionID=<null>, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetStatusClientComponentTest-cibuild01, from=incompleteSetOfIdendifyResponses, to=<null>, version=28, minVersion=24, auditTrailInformation=, contributor=Pillar1]
Test success: incompleteSetOfIdendifyResponses
Test starting: verifyGetStatusClientFromFactory
Test success: verifyGetStatusClientFromFactory
Starting testcase PutFileCmdTest
Test starting: checksumArgumentNonSaltAlgorithmWitoutSaltTest
Description: Test MD5 checksum without salt -> no failure
Test success: checksumArgumentNonSaltAlgorithmWitoutSaltTest
Test starting: checksumArgumentSaltAlgorithmWithSaltTest
Description: Test HMAC_SHA256 checksum with salt -> No failure
Test success: checksumArgumentSaltAlgorithmWithSaltTest
Test starting: defaultSuccessScenarioTest
Description: Tests simplest arguments for running the CmdLineClient
Test success: defaultSuccessScenarioTest
Test starting: missingChecksumWhenFileArgumentTest
Description: Tests the scenario, where no checksum argument is given, but a file is given.
Test success: missingChecksumWhenFileArgumentTest
Test starting: missingChecksumWhenURLArgumentTest
Description: Tests the scenario, where no checksum argument is given, but a URL is given.
Invalid argument: The URL argument requires also the checksum argument (-c).
Test success: missingChecksumWhenURLArgumentTest
Test starting: missingCollectionArgumentTest
Description: Tests the scenario, where the collection arguments is missing.
Takes the following arguments:
-s The path to the directory with the settings files for the client
-k The path to the file containing the private key.
-v Makes the client more verbose
-c The id for the collection to perform the operation on.
-i The id for the file to perform the operation on.
-p [OPTIONAL] The id of the pillar where the should be performed. If undefined the operations is performed on all pillars.
-f The path to the file, which is wanted to be put. Is required, unless a URL is given.
-u The URL for the file to be put. Is required, unless the actual file is given.
-C The checksum for the file to be retreived. Required if using an URL.
-R [OPTIONAL] The algorithm of checksum to request in the response from the pillars.
-S [OPTIONAL] The salt of checksum to request in the response. Requires the ChecksumType argument.
-d If this argument is present, then the file will be removed from the server, when the operation is complete.
Missing argument: Missing required option: c
Test success: missingCollectionArgumentTest
Test starting: missingFileIDWhenFileArgumentTest
Description: Tests the scenario, where no checksum argument is given, but a URL is given.
Test success: missingFileIDWhenFileArgumentTest
Test starting: missingFileIDWhenURLArgumentTest
Description: Tests the scenario, where no checksum argument is given, but a URL is given.
Invalid argument: The URL argument requires also the argument for the ID of the file (-i).
Test success: missingFileIDWhenURLArgumentTest
Test starting: missingFileOrURLArgumentTest
Description: Tests the scenario, where no arguments for file or url is given.
Invalid argument: Requires either the file argument (-f) or the URL argument (-u).
Test success: missingFileOrURLArgumentTest
Test starting: specificPillarArgumentTest
Description: Test argument for a specific pillar
Test success: specificPillarArgumentTest
Test starting: unknownPillarArgumentTest
Description: Testing against a non-existing pillar id -> Should fail
Invalid argument: Random1454030410949pillar is not a valid pillar for collection TwoPillarCollection
The collection contains the following pillars: [Pillar1, Pillar2]
Test success: unknownPillarArgumentTest
Test starting: urlSuccessScenarioTest
Description: Tests arguments for putting a file on a given URL
Test success: urlSuccessScenarioTest
Starting testcase ReplaceFileCmdTest
Test starting: URLSuccessScenarioTest
Description: Tests the scenario, where a URL instead of a file is used for the replacement file.
Test success: URLSuccessScenarioTest
Test starting: bothFileAndURLArgumentTest
Description: Tests the scenario, where both arguments for file or url is given.
Invalid argument: Cannot take both a file (-f) and an URL (-u) as argument.
Test success: bothFileAndURLArgumentTest
Test starting: checksumArgumentNonSaltAlgorithmWitoutSaltTest
Description: Test MD5 checksum without salt -> no failure
Test success: checksumArgumentNonSaltAlgorithmWitoutSaltTest
Test starting: checksumArgumentSaltAlgorithmWithSaltTest
Description: Test HMAC_SHA256 checksum with salt -> No failure
Test success: checksumArgumentSaltAlgorithmWithSaltTest
Test starting: defaultSuccessScenarioTest
Description: Tests simplest arguments for running the CmdLineClient
Test success: defaultSuccessScenarioTest
Test starting: missingChecksumForExistingFileWhenUsingFileArgumentTest
Description: Tests the scenario, where no checksum argument is given, but a File is given.
Invalid argument: Checksum argument (-C) are mandatory for Replace and replace operations as defined in RepositorySettings.
Test success: missingChecksumForExistingFileWhenUsingFileArgumentTest
Test starting: missingChecksumForExistingFileWhenUsingURLArgumentTest
Description: Tests the scenario, where no checksum argument is given, but a URL is given.
Invalid argument: Checksum argument (-C) are mandatory for Replace and replace operations as defined in RepositorySettings.
Test success: missingChecksumForExistingFileWhenUsingURLArgumentTest
Test starting: missingChecksumForNewFileWhenUsingFileArgumentTest
Description: Tests the scenario, where no checksum argument is given, but a File is given.
Test success: missingChecksumForNewFileWhenUsingFileArgumentTest
Test starting: missingChecksumForNewFileWhenUsingURLArgumentTest
Description: Tests the scenario, where no checksum argument is given, but a URL is given.
Invalid argument: The URL argument requires also the checksum argument for the file to replace with (-r).
Test success: missingChecksumForNewFileWhenUsingURLArgumentTest
Test starting: missingCollectionArgumentTest
Description: Tests the scenario, where the collection arguments is missing.
Takes the following arguments:
-s The path to the directory with the settings files for the client
-k The path to the file containing the private key.
-v Makes the client more verbose
-c The id for the collection to perform the operation on.
-i The id for the file to perform the operation on.
-p [OPTIONAL] The id of the pillar where the should be performed. If undefined the operations is performed on all pillars.
-C [OPTIONAL] The checksum of the file to be replaced.
-f The path to the new file for the replacement. Required unless using the URL argument.
-u The URL for the file to be retreived. Is required, unless the actual file is given.
-r The checksum for the file to replace with. Required when using the URL argument.
-R [OPTIONAL] The algorithm of checksum to request in the response from the pillars.
-S [OPTIONAL] The salt of checksum to request in the response. Requires the ChecksumType argument.
-d If this argument is present, then the file will be removed from the server, when the operation is complete.
Missing argument: Missing required option: c
Test success: missingCollectionArgumentTest
Test starting: missingFileIDWhenFileArgumentTest
Description: Tests the scenario, where no checksum argument is given, but a URL is given.
Test success: missingFileIDWhenFileArgumentTest
Test starting: missingFileIDWhenURLArgumentTest
Description: Tests the scenario, where no checksum argument is given, but a URL is given.
Invalid argument: The URL argument requires also the argument for the ID of the file (-i).
Test success: missingFileIDWhenURLArgumentTest
Test starting: missingFileOrURLArgumentTest
Description: Tests the scenario, where no arguments for file or url is given.
Invalid argument: Requires either the file argument (-f) or the URL argument (-u).
Test success: missingFileOrURLArgumentTest
Test starting: missingPillarArgumentTest
Description: Tests the different scenarios, with the pillar argument.
Invalid argument: The pillar argument (-p) must defined for the Replace operation, only single pillar Replaces are allowed
Test success: missingPillarArgumentTest
Test starting: unknownPillarArgumentTest
Step: Testing against a non-existing pillar id
Invalid argument: Random1454030414373pillar is not a valid pillar for collection TwoPillarCollection
The collection contains the following pillars: [Pillar1, Pillar2]
Test success: unknownPillarArgumentTest
Starting testcase UnexpectedResponseExceptionTest
Test starting: testUnexpectedResponse
Description: Test the instantiation of the exception
Step: Setup
Step: Try to throw such an exception
Step: Throw the exception with an embedded exception
Test success: testUnexpectedResponse
Starting testcase GetFileClientComponentTest
Test starting: chooseFastestPillarGetFileClient
Description: Set the GetClient to retrieve a file as fast as possible, where it has to choose between to pillars with different times. The messages should be delivered at the same time.
Step: Create a GetFileClient configured to use a fast and a slow pillar.
Step: Defining the variables for the GetFileClient and defining them in the configuration
Step: Make the GetClient ask for fastest pillar.
Stimuli: Calling getFileFromFastestPillar(default-test-file.txt, file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileRequest@7476a4b5[correlationID=415c16e7-a8b4-40d4-9660-9170cbaaf0bb, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=chooseFastestPillarGetFileClient, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt]
Result: Received event: 415c16e7: GET_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetFile
Step: Three pillars send responses. First an average timeToDeliver, then a fast timeToDeliver and last a slow timeToDeliver.
Result: Received event: 415c16e7: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID THE-AVERAGE-PILLAR
Result: Received event: 415c16e7: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID THE-FAST-PILLAR
Result: Received event: 415c16e7: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID THE-SLOW-PILLAR
Result: Received event: 415c16e7: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [THE-FAST-PILLAR]
Result: Received event: 415c16e7: GET_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID SelectedComponentInfo: componentID=THE-FAST-PILLAR, componentTopic=Pillar1_topic-cibuild01, Sending GetFileRequest to
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileRequest@bfeaa61[correlationID=415c16e7-a8b4-40d4-9660-9170cbaaf0bb, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=chooseFastestPillarGetFileClient, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=THE-FAST-PILLAR, fileID=default-test-file.txt, filePart=<null>, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt]
Test success: chooseFastestPillarGetFileClient
Test starting: conversationTimeout
Description: Tests the the GetFileClient handles lack of IdentifyPillarResponses gracefully
Step: Set the number of pillars to 100ms and a 300 ms timeout for the conversation.
Step: Request the delivery of a file from a specific pillar. A callback listener should be supplied.
Stimuli: Calling getFileFromSpecificPillar(default-test-file.txt, file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, Pillar1)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileRequest@2f787374[correlationID=9e3d5094-a918-4a8d-848e-c4d5bea6e0ee, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=conversationTimeout, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt]
Result: Received event: 9e3d5094: GET_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetFile
Step: The pillar sends a response to the identify message.
Result: Received event: 9e3d5094: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 9e3d5094: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 9e3d5094: GET_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID SelectedComponentInfo: componentID=Pillar1, componentTopic=Pillar1_topic-cibuild01, Sending GetFileRequest to
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileRequest@194904a4[correlationID=9e3d5094-a918-4a8d-848e-c4d5bea6e0ee, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=conversationTimeout, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, filePart=<null>, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt]
Step: Wait for 1 second
02:20:15.643 WARN o.b.c.c.m.CollectionBasedConversationMediator - Failing timed out conversation 9e3d5094-a918-4a8d-848e-c4d5bea6e0ee (Age 1018ms)
Result: Received event: 9e3d5094: GET_FILE for file default-test-file.txt: FAILED: , Failing timed out conversation 9e3d5094-a918-4a8d-848e-c4d5bea6e0ee
Test success: conversationTimeout
Test starting: failureDuringPerform
Description: Verify that the GetFile reports a failed operation, in case of a component failing during the performing phase.
Step: Request a getFile from the fastest pillar.
Stimuli: Calling getFileFromFastestPillar(default-test-file.txt, file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileRequest@1b327a8f[correlationID=03c470fe-4fb4-4b07-90fb-86f37a1df778, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=failureDuringPerform, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt]
Result: Received event: 03c470fe: GET_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetFile
Step: Send a identification response from pillar1 and pillar2 with pillar1 the fastest.
Result: Received event: 03c470fe: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 03c470fe: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 03c470fe: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 03c470fe: GET_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID SelectedComponentInfo: componentID=Pillar1, componentTopic=Pillar1_topic-cibuild01, Sending GetFileRequest to
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileRequest@4ad4366[correlationID=03c470fe-4fb4-4b07-90fb-86f37a1df778, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=failureDuringPerform, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, filePart=<null>, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt]
Step: Send a failure response from pillar1
Result: Received event: 03c470fe: GET_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE
Result: Received event: 03c470fe: GET_FILE for file default-test-file.txt: FAILED: , Failed to get file from Pillar1, org.bitrepository.bitrepositoryelements.ResponseInfo@513028e3[responseCode=FAILURE, responseText=<null>]
Test success: failureDuringPerform
Test starting: getFileClientWithChecksumPillarInvolved
Description: Verify that the GetFile works correctly when a checksum pillar respond.
Step: Call getFile form fastest pillar.
Stimuli: Calling getFileFromFastestPillar(default-test-file.txt, file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileRequest@5a4d9c49[correlationID=d0afeb41-bcbd-44dd-bcc9-9c2c9eb28dab, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=getFileClientWithChecksumPillarInvolved, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt]
Result: Received event: d0afeb41: GET_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetFile
Step: Send a identification response from pillar1 with a REQUEST_NOT_SUPPORTED response code.
Step: Send a identification response from pillar2 with a IDENTIFICATION_POSITIVE response code .
Result: Received event: d0afeb41: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: d0afeb41: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: d0afeb41: GET_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID SelectedComponentInfo: componentID=Pillar2, componentTopic=Pillar2_topic-cibuild01, Sending GetFileRequest to
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileRequest@7f55b4d3[correlationID=d0afeb41-bcbd-44dd-bcc9-9c2c9eb28dab, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=getFileClientWithChecksumPillarInvolved, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar2, fileID=default-test-file.txt, filePart=<null>, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt]
Step: Verify that the client continues to the performing phase.
Step: Send a final response upload message
Result: Received event: d0afeb41: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2
Result: Received event: d0afeb41: GET_FILE for file default-test-file.txt: COMPLETE:
Test success: getFileClientWithChecksumPillarInvolved
Test starting: getFileClientWithIdentifyTimeout
Description: Verify that the GetFile works correct without receiving responses from all pillars.
Added fixture: Set the identification timeout to 500ms
Step: Call getFile form fastest pillar.
Stimuli: Calling getFileFromFastestPillar(default-test-file.txt, file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileRequest@75b180d0[correlationID=587211c0-f940-4fdc-8e94-6bf0385b45db, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=getFileClientWithIdentifyTimeout, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt]
Result: Received event: 587211c0: GET_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetFile
Step: Send a identification response from pillar1.
Result: Received event: 587211c0: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Step: Wait 1 second.
Result: Received event: 587211c0: GET_FILE for file default-test-file.txt: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar2]
Result: Received event: 587211c0: GET_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
Result: Received event: 587211c0: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 587211c0: GET_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID SelectedComponentInfo: componentID=Pillar1, componentTopic=Pillar1_topic-cibuild01, Sending GetFileRequest to
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileRequest@76c0b992[correlationID=587211c0-f940-4fdc-8e94-6bf0385b45db, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=getFileClientWithIdentifyTimeout, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, filePart=<null>, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt]
Step: Verify that the client continues to the performing phase.
Step: Send a final response upload message
Result: Received event: 587211c0: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1
Result: Received event: 587211c0: GET_FILE for file default-test-file.txt: COMPLETE:
Test success: getFileClientWithIdentifyTimeout
Test starting: getFileFromOtherCollection
Description: Tests the getFiles client will correctly try to get from a second collection if required
Added fixture: Configure collection1 to contain both pillars and collection 2 to only contain pillar2
Step: Request the getting of a file through the client for collection2
Stimuli: Calling getFileFromFastestPillar(default-test-file.txt, file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileRequest@33389710[correlationID=bb673428-4995-478a-b3be-c1e762b2ea8b, collectionID=SinglePillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=getFileFromOtherCollection, to=Pillar2, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt]
Result: Received event: bb673428: GET_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetFile
Step: Send an identification response from pillar2.
Result: Received event: bb673428: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: bb673428: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: bb673428: GET_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID SelectedComponentInfo: componentID=Pillar2, componentTopic=Pillar2_topic-cibuild01, Sending GetFileRequest to
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileRequest@1d386de6[correlationID=bb673428-4995-478a-b3be-c1e762b2ea8b, collectionID=SinglePillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=getFileFromOtherCollection, to=Pillar2, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar2, fileID=default-test-file.txt, filePart=<null>, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt]
Step: Send a complete event from the pillar
Result: Received event: bb673428: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2
Result: Received event: bb673428: GET_FILE for file default-test-file.txt: COMPLETE:
Test success: getFileFromOtherCollection
Test starting: getFileFromSpecificPillar
Description: Tests that the GetClient client works correctly when requesting a file from a specific pillar
Step: Request the delivery of a file from pillar2.
Stimuli: Calling getFileFromSpecificPillar(default-test-file.txt, file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, Pillar2)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileRequest@13a8de0b[correlationID=86fa3405-47a8-4883-82f3-5995d0e12557, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=getFileFromSpecificPillar, to=Pillar2, version=28, minVersion=24, auditTrailInformation=AuditTrailInfo for getFileFromSpecificPillarTest, fileID=default-test-file.txt]
Result: Received event: 86fa3405: GET_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetFile
Step: Send a response from pillar1
Step: Send a response from pillar2
Result: Received event: 86fa3405: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 86fa3405: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: 86fa3405: GET_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID SelectedComponentInfo: componentID=Pillar2, componentTopic=Pillar2_topic-cibuild01, Sending GetFileRequest to
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileRequest@64635346[correlationID=86fa3405-47a8-4883-82f3-5995d0e12557, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=getFileFromSpecificPillar, to=Pillar2, version=28, minVersion=24, auditTrailInformation=AuditTrailInfo for getFileFromSpecificPillarTest, pillarID=Pillar2, fileID=default-test-file.txt, filePart=<null>, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt]
Step: Send a GetFileProgressResponse.
Result: Received event: 86fa3405: GET_FILE for file default-test-file.txt: PROGRESS: ContributorID Pillar2, First test progress response message
Step: Send a GetFileFinalResponse.
Result: Received event: 86fa3405: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2
Result: Received event: 86fa3405: GET_FILE for file default-test-file.txt: COMPLETE:
Test success: getFileFromSpecificPillar
Test starting: getFileFromSpecificPillarWithFilePart
Description: Tests that the GetClient client works for a single pillar participates. Also validate, that the 'FilePart' can be used.
Step: Set the number of pillars to 1
Step: Request the delivery of a file from a specific pillar. A callback listener should be supplied.
Stimuli: Calling getFileFromSpecificPillar(default-test-file.txt, file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, Pillar1)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileRequest@469640e4[correlationID=ba09f633-d672-40ce-bee9-f0dcf071c27b, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=getFileFromSpecificPillarWithFilePart, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt]
Result: Received event: ba09f633: GET_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetFile
Step: The pillar sends a response to the identify message.
Result: Received event: ba09f633: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: ba09f633: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: ba09f633: GET_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID SelectedComponentInfo: componentID=Pillar1, componentTopic=Pillar1_topic-cibuild01, Sending GetFileRequest to
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileRequest@71cdc44c[correlationID=ba09f633-d672-40ce-bee9-f0dcf071c27b, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=getFileFromSpecificPillarWithFilePart, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, filePart=org.bitrepository.bitrepositoryelements.FilePart@72744ebe[partOffSet=1, partLength=10], fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt]
Step: The pillar sends a getFile response to the GetClient.
Result: Received event: ba09f633: GET_FILE for file default-test-file.txt: PROGRESS: ContributorID Pillar1, First test progress response message
Step: The file is uploaded to the indicated url and the pillar sends a final response upload message
Result: Received event: ba09f633: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1
Result: Received event: ba09f633: GET_FILE for file default-test-file.txt: COMPLETE:
Test success: getFileFromSpecificPillarWithFilePart
Test starting: noIdentifyResponse
Description: Tests the the GetFileClient handles lack of IdentifyPillarResponses gracefully
Step: Set a 500 ms timeout for identifying pillar.
Step: Make the GetClient ask for fastest pillar.
Stimuli: Calling getFileFromFastestPillar(default-test-file.txt, file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileRequest@7b7adf6[correlationID=f3b0750e-53a3-4081-9ef4-38ab0d3e72db, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=noIdentifyResponse, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt]
Result: Received event: f3b0750e: GET_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetFile
Step: Wait for 1 seconds
Result: Received event: f3b0750e: GET_FILE for file default-test-file.txt: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar1, Pillar2]
Result: Received event: f3b0750e: GET_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor
Result: Received event: f3b0750e: GET_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: null, Timeout for identifying contributor
Result: Received event: f3b0750e: GET_FILE for file default-test-file.txt: FAILED: , Unable to continue operation, contributors unavailable.
Test success: noIdentifyResponse
Test starting: singleComponentFailureDuringIdentify
Description: Verify that the GetFile reports a complete (not failed), in case of a component failing during the identify phase.
Step: Call getFile from the fastest pillar.
Stimuli: Calling getFileFromFastestPillar(default-test-file.txt, file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileRequest@2be51759[correlationID=01733a26-33dd-4b2c-9c15-8a47dca79509, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=singleComponentFailureDuringIdentify, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt]
Result: Received event: 01733a26: GET_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetFile
Step: Send a identification response from pillar1 with a IDENTIFICATION_NEGATIVE response code .
Result: Received event: 01733a26: GET_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: IDENTIFICATION_NEGATIVE
Step: Send a identification response from pillar2 with a IDENTIFICATION_POSITIVE response code .
Result: Received event: 01733a26: GET_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar2
Result: Received event: 01733a26: GET_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar2]
Result: Received event: 01733a26: GET_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID SelectedComponentInfo: componentID=Pillar2, componentTopic=Pillar2_topic-cibuild01, Sending GetFileRequest to
Result: Received message on Pillar2_topic-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileRequest@27476506[correlationID=01733a26-33dd-4b2c-9c15-8a47dca79509, collectionID=TwoPillarCollection, destination=Pillar2_topic-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=singleComponentFailureDuringIdentify, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar2, fileID=default-test-file.txt, filePart=<null>, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt]
Step: Verify that the client continues to the performing phase.
Step: Send a final response upload message
Result: Received event: 01733a26: GET_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar2
Result: Received event: 01733a26: GET_FILE for file default-test-file.txt: COMPLETE:
Test success: singleComponentFailureDuringIdentify
Test starting: testNoSuchFileMultiplePillars
Description: Testing how a request for a non-existing file is handled when all pillars miss the file.
Step: Use the default 2 pillars.
Step: Call getFileFromFastestPillar.
Stimuli: Calling getFileFromFastestPillar(ERROR-NO-SUCH-FILE-ERROR, file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileRequest@6604c7cc[correlationID=f9bb0b38-7622-4a83-a695-2ca5a8538ba7, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=testNoSuchFileMultiplePillars, to=<null>, version=28, minVersion=24, auditTrailInformation=<null>, fileID=ERROR-NO-SUCH-FILE-ERROR]
Result: Received event: f9bb0b38: GET_FILE for file ERROR-NO-SUCH-FILE-ERROR: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetFile
Step: Both pillars sends a FILE_NOT_FOUND response
Result: Received event: f9bb0b38: GET_FILE for file ERROR-NO-SUCH-FILE-ERROR: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FILE_NOT_FOUND_FAILURE, File ERROR-NO-SUCH-FILE-ERROR not present on this pillar
Result: Received event: f9bb0b38: GET_FILE for file ERROR-NO-SUCH-FILE-ERROR: COMPONENT_FAILED: ContributorID Pillar2 ResponseCode: FILE_NOT_FOUND_FAILURE, File ERROR-NO-SUCH-FILE-ERRORnot present on this pillar
Result: Received event: f9bb0b38: GET_FILE for file ERROR-NO-SUCH-FILE-ERROR: FAILED: , Unable to continue operation, contributors unavailable.
Test success: testNoSuchFileMultiplePillars
Test starting: testNoSuchFileSpecificPillar
Description: Testing how a request for a non-existing file is handled on a specific pillar request.
Step: Define 1 pillar.
Step: Call getFileFromSpecificPillar.
Stimuli: Calling getFileFromSpecificPillar(ERROR-NO-SUCH-FILE-ERROR, file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, Pillar1)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileRequest@27de21bc[correlationID=639de836-9bde-43a9-bd98-8e45aac0cce0, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-GetFileClientComponentTest-cibuild01, from=testNoSuchFileSpecificPillar, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=ERROR-NO-SUCH-FILE-ERROR]
Result: Received event: 639de836: GET_FILE for file ERROR-NO-SUCH-FILE-ERROR: IDENTIFY_REQUEST_SENT: , Identifying pillars for GetFile
Step: The specified pillars sends a FILE_NOT_FOUND response
Result: Received event: 639de836: GET_FILE for file ERROR-NO-SUCH-FILE-ERROR: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FILE_NOT_FOUND_FAILURE, File ERROR-NO-SUCH-FILE-ERROR not present on this pillar Pillar1
Result: Received event: 639de836: GET_FILE for file ERROR-NO-SUCH-FILE-ERROR: FAILED: , Unable to continue operation, contributors unavailable.
Test success: testNoSuchFileSpecificPillar
Test starting: verifyGetFileClientFromFactory
Test success: verifyGetFileClientFromFactory
Starting testcase DeleteFileClientComponentTest
Test starting: deleteClientIdentificationTimeout
Description: Tests the handling of a failed identification for the DeleteClient
Step: Initialise the number of pillars and the DeleteClient. Sets the identification timeout to 1 sec.
Step: Request a file to be deleted on the default pillar.
Stimuli: Calling deleteFile(default-test-file.txt, Pillar1, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@3abbfac7[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7786c47d[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7604bb54[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], eventHandler, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@2f527503[correlationID=fb816978-ae61-4989-b77a-cec4cd756566, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientIdentificationTimeout, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt]
Result: Received event: fb816978: DELETE_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for delete file
Step: Do not respond. Just await the timeout.
Result: Received event: fb816978: DELETE_FILE for file default-test-file.txt: IDENTIFY_TIMEOUT: , Time has run out for looking up contributors
The following contributors didn't respond: [Pillar1]
Result: Received event: fb816978: DELETE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: null, Timeout for identifying contributor
Result: Received event: fb816978: DELETE_FILE for file default-test-file.txt: FAILED: , Unable to continue operation, contributors unavailable.
Test success: deleteClientIdentificationTimeout
Test starting: deleteClientOperationTimeout
Description: Tests the handling of a failed operation for the DeleteClient
Step: Initialise the number of pillars and the DeleteClient. Sets the operation timeout to 100 ms.
Step: Request a file to be deleted on the default pillar.
Stimuli: Calling deleteFile(default-test-file.txt, Pillar1, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@203c9b37[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@584ffec8[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7d6a0a50[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], eventHandler, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@661b5520[correlationID=810d15d6-c5a2-49b6-8c2e-e11cb6e82022, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientOperationTimeout, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt]
Result: Received event: 810d15d6: DELETE_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for delete file
Step: Make response for the pillar.
Result: Received event: 810d15d6: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 810d15d6: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 810d15d6: DELETE_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for deleting file
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.DeleteFileRequest@5249cd6[correlationID=810d15d6-c5a2-49b6-8c2e-e11cb6e82022, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientOperationTimeout, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@203c9b37[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@584ffec8[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@7d6a0a50[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>]]
Step: Validate the steps of the DeleteClient by going through the events.
Step: Do not respond. Just await the timeout.
Result: Received event: 810d15d6: DELETE_FILE for file default-test-file.txt: FAILED: , Failed to receive responses from all contributors before timeout(100ms). Missing contributors [Pillar1]
Test success: deleteClientOperationTimeout
Test starting: deleteClientOtherPillarFailedDuringIdentification
Description: Tests the handling of a identification failure for a pillar for the DeleteClient.
Step: Request a file to be deleted on the pillar1.
Stimuli: Calling deleteFile(default-test-file.txt, Pillar1, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@72ddb47a[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1421e0d4[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2016-01-29T02:20:20.938+01:00], null, eventHandler, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@216d16c8[correlationID=023ef3c5-c529-4866-9a63-2c5660332dab, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientOtherPillarFailedDuringIdentification, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt]
Result: Received event: 023ef3c5: DELETE_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for delete file
Step: Send a failed response from pillar2.
Step: Send a ok response from pillar1.
Result: Received event: 023ef3c5: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 023ef3c5: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 023ef3c5: DELETE_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for deleting file
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.DeleteFileRequest@3b829217[correlationID=023ef3c5-c529-4866-9a63-2c5660332dab, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientOtherPillarFailedDuringIdentification, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@72ddb47a[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1421e0d4[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2016-01-29T02:20:20.938+01:00], checksumRequestForExistingFile=<null>]
Step: Send a final response message from pillar 1 to the DeleteClient.
Result: Received event: 023ef3c5: DELETE_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, DeleteFileResult=null
Result: Received event: 023ef3c5: DELETE_FILE for file default-test-file.txt: COMPLETE:
Test success: deleteClientOtherPillarFailedDuringIdentification
Test starting: deleteClientPillarFailedDuringPerform
Description: Tests the handling of a operation failure for the DeleteClient.
Step: Initialise the number of pillars to one
Step: Request a file to be deleted on the default pillar.
Stimuli: Calling deleteFile(default-test-file.txt, Pillar1, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@7142c345[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@4ff9fa2b[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1fbb8c0[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], eventHandler, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@58b1eca1[correlationID=a1dcad00-008e-43b1-91e9-7ca67320c319, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientPillarFailedDuringPerform, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt]
Result: Received event: a1dcad00: DELETE_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for delete file
Step: Make response for the pillar.
Result: Received event: a1dcad00: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: a1dcad00: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: a1dcad00: DELETE_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for deleting file
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.DeleteFileRequest@3f26d961[correlationID=a1dcad00-008e-43b1-91e9-7ca67320c319, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientPillarFailedDuringPerform, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@7142c345[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@4ff9fa2b[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1fbb8c0[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>]]
Step: Validate the steps of the DeleteClient by going through the events.
Step: Send a failed response message to the DeleteClient.
Result: Received event: a1dcad00: DELETE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE, Verifying that a failure can be understood!
Result: Received event: a1dcad00: DELETE_FILE for file default-test-file.txt: FAILED: , Failed operation. Cause(s):
[a1dcad00: DELETE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: FAILURE, Verifying that a failure can be understood!]
Test success: deleteClientPillarFailedDuringPerform
Test starting: deleteClientSpecifiedPillarFailedDuringIdentification
Description: Tests the handling of a identification failure for a pillar for the DeleteClient.
Step: Request a file to be deleted on the pillar1.
Stimuli: Calling deleteFile(default-test-file.txt, Pillar1, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@490ab739[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1838104d[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2016-01-29T02:20:22.453+01:00], null, eventHandler, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@5d1ef2ce[correlationID=bdfb226c-d854-4486-b446-b681122eba4c, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientSpecifiedPillarFailedDuringIdentification, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt]
Result: Received event: bdfb226c: DELETE_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for delete file
Step: Send a failed response from pillar1.
Result: Received event: bdfb226c: DELETE_FILE for file default-test-file.txt: COMPONENT_FAILED: ContributorID Pillar1 ResponseCode: IDENTIFICATION_NEGATIVE
Result: Received event: bdfb226c: DELETE_FILE for file default-test-file.txt: FAILED: , Can not continue with delete operation, as Pillar1 is unable to perform the deletion.
Test success: deleteClientSpecifiedPillarFailedDuringIdentification
Test starting: deleteClientTester
Description: Tests the DeleteClient. Makes a whole conversation for the delete client for a 'good' scenario.
Step: Initialise the number of pillars to one
Step: Request a file to be deleted on all pillars (which means only the default pillar).
Stimuli: Calling deleteFile(default-test-file.txt, Pillar1, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@50752b7f[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@20f234ec[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@519427cd[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>], eventHandler, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@3e0af3c[correlationID=0a2f4ce4-f914-466b-be88-64af9ac37c2f, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientTester, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt]
Result: Received event: 0a2f4ce4: DELETE_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for delete file
Step: Make response for the pillar.
Result: Received event: 0a2f4ce4: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 0a2f4ce4: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 0a2f4ce4: DELETE_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for deleting file
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.DeleteFileRequest@4b534c12[correlationID=0a2f4ce4-f914-466b-be88-64af9ac37c2f, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteClientTester, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@50752b7f[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@20f234ec[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={49,50,51,99,104,101,99,107,115,117,109,51,50,49}, calculationTimestamp=1970-01-01T01:00:00.000+01:00], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@519427cd[checksumType=SHA1, checksumSalt=<null>, otherChecksumType=<null>]]
Step: Validate the steps of the DeleteClient by going through the events.
Step: The pillar sends a progress response to the DeleteClient.
Result: Received event: 0a2f4ce4: DELETE_FILE for file default-test-file.txt: PROGRESS: ContributorID Pillar1, First test progress response message
Step: Send a final response message to the DeleteClient.
Result: Received event: 0a2f4ce4: DELETE_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, DeleteFileResult=null
Result: Received event: 0a2f4ce4: DELETE_FILE for file default-test-file.txt: COMPLETE:
Test success: deleteClientTester
Test starting: deleteOnChecksumPillar
Description: Verify that the DeleteClient works correctly when a checksum pillar is present.
Step: Request a file to be deleted on the pillar1.
Stimuli: Calling deleteFile(default-test-file.txt, Pillar1, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@84d838[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@60eed3d7[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2016-01-29T02:20:22.917+01:00], null, eventHandler, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@5650f99f[correlationID=f1ede4e8-2f40-40c5-b382-4bfba4e651ae, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteOnChecksumPillar, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt]
Result: Received event: f1ede4e8: DELETE_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for delete file
Step: Send an identification response from pillar2.
Step: Send a response from pillar1 with PillarChecksumSpec element set, indicating that this is a checksum pillar.
Result: Received event: f1ede4e8: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: f1ede4e8: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: f1ede4e8: DELETE_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for deleting file
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.DeleteFileRequest@5111651f[correlationID=f1ede4e8-2f40-40c5-b382-4bfba4e651ae, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteOnChecksumPillar, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@84d838[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@60eed3d7[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2016-01-29T02:20:22.917+01:00], checksumRequestForExistingFile=<null>]
Test success: deleteOnChecksumPillar
Test starting: deleteOnChecksumPillarWithDefaultReturnChecksumType
Description: Verify that the DeleteClient works correctly when a return checksum of the default typeis requested.
Step: Request a file to be deleted on the pillar1. The call should include a request for a check sum of the default type
Stimuli: Calling deleteFile(default-test-file.txt, Pillar1, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@7f7ec5f5[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@4018055d[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2016-01-29T02:20:25.149+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1439b119[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], eventHandler, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@2293db81[correlationID=a333cdd3-727e-46d2-98e9-aaff17fcf7a7, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteOnChecksumPillarWithDefaultReturnChecksumType, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt]
Result: Received event: a333cdd3: DELETE_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for delete file
Step: Send a response from pillar1 with PillarChecksumSpec element set, indicating that this is a checksum pillar.
Result: Received event: a333cdd3: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: a333cdd3: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: a333cdd3: DELETE_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for deleting file
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.DeleteFileRequest@2b793982[correlationID=a333cdd3-727e-46d2-98e9-aaff17fcf7a7, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteOnChecksumPillarWithDefaultReturnChecksumType, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@7f7ec5f5[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@4018055d[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2016-01-29T02:20:25.149+01:00], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1439b119[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>]]
Test success: deleteOnChecksumPillarWithDefaultReturnChecksumType
Test starting: deleteOnChecksumPillarWithSaltedReturnChecksumType
Description: Verify that the DeleteClient works correctly when a return checksum with a salt is requested.
Step: Request a file to be deleted on the pillar1. The call should include a request for a salted check sum
Stimuli: Calling deleteFile(default-test-file.txt, Pillar1, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@204b63a7[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@103b392f[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2016-01-29T02:20:25.342+01:00], org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@3d2a0be7[checksumType=MD5, checksumSalt={-86}, otherChecksumType=<null>], eventHandler, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@3daada72[correlationID=05124722-7f68-4032-9bd8-82ddfd420417, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteOnChecksumPillarWithSaltedReturnChecksumType, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt]
Result: Received event: 05124722: DELETE_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for delete file
Step: Send a response from pillar1 with PillarChecksumSpec element set, indicating that this is a checksum pillar.
Result: Received event: 05124722: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 05124722: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: [Pillar1]
Result: Received event: 05124722: DELETE_FILE for file default-test-file.txt: REQUEST_SENT: ContributorID [Pillar1], Sending request for deleting file
Result: Received message on Pillar1_topic-cibuild01 : org.bitrepository.bitrepositorymessages.DeleteFileRequest@f3c6b85[correlationID=05124722-7f68-4032-9bd8-82ddfd420417, collectionID=TwoPillarCollection, destination=Pillar1_topic-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=deleteOnChecksumPillarWithSaltedReturnChecksumType, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, pillarID=Pillar1, fileID=default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@204b63a7[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@103b392f[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2016-01-29T02:20:25.342+01:00], checksumRequestForExistingFile=<null>]
Test success: deleteOnChecksumPillarWithSaltedReturnChecksumType
Test starting: fileAlreadyDeletedFromPillar
Description: Test that a delete on a pillar completes successfully when the file is missing (has already been deleted). This is a test of the Idempotent behaviour of the delete client
Step: Request a file to be deleted on pillar1.
Stimuli: Calling deleteFile(default-test-file.txt, Pillar1, org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@3736c1f2[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@36532ee6[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={-108,10,81,-78,80,-25,-86,-126,-40,-24,-22,49,33,127,-14,103}, calculationTimestamp=2016-01-29T02:20:25.512+01:00], null, eventHandler, null)
Result: Received message on TEST-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileRequest@63868bca[correlationID=970fbeff-ab7f-4a92-a757-fe12eeb90390, collectionID=TwoPillarCollection, destination=TEST-TOPIC-cibuild01, replyTo=TEST-TOPIC-DeleteFileClientComponentTest-cibuild01, from=fileAlreadyDeletedFromPillar, to=Pillar1, version=28, minVersion=24, auditTrailInformation=<null>, fileID=default-test-file.txt]
Result: Received event: 970fbeff: DELETE_FILE for file default-test-file.txt: IDENTIFY_REQUEST_SENT: , Identifying pillars for delete file
Step: Send a identify response from Pillar1 with a missing file response.
Result: Received event: 970fbeff: DELETE_FILE for file default-test-file.txt: COMPONENT_IDENTIFIED: ContributorID Pillar1
Result: Received event: 970fbeff: DELETE_FILE for file default-test-file.txt: COMPONENT_COMPLETE: ContributorID Pillar1, DeleteFileResult=null
Result: Received event: 970fbeff: DELETE_FILE for file default-test-file.txt: IDENTIFICATION_COMPLETE: Contributors: []
Result: Received event: 970fbeff: DELETE_FILE for file default-test-file.txt: COMPLETE:
Step: The client should then continue to the performing phase and finish immediately as the pillar has already had the file removed apparently .
Step: Send a identify response from Pillar2
Test success: fileAlreadyDeletedFromPillar
Test starting: verifyDeleteClientFromFactory
Description: Testing the initialization through the ModifyComponentFactory.
Step: Use the ModifyComponentFactory to instantiate a PutFileClient.
Test success: verifyDeleteClientFromFactory
Finished testcase
Finished suite
Finished project
Tests run: 156, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 65.312 sec - in TestSuite
Results :
Tests run: 156, Failures: 0, Errors: 0, Skipped: 0
[JENKINS] Recording test results
[INFO]
[INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ bitrepository-client ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/target/bitrepository-client-1.7-SNAPSHOT.jar
[INFO]
[INFO] --- maven-jar-plugin:2.4:test-jar (default) @ bitrepository-client ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/target/bitrepository-client-1.7-SNAPSHOT-tests.jar
[INFO]
[INFO] --- maven-source-plugin:2.2.1:jar-no-fork (attach-sources-no-fork) @ bitrepository-client ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/target/bitrepository-client-1.7-SNAPSHOT-sources.jar
[INFO]
[INFO] --- maven-assembly-plugin:2.4:single (make-assembly) @ bitrepository-client ---
[INFO] Reading assembly descriptor: src/main/assembly/assembly.xml
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/target/bitrepository-client-1.7-SNAPSHOT-distribution.tar.gz
[INFO]
[INFO] --- maven-install-plugin:2.5.1:install (default-install) @ bitrepository-client ---
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/target/bitrepository-client-1.7-SNAPSHOT.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-client/1.7-SNAPSHOT/bitrepository-client-1.7-SNAPSHOT.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-client/1.7-SNAPSHOT/bitrepository-client-1.7-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/target/bitrepository-client-1.7-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-client/1.7-SNAPSHOT/bitrepository-client-1.7-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/target/bitrepository-client-1.7-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-client/1.7-SNAPSHOT/bitrepository-client-1.7-SNAPSHOT-sources.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-client/target/bitrepository-client-1.7-SNAPSHOT-distribution.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-client/1.7-SNAPSHOT/bitrepository-client-1.7-SNAPSHOT-distribution.tar.gz
[JENKINS] Archiving disabled
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Service 1.7-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-service ---
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ bitrepository-service ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 7 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ bitrepository-service ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 53 source files to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-service/target/classes
[INFO]
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ bitrepository-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-service ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 9 source files to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-service/target/test-classes
[INFO]
[INFO] --- maven-surefire-plugin:2.17:test (default-test) @ bitrepository-service ---
[INFO] Surefire report directory: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-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 IdentifyContributorExceptionTest
Test starting: testIdentifyContributor
Description: Test the instantiation of the exception
Step: Setup
Step: Try to throw such an exception
Step: Throw the exception with an embedded exception
Test success: testIdentifyContributor
Test starting: componentIDTest
Test success: componentIDTest
Starting testcase AuditTrailContributorDatabaseTest
Test starting: testAuditTrailDatabaseFunctions
Description: Testing the basic functions of the audit trail database interface.
Step: Setup varibles and the database connection.
Step: Populate the database.
Step: Test extracting all the events
Step: Test extracting the events for fileID1
Step: Test extracting the events for fileID2
Step: Test extracting the events with the sequence number at least equal to the largest sequence number.
Step: Test extracting the events for fileID1 with sequence number 2 or more
Step: Test extracting the events for fileID1 with at most sequence number 2
Step: Test extracting at most 3 events
Step: Test extracting at most 1000 events
Step: Test extracting from another collection
Test success: testAuditTrailDatabaseFunctions
Test starting: testAuditTrailDatabaseIngest
Description: Testing the ingest of data.
Step: Setup varibles and the database connection.
Step: Test with all data.
Step: Test with no collection
Step: Test with with no file id.
Step: Test with with no actor.
Step: Test with with no info.
Step: Test with with no audittrail.
Step: Test with with no operationID.
Step: Test with with no certificateID.
Step: Test with with no action.
Step: Test with with very large file id.
Step: Test with with very large actor name.
Step: Test with with very large info.
Step: Test with with very large audittrail.
Test success: testAuditTrailDatabaseIngest
Starting testcase IllegalOperationExceptionTest
Test starting: testIdentifyContributor
Description: Test the instantiation of the exception
Step: Setup
Step: Try to throw such an exception
Step: Throw the exception with an embedded exception
Test success: testIdentifyContributor
Starting testcase InvalidMessageExceptionTest
Test starting: testIdentifyContributor
Description: Test the instantiation of the exception
Step: Setup
Step: Try to throw such an exception
Step: Throw the exception with an embedded exception
Test success: testIdentifyContributor
Starting testcase AuditTrailContributorDatabaseMigrationTest
Test starting: testMigratingAuditContributorDatabase
Description: Tests that the database can be migrated to latest version with the provided scripts.
Step: Validate setup
Step: Ingest a entry to the database without the collection id
Step: Perform migration
02:20:54.610 WARN o.b.service.database.DatabaseUtils - Migrating AuditContributorDB from version 1 to 2.
02:20:54.731 WARN o.b.service.database.DatabaseUtils - Migrating AuditContributorDB from version 2 to 3.
02:20:55.318 WARN o.b.service.database.DatabaseUtils - Migrating AuditContributorDB from version 3 to 4.
Test success: testMigratingAuditContributorDatabase
Finished testcase
Finished suite
Finished project
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 16.414 sec - in TestSuite
Results :
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0
[JENKINS] Recording test results
[INFO]
[INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ bitrepository-service ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-service/target/bitrepository-service-1.7-SNAPSHOT.jar
[INFO]
[INFO] --- maven-jar-plugin:2.4:test-jar (default) @ bitrepository-service ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-service/target/bitrepository-service-1.7-SNAPSHOT-tests.jar
[INFO]
[INFO] --- maven-source-plugin:2.2.1:jar-no-fork (attach-sources-no-fork) @ bitrepository-service ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-service/target/bitrepository-service-1.7-SNAPSHOT-sources.jar
[INFO]
[INFO] --- maven-install-plugin:2.5.1:install (default-install) @ bitrepository-service ---
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-service/target/bitrepository-service-1.7-SNAPSHOT.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-service/1.7-SNAPSHOT/bitrepository-service-1.7-SNAPSHOT.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-service/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-service/1.7-SNAPSHOT/bitrepository-service-1.7-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-service/target/bitrepository-service-1.7-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-service/1.7-SNAPSHOT/bitrepository-service-1.7-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-service/target/bitrepository-service-1.7-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-service/1.7-SNAPSHOT/bitrepository-service-1.7-SNAPSHOT-sources.jar
[JENKINS] Archiving disabled
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Integrity Service 1.7-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-integrity-service ---
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ bitrepository-integrity-service ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 12 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ bitrepository-integrity-service ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 67 source files to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integrity-service/target/classes
[INFO]
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ bitrepository-integrity-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-integrity-service ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 24 source files to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integrity-service/target/test-classes
[INFO]
[INFO] --- maven-surefire-plugin:2.17:test (default-test) @ bitrepository-integrity-service ---
[INFO] Surefire report directory: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integrity-service/target/surefire-reports
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running TestSuite
Configuring TestNG with: TestNG652Configurator
Starting test project Integration Service Test
Suite: Surefire suite
Starting testcase HandleChecksumValidationStepTest
Test starting: testAuditTrailsForChecksumErrors
Description: Test audit trails for checksum errors. Verify that a pillar with a single checksum will be pointed out as the possible cause.
02:21:15.975 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:21:15.979 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Step: Test step on data without checksum error
Step: Test step on data where only two pillars have the file and they disagree about the checksum.
number of files in the collection2
number of fileinfos: 3
Step: remove the last auditinfo
Step: Test step on data where two pillars have one checksum and the last pillar has a different one
Test success: testAuditTrailsForChecksumErrors
Test starting: testChecksumMajority
Description: Test the checksum integrity validator when two pillars have one checksum and the last pillar has another checksum.
02:21:22.200 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:21:22.204 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Step: Add data to the cache
Step: Perform the checksum validation step
Step: Validate the file ids
Test success: testChecksumMajority
Test starting: testMissingAtOnePillar
Description: Test the checksum integrity validator when one pillar is missing the data.
02:21:28.531 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:21:28.534 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Step: Update the cache with identitical data for both pillars.
Step: Perform the step
Step: Validate the file ids
Test success: testMissingAtOnePillar
Test starting: testNoData
Description: Test the checksum integrity validator without any data in the cache.
02:21:33.336 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:21:33.393 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Step: Validate the file ids
Test success: testNoData
Test starting: testSimilarData
Description: Test the checksum integrity validator when all pillars have similar data.
02:21:39.227 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:21:39.234 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Step: Add data to the cache
Step: Perform the step
Step: Validate the file ids
Test success: testSimilarData
Test starting: testThreeDisagreeingChecksums
Description: Test the checksum integrity validator when all pillars have different checksums.
02:21:44.783 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:21:44.787 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Step: Add data to the cache
Step: Perform the step
Step: Validate the file ids
Test success: testThreeDisagreeingChecksums
Test starting: testTwoDisagreeingChecksums
Description: Test the checksum integrity validator when only two pillar has data, but it it different.
02:21:50.505 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:21:50.514 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Step: Add data to the cache
Step: Perform the step
Step: Validate the file ids
Test success: testTwoDisagreeingChecksums
Starting testcase MaxChecksumAgeProviderTest
Test starting: testNoPillarSpecificSetting
Description: Test the MaxChecksumAge when no settings are defined for the specific pillar
Step: Create a MaxChecksumAgeProvider with settings containing a default MaxAge of 10 and no pillar specific settings
Test success: testNoPillarSpecificSetting
Test starting: testNoSettings
Description: Test the MaxChecksumAge when no settings are defined
Step: Create a MaxChecksumAgeProvider with null settings and a default MaxAge of 100
Test success: testNoSettings
Test starting: testPillarSpecificSetting
Description: Test the MaxChecksumAge when a value has been defined for specific pillars
Step: Create a MaxChecksumAgeProvider with settings containing a default MaxAge of 10, pillar1MaxChecksumAge of 1001 and pillar2 MaxChecksumAge of 1002
Test success: testPillarSpecificSetting
Starting testcase PutFileStepTest
Test starting: testNegativeReply
Description: Test the step for getting the file can handle FAILURE operation event.
Test success: testNegativeReply
Test starting: testPositiveReply
Description: Test the step for getting the file can handle COMPLETE operation event.
Test success: testPositiveReply
Starting testcase UpdateFileIDsStepTest
Test starting: testAbortWorkflowWhenNegativeReply
Description: Test the step for updating the file ids will throw an WorkflowAbortedExceptionwhen AbortOnFailedContributor is set to true and a FAILED event is received.
02:21:52.609 WARN o.b.i.c.IntegrityCollectorEventHandler - Component failure for 'test-pillar-1'.
02:21:52.609 WARN o.b.i.c.IntegrityCollectorEventHandler - Failure: null: null: FAILED: , Operation failed
Test success: testAbortWorkflowWhenNegativeReply
Test starting: testContinueWorkflowWhenNegativeReply
Description: Test the step for updating the file ids will continue when getting an FAILED operation event when AbortOnFailedContributor is set to false
02:21:52.736 WARN o.b.i.c.IntegrityCollectorEventHandler - Component failure for 'test-pillar-1'.
02:21:52.736 WARN o.b.i.c.IntegrityCollectorEventHandler - Failure: null: null: FAILED: , Operation failed
Test success: testContinueWorkflowWhenNegativeReply
Test starting: testIngestOfResults
Description: Test the step for updating the file ids can ingest the data correctly into the store.
Test success: testIngestOfResults
Test starting: testPartialResults
Description: Test that the number of partial is used for generating more than one request.
Step: Setup the collector mock to generate a isPartialResult=true event the first time and a isPartialResult=false the second time
Test success: testPartialResults
Test starting: testPositiveReply
Description: Test the step for updating the file ids can handle COMPLETE operation event.
Test success: testPositiveReply
Test starting: testRetryCollectionWhenNegativeReply
Description: Test the step for updating the file ids will retry on a FAILED event
02:21:53.548 WARN o.b.i.c.IntegrityCollectorEventHandler - Component failure for 'test-pillar-1'.
02:21:53.549 WARN o.b.i.c.IntegrityCollectorEventHandler - Failure: null: null: FAILED: , Operation failed
Test success: testRetryCollectionWhenNegativeReply
Test starting: testConstructor
Test success: testConstructor
Test starting: testFailContributor
Test success: testFailContributor
Test starting: testFinishContributor
Test success: testFinishContributor
Test starting: testReloadContributors
Test success: testReloadContributors
Test starting: testRetry
Test success: testRetry
Test starting: testSucceed
Test success: testSucceed
Starting testcase IntegrityDAOTest
Test starting: initialStateExtractionTest
Description: Tests the initial state of the IntegrityModel. Should not contain any data.
02:21:57.089 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:21:57.095 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Test success: initialStateExtractionTest
Test starting: instantiationTest
Description: Testing the connection to the integrity database.
02:22:02.026 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:22:02.031 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Test success: instantiationTest
Test starting: reinitialiseDatabaseTest
Description: Testing the connection to the integrity database.
Step: Setup manually.
02:22:04.937 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:22:04.944 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Step: Close the connection and create another one.
Test success: reinitialiseDatabaseTest
Test starting: testDeletingEntry
Description: Tests the deletion of an FileID entry from a collection. Checks that it does not effect another collection with a fileID equal to the deleted
02:22:09.262 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:22:09.265 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Step: Create data
Step: Ensure that the data is present
Step: Delete the entry for the first pillar
Step: Delete the entry for the second pillar
Step: Check that the data in the extra collection is still present
Test success: testDeletingEntry
Test starting: testDeletingNonExistingEntry
Description: Tests the deletion of an nonexisting FileID entry.
02:22:12.413 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:22:12.414 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Step: Create data
Step: Delete a nonexisting entry
Test success: testDeletingNonExistingEntry
Test starting: testExtractCollectionFileSize
Description: Tests that the accumulated size of the collection can be extracted
02:22:16.889 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:22:16.891 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Step: Insert test data into database
Step: Check the reported size of the first pillar in the collection
Step: Check the reported size of the second pillar in the collection
Step: Check the reported size of the whole collection
Test success: testExtractCollectionFileSize
Test starting: testExtractingAllKnownFilesForPillars
Description: Tests that known files can be extracted for specific pillars.
02:22:22.044 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:22:22.047 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Step: Insert two files into database for a pillar
Step: Insert a file to the extra collection for the common pillar
Step: Extract all the existing file ids for the pillar for collection 'TwoPillarCollection'
Step: Extract the single fileID for the extra collection
Step: Extract all the existing file ids for another pillar
Test success: testExtractingAllKnownFilesForPillars
Test starting: testExtractingAllKnownFilesForPillarsLimits
Description: Tests the limits for extracting files for specific pillars.
02:22:25.982 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:22:26.014 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Step: Insert two files into database for a pillar
Step: Extract with a maximum of 1
Step: Extract with a minimum of 1 and maximum of infinite
Test success: testExtractingAllKnownFilesForPillarsLimits
Test starting: testExtractingAllMissingFilesForPillars
Description: Tests that missing files can be extracted for specific pillars.
02:22:30.085 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:22:30.134 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Step: Insert two files into database for a pillar and mark them as missing
Step: Check the number of files in collection and on pillars
Step: Extract missing files from the first pillar
Step: Extract missing files from the second pillar
Test success: testExtractingAllMissingFilesForPillars
Test starting: testExtractingAllMissingFilesForPillarsLimits
Description: Tests the limits for extracting missing files for specific pillars.
02:22:34.579 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:22:34.581 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Step: Insert two files into database for a pillar and set them to missing
Step: Extract with a maximum of 1
Step: Extract with a minimum of 1 and maximum of infinite
Test success: testExtractingAllMissingFilesForPillarsLimits
Test starting: testFindInconsistentChecksum
Description: Testing the localization of inconsistent checksums
02:22:38.528 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:22:38.529 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Step: Update the database with 2 inconsistent files and one consistent file.
Step: Find the files with inconsistent checksums
Test success: testFindInconsistentChecksum
Test starting: testFindOrphanFiles
Description: Tests the ability to find orphan files.
02:22:40.927 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:22:40.929 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Step: Create data
Test success: testFindOrphanFiles
Test starting: testGetLatestChecksumDateEntryForCollection
Description: Tests that checksum date entries can be retrieved and manipulated.
02:22:45.867 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:22:45.933 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Step: Create data
Test success: testGetLatestChecksumDateEntryForCollection
Test starting: testGetLatestFileDateEntryForCollection
Description: Tests that checksum date entries can be retrieved and manipulated.
02:22:51.300 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:22:51.302 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Step: Create data
Test success: testGetLatestFileDateEntryForCollection
Test starting: testIngestOfChecksumsData
Description: Tests the ingesting of checksums data
02:22:54.217 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:22:54.219 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Step: Create data
Step: Extract the data
Step: Check that the extra collection is untouched by the ingest
Test success: testIngestOfChecksumsData
Test starting: testIngestOfFileIDsData
Description: Tests the ingesting of file ids data
02:22:58.245 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:22:58.246 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Step: Create data
Step: Extract the data
Step: Check that the extra collection is untouched by the ingest
Test success: testIngestOfFileIDsData
Test starting: testMissingChecksums
Description: Testing the checksum validation, when only one pillar has a checksum for a file.
02:23:02.202 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:23:02.204 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Step: Update the database with 1 file, missing its checksum on one pillar.
Step: Finding the files with inconsistent checksums
Test success: testMissingChecksums
Test starting: testMissingChecksumsChecksumNotUpdated
Description: Testing the checksum validation, when only one pillar has a checksum for a file.
02:23:05.366 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:23:05.368 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Step: Update the database with 1 file, no missing checksums.
Step: Finding the files with inconsistent checksums
Step: Updating the checksum for one pillar, and checking that the other pillars checksum is now missing
Step: Finding the files with inconsistent checksums
Test success: testMissingChecksumsChecksumNotUpdated
Test starting: testNoChecksums
Description: Testing the checksum validation, when no checksums exists.
02:23:10.636 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:23:10.639 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Step: Update the database with 2 inconsistent files and one consistent file.
Step: Finding the files with inconsistent checksums
Test success: testNoChecksums
Test starting: testOutdatedChecksums
Description: Testing the checksum validation, when only one pillar has a checksum for a file.
02:23:13.328 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:23:13.330 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Step: Update the database with one file, one pillar having an outdated checksum.
Step: Finding the files with inconsistent checksums
Test success: testOutdatedChecksums
Starting testcase IntegrityAlerterTest
Test starting: testIntegrityFailed
Description: Test the IntegrityFailed method for the IntegrityAlerter
Step: Call the function for integrity failure.
02:23:15.953 WARN o.b.i.a.IntegrityAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@765d2d4d[origDateTime=2016-01-29T02:23:15.953+01:00, alarmCode=INTEGRITY_ISSUE, alarmRaiser=IntegrityAlerterTest, alarmText=Testaintegrity alarm, fileID=<null>, collectionID=TwoPillarCollection]
Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@66e17bf2[correlationID=a7eaee04-dc44-4d92-9d89-4a2714a8dd04, collectionID=TwoPillarCollection, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-IntegrityAlerterTest-cibuild01-contributor, from=IntegrityAlerterTest, to=<null>, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@765d2d4d[origDateTime=2016-01-29T02:23:15.953+01:00, alarmCode=INTEGRITY_ISSUE, alarmRaiser=IntegrityAlerterTest, alarmText=Testaintegrity alarm, fileID=<null>, collectionID=TwoPillarCollection]]
Test success: testIntegrityFailed
Test starting: testOperationFailed
Description: Test the OperationFailed method for the IntegrityAlerter
Step: Call the function for integrity failure.
02:23:16.973 WARN o.b.i.a.IntegrityAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@4ea01c2a[origDateTime=2016-01-29T02:23:16.972+01:00, alarmCode=FAILED_OPERATION, alarmRaiser=IntegrityAlerterTest, alarmText=Testing the ability to fail., fileID=<null>, collectionID=TwoPillarCollection]
Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@7ec02149[correlationID=8c5d4f99-e487-4cdd-b6ca-454643b75ac0, collectionID=TwoPillarCollection, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-IntegrityAlerterTest-cibuild01-contributor, from=IntegrityAlerterTest, to=<null>, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@4ea01c2a[origDateTime=2016-01-29T02:23:16.972+01:00, alarmCode=FAILED_OPERATION, alarmRaiser=IntegrityAlerterTest, alarmText=Testing the ability to fail., fileID=<null>, collectionID=TwoPillarCollection]]
Test success: testOperationFailed
Starting testcase IntegrityWorkflowManagerTest
Test starting: collectionSpecificWorkflows
Description: Verifies that the IntegrityWorkflowManager loads correctly for workflows configured for specific collection.
Step: Create a IntegrityWorkflowManager based on a workflow with different schedules for collection 1 and 2 (daily and hourly)
Test success: collectionSpecificWorkflows
Test starting: noWorkflowPackage
Description: Verifies that the IntegrityWorkflowManager loads correctly for at workflow configuration with a workflow class name without a package scope (located in the deafult workflow package).
Step: Create a IntegrityWorkflowManager based on a single Testworkflow with a daily schedule in a to collection system, where the className is just the simplename
Test success: noWorkflowPackage
Test starting: noWorkflowSettings
Description: Verifies that the IntegrityWorkflowManager loads correctly for missing reference settings a workflow settings element.
Step: Create a IntegrityWorkflowManager based on a workflowsettingsless configuration
Test success: noWorkflowSettings
Test starting: normalWorkflowSettings
Description: Verifies that the IntegrityWorkflowManager loads correctly for at normally defined workflow.
Step: Create a IntegrityWorkflowManager based on a single Testworkflow with a daily schedule in a to collection system
Test success: normalWorkflowSettings
Test starting: startWorkflow
Description: Verifies that the that it is possible to manually start a workflow.
Step: Call the startWorkflow with a workflow defined in the configuration
Test success: startWorkflow
Test starting: unscheduledWorkflow
Description: Verifies that the IntegrityWorkflowManager loads workflow correctly for workflows without a defined schedule meaning they are never run automatically.
Step: Create a IntegrityWorkflowManager based on a single Testworkflow without a schedule
Test success: unscheduledWorkflow
Starting testcase IntegrityDatabaseTest
Test starting: initialStateExtractionTest
Description: Tests the initial state of the IntegrityModel. Should not contain any data.
02:23:20.141 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:23:20.156 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Step: Test the 'findChecksumsOlderThan'
Step: Test the 'findMissingChecksums'
Step: Test the 'findMissingFiles'
Step: Test the 'getAllFileIDs'
Step: Test the 'getFileInfos'
Step: Test the 'getNumberOfFiles'
Test success: initialStateExtractionTest
Test starting: instantiationTest
Description: Tests that the connection can be instantaited.
02:23:23.019 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:23:23.021 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Test success: instantiationTest
Test starting: testDeletingEntry
Description: Tests the deletion of an FileID entry.
02:23:26.317 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:23:26.329 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Step: Create data
Step: Delete the entry
Test success: testDeletingEntry
Test starting: testIngestOfChecksumsData
Description: Tests the ingesting of checksums data
02:23:29.608 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:23:29.623 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Step: Create data
Step: Extract the data
Test success: testIngestOfChecksumsData
Test starting: testIngestOfFileIDsData
Description: Tests the ingesting of file ids data
02:23:33.311 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:23:33.316 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Step: Create data
Step: Extract the data
Test success: testIngestOfFileIDsData
Starting testcase RepairMissingFilesWorkflowTest
Test starting: testFailedGetFile
Description: Test that the workflow does not try to put a file, if it fails to get it.
Step: Prepare for calls to mocks to fail when performing get-file
Step: Run missing checksum step.
02:23:33.824 ERROR o.b.i.w.RepairMissingFilesWorkflow - Failure in step: 'Performing GetFile for 'test-file-1'.'.
java.lang.IllegalStateException: Aborting workflow due to failure getting the file 'test-file-1'. Cause: null: null: FAILED: , failure
at org.bitrepository.integrityservice.workflow.step.GetFileStep.performStep(GetFileStep.java:74) ~[classes/:na]
at org.bitrepository.service.workflow.Workflow.performStep(Workflow.java:63) ~[bitrepository-service-1.7-SNAPSHOT.jar:1.7-SNAPSHOT]
at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflow.getFileStep(RepairMissingFilesWorkflow.java:177) [classes/:na]
at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflow.repairMissingFilesForPillar(RepairMissingFilesWorkflow.java:117) [classes/:na]
at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflow.start(RepairMissingFilesWorkflow.java:89) [classes/:na]
at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflowTest.testFailedGetFile(RepairMissingFilesWorkflowTest.java:194) [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]
02:23:33.839 WARN o.b.i.w.RepairMissingFilesWorkflow - Error occured during repair of missing file, 'test-file-1'. Tries to continue.
java.lang.RuntimeException: Failed to run step Performing GetFile for 'test-file-1'.
at org.bitrepository.service.workflow.Workflow.performStep(Workflow.java:69) ~[bitrepository-service-1.7-SNAPSHOT.jar:1.7-SNAPSHOT]
at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflow.getFileStep(RepairMissingFilesWorkflow.java:177) [classes/:na]
at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflow.repairMissingFilesForPillar(RepairMissingFilesWorkflow.java:117) [classes/:na]
at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflow.start(RepairMissingFilesWorkflow.java:89) [classes/:na]
at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflowTest.testFailedGetFile(RepairMissingFilesWorkflowTest.java:194) [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]
Caused by: java.lang.IllegalStateException: Aborting workflow due to failure getting the file 'test-file-1'. Cause: null: null: FAILED: , failure
at org.bitrepository.integrityservice.workflow.step.GetFileStep.performStep(GetFileStep.java:74) ~[classes/:na]
at org.bitrepository.service.workflow.Workflow.performStep(Workflow.java:63) ~[bitrepository-service-1.7-SNAPSHOT.jar:1.7-SNAPSHOT]
... 32 common frames omitted
Test success: testFailedGetFile
Test starting: testFailedPutFile
Description: Test that the workflow makes calls to the collector for get and put file, even when put file fails.
Step: Prepare for calls to mocks
Step: Run workflow to repair missing files.
02:23:33.991 ERROR o.b.i.w.RepairMissingFilesWorkflow - Failure in step: 'Performing PutFile for 'test-file-1'.'.
java.lang.IllegalStateException: Aborting workflow due to failure putting the file 'test-file-1'. Cause: null: null: FAILED: , failure
at org.bitrepository.integrityservice.workflow.step.PutFileStep.performStep(PutFileStep.java:88) ~[classes/:na]
at org.bitrepository.service.workflow.Workflow.performStep(Workflow.java:63) ~[bitrepository-service-1.7-SNAPSHOT.jar:1.7-SNAPSHOT]
at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflow.putFileStep(RepairMissingFilesWorkflow.java:192) [classes/:na]
at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflow.repairMissingFilesForPillar(RepairMissingFilesWorkflow.java:118) [classes/:na]
at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflow.start(RepairMissingFilesWorkflow.java:89) [classes/:na]
at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflowTest.testFailedPutFile(RepairMissingFilesWorkflowTest.java:242) [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]
02:23:33.997 WARN o.b.i.w.RepairMissingFilesWorkflow - Error occured during repair of missing file, 'test-file-1'. Tries to continue.
java.lang.RuntimeException: Failed to run step Performing PutFile for 'test-file-1'.
at org.bitrepository.service.workflow.Workflow.performStep(Workflow.java:69) ~[bitrepository-service-1.7-SNAPSHOT.jar:1.7-SNAPSHOT]
at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflow.putFileStep(RepairMissingFilesWorkflow.java:192) [classes/:na]
at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflow.repairMissingFilesForPillar(RepairMissingFilesWorkflow.java:118) [classes/:na]
at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflow.start(RepairMissingFilesWorkflow.java:89) [classes/:na]
at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflowTest.testFailedPutFile(RepairMissingFilesWorkflowTest.java:242) [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]
Caused by: java.lang.IllegalStateException: Aborting workflow due to failure putting the file 'test-file-1'. Cause: null: null: FAILED: , failure
at org.bitrepository.integrityservice.workflow.step.PutFileStep.performStep(PutFileStep.java:88) ~[classes/:na]
at org.bitrepository.service.workflow.Workflow.performStep(Workflow.java:63) ~[bitrepository-service-1.7-SNAPSHOT.jar:1.7-SNAPSHOT]
... 32 common frames omitted
Test success: testFailedPutFile
Test starting: testNoMissingFiles
Description: Test that the workflow does nothing, when it has no missing files.
Step: Prepare for calls to mocks
Step: Run workflow for repairing missing files.
Test success: testNoMissingFiles
Test starting: testSuccesRepair
Description: Test that the workflow makes calls to the collector, when a file is missing
Step: Prepare for calls to mocks to handle a repair
Step: Run workflow for repairing missing files.
02:23:34.913 WARN o.b.i.w.RepairMissingFilesWorkflow - Issue deleting file from FileExchange
org.apache.http.conn.HttpHostConnectException: Connect to localhost:80 [localhost/127.0.0.1] failed: Connection refused
at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:151) ~[httpclient-4.5.1.jar:4.5.1]
at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:353) ~[httpclient-4.5.1.jar:4.5.1]
at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:380) ~[httpclient-4.5.1.jar:4.5.1]
at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236) ~[httpclient-4.5.1.jar:4.5.1]
at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:184) ~[httpclient-4.5.1.jar:4.5.1]
at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:88) ~[httpclient-4.5.1.jar:4.5.1]
at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110) ~[httpclient-4.5.1.jar:4.5.1]
at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184) ~[httpclient-4.5.1.jar:4.5.1]
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82) ~[httpclient-4.5.1.jar:4.5.1]
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:107) ~[httpclient-4.5.1.jar:4.5.1]
at org.bitrepository.protocol.http.HttpFileExchange.deleteFile(HttpFileExchange.java:261) ~[bitrepository-core-1.7-SNAPSHOT.jar:1.7-SNAPSHOT]
at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflow.deleteUrl(RepairMissingFilesWorkflow.java:207) [classes/:na]
at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflow.repairMissingFilesForPillar(RepairMissingFilesWorkflow.java:119) [classes/:na]
at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflow.start(RepairMissingFilesWorkflow.java:89) [classes/:na]
at org.bitrepository.integrityservice.workflow.RepairMissingFilesWorkflowTest.testSuccesRepair(RepairMissingFilesWorkflowTest.java:157) [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]
Caused by: java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method) ~[na:1.8.0_11]
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:345) ~[na:1.8.0_11]
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) ~[na:1.8.0_11]
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) ~[na:1.8.0_11]
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) ~[na:1.8.0_11]
at java.net.Socket.connect(Socket.java:589) ~[na:1.8.0_11]
at org.apache.http.conn.socket.PlainConnectionSocketFactory.connectSocket(PlainConnectionSocketFactory.java:74) ~[httpclient-4.5.1.jar:4.5.1]
at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:134) ~[httpclient-4.5.1.jar:4.5.1]
... 42 common frames omitted
Test success: testSuccesRepair
Starting testcase GetFileStepTest
Test starting: testNegativeReply
Description: Test the step for getting the file can handle FAILURE operation event.
Test success: testNegativeReply
Test starting: testPositiveReply
Description: Test the step for getting the file can handle COMPLETE operation event.
Test success: testPositiveReply
Starting testcase UpdateChecksumsStepTest
Test starting: testAbortWorkflowWhenNegativeReply
Description: Test the step for updating the checksums will abort the workflow in case of FAILURE operation event and AbortOnFailedContributor = true .
02:23:35.996 WARN o.b.i.c.IntegrityCollectorEventHandler - Component failure for 'test-pillar-1'.
02:23:35.997 WARN o.b.i.c.IntegrityCollectorEventHandler - Failure: null: null: FAILED: , Problem encountered
Test success: testAbortWorkflowWhenNegativeReply
Test starting: testCallForChangingChecksumStates
Description: Test the step for updating the checksums delivers the results to the integrity model.
Test success: testCallForChangingChecksumStates
Test starting: testContinueWorkflowNegativeReply
Description: Test the step for updating the checksums will continue the workflow in case of FAILURE operation event and AbortOnFailedContributor = false .
02:23:36.220 WARN o.b.i.c.IntegrityCollectorEventHandler - Component failure for 'test-pillar-1'.
02:23:36.220 WARN o.b.i.c.IntegrityCollectorEventHandler - Failure: null: null: FAILED: , Problem encountered
Test success: testContinueWorkflowNegativeReply
Test starting: testFullChecksumCollection
Description: Test that the full list of checksums is requested.
Test success: testFullChecksumCollection
Test starting: testIncrementalChecksumCollection
Description: Test that only the list of new checksums is requested.
Test success: testIncrementalChecksumCollection
Test starting: testIngestOfResults
Description: Test the step for updating the checksums delivers the results to the integrity model.
Test success: testIngestOfResults
Test starting: testPartialResults
Description: Test that the number of partial is used for generating more than one request.
Step: Setup the collector mock to generate a isPartialResult=true event the first time and a isPartialResult=false the second time
Test success: testPartialResults
Test starting: testPositiveReply
Description: Test the step for updating the checksums can handle COMPLETE operation event.
Test success: testPositiveReply
Test starting: testRetryCollectionWhenNegativeReply
Description: Test the step for updating the file ids will retry on a FAILED event
02:23:36.791 WARN o.b.i.c.IntegrityCollectorEventHandler - Component failure for 'test-pillar-1'.
02:23:36.791 WARN o.b.i.c.IntegrityCollectorEventHandler - Failure: null: null: FAILED: , Problem encountered
Test success: testRetryCollectionWhenNegativeReply
Starting testcase IntegrityDBToolsTest
Test starting: testAddCollectionSuccess
Description: Tests that a new collection can be added to the integrity database
02:23:40.202 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:23:40.204 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Step: Extract initial list of collections
Step: Add the new collection
Test success: testAddCollectionSuccess
Test starting: testAddExistingCollection
Description: Tests that an existing collectionID cannot be added to the integrity database.
02:23:42.485 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:23:42.494 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Step: Extract initial list of collections.
Step: Attempt to add the new collection.
Test success: testAddExistingCollection
Test starting: testRemoveNonExistingCollection
Description: Tests that a non existing collection can't be removed from the integrity database.
02:23:45.529 WARN o.b.i.cache.IntegrityDatabaseManager - Database needs to be migrated, attempting to automigrate.
02:23:45.530 WARN o.b.service.database.DatabaseUtils - Migrating integrityDB from version 5 to 6
Step: Extract initial list of collections.
Step: Attempt to remove the non-existing collection.
Test success: testRemoveNonExistingCollection
Starting testcase BasicIntegrityReporterTest
Test starting: checksumIssuesTest
Description: Verifies that missing files are reported correctly
Step: Report a checksum issue
Step: Report another checksum issue on the same pillar
Step: Report a checksum issue on another pillar
Test success: checksumIssuesTest
Test starting: deletedFilesTest
Description: Verifies that the hasIntegrityIssues() reports deleted files correctly
Step: Report a delete file for a new Reporter
Test success: deletedFilesTest
Test starting: missingChecksumTest
Description: Verifies that missing checksums are reported correctly
Step: Report a missing checksum
Step: Report another missing checksum on the same pillar
Step: Report a missing checksum on another pillar
Test success: missingChecksumTest
Test starting: missingFilesTest
Description: Verifies that missing files are reported correctly
Step: Report a missing file
Step: Report another missing file on the same pillar
Step: Report a missing file on another pillar
Test success: missingFilesTest
Test starting: noIntegrityIssuesTest
Description: Verifies that missing files are reported correctly
Step: Create a clean reporter
Test success: noIntegrityIssuesTest
Test starting: obsoleteChecksumTest
Description: Verifies that obsolete checksums are reported correctly
Step: Report a obsolete checksum
Step: Report another obsolete checksum on the same pillar
Step: Report a obsolete checksum on another pillar
Test success: obsoleteChecksumTest
Starting testcase FileInfoTest
Test starting: testFileInfo
Description: Tests the FileInfo element. Adds all data and extracts it again.
Step: Setup the file info.
Step: Change the checksum
Step: Change the date for last file id check
Step: Change the date for last checksum check
Test success: testFileInfo
Starting testcase IntegrityInformationCollectorTest
Test starting: testCollectorGetChecksums
Description: Tests that the collector calls the GetChecksumsClient
Step: Define variables
Step: Setup a GetChecksumsClient for test purpose.
Step: Call the getChecksumsClient on the collector.
Step: Call the getChecksumsClient on the collector four times more.
Test success: testCollectorGetChecksums
Test starting: testCollectorGetFile
Description: Tests that the collector calls the GetFileClient
Step: Define variables
Step: Setup a GetFileClient for test purpose.
Step: Call the GetFileClient on the collector.
Step: Call the GetFileClient on the collector four times more.
Test success: testCollectorGetFile
Test starting: testCollectorGetFileIDs
Description: Tests that the collector calls the GetFileClient
Step: Define variables
Step: Setup a GetFileIDsClient for test purpose.
Step: Call the getFileIDs on the collector.
Step: Call the getFileIDs on the collector four times more.
Test success: testCollectorGetFileIDs
Test starting: testCollectorHandleChecksumClientFailures
Description: Test that the IntegrityInformationCollector works as a fault-barrier.
Step: Setup variables for the test
Step: Setup a failing GetChecksumClient for test purpose.
Step: Verify that the collector does not fail, just because the GetChecksumClient does so
02:23:45.656 ERROR o.b.i.c.DelegatingIntegrityInformationCollector - Unexpected failure!
java.lang.RuntimeException: null
at org.bitrepository.integrityservice.collector.DelegatingIntegrityInformationCollector.getChecksums(DelegatingIntegrityInformationCollector.java:89) ~[classes/:na]
at org.bitrepository.integrityservice.collector.IntegrityInformationCollectorTest.testCollectorHandleChecksumClientFailures(IntegrityInformationCollectorTest.java:202) [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]
Test success: testCollectorHandleChecksumClientFailures
Test starting: testCollectorHandleGetFileClientFailures
Description: Test that the IntegrityInformationCollector works as a fault-barrier.
Step: Define variables
Step: Setup a GetFileClient for test purpose, and ensure that it throws an error when called.
Step: Verify that the collector does not fail, just because the GetFileClient does so
02:23:45.662 ERROR o.b.i.c.DelegatingIntegrityInformationCollector - Unexpected failure!
java.lang.RuntimeException: null
at org.bitrepository.integrityservice.collector.DelegatingIntegrityInformationCollector.getFile(DelegatingIntegrityInformationCollector.java:100) ~[classes/:na]
at org.bitrepository.integrityservice.collector.IntegrityInformationCollectorTest.testCollectorHandleGetFileClientFailures(IntegrityInformationCollectorTest.java:241) [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]
Test success: testCollectorHandleGetFileClientFailures
Test starting: testCollectorHandleGetFileIDsClientFailures
Description: Test that the IntegrityInformationCollector works as a fault-barrier.
Step: Setup variables for the test
Step: Setup a DyingGetFileIDsClient for test purpose.
Step: Verify that the collector does not fail, just because the GetChecksumClient does so
02:23:45.664 ERROR o.b.i.c.DelegatingIntegrityInformationCollector - Unexpected failure!
java.lang.RuntimeException: null
at org.bitrepository.integrityservice.collector.DelegatingIntegrityInformationCollector.getFileIDs(DelegatingIntegrityInformationCollector.java:78) ~[classes/:na]
at org.bitrepository.integrityservice.collector.IntegrityInformationCollectorTest.testCollectorHandleGetFileIDsClientFailures(IntegrityInformationCollectorTest.java:221) [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]
Test success: testCollectorHandleGetFileIDsClientFailures
Test starting: testCollectorHandlePutFileClientFailures
Description: Test that the IntegrityInformationCollector works as a fault-barrier.
Step: Define variables
Step: Setup a PutFileClient for test purpose, and ensure that it throws an error when called.
Step: Verify that the collector does not fail, just because the PutFileClient does so
02:23:45.670 ERROR o.b.i.c.DelegatingIntegrityInformationCollector - Unexpected failure!
java.lang.RuntimeException: null
at org.bitrepository.integrityservice.collector.DelegatingIntegrityInformationCollector.putFile(DelegatingIntegrityInformationCollector.java:111) ~[classes/:na]
at org.bitrepository.integrityservice.collector.IntegrityInformationCollectorTest.testCollectorHandlePutFileClientFailures(IntegrityInformationCollectorTest.java:262) [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]
Test success: testCollectorHandlePutFileClientFailures
Test starting: testCollectorPutFile
Description: Tests that the collector calls the PutFileClient
Step: Define variables
Step: Setup a PutFileClient for test purpose.
Step: Call the PutFileClient on the collector.
Step: Call the PutFileClient on the collector four times more.
Test success: testCollectorPutFile
Finished testcase
Finished suite
Finished project
Tests run: 90, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 163.63 sec - in TestSuite
Results :
Tests run: 90, Failures: 0, Errors: 0, Skipped: 0
[JENKINS] Recording test results
[INFO]
[INFO] --- maven-war-plugin:2.4:war (default-war) @ bitrepository-integrity-service ---
[INFO] Packaging webapp
[INFO] Assembling webapp [bitrepository-integrity-service] in [/home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integrity-service/target/bitrepository-integrity-service-1.7-SNAPSHOT]
[INFO] Processing war project
[INFO] Copying webapp resources [/home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integrity-service/src/main/webapp]
[INFO] Webapp assembled in [561 msecs]
[INFO] Building war: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integrity-service/target/bitrepository-integrity-service-1.7-SNAPSHOT.war
[INFO]
[INFO] --- maven-jar-plugin:2.4:test-jar (default) @ bitrepository-integrity-service ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integrity-service/target/bitrepository-integrity-service-1.7-SNAPSHOT-tests.jar
[INFO]
[INFO] --- maven-source-plugin:2.2.1:jar-no-fork (attach-sources-no-fork) @ bitrepository-integrity-service ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integrity-service/target/bitrepository-integrity-service-1.7-SNAPSHOT-sources.jar
[INFO]
[INFO] --- maven-assembly-plugin:2.4:single (distribution) @ bitrepository-integrity-service ---
[INFO] Reading assembly descriptor: src/main/assembly/assembly.xml
[JENKINS] Archiving disabled
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integrity-service/target/bitrepository-integrity-service-1.7-SNAPSHOT-distribution.tar.gz
[INFO]
[INFO] --- maven-install-plugin:2.5.1:install (default-install) @ bitrepository-integrity-service ---
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integrity-service/target/bitrepository-integrity-service-1.7-SNAPSHOT.war to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integrity-service/1.7-SNAPSHOT/bitrepository-integrity-service-1.7-SNAPSHOT.war
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integrity-service/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integrity-service/1.7-SNAPSHOT/bitrepository-integrity-service-1.7-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integrity-service/target/bitrepository-integrity-service-1.7-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integrity-service/1.7-SNAPSHOT/bitrepository-integrity-service-1.7-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integrity-service/target/bitrepository-integrity-service-1.7-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integrity-service/1.7-SNAPSHOT/bitrepository-integrity-service-1.7-SNAPSHOT-sources.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integrity-service/target/bitrepository-integrity-service-1.7-SNAPSHOT-distribution.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integrity-service/1.7-SNAPSHOT/bitrepository-integrity-service-1.7-SNAPSHOT-distribution.tar.gz
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Alarm Service 1.7-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-alarm-service ---
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ bitrepository-alarm-service ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 5 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ bitrepository-alarm-service ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 26 source files to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-alarm-service/target/classes
[INFO]
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ bitrepository-alarm-service ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ bitrepository-alarm-service ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 6 source files to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-alarm-service/target/test-classes
[INFO]
[INFO] --- maven-surefire-plugin:2.17:test (default-test) @ bitrepository-alarm-service ---
[INFO] Surefire report directory: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-alarm-service/target/surefire-reports
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running TestSuite
Configuring TestNG with: TestNG652Configurator
Starting test project Alarm Service Test
Suite: Surefire suite
Starting testcase AlarmDatabaseExtractionModelTest
Test starting: alarmExceptionTest
Description: Test the AlarmDatabaseExtractionModel class
Step: Define constants etc.
Step: Create an empty model
Step: Test the AlarmCode
Step: Test the ascending
Step: Test the ComponentID
Step: Test the EndDate
Step: Test the FileID
Step: Test the MaxCount
Step: Test the StartDate
Step: Test the CollectionID
Test success: alarmExceptionTest
Starting testcase AlarmHandlerTest
Test starting: alarmMediatorTest
Description: Test the mediator handling of alarm messages.
Step: Setup mediator and create alarm handler.
Step: Try giving it a non-alarm message
02:24:01.215 WARN o.b.alarm.handling.AlarmMediator - Recieved unexpected message: 'org.bitrepository.bitrepositorymessages.Message@11392934[correlationID=<null>, collectionID=<null>, destination=<null>, replyTo=<null>, from=<null>, to=<null>, version=<null>, minVersion=<null>]'
Step: Giv the mediator an AlarmMessage
Step: Close the mediator.
Test success: alarmMediatorTest
Starting testcase AlarmDatabaseTest
Test starting: AlarmDatabaseExtractionTest
Description: Testing the connection to the alarm 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: Populate the database with two alarms.
Step: Try to extract all the data from the database.
Step: Try to extract the alarms for component 1.
Step: Try to extract the alarms for component 2.
Step: Try to extract the alarms for the alarm code 'COMPONENT_FAILURE'.
Step: Try to extract the alarms for the alarm code 'CHECKSUM_ALARM'.
Step: Try to extract the new alarm.
Step: Try to extract the old alarm.
Step: Try to extract the alarms for the file id.
Step: Try to extract the alarms for the collection id.
Step: Try to extract the oldest alarm from the database.
Step: Try to extract the newest alarm from the database.
Test success: AlarmDatabaseExtractionTest
Test starting: AlarmDatabaseLargeIngestionTest
Description: Testing the ingestion of a large texts into the database
Step: Setup and create alarm
Step: Insert the data into the database
Test success: AlarmDatabaseLargeIngestionTest
Step: Cleanup after test.
Starting testcase AlarmExceptionTest
Test starting: alarmExceptionTest
Description: Tests that AlarmExceptions can be thrown.
Test success: alarmExceptionTest
Finished testcase
Finished suite
Finished project
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 17.886 sec - in TestSuite
Results :
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0
[JENKINS] Recording test results
[INFO]
[INFO] --- maven-war-plugin:2.4:war (default-war) @ bitrepository-alarm-service ---
[INFO] Packaging webapp
[INFO] Assembling webapp [bitrepository-alarm-service] in [/home/cibuild01/workspace/Bitrepository-sonar/bitrepository-alarm-service/target/bitrepository-alarm-service-1.7-SNAPSHOT]
[INFO] Processing war project
[INFO] Copying webapp resources [/home/cibuild01/workspace/Bitrepository-sonar/bitrepository-alarm-service/src/main/webapp]
[INFO] Webapp assembled in [97 msecs]
[INFO] Building war: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-alarm-service/target/bitrepository-alarm-service-1.7-SNAPSHOT.war
[INFO]
[INFO] --- maven-jar-plugin:2.4:test-jar (default) @ bitrepository-alarm-service ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-alarm-service/target/bitrepository-alarm-service-1.7-SNAPSHOT-tests.jar
[INFO]
[INFO] --- maven-source-plugin:2.2.1:jar-no-fork (attach-sources-no-fork) @ bitrepository-alarm-service ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-alarm-service/target/bitrepository-alarm-service-1.7-SNAPSHOT-sources.jar
[INFO]
[INFO] --- maven-assembly-plugin:2.4:single (distribution) @ bitrepository-alarm-service ---
[INFO] Reading assembly descriptor: src/main/assembly/assembly.xml
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-alarm-service/target/bitrepository-alarm-service-1.7-SNAPSHOT-distribution.tar.gz
[INFO]
[INFO] --- maven-install-plugin:2.5.1:install (default-install) @ bitrepository-alarm-service ---
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-alarm-service/target/bitrepository-alarm-service-1.7-SNAPSHOT.war to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-alarm-service/1.7-SNAPSHOT/bitrepository-alarm-service-1.7-SNAPSHOT.war
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-alarm-service/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-alarm-service/1.7-SNAPSHOT/bitrepository-alarm-service-1.7-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-alarm-service/target/bitrepository-alarm-service-1.7-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-alarm-service/1.7-SNAPSHOT/bitrepository-alarm-service-1.7-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-alarm-service/target/bitrepository-alarm-service-1.7-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-alarm-service/1.7-SNAPSHOT/bitrepository-alarm-service-1.7-SNAPSHOT-sources.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-alarm-service/target/bitrepository-alarm-service-1.7-SNAPSHOT-distribution.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-alarm-service/1.7-SNAPSHOT/bitrepository-alarm-service-1.7-SNAPSHOT-distribution.tar.gz
[JENKINS] Archiving disabled
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Audit Trail Service 1.7-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-audit-trail-service ---
[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 AuditCollectorTest
Test starting: auditCollectorIntervalTest
Description: Test that the collector calls the AuditClient at the correct intervals.
02:24:24.830 WARN o.b.a.collector.IncrementalCollector - Received bad collection id! Expected 'TwoPillarCollection', but got 'dummy-collection'.
02:24:25.845 WARN o.b.a.collector.IncrementalCollector - Received bad collection id! Expected 'TwoPillarCollection', but got 'dummy-collection'.
Test success: auditCollectorIntervalTest
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:24:30.090 WARN o.b.service.database.DatabaseUtils - Migrating AuditServiceDB from version 2 to 3.
02:24:31.837 WARN o.b.service.database.DatabaseUtils - Migrating AuditServiceDB from version 3 to 4.
02:24:32.164 WARN o.b.service.database.DatabaseUtils - Migrating AuditServiceDB from version 4 to 5.
Test success: testMigratingAuditServiceDatabase
Starting testcase AuditPreservationEventHandlerTest
Test starting: auditPreservationEventHandlerTest
Description: Test the handling of the audit trail event handler.
Step: Setup
Step: Test the handling of another complete event.
Test success: auditPreservationEventHandlerTest
Starting testcase IncrementalCollectorTest
Test starting: collectionIDFailureTest
Description: Tests what happens when a wrong collection id is received.
Step:
Step: Start a collection with two contributors
Step: Send an auditTrail result from contributor 1 with a wrong collection id.
02:24:33.155 WARN o.b.a.collector.IncrementalCollector - Received bad collection id! Expected 'dummy-collection', but got 'FalseCollection1454030673036'.
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:24:33.298 WARN o.b.a.collector.IncrementalCollector - Event: null: null: COMPONENT_FAILED: ContributorID Contributor1 ResponseCode: REQUEST_NOT_SUPPORTED
02:24:33.302 WARN o.b.a.collector.IncrementalCollector - Event: null: null: FAILED: ,
02:24:33.306 ERROR o.b.a.collector.IncrementalCollector - Problem in collecting audittrails, collection will not be complete for collection 'dummy-collection'
org.bitrepository.client.exceptions.NegativeResponseException:
at org.bitrepository.access.getaudittrails.BlockingAuditTrailClient.getAuditTrails(BlockingAuditTrailClient.java:65) ~[bitrepository-client-1.7-SNAPSHOT.jar:1.7-SNAPSHOT]
at org.bitrepository.audittrails.collector.IncrementalCollector.collect(IncrementalCollector.java:137) [classes/:na]
at org.bitrepository.audittrails.collector.IncrementalCollector.performCollection(IncrementalCollector.java:114) [classes/:na]
at org.bitrepository.audittrails.collector.IncrementalCollectorTest$CollectionRunner.run(IncrementalCollectorTest.java:288) [test-classes/:na]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_11]
Step: Send another audit trail result from contributor 2 with PartialResults set to false
Test success: contributorFailureTest
Test starting: multipleIncrementTest
Description: Verifies the behaviour in the case where the adit trails needs to be reteived in multiple requests because of MaxNumberOfResults limits.
Step: Start a collection with two contributors
Step: Send a audit trail result from contributor 1 and 2 with the PartialResults boolean set to true
Step: Send another audit trail result from the contributors, now with PartialResults set to false
Test success: multipleIncrementTest
Test starting: singleIncrementTest
Description: Verifies the behaviour in the simplest case with just one result set
Step: Start a collection with two contributors
Step: Send a audit trail result from contributor 1
Step: Send a audit trail result from contributor 2
Test success: singleIncrementTest
Starting testcase AuditDatabaseTest
Test starting: AuditDatabaseExtractionTest
Description: Testing the connection to the audit trail service database especially with regards to extracting the data from it.
Step: Setup the variables and constants.
Step: Adds the variables to the settings and instantaites the database cache
Step: Validate that the database is empty and then populate it.
Step: Extract the audit trails
Step: Test the extraction of FileID
Step: Test the extraction of CollectionID
Step: Perform extraction based on the component id.
Step: Perform extraction based on the sequence number restriction
Step: Perform extraction based on actor id restriction.
Step: Perform extraction based on operation restriction.
Step: Perform extraction based on date restriction.
Step: Perform extraction based on fingerprint restriction.
Step: Perform extraction based on operationID restriction.
Test success: AuditDatabaseExtractionTest
Test starting: AuditDatabaseGoodIngestTest
Description: Testing good case ingest of audittrails into the database
Step: Adds the variables to the settings and instantaites the database cache
Step: Build test data
Test success: AuditDatabaseGoodIngestTest
Test starting: AuditDatabaseIngestTest
Description: Testing ingest of audittrails into the database
Step: Adds the variables to the settings and instantaites the database cache
Step: Test ingesting with all data
Step: Test ingesting with no timestamp
Step: Test ingesting with no file action
Step: Test ingesting with no actor
Step: Test ingesting with no audit info
Step: Test ingesting with no file id
Step: Test ingesting with no info
Step: Test ingesting with no component id
Step: Test ingesting with no sequence number
Step: Test ingest with very long auditInfo (255+)
Step: Test ingest with very long info (255+)
Test success: AuditDatabaseIngestTest
Test starting: AuditDatabasePreservationTest
Description: Tests the functions related to the preservation of the database.
Step: Adds the variables to the settings and instantaites the database cache
Step: Validate the preservation sequence number
Step: Validate the insertion of the preservation sequence number
Test success: AuditDatabasePreservationTest
Starting testcase 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
Finished testcase
Finished suite
Finished project
Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 40.015 sec - in TestSuite
Results :
Tests run: 12, Failures: 0, Errors: 0, Skipped: 0
[JENKINS] Recording test results
[INFO]
[INFO] --- maven-war-plugin:2.4:war (default-war) @ bitrepository-audit-trail-service ---
[INFO] Packaging webapp
[INFO] Assembling webapp [bitrepository-audit-trail-service] in [/home/cibuild01/workspace/Bitrepository-sonar/bitrepository-audit-trail-service/target/bitrepository-audit-trail-service-1.7-SNAPSHOT]
[INFO] Processing war project
[INFO] Copying webapp resources [/home/cibuild01/workspace/Bitrepository-sonar/bitrepository-audit-trail-service/src/main/webapp]
[INFO] Webapp assembled in [236 msecs]
[INFO] Building war: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-audit-trail-service/target/bitrepository-audit-trail-service-1.7-SNAPSHOT.war
[INFO]
[INFO] --- maven-jar-plugin:2.4:test-jar (default) @ bitrepository-audit-trail-service ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-audit-trail-service/target/bitrepository-audit-trail-service-1.7-SNAPSHOT-tests.jar
[INFO]
[INFO] --- maven-source-plugin:2.2.1:jar-no-fork (attach-sources-no-fork) @ bitrepository-audit-trail-service ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-audit-trail-service/target/bitrepository-audit-trail-service-1.7-SNAPSHOT-sources.jar
[INFO]
[INFO] --- maven-assembly-plugin:2.4:single (distribution) @ bitrepository-audit-trail-service ---
[INFO] Reading assembly descriptor: src/main/assembly/assembly.xml
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-audit-trail-service/target/bitrepository-audit-trail-service-1.7-SNAPSHOT-distribution.tar.gz
[INFO]
[INFO] --- maven-install-plugin:2.5.1:install (default-install) @ bitrepository-audit-trail-service ---
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-audit-trail-service/target/bitrepository-audit-trail-service-1.7-SNAPSHOT.war to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-audit-trail-service/1.7-SNAPSHOT/bitrepository-audit-trail-service-1.7-SNAPSHOT.war
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-audit-trail-service/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-audit-trail-service/1.7-SNAPSHOT/bitrepository-audit-trail-service-1.7-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-audit-trail-service/target/bitrepository-audit-trail-service-1.7-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-audit-trail-service/1.7-SNAPSHOT/bitrepository-audit-trail-service-1.7-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-audit-trail-service/target/bitrepository-audit-trail-service-1.7-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-audit-trail-service/1.7-SNAPSHOT/bitrepository-audit-trail-service-1.7-SNAPSHOT-sources.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-audit-trail-service/target/bitrepository-audit-trail-service-1.7-SNAPSHOT-distribution.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-audit-trail-service/1.7-SNAPSHOT/bitrepository-audit-trail-service-1.7-SNAPSHOT-distribution.tar.gz
[JENKINS] Archiving disabled
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Reference Pillar 1.7-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-reference-pillar ---
[INFO]
[INFO] --- maven-dependency-plugin:2.8:unpack-dependencies (unpack-shared-sqlscripts) @ bitrepository-reference-pillar ---
[INFO] Unpacking /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-service/target/bitrepository-service-1.7-SNAPSHOT.jar to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/classes with includes "**/*.sql" and excludes ""
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ bitrepository-reference-pillar ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 10 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ bitrepository-reference-pillar ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 44 source files to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/classes
[INFO]
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ bitrepository-reference-pillar ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 12 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ bitrepository-reference-pillar ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 70 source files to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/test-classes
[INFO]
[INFO] --- maven-surefire-plugin:2.17:test (default-test) @ bitrepository-reference-pillar ---
[INFO] Surefire report directory: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/surefire-reports
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running TestSuite
Configuring TestNG with: TestNG652Configurator
Starting test project Reference Pillar Test
Suite: Surefire suite
Starting testcase ArchiveDirectoryTest
Test starting: testArchiveDirectoryExistingFile
Description: Test the ArchiveDirectory when the file exists
Step: Setup
Step: Validate the existence of the file
Step: Delete the file.
Test success: testArchiveDirectoryExistingFile
Test starting: testArchiveDirectoryMissingFile
Description: Test the ArchiveDirectory when the file is missing.
Step: Setup
Step: Validate the existence of the file
Step: Delete the file.
Test success: testArchiveDirectoryMissingFile
Test starting: testArchiveDirectoryMoveFileToArchive
Description: Testing the error scenarios when moving a file from tmp to archive for the ArchiveDirectory.
Step: Setup
Step: Moving file from tmp to archive
Step: Create file in both tmp and archive.
Step: Moving file from tmp to archive
Step: Remove the file from archive and try again
Test success: testArchiveDirectoryMoveFileToArchive
Test starting: testArchiveDirectoryNewFile
Description: Testing the ArchiveDirectory handling of a new file.
Step: Setup
Step: Retrieve tmp file
Step: Request a new file for the tmp dir
Step: Retrieve tmp file
Step: Request another new file with the same name
Step: Move the file from tmp to archive
Test success: testArchiveDirectoryNewFile
Test starting: testArchiveDirectoryRemoveFile
Description: Testing the error scenarios when removing files from the archive.
Step: Setup
Step: Remove nonexisting file from archive
Step: Remove nonexisting file from tmp
Step: Create file in both tmp, archive and retain directories.
Step: Remove the file from archive and tmp
Test success: testArchiveDirectoryRemoveFile
Starting testcase 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 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:25:17.095 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@6b5966e1[correlationID=e171911b-fcf5-402d-9409-2bc6dbe75bec, 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@65e61854[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseIdentification, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@1568159[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:25:18.955 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@52eacb4b[correlationID=2083e5d8-670e-4cc1-bd12-915542b1e62d, 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@5528a42c[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@2a551a63[fileID=DefaultFilebadCaseOperationNoFile, allFileIDs=<null>], resultingFileIDs=<null>, partialResult=<null>]
Step: Retrieve the FinalResponse for the GetFileIDs request
Test success: badCaseOperationNoFile
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@19542407[correlationID=85c98821-9fd4-417f-a357-7b5069660c60, 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@6f95cd51[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], pillarID=Pillar-goodCaseIdentification, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@c7a977f[fileID=DefaultFilegoodCaseIdentification, allFileIDs=<null>], timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@55caeb35[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:25:25.246 WARN o.b.pillar.MediatorTest$TestMediator - Unexpected exception caught.
java.lang.RuntimeException: I am supposed to throw a RuntimeException
at org.bitrepository.pillar.MediatorTest$ErroneousRequestHandler.processRequest(MediatorTest.java:122) ~[test-classes/:na]
at org.bitrepository.pillar.MediatorTest$ErroneousRequestHandler.processRequest(MediatorTest.java:113) ~[test-classes/:na]
at org.bitrepository.pillar.messagehandler.PillarMediator.handleRequest(PillarMediator.java:80) ~[classes/:na]
at org.bitrepository.service.contributor.AbstractContributorMediator$GeneralRequestHandler.onMessage(AbstractContributorMediator.java:101) [bitrepository-service-1.7-SNAPSHOT.jar:1.7-SNAPSHOT]
at org.bitrepository.protocol.messagebus.SimpleMessageBus.lambda$sendMessage$0(SimpleMessageBus.java:73) [bitrepository-core-1.7-SNAPSHOT.jar:1.7-SNAPSHOT]
at org.bitrepository.protocol.messagebus.SimpleMessageBus$$Lambda$1/1533547487.accept(Unknown Source) [bitrepository-core-1.7-SNAPSHOT.jar:1.7-SNAPSHOT]
at java.lang.Iterable.forEach(Iterable.java:75) [na:1.8.0_11]
at org.bitrepository.protocol.messagebus.SimpleMessageBus.sendMessage(SimpleMessageBus.java:73) [bitrepository-core-1.7-SNAPSHOT.jar:1.7-SNAPSHOT]
at org.bitrepository.pillar.MediatorTest.testMediatorRuntimeExceptionHandling(MediatorTest.java:84) [test-classes/:na]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_11]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_11]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_11]
at java.lang.reflect.Method.invoke(Method.java:483) ~[na:1.8.0_11]
at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84) [testng-6.8.8.jar:na]
at org.testng.internal.Invoker.invokeMethod(Invoker.java:714) [testng-6.8.8.jar:na]
at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901) [testng-6.8.8.jar:na]
at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231) [testng-6.8.8.jar:na]
at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127) [testng-6.8.8.jar:na]
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111) [testng-6.8.8.jar:na]
at org.testng.TestRunner.privateRun(TestRunner.java:767) [testng-6.8.8.jar:na]
at org.testng.TestRunner.run(TestRunner.java:617) [testng-6.8.8.jar:na]
at org.testng.SuiteRunner.runTest(SuiteRunner.java:348) [testng-6.8.8.jar:na]
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:343) [testng-6.8.8.jar:na]
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:305) [testng-6.8.8.jar:na]
at org.testng.SuiteRunner.run(SuiteRunner.java:254) [testng-6.8.8.jar:na]
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) [testng-6.8.8.jar:na]
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) [testng-6.8.8.jar:na]
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1224) [testng-6.8.8.jar:na]
at org.testng.TestNG.runSuitesLocally(TestNG.java:1149) [testng-6.8.8.jar:na]
at org.testng.TestNG.run(TestNG.java:1057) [testng-6.8.8.jar:na]
at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:115) [surefire-testng-2.17.jar:2.17]
at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:204) [surefire-testng-2.17.jar:2.17]
at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:107) [surefire-testng-2.17.jar:2.17]
at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:112) [surefire-testng-2.17.jar:2.17]
at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) [surefire-booter-2.17.jar:2.17]
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) [surefire-booter-2.17.jar:2.17]
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) [surefire-booter-2.17.jar:2.17]
Result: Received message on TEST-TOPIC-testMediatorRuntimeExceptionHandling-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetStatusResponse@6edaa77a[correlationID=044c6e1f-89a7-4697-87cc-bebc7faad5e2, 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@1e63d216[responseCode=FAILURE, responseText=java.lang.RuntimeException: I am supposed to throw a RuntimeException], contributor=TEST-TOPIC-cibuild01, timeToDeliver=<null>]
02:25:25.256 WARN o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@16c3ca31[origDateTime=2016-01-29T02:25:25.254+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@2d195ee4[correlationID=446aa75a-88b4-4652-903b-599c74568d60, 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@16c3ca31[origDateTime=2016-01-29T02:25:25.254+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
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@27a2a089[correlationID=41d5ea53-69c8-4132-8230-a845556aa752, 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@54657dd2[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@9fc9f91[correlationID=b9708df1-8611-4c82-a617-8658e58261c5, 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@1fac1d5c[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@7b306b9f[correlationID=293771f9-584a-4f21-badf-62b829d6927b, 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@142213d5[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:25:30.743 WARN o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@934b52f[origDateTime=2016-01-29T02:25:30.743+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@2630dbc4[correlationID=1fec323f-44fe-44b0-92ce-a02cb9bb8ff1, 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@934b52f[origDateTime=2016-01-29T02:25:30.743+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@7add838c[correlationID=802aeb30-28f1-4ec1-981c-3c38fb2e48fa, 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@3662bdff[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:25:31.221 WARN o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@1bb15351[origDateTime=2016-01-29T02:25:31.221+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@4fa822ad[correlationID=a2824758-1922-4225-a949-1e09ac29ee35, 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@1bb15351[origDateTime=2016-01-29T02:25:31.221+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:25:31.615 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@57545c3f[correlationID=a7a68a9c-d97d-4d1e-afe4-060b5ddd618a, 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@326e0b8e[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:25:31.617 WARN o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@36baa049[origDateTime=2016-01-29T02:25:31.617+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@41184371[correlationID=886a0e47-4aa6-4595-ab96-9c2c4e7f4647, 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@36baa049[origDateTime=2016-01-29T02:25:31.617+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@441fbe89[correlationID=220baccd-7d08-4250-9c17-825ee2815755, 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@6088451e[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], fileID=DefaultFile, pillarID=Pillar-goodCaseIdentification, pillarChecksumSpec=<null>, timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@45ab3bdd[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@39de9bda[correlationID=07d847bf-338f-4826-bbcc-4339ea0af96b, 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@47148f3f[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@6dee8ae6[correlationID=07d847bf-338f-4826-bbcc-4339ea0af96b, 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@5af64ce0[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@7f4596d0[correlationID=997acbc1-cb80-41f3-8ad3-9cb123c2c7b7, 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@6002e944[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@588545ac[correlationID=997acbc1-cb80-41f3-8ad3-9cb123c2c7b7, 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@2b08772d[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@78a8978a[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@f171912[checksumType=HMAC_SHA512, checksumSalt={97,98}, otherChecksumType=<null>], checksumValue={18,52,-52,-52,-52,-52,67,34}, calculationTimestamp=2016-01-29T02:25:34.788+01:00], checksumDataForNewFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@7d4d8579[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@159424e2[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2016-01-29T02:25:34.789+01:00]]
Step: Retrieve the ProgressResponse for the GetFileIDs request
Step: Retrieve the FinalResponse for the ReplaceFile request
Test success: goodCaseOperationWithChecksumsReturn
Starting testcase ChecksumDatabaseMigrationTest
Test starting: testMigratingDatabaseChecksumsTable
Description: Tests that the checksums table can be migrated from version 1 to 2, e.g. getting the column collectionid, which should be set to the default in settings.
Step: Validate setup
Step: Ingest a entry to the database without the collection id
Step: Perform migration
02:25:40.856 WARN o.b.service.database.DatabaseUtils - Migrating the checksums table from version 1 to 2 in the ChecksumDatabase.
02:25:41.082 WARN o.b.service.database.DatabaseUtils - Migrating ChecksumDB from version 2 to 3.
Step: Validate the entry
Test success: testMigratingDatabaseChecksumsTable
Starting testcase ChecksumDatabaseTest
Test starting: testChecksumDatabaseExtraction
Description: Test the extraction of data from the checksum database.
Step: Check whether the default entry exists.
Step: Extract calculation date
Step: Extract the checksum
Step: Extract the whole entry
Step: Extract all entries
Test success: testChecksumDatabaseExtraction
Test starting: testDeletion
Description: Test that data can be deleted from the database.
Step: Check whether the default entry exists.
Step: Remove the default entry
Test success: testDeletion
Test starting: testExtractionOfMissingData
Description: Test the handling of bad arguments.
Step: Try to get the date of a wrong file id.
Step: Try to get the date of a wrong file id.
Step: Try to remove a bad file id
Test success: testExtractionOfMissingData
Test starting: testGetFileIDsRestrictions
Description: Tests the restrictions on the GetFileIDs call to the database.
Step: Instantiate database with appropriate data.
Step: Test with no time restrictions and 10000 max_results
Step: Test with minimum-date earlier than first file
Step: Test with maximum-date earlier than first file
Step: Test with minimum-date set to later than second file.
Step: Test with maximum-date set to later than second file.
Step: Test with minimum-date set to middle date.
Step: Test with maximum-date set to middle date.
Step: Test with both minimum-date and maximum-date set to middle date.
Step: Test the first file-id, with no other restrictions
Step: Test the second file-id, with no other restrictions
Step: Test the date for the first file-id, while requesting the second file-id
Test success: testGetFileIDsRestrictions
Test starting: testReplacingExistingEntry
Description: Test that an entry can be replaced by another in the database.
Step: Check whether the default entry exists.
Step: Replace the checksum and date
Test success: testReplacingExistingEntry
Test starting: testSpecifiedEntryExtraction
Description: Test that specific entries can be extracted. Has two entries in the database: one for the current timestamp and one for the epoch.
Step: Instantiate database with appropriate data.
Step: Extract with out restrictions
Step: Extract with a maximum of 1 entry
Step: Extract all dates older than this tests instantiation
Step: Extract all dates newer than this tests instantiation
Step: Extract all dates older than the newest instance
Step: Extract all dates newer than the oldest instantiation
Test success: testSpecifiedEntryExtraction
Starting testcase FullPillarModelTest
Test starting: testPillarModelBasicFunctionality
Description: Test the basic functions of the full reference pillar model.
Step: Check the pillar id in the pillar model
Step: Ask whether it can handle a file of size 0
Step: Ask whether it can handle a file of maximum size
Step: Check the ChecksumPillarSpec
Test success: testPillarModelBasicFunctionality
Test starting: testPillarModelHasFile
Description: Test that the file exists, when placed in the archive and cache
Step: Setup
Step: Check whether file exists and retrieve it.
Step: Verify that no exceptions are thrown when verifying file existance.
Step: Check retrieval of non-default checksum
Test success: testPillarModelHasFile
Test starting: testPillarModelNoFile
Description: Test that the file exists, when placed in the archive and cache
Step: Setup
Step: Check whether file exists and try to retrieve it.
Step: Verify that anexceptions are thrown when verifying file existance.
02:26:13.634 WARN o.b.pillar.store.FileStorageModel - The file 'DefaultFile' has been requested, but we do not have that file in collection 'TwoPillarCollection'!
Test success: testPillarModelNoFile
Starting testcase GetAuditTrailsTest
Added fixture: Initialize a new Pillar.
Test starting: checksumPillarGetAuditTrailsMaximumNumberOfResults
Description: Tests the GetAuditTrails functionality of the pillar for the successful scenario, where a limited number of audit trails are requested.
Step: Set up constants and variables.
Step: Send the request for the limited amount of audit trails to the pillar.
Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsMaximumNumberOfResults-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsProgressResponse@6a3a56de[correlationID=14767aa8-2dc9-4d0a-b4fc-911ac306e66a, 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@2ed84be9[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@7cf66cf9[correlationID=14767aa8-2dc9-4d0a-b4fc-911ac306e66a, 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@38f63756[responseCode=OPERATION_COMPLETED, responseText=<null>], contributor=Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@3d7caf9c[resultAddress=<null>, auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@4e26040f[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@1782896[sequenceNumber=1, fileID=fileID1454030774246, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=CHECKSUM_CALCULATED, actionDateTime=2016-01-29T02:26:14.246+01:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@8bde368[sequenceNumber=2, fileID=fileID1454030774246, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=DELETE_FILE, actionDateTime=2016-01-29T02:26:14.247+01:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@5065bdac[sequenceNumber=3, fileID=fileID1454030774246, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=FAILURE, actionDateTime=2016-01-29T02:26:14.247+01:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@2e9dcdd3[sequenceNumber=4, fileID=fileID1454030774246, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=FILE_MOVED, actionDateTime=2016-01-29T02:26:14.247+01:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@6e617c0e[sequenceNumber=5, fileID=fileID1454030774246, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=GET_CHECKSUMS, actionDateTime=2016-01-29T02:26:14.247+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@60b4c754[correlationID=b22f6d32-6cda-4b2e-80ac-b988b452e285, 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@2c846d55[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@67689c81[correlationID=b22f6d32-6cda-4b2e-80ac-b988b452e285, 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@21a0795f[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@2ec156fb[correlationID=b22f6d32-6cda-4b2e-80ac-b988b452e285, 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@56d742ad[responseCode=OPERATION_COMPLETED, responseText=<null>], contributor=Pillar-checksumPillarGetAuditTrailsSpecificRequests, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@75784062[resultAddress=<null>, auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@5730b513[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@73e25780[sequenceNumber=1, fileID=fileID1454030774582, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=OTHER, actionDateTime=2016-01-29T02:26:14.582+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@1f4cb17b[correlationID=b22f6d32-6cda-4b2e-80ac-b988b452e285, 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@280099a0[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@7aca299e[correlationID=b22f6d32-6cda-4b2e-80ac-b988b452e285, 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@1bf52f10[responseCode=OPERATION_COMPLETED, responseText=<null>], contributor=Pillar-checksumPillarGetAuditTrailsSpecificRequests, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@6148827c[resultAddress=<null>, auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@4da9da6c[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@73e25780[sequenceNumber=1, fileID=fileID1454030774582, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=OTHER, actionDateTime=2016-01-29T02:26:14.582+01:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@66048c9e[sequenceNumber=2, fileID=notThisFile, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=UnknownActor, actionOnFile=FAILURE, actionDateTime=2016-01-29T02:26:14.582+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@1820f274[correlationID=bb7c3c0b-7f43-40da-8fc9-74ad11ebf1a8, 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@221cdd87[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@4d66cb[correlationID=bb7c3c0b-7f43-40da-8fc9-74ad11ebf1a8, 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@7c79f2cf[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@63551c66[correlationID=bb7c3c0b-7f43-40da-8fc9-74ad11ebf1a8, 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@2761156e[responseCode=OPERATION_COMPLETED, responseText=<null>], contributor=Pillar-checksumPillarGetAuditTrailsSuccessful, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@4cf15477[resultAddress=<null>, auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@7fad28ac[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@3450bd13[sequenceNumber=1, fileID=fileid, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=actor, actionOnFile=OTHER, actionDateTime=2016-01-29T02:26:14.715+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 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@67e1a5fd[correlationID=eba12064-ce96-4227-bd58-4d552c2da060, 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@4b9dc62f[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@6cb3463b[fileID=DefaultFilebadCaseIdentification, allFileIDs=<null>], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2f9236d8[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:26:16.361 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@634d3439[correlationID=ca4e7636-50a3-4f1e-962f-b7f60af5ebc5, 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@44e0c3d[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@71891d6b[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], resultingChecksums=<null>, partialResult=<null>]
02:26:16.395 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@2259d54f[correlationID=ca4e7636-50a3-4f1e-962f-b7f60af5ebc5, 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@1b82f62a[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@71891d6b[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], resultingChecksums=<null>, partialResult=<null>]
Step: Retrieve the FinalResponse for the GetChecksums request
Test success: badCaseOperationNoFile
Result: The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@2259d54f[correlationID=ca4e7636-50a3-4f1e-962f-b7f60af5ebc5, 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@1b82f62a[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@71891d6b[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], resultingChecksums=<null>, partialResult=<null>]
02:26:17.414 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@2259d54f[correlationID=ca4e7636-50a3-4f1e-962f-b7f60af5ebc5, 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@1b82f62a[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@71891d6b[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], resultingChecksums=<null>, partialResult=<null>]
Added fixture: Initialize a new Pillar.
Test starting: goodCaseIdentification
Description: Tests the identification for a GetChecksums operation on the pillar for the successful scenario.
Step: Set up constants and variables.
Step: Setup for having the file and delivering pillar id
Step: Create and send the identify request message.
Result: Received message on TEST-TOPIC-goodCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsResponse@53b7f08[correlationID=5f4da59b-ae1e-4191-af26-19bfccd3ee25, 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@24536f07[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@32430075[fileID=DefaultFilegoodCaseIdentification, allFileIDs=<null>], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1a45e29f[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], pillarID=Pillar-goodCaseIdentification, pillarChecksumSpec=<null>, timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@44580de0[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@7bb3294c[correlationID=f6b3cbd0-9990-45bb-a07a-c64e1b56f883, 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@f391e52[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to calculate checksums.], pillarID=Pillar-goodCaseOperationAllFiles, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@5857d723[fileID=<null>, allFileIDs=true], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@4b518645[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], resultAddress=<null>]
Result: Received message on TEST-TOPIC-goodCaseOperationAllFiles-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@4fea9f19[correlationID=f6b3cbd0-9990-45bb-a07a-c64e1b56f883, 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@37a14aa1[responseCode=OPERATION_COMPLETED, responseText=<null>], pillarID=Pillar-goodCaseOperationAllFiles, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@4b518645[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], resultingChecksums=org.bitrepository.bitrepositoryelements.ResultingChecksums@6ac4f31d[resultAddress=<null>, checksumDataItems={org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@106f2425[fileID=DefaultFile, checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2016-01-29T02:26:19.152+01:00],org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@b666366[fileID=goodCaseOperationAllFiles-cibuild01--Test-File-1454030779141, 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@2d1f9ec3[correlationID=af7b9540-478c-4ea1-82af-fd47340987fc, 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@148f94dc[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to calculate checksums.], pillarID=Pillar-goodCaseOperationSingleFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@2f11d889[fileID=DefaultFilegoodCaseOperationSingleFile, allFileIDs=<null>], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@d1973e8[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], resultAddress=<null>]
Result: Received message on TEST-TOPIC-goodCaseOperationSingleFile-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@5ca10d0e[correlationID=af7b9540-478c-4ea1-82af-fd47340987fc, 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@34604b32[responseCode=OPERATION_COMPLETED, responseText=<null>], pillarID=Pillar-goodCaseOperationSingleFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@d1973e8[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], resultingChecksums=org.bitrepository.bitrepositoryelements.ResultingChecksums@159408a7[resultAddress=<null>, checksumDataItems={org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@5354bfce[fileID=DefaultFilegoodCaseOperationSingleFile, checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2016-01-29T02:26:19.618+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@b4c89b6[correlationID=f61102e7-57d4-45df-b9da-e35e7f8f9e01, 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@54f62ac6[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to calculate checksums.], pillarID=Pillar-testRestrictions, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@7be86438[fileID=<null>, allFileIDs=true], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@5fe4848[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], resultAddress=<null>]
Result: Received message on TEST-TOPIC-testRestrictions-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@6a906078[correlationID=f61102e7-57d4-45df-b9da-e35e7f8f9e01, 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@fd5c7f6[responseCode=OPERATION_COMPLETED, responseText=<null>], pillarID=Pillar-testRestrictions, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@5fe4848[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], resultingChecksums=org.bitrepository.bitrepositoryelements.ResultingChecksums@3724ab90[resultAddress=<null>, checksumDataItems={org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@40ef1934[fileID=DefaultFile, checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2016-01-29T02:26:19.952+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 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@281028ce[correlationID=267a2bd7-a1c5-4324-8623-9ff8e3d14b70, 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@46ef7340[responseCode=DUPLICATE_FILE_FAILURE, responseText=<null>], pillarID=Pillar-badCaseIdentification, fileID=DefaultFilebadCaseIdentification, pillarChecksumSpec=<null>, checksumDataForExistingFile=<null>, timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@75caecf7[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@7be85f15[correlationID=55e42ea9-9fbc-479e-a7d5-e38dc2eb54ba, 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@48619f15[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@1b897ffb[correlationID=d3f4ebc3-566b-4c90-ab66-8da2563dabd9, 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@2ec258f1[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:26:22.489 WARN o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@3074575a[origDateTime=2016-01-29T02:26:22.489+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@7e4bbda4[correlationID=5ca78d2b-8de3-4c62-9c1c-c1bd5e6ef4dc, 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@3074575a[origDateTime=2016-01-29T02:26:22.489+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@2c56e044[correlationID=d60d6b3a-1687-46a9-bee7-397f899ba3d6, 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@d970881[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], pillarID=Pillar-goodCaseIdentification, fileID=DefaultFilegoodCaseIdentification, pillarChecksumSpec=<null>, checksumDataForExistingFile=<null>, timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@153cf928[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@2898c70d[correlationID=c841123d-33a0-4a99-ba24-519b7badb063, 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@ec67be1[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@347f0950[correlationID=c841123d-33a0-4a99-ba24-519b7badb063, 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@5ab1107d[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@671561b9[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@3aebdb4[checksumType=MD5, checksumSalt=<null>, otherChecksumType=<null>], checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2016-01-29T02:26:24.557+01:00], checksumDataForExistingFile=<null>]
Step: Retrieve the ProgressResponse for the GetFileIDs request
Step: Retrieve the FinalResponse for the PutFile request
Test success: goodCaseOperationWithChecksumReturn
Starting testcase ReferenceArchiveTest
Added fixture: Initialize the Reference pillar cache with an empty file in default collection TwoPillarCollection
Test starting: testReferenceArchive
Description: Test the ReferenceArchive.
Step: Setup
Step: test 'hasFile'
Step: Test 'getFile'
Step: Test getAllFileIDs
Step: Test 'getFileAsInputstream'
Step: Delete, recreate and delete again
Step: Try to delete missing file.
Step: Replace a file, which does not exist in the filedir.
Step: Copy a file into the tmpDir and then use replace.
Step: Try performing the replace, when the file in the tempdir has been removed.
Test success: testReferenceArchive
Starting testcase 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@2ef5df8f[correlationID=cc652d04-3776-49da-84a4-5f5f238142f4, 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@708f238f[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@39bd07fe[correlationID=f89b003f-04e3-44fb-99b0-04b835225f64, 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@5ca896af[responseCode=EXISTING_FILE_CHECKSUM_FAILURE, responseText=No mandatory checksum for destructive operation was supplied.], pillarID=Pillar-badCaseOperationMissingVerification, fileID=DefaultFilebadCaseOperationMissingVerification, checksumDataForExistingFile=<null>]
02:26:27.278 WARN o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@324ee3ca[origDateTime=2016-01-29T02:26:27.276+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@639d808a[correlationID=3021fecf-c5ac-4679-9ee7-26536e20eb82, 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@324ee3ca[origDateTime=2016-01-29T02:26:27.276+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@b89cbf9[correlationID=9207916b-e422-464f-b121-bddf0613b1ec, 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@2f318251[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@5e352e3a[correlationID=9207916b-e422-464f-b121-bddf0613b1ec, 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@1b26f006[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@797dd7ef[correlationID=9207916b-e422-464f-b121-bddf0613b1ec, 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@ece7204[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@5e352e3a[correlationID=9207916b-e422-464f-b121-bddf0613b1ec, 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@1b26f006[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileID=DefaultFilebadCaseOperationNoFile, checksumDataForExistingFile=<null>]
org.bitrepository.bitrepositorymessages.DeleteFileFinalResponse@797dd7ef[correlationID=9207916b-e422-464f-b121-bddf0613b1ec, 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@ece7204[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileID=DefaultFilebadCaseOperationNoFile, checksumDataForExistingFile=<null>]
02:26:28.493 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.DeleteFileFinalResponse@5e352e3a[correlationID=9207916b-e422-464f-b121-bddf0613b1ec, 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@1b26f006[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileID=DefaultFilebadCaseOperationNoFile, checksumDataForExistingFile=<null>]
org.bitrepository.bitrepositorymessages.DeleteFileFinalResponse@797dd7ef[correlationID=9207916b-e422-464f-b121-bddf0613b1ec, 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@ece7204[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@2591477f[correlationID=324286fc-1406-4560-8df0-ef54581806a6, 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@761d3c20[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], fileID=DefaultFilegoodCaseIdentification, pillarID=Pillar-goodCaseIdentification, pillarChecksumSpec=<null>, timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@172f2717[timeMeasureUnit=MILLISECONDS, timeMeasureValue=1000]]
Step: Retrieve and validate the response getPillarID() the pillar.
Test success: goodCaseIdentification
Test starting: componentIDTest
Test success: componentIDTest
Test starting: getPillarCollectionsTest
Test success: getPillarCollectionsTest
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 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@2ae92511[correlationID=ae23cdec-ccd3-48ac-978b-986f5c8cdfee, 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@582ce329[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@7f9ebcfe[correlationID=2b2d0b0e-995c-4021-aaac-6afbb0b5b6f8, 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@3d577add[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], fileID=DefaultFilegoodCaseIdentification, pillarID=Pillar-goodCaseIdentification, timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@712adc04[timeMeasureUnit=MILLISECONDS, timeMeasureValue=1000]]
Step: Retrieve and validate the response getPillarID() the pillar.
Test success: goodCaseIdentification
Finished testcase
Finished suite
Finished project
Tests run: 57, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 81.97 sec - in TestSuite
Results :
Tests run: 57, Failures: 0, Errors: 0, Skipped: 0
[JENKINS] Recording test results
[INFO]
[INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ bitrepository-reference-pillar ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.7-SNAPSHOT.jar
[INFO]
[INFO] --- maven-jar-plugin:2.4:test-jar (default) @ bitrepository-reference-pillar ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.7-SNAPSHOT-tests.jar
[INFO]
[INFO] --- maven-source-plugin:2.2.1:jar-no-fork (attach-sources-no-fork) @ bitrepository-reference-pillar ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.7-SNAPSHOT-sources.jar
[INFO]
[INFO] --- maven-assembly-plugin:2.4:single (distribution) @ bitrepository-reference-pillar ---
[INFO] Reading assembly descriptor: src/main/assembly/assembly.xml
[INFO] Reading assembly descriptor: src/test/assembly/assembly.xml
[INFO] Reading assembly descriptor: src/main/assembly/deploy-assembly.xml
[INFO] Reading assembly descriptor: src/test/assembly/test-deploy-assembly.xml
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.7-SNAPSHOT-distribution.tar.gz
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.7-SNAPSHOT-acceptance-test.tar.gz
[WARNING] Entry: bitrepository-reference-pillar-1.7-SNAPSHOT/lib/bitrepository-reference-pillar-1.7-SNAPSHOT-tests.jar longer than 100 characters.
[WARNING] Resulting tar file can only be processed successfully by GNU compatible tar commands
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.7-SNAPSHOT-deploy.tar.gz
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.7-SNAPSHOT-acceptance-test-deploy.tar.gz
[INFO]
[INFO] --- maven-install-plugin:2.5.1:install (default-install) @ bitrepository-reference-pillar ---
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.7-SNAPSHOT.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.7-SNAPSHOT/bitrepository-reference-pillar-1.7-SNAPSHOT.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.7-SNAPSHOT/bitrepository-reference-pillar-1.7-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.7-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.7-SNAPSHOT/bitrepository-reference-pillar-1.7-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.7-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.7-SNAPSHOT/bitrepository-reference-pillar-1.7-SNAPSHOT-sources.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.7-SNAPSHOT-distribution.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.7-SNAPSHOT/bitrepository-reference-pillar-1.7-SNAPSHOT-distribution.tar.gz
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.7-SNAPSHOT-acceptance-test.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.7-SNAPSHOT/bitrepository-reference-pillar-1.7-SNAPSHOT-acceptance-test.tar.gz
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.7-SNAPSHOT-deploy.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.7-SNAPSHOT/bitrepository-reference-pillar-1.7-SNAPSHOT-deploy.tar.gz
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.7-SNAPSHOT-acceptance-test-deploy.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.7-SNAPSHOT/bitrepository-reference-pillar-1.7-SNAPSHOT-acceptance-test-deploy.tar.gz
[JENKINS] Archiving disabled
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Monitoring Service 1.7-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-monitoring-service ---
[INFO]
[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:26:46.971 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 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 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:26:49.647 WARN o.b.m.a.BasicMonitoringServiceAlerter - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@5d908d47[origDateTime=2016-01-29T02:26:49.639+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@79defdc[correlationID=0bc6e33f-b630-4ee3-9aa5-5d15d4dd03dc, 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@5d908d47[origDateTime=2016-01-29T02:26:49.639+01:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MonitorAlerterUnderTest, alarmText=The following components have become unresponsive: [TestMonitorService], fileID=<null>, collectionID=<null>]]
Test success: testMonitorAlerter
Starting testcase StatusCollectorTest
Test starting: testStatusCollector
Description: Tests the status collector.
Step: Setup
Step: Create the collector
Step: Start the collector
Step: wait 2 * the interval
Step: wait the interval + delay again
Test success: testStatusCollector
Finished testcase
Finished suite
Finished project
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 9.573 sec - in TestSuite
Results :
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0
[JENKINS] Recording test results
[INFO]
[INFO] --- maven-war-plugin:2.4:war (default-war) @ bitrepository-monitoring-service ---
[INFO] Packaging webapp
[INFO] Assembling webapp [bitrepository-monitoring-service] in [/home/cibuild01/workspace/Bitrepository-sonar/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.7-SNAPSHOT]
[INFO] Processing war project
[INFO] Copying webapp resources [/home/cibuild01/workspace/Bitrepository-sonar/bitrepository-monitoring-service/src/main/webapp]
[INFO] Webapp assembled in [317 msecs]
[INFO] Building war: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.7-SNAPSHOT.war
[INFO]
[INFO] --- maven-jar-plugin:2.4:test-jar (default) @ bitrepository-monitoring-service ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.7-SNAPSHOT-tests.jar
[INFO]
[INFO] --- maven-source-plugin:2.2.1:jar-no-fork (attach-sources-no-fork) @ bitrepository-monitoring-service ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.7-SNAPSHOT-sources.jar
[INFO]
[INFO] --- maven-assembly-plugin:2.4:single (distribution) @ bitrepository-monitoring-service ---
[INFO] Reading assembly descriptor: src/main/assembly/assembly.xml
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.7-SNAPSHOT-distribution.tar.gz
[INFO]
[INFO] --- maven-install-plugin:2.5.1:install (default-install) @ bitrepository-monitoring-service ---
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.7-SNAPSHOT.war to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-monitoring-service/1.7-SNAPSHOT/bitrepository-monitoring-service-1.7-SNAPSHOT.war
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-monitoring-service/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-monitoring-service/1.7-SNAPSHOT/bitrepository-monitoring-service-1.7-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.7-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-monitoring-service/1.7-SNAPSHOT/bitrepository-monitoring-service-1.7-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.7-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-monitoring-service/1.7-SNAPSHOT/bitrepository-monitoring-service-1.7-SNAPSHOT-sources.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.7-SNAPSHOT-distribution.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-monitoring-service/1.7-SNAPSHOT/bitrepository-monitoring-service-1.7-SNAPSHOT-distribution.tar.gz
[JENKINS] Archiving disabled
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Webclient 1.7-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-webclient ---
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ bitrepository-webclient ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ bitrepository-webclient ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 12 source files to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-webclient/target/classes
[INFO]
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ bitrepository-webclient ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-webclient/src/test/resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ bitrepository-webclient ---
[INFO] No sources to compile
[INFO]
[INFO] --- maven-surefire-plugin:2.17:test (default-test) @ bitrepository-webclient ---
[INFO] No tests to run.
[JENKINS] Recording test results
[INFO]
[INFO] --- maven-war-plugin:2.4:war (default-war) @ bitrepository-webclient ---
[INFO] Packaging webapp
[INFO] Assembling webapp [bitrepository-webclient] in [/home/cibuild01/workspace/Bitrepository-sonar/bitrepository-webclient/target/bitrepository-webclient-1.7-SNAPSHOT]
[INFO] Processing war project
[INFO] Copying webapp webResources [/home/cibuild01/workspace/Bitrepository-sonar/bitrepository-webclient/src/main/webapp] to [/home/cibuild01/workspace/Bitrepository-sonar/bitrepository-webclient/target/bitrepository-webclient-1.7-SNAPSHOT]
[INFO] Copying webapp resources [/home/cibuild01/workspace/Bitrepository-sonar/bitrepository-webclient/src/main/webapp]
[INFO] Webapp assembled in [1463 msecs]
[INFO] Building war: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-webclient/target/bitrepository-webclient-1.7-SNAPSHOT.war
[INFO]
[INFO] --- maven-jar-plugin:2.4:test-jar (default) @ bitrepository-webclient ---
[WARNING] JAR will be empty - no content was marked for inclusion!
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-webclient/target/bitrepository-webclient-1.7-SNAPSHOT-tests.jar
[INFO]
[INFO] --- maven-source-plugin:2.2.1:jar-no-fork (attach-sources-no-fork) @ bitrepository-webclient ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-webclient/target/bitrepository-webclient-1.7-SNAPSHOT-sources.jar
[INFO]
[INFO] --- maven-assembly-plugin:2.4:single (distribution) @ bitrepository-webclient ---
[INFO] Reading assembly descriptor: src/main/assembly/assembly.xml
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-webclient/target/bitrepository-webclient-1.7-SNAPSHOT-distribution.tar.gz
[INFO]
[INFO] --- maven-install-plugin:2.5.1:install (default-install) @ bitrepository-webclient ---
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-webclient/target/bitrepository-webclient-1.7-SNAPSHOT.war to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-webclient/1.7-SNAPSHOT/bitrepository-webclient-1.7-SNAPSHOT.war
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-webclient/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-webclient/1.7-SNAPSHOT/bitrepository-webclient-1.7-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-webclient/target/bitrepository-webclient-1.7-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-webclient/1.7-SNAPSHOT/bitrepository-webclient-1.7-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-webclient/target/bitrepository-webclient-1.7-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-webclient/1.7-SNAPSHOT/bitrepository-webclient-1.7-SNAPSHOT-sources.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-webclient/target/bitrepository-webclient-1.7-SNAPSHOT-distribution.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-webclient/1.7-SNAPSHOT/bitrepository-webclient-1.7-SNAPSHOT-distribution.tar.gz
[JENKINS] Archiving disabled
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Integration 1.7-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-integration ---
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ bitrepository-integration ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 33 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ bitrepository-integration ---
[INFO] No sources to compile
[INFO]
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ bitrepository-integration ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO]
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ bitrepository-integration ---
[INFO] No sources to compile
[INFO]
[INFO] --- maven-surefire-plugin:2.17:test (default-test) @ bitrepository-integration ---
[JENKINS] Recording test results
[INFO]
[INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ bitrepository-integration ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integration/target/bitrepository-integration-1.7-SNAPSHOT.jar
[INFO]
[INFO] --- maven-jar-plugin:2.4:test-jar (default) @ bitrepository-integration ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integration/target/bitrepository-integration-1.7-SNAPSHOT-tests.jar
[INFO]
[INFO] --- maven-source-plugin:2.2.1:jar-no-fork (attach-sources-no-fork) @ bitrepository-integration ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integration/target/bitrepository-integration-1.7-SNAPSHOT-sources.jar
[INFO]
[INFO] --- maven-assembly-plugin:2.4:single (make-assembly) @ bitrepository-integration ---
[INFO] Reading assembly descriptor: src/main/assembly/assembly.xml
[INFO] Reading assembly descriptor: src/main/assembly/tools-assembly.xml
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integration/target/bitrepository-integration-1.7-SNAPSHOT-quickstart.tar.gz
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integration/target/bitrepository-integration-1.7-SNAPSHOT-tools.tar.gz
[WARNING] Entry: bitrepository-integration-1.7-SNAPSHOT/lib/bitrepository-reference-pillar-1.7-SNAPSHOT-distribution.tar.gz longer than 100 characters.
[WARNING] Resulting tar file can only be processed successfully by GNU compatible tar commands
[INFO]
[INFO] --- maven-install-plugin:2.5.1:install (default-install) @ bitrepository-integration ---
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integration/target/bitrepository-integration-1.7-SNAPSHOT.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integration/1.7-SNAPSHOT/bitrepository-integration-1.7-SNAPSHOT.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integration/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integration/1.7-SNAPSHOT/bitrepository-integration-1.7-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integration/target/bitrepository-integration-1.7-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integration/1.7-SNAPSHOT/bitrepository-integration-1.7-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integration/target/bitrepository-integration-1.7-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integration/1.7-SNAPSHOT/bitrepository-integration-1.7-SNAPSHOT-sources.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integration/target/bitrepository-integration-1.7-SNAPSHOT-quickstart.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integration/1.7-SNAPSHOT/bitrepository-integration-1.7-SNAPSHOT-quickstart.tar.gz
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integration/target/bitrepository-integration-1.7-SNAPSHOT-tools.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integration/1.7-SNAPSHOT/bitrepository-integration-1.7-SNAPSHOT-tools.tar.gz
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Bitrepository ..................................... SUCCESS [ 8.281 s]
[INFO] Bitrepository Reference Settings .................. SUCCESS [ 19.758 s]
[INFO] Bitrepository Core ................................ SUCCESS [01:00 min]
[INFO] Bitrepository Client .............................. SUCCESS [01:13 min]
[INFO] Bitrepository Service ............................. SUCCESS [ 23.530 s]
[INFO] Bitrepository Integrity Service ................... SUCCESS [02:56 min]
[INFO] Bitrepository Alarm Service ....................... SUCCESS [ 23.778 s]
[INFO] Bitrepository Audit Trail Service ................. SUCCESS [ 46.418 s]
[INFO] Bitrepository Reference Pillar .................... SUCCESS [01:34 min]
[INFO] Bitrepository Monitoring Service .................. SUCCESS [ 17.088 s]
[INFO] Bitrepository Webclient ........................... SUCCESS [ 5.417 s]
[INFO] Bitrepository Integration ......................... SUCCESS [ 20.077 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 09:46 min
[INFO] Finished at: 2016-01-29T02:27:35+01:00
[INFO] Final Memory: 41M/142M
[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/codehaus/mojo/maven-metadata.xml (24 KB at 6.3 KB/sec)
[INFO] Downloaded: https://sbforge.org/nexus/content/groups/public/org/apache/maven/plugins/maven-metadata.xml (14 KB at 3.7 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 (952 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.7-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- sonar-maven-plugin:3.0.1:sonar (default-cli) @ bitrepository-parent ---
[INFO] User cache: /home/cibuild01/.sonar/cache
[INFO] SonarQube version: 4.4
[WARNING] With SonarQube prior to 4.5, it is recommended to use maven-sonar-plugin 2.6
[INFO] Default locale: "en_US", source code encoding: "UTF-8"
[INFO] [02:28:09.168] Load global settings
[INFO] [02:28:09.989] User cache: /home/cibuild01/.sonar/cache
[INFO] [02:28:10.038] Install plugins
[INFO] [02:28:13.719] Install JDBC driver
[INFO] [02:28:13.831] Create JDBC datasource for jdbc:postgresql://leda/sonar
[INFO] [02:28:14.602] Initializing Hibernate
[ERROR] [02:28:27.229] Invalid value of sonar.sources for org.bitrepository.reference:bitrepository-reference-settings
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Bitrepository ..................................... FAILURE [ 30.273 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: 41.700 s
[INFO] Finished at: 2016-01-29T02:28:27+01:00
[INFO] Final Memory: 26M/70M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.sonarsource.scanner.maven:sonar-maven-plugin:3.0.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.sonarsource.scanner.maven:sonar-maven-plugin:3.0.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.sonarsource.scanner.maven.bootstrap.ExceptionHandling.handle(ExceptionHandling.java:36)
at org.sonarsource.scanner.maven.bootstrap.RunnerBootstrapper.execute(RunnerBootstrapper.java:81)
at org.sonarsource.scanner.maven.SonarQubeMojo.execute(SonarQubeMojo.java:112)
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:86)
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:283)
at org.sonar.runner.api.EmbeddedRunner.runAnalysis(EmbeddedRunner.java:165)
at org.sonar.runner.api.EmbeddedRunner.runAnalysis(EmbeddedRunner.java:152)
at org.sonarsource.scanner.maven.bootstrap.RunnerBootstrapper.execute(RunnerBootstrapper.java:78)
... 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 jolf@kb.dk thorbjoern@gmail.com tra@statsbiblioteket.dk
Finished: FAILURE
Console Output
Help us localize this page