Hi folks,

I've just come across something very strange in a jenkins build that
others should be aware of in case they hit across the same thing.

https://builds.apache.org/job/pulsar_precommit_integrationtests/1782/

This build is a bulld of the branch
69b5976d8b40789f7f139185ffc1e5cc0bbe4f4b
https://github.com/ivankelly/incubator-pulsar/tree/69b5976d8b40789f7f139185ffc1e5cc0bbe4f4b

It failed on the command

timeout 60 bash -c until test -S /var/run/supervisor/supervisor.sock;
do sleep 0.1; done

https://builds.apache.org/job/pulsar_precommit_integrationtests/1782/artifact/tests/integration/smoke/target/surefire-reports/org.apache.pulsar.tests.integration.TestSmoke-output.txt

Now, the command it failed on isn't what is interesting (I'm still
working on this stuff), but what is interesting it that the timeout is
not part of 69b5976. It was a patch I submitted in parallel.

The place it should be picking it up from the classpath is
/home/jenkins/jenkins-slave/workspace/pulsar_precommit_integrationtests/tests/integration-tests-utils/target/classes,
and this cleaned and installed into earlier in the test.

So, somehow maven is picking up artifacts from somewhere else, and I'm
stumped to know where.

-ivan

Reply via email to