See https://lists.fedoraproject.org/archives/list/resultsdb-users@lists.fedoraproject.org/message/DJSIOLA3YEH6HNSJEXVPLIZT5TW4CDED/
for some discussion of this. To make life easier for consumers
of our results from ResultsDB, we should report the 'scenario'
of the test. This allows consumers to conveniently deduplicate
results: results for the same 'item' and 'scenario' are dupes,
so usually, consumers will only want to consider the most recent
one.
Details
Details
- Reviewers
jsedlak jskladan - Commits
- rOPENQA4c7613cd8b70: Report test 'scenario' to ResultsDB
Check the tests pass, report some results to a test
ResultsDB and check the scenario item in the extradata looks
correct.
Diff Detail
Diff Detail
- Repository
- rOPENQA fedora_openqa
- Branch
- scenario (branched from master)
- Lint
No Linters Available - Unit
No Unit Test Coverage - Build Status
Buildable 1086 Build 1086: arc lint + arc unit
Comment Actions
Code looks OK and if we need it right now, feel free to merge it, but I wonder how will the discussion evolve.
Comment Actions
I think we're OK to go with this for now, too, at least if I'm reading @kparal correctly - if anything, his remaining question is whether the test name should be in the scenario. But even if we decided to take it out in future, I don't think that's a problem, intended usages wouldn't be affected by the change I don't think. So I'm gonna go ahead and merge this.