adds functionality to resultsdb directive so that the job is created during reporting.
Details
new unit tests created, tested locally with dev instance of resultsdb
Diff Detail
- Lint
Lint Skipped - Unit
Unit Tests Skipped
- updating docstrings to reflect actual TAP output
- fixing docstrings to be valid and complete
I don't have anything but a few nitpicks. I'm not really able to verify that it's semantically correct, @jskladan should be able to confirm that. But if we break something, I assume we'll learn it soon enough :)
libtaskotron/directives/resultsdb_directive.py | ||
---|---|---|
55–56 | I'm not really fond of matching error messages. If we need to distinguish different cases, let's create a child exception and than compare by its class. If we need to push this ASAP, let's create a ticket for it instead and add FIXME to the code. | |
59 | IIUIC and we intend to patch this, please prepend with FIXME. | |
70–72 | Again, please prepend with FIXME or TODO. Some editors nicely highlight it, and it's easy to grep for these words in console. | |
106 | It's better to print e, because e.message might be empty. I don't know how it works in this particular case. |
I'm not really fond of matching error messages. If we need to distinguish different cases, let's create a child exception and than compare by its class.
If we need to push this ASAP, let's create a ticket for it instead and add FIXME to the code.