Skip to content

Commit

Permalink
doc/submitter_guide: mention "running" around the absent status
Browse files Browse the repository at this point in the history
In addition to "scheduled", there's a consensus that the absent status
can also mean "running", because it would be too resource intensive to
track each running test, both to KCIDB and the runners.

Signed-off-by: Tales da Aparecida <tales.aparecida@redhat.com>
  • Loading branch information
Tales da Aparecida authored and spbnick committed Jun 9, 2024
1 parent cf47526 commit 6c73866
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions doc/submitter_guide.md
Original file line number Diff line number Diff line change
Expand Up @@ -312,8 +312,8 @@ means that the harness worked alright, and either it, or the test itself,
decided not to run this specific test, because it was inapplicable.

Finally, the last line in the table above (without a status) corresponds to
the absent "status" field, and means that the test is only scheduled to
execute, the system hasn't got to it yet, and so we have no data on anything.
the absent "status" field, and means that the test is either only scheduled,
or is still executing, and so we have no status data yet.

Another way to visualize the status values and the three layered testing stack,
is to put them into an execution outcome chart:
Expand Down

0 comments on commit 6c73866

Please sign in to comment.