The autoland job just runs a plain 'tox' on the source tree [1], and I can reproduce that problem locally on my Groovy system.
It's annoying when the autolander job runs in this kind of loop. One easy way to prevent it would be to have the autolander job to set the MP back to "Needs review" on failure. What do you think? It would be nice to have it set the MP back to "Needs review" after e.g. 3 failures. I was thinking of doing this using the Jenkins "unstable" state, but this is not possible as the status of job is not per-MP. [1] https://github.com/canonical/server-jenkins-jobs/blob/master/curtin/jobs-ci.yaml#L187 -- https://code.launchpad.net/~falcojr/curtin/+git/curtin/+merge/383601 Your team curtin developers is subscribed to branch curtin:master. -- Mailing list: https://launchpad.net/~curtin-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~curtin-dev More help : https://help.launchpad.net/ListHelp
