From 84d5521c963ec25e019b977fbb44845f76a8d75a Mon Sep 17 00:00:00 2001 From: Arkadiusz Hiler Date: Fri, 31 Jul 2020 10:23:14 +0300 Subject: [PATCH] site: Explain incompletes and aborts They seem to confuse people and the severity is not obvious immediately. Let's put that in plain text. Issue: https://gitlab.freedesktop.org/gfx-ci/i915-infra/-/issues/92 Signed-off-by: Arkadiusz Hiler --- site/pre-merge-results.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/site/pre-merge-results.md b/site/pre-merge-results.md index 339efc4..40fa91e 100644 --- a/site/pre-merge-results.md +++ b/site/pre-merge-results.md @@ -91,6 +91,20 @@ Each test state change (e.g. pass→fail) has few things listed: * **numer of occurences of same transition across multiple machines:** `+3 similar issues` +## How Serious Are Incompletes And Aborts? + +**Incomplete** means that the machine haven't been able to complete execution +of a test (most often because of a kernel panic or a hard hang). Incompletes +signal very serious issues with stability. Any tests that were supposed to +follow, that are on the same testlist (shard, fast-feedback), are not going to +be executed. + +**Aborts** are as serious as incompletes but the abnormal state was detected +either by IGT Runner or the test itself. They signal that no further testing +is going to be done because the results would not be trustworthy do to the +machine's / kernel condition. + + ## I've Got Some False Positives, What Now? Reply to the e-mail with the results and explain why do those results are -- GitLab