taskotron

#274 Allow CRASHED outcome in resultsdb.
Closed: Fixed by kparal. Opened by jskladan.

Closed: Fixed
Reopen Issue

Since our ExecDB plans didn't fully work out, please add CRASHED outcome so that we allow maintainers to get notified and inspect their crashed jobs (as long as they manage to generate results.yml). See https://pagure.io/task-abicheck/issue/19 for a concrete use case.

ResultsDB supports any outcome you want, on top of the default 'PASSED', 'INFO', 'FAILED', 'NEEDS_INSPECTION' set, you just need to set the ADDITIONAL_RESULT_OUTCOMES config value (in /etc/resultsdb/settings.py) properly. In this particular case:
ADDITIONAL_RESULT_OUTCOMES = ['CRASHED']
should be the right value

Was: https://pagure.io/taskotron/resultsdb/issue/127

Deployed to dev:
https://infrastructure.fedoraproject.org/cgit/ansible.git/commit/?id=c65ca8cdaefaef337ead9f1e10276e181c069abf

Metadata Update from @kparal:
- Issue assigned to kparal

Commit d02914c6 relates to this ticket

Just a note, @kparal, there is a reason i used ['CRASHED'] instead of (CRASHED) in the "what you should add" part of the ticket, and that is the slight difference between x = ('CRASHED') and x = ('CRASHED',), of which you used the wrong one ;-)

Fixed it for you: https://infrastructure.fedoraproject.org/cgit/ansible.git/commit/?id=dd7ded3ca5a8bbd8415faa0f23dd1b25f92ae071

Deployed to production some time ago:
https://infrastructure.fedoraproject.org/cgit/ansible.git/commit/?id=633f9fa
Closing.

Metadata Update from @kparal:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)
Metadata

easyfix infra

None
None
Low
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.