On Wed, 2020-02-05 at 14:01 -0500, Randy Barlow wrote:
On Wed, 2020-02-05 at 11:19 -0700, Tim Flink wrote:
Can you elaborate a bit more on why you think that's the case. I'm more of the mind that they don't belong in resultsdb because "error" as defined in the messaging standard isn't a test result - it's an execution state. I can't see an error state ever being used in a gating decision and thus don't see why errors should be in resultsdb.
I agree with you. However, I do think execution states would be good to store somewhere, so that UIs can show users the state of the tests as they are running (queued, running, error). It makes sense to me not to store them in the same place as results.
We've kicked around the idea of an "execdb" before, I think...