Both of the examples you gave are for the state/presence failure. The title of this bug implies the original failures were seen in worker/provisioner, and I see that in this run, the failure was in worker/provisioner: http://reports.vapour.ws/releases/2601/job/run-unit-tests-win2012-amd64/attempt/338
TestProvisionerRetriesTransientErrors is implicated in the trace back on that run.
Maybe also specifying the failing package would help differentiate?
Both of the examples you gave are for the state/presence failure. The title of this bug implies the original failures were seen in worker/provisioner, and I see that in this run, the failure was in worker/provisioner: http:// reports. vapour. ws/releases/ 2601/job/ run-unit- tests-win2012- amd64/attempt/ 338
TestProvisioner RetriesTransien tErrors is implicated in the trace back on that run.
Maybe also specifying the failing package would help differentiate?