JoeW, I'm not familiar with the Kafka processors, could it be a firewall issue?
JoeS On Thu, Apr 7, 2016 at 11:56 PM, Joe Witt <[email protected]> wrote: > Interesting. Appears the embedded Kafka instance is somehow not > running there or not accessible. Yet it is spun up in the tests. > Even more interesting is that Travis-CI runs on Ubuntu (older version) > as shown in the travis-ci build information linked to our github > > Distributor ID: Ubuntu > Description: Ubuntu 12.04.5 LTS > Release: 12.04 > Codename: precise > > On Thu, Apr 7, 2016 at 11:37 PM, Joe Skora <[email protected]> wrote: > > Build worked on a Centos 7 system but is failing the Kafka tests on 2 > > different Ubuntu 15.10 systems. > > > > Failed tests: > > TestPutKafka.testComplexLeftPartialDelimitedMessages:225 Expected > > all Transferred FlowFiles to go to success but 1 were routed to failure > > TestPutKafka.testComplexPartialMatchDelimitedMessages:248 Expected > > all Transferred FlowFiles to go to success but 1 were routed to failure > > TestPutKafka.testComplexRightPartialDelimitedMessages:204 Expected > > all Transferred FlowFiles to go to success but 1 were routed to failure > > TestPutKafka.testWithEmptyMessages:174 > > org.apache.kafka.common.errors.TimeoutException: Failed to update > metadata > > after 30000 ms. > > > > Tests in error: > > KafkaPublisherTest.validateSuccessfulReSendOfFailedSegments:167 » > > ConsumerTimeout > > KafkaPublisherTest.validateSuccessfulSendAsDelimited:114 » > > ConsumerTimeout > > KafkaPublisherTest.validateSuccessfulSendAsDelimited2:140 » > > ConsumerTimeout > > KafkaPublisherTest.validateSuccessfulSendAsWhole:92 » > ConsumerTimeout > > KafkaPublisherTest.validateWithMultiByteCharacters:195 » > > ConsumerTimeout > > > > Tests run: 18, Failures: 4, Errors: 5, Skipped: 3 > > > > I'm still trying to track down possible the cause. > > > > > > On Thu, Apr 7, 2016 at 10:43 PM, Tony Kurc <[email protected]> wrote: > > > >> Still working on the validation, but I was able to get past the point in > >> 0.6.0 on my Windows 10 rig that kept failing in unit tests. > >> > >> On Wed, Apr 6, 2016 at 5:51 PM, Joe Witt <[email protected]> wrote: > >> > >> > Hello Apache NiFi community, > >> > > >> > Please find the associated guidance to help those interested in > >> > validating/verifying the release so they can vote. > >> > > >> > # Download latest KEYS file: > >> > https://dist.apache.org/repos/dist/dev/nifi/KEYS > >> > > >> > # Import keys file: > >> > gpg --import KEYS > >> > > >> > # [optional] Clear out local maven artifact repository > >> > > >> > # Pull down nifi-0.6.1 source release artifacts for review: > >> > > >> > wget > >> > > >> > https://dist.apache.org/repos/dist/dev/nifi/nifi-0.6.1/nifi-0.6.1-source-release.zip > >> > wget > >> > > >> > https://dist.apache.org/repos/dist/dev/nifi/nifi-0.6.1/nifi-0.6.1-source-release.zip.asc > >> > wget > >> > > >> > https://dist.apache.org/repos/dist/dev/nifi/nifi-0.6.1/nifi-0.6.1-source-release.zip.md5 > >> > wget > >> > > >> > https://dist.apache.org/repos/dist/dev/nifi/nifi-0.6.1/nifi-0.6.1-source-release.zip.sha1 > >> > > >> > # Verify the signature > >> > gpg --verify nifi-0.6.1-source-release.zip.asc > >> > > >> > # Verify the hashes (md5, sha1) match the source and what was provided > >> > in the vote email thread > >> > md5sum nifi-0.6.1-source-release.zip > >> > sha1sum nifi-0.6.1-source-release.zip > >> > > >> > # Unzip nifi-0.6.1-source-release.zip > >> > > >> > # Verify the build works including release audit tool (RAT) checks > >> > cd nifi-0.6.1 > >> > mvn clean install -Pcontrib-check > >> > > >> > # Verify the contents contain a good README, NOTICE, and LICENSE. > >> > > >> > # Verify the git commit ID is correct > >> > > >> > # Verify the RC was branched off the correct git commit ID > >> > > >> > # Look at the resulting convenience binary as found in > >> nifi-assembly/target > >> > > >> > # Make sure the README, NOTICE, and LICENSE are present and correct > >> > > >> > # Run the resulting convenience binary and make sure it works as > expected > >> > > >> > # Send a response to the vote thread indicating a +1, 0, -1 based on > >> > your findings. > >> > > >> > Thank you for your time and effort to validate the release! > >> > > >> >
