ignore ABORTED, CRASHED results when posting bodhi comments. Fixes T467
ClosedPublic

Authored by tflink on Apr 30 2015, 8:42 PM.

Details

Summary

The libtaskotron part of this change - ignores results with state of ABORTED or CRASHED when reporting to bodhi with comments

Test Plan

unit tests added

Diff Detail

Repository
rLTRN libtaskotron
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.
tflink retitled this revision from to ignore ABORTED, CRASHED results when posting bodhi comments. Fixes T467.Apr 30 2015, 8:42 PM
tflink updated this object.
tflink edited the test plan for this revision. (Show Details)
tflink added reviewers: jskladan, kparal.
jskladan accepted this revision.May 4 2015, 8:33 AM
This revision is now accepted and ready to land.May 4 2015, 8:33 AM
kparal accepted this revision.May 4 2015, 4:12 PM
kparal added a comment.May 5 2015, 7:56 AM

Just a side note, this will also resolve other issues like these:
https://admin.fedoraproject.org/updates/FEDORA-2015-4630/mpich-3.1.4-2.fc22
https://taskotron.fedoraproject.org/taskmaster//builders/x86_64/builds/67165/steps/runtask/logs/stdio

I was debugging this today and these are the problems:

  1. ABORTED result is posted to Bodhi -> will be fixed by this patch
  2. there is a crash in bodhi_comment_directive.py, because update is None, because the update got edited in the middle of the execution -> will be fixed by this patch, we will no longer reach that code. I consider that satisfactory solution.
  3. the result was not reported to ResultsDB -> should be fixed by @jskladan's D345.
This revision was automatically updated to reflect the committed changes.