commit | d0033b71e1de8d3b0e059669c1c9c9c62ba533fb | [log] [tgz] |
---|---|---|
author | James E. Blair <jeblair@redhat.com> | Tue Oct 17 15:13:15 2017 -0700 |
committer | James E. Blair <jeblair@redhat.com> | Tue Oct 17 15:13:15 2017 -0700 |
tree | c54a2bcc5f88fcb4c830bf11eac322e5623f4e70 | |
parent | bacbb888b6229c5862fa1d028fd3e618e611eb88 [diff] |
Don't set the build result to ABORTED We pass 'ABORTED' back from the executor in some cases, mostly to aid in testing (so we know when the executor has intentionally aborted a job). However, that's a non-final result, and other parts of zuul (like areAllJobsCompleted) shouldn't need to know about it. If the executor client receives ABORTED (or DISCONNECT), log it, but don't pass it any further up the chain. Change-Id: If2cbf2f6eecb9a7fdef4d0a6eebeb5fe2549e276