Issue #38: resultsdb doesn't support ABORTED outcome - resultsdb

taskotron / resultsdb

#38 resultsdb doesn't support ABORTED outcome

Closed: Fixed None Opened 9 years ago by kparal.

I see these errors:

[libtaskotron:resultsdb_directive.py:187] 2015-04-08 16:21:00 INFO    Posting 50 results to ResultsDB...
[libtaskotron:resultsdb_directive.py:202] 2015-04-08 16:21:05 ERROR   outcome must be one of ('PASSED', 'INFO', 'FAILED', 'ERROR', 'WAIVED', 'NEEDS_INSPECTION')
[libtaskotron:resultsdb_directive.py:204] 2015-04-08 16:21:05 ERROR   Failed to store ResulsDB: `myproxy-6.1.13-1.fc22,globus-xio-5.8-1.fc22,globus-simple-ca-4.19-1.fc22,globus-scheduler-event-generator-5.11-1.fc22,globus-gridftp-server-7.25-1.fc22,globus-gatekeeper-10.10-1.fc22,globus-common-15.29-1.fc22` `depcheck` `ABORTED`

here:
https://taskotron.fedoraproject.org/taskmaster//builders/x86_64/builds/56193/steps/runtask/logs/stdio

I don't know if resultsdb actually doesn't support ABORTED, or it's simply a resultsdb_directive bug, but I guess it should work. Is there any reason to not support this outcome?