From: Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com>
To: igt-dev@lists.freedesktop.oef
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] [RFC PATCH 2/2] intel-ci: Unblock core_hotunplug@*hot*bind* subtests
Date: Thu, 8 Apr 2021 10:30:09 +0200 [thread overview]
Message-ID: <20210408083009.22860-2-janusz.krzysztofik@linux.intel.com> (raw)
In-Reply-To: <20210408083009.22860-1-janusz.krzysztofik@linux.intel.com>
Commit be529747d8ea ("intel-ci: Broaden core_hotunplug blacklist")
blamed issues triggered by hot variants[*] as responsible for random
failures in subsequently executed tests,
According to the issue history[*], last reported occurrences were
not related to core_hotunplug. Remove *hot*bind* subtests from CI
blocklist.
[*] https://gitlab.freedesktop.org/drm/intel/-/issues/2644.
Signed-off-by: Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com>
---
tests/intel-ci/blacklist.txt | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/tests/intel-ci/blacklist.txt b/tests/intel-ci/blacklist.txt
index 33f92e37f..595fd0ca6 100644
--- a/tests/intel-ci/blacklist.txt
+++ b/tests/intel-ci/blacklist.txt
@@ -112,10 +112,10 @@ igt@.*@.*pipe-f($|-.*)
# Temporary workarounds for CI-impacting bugs
###############################################
-# Currently fails and leaves the machine in a very bad state, and
-# causes coverage loss for other tests. IOMMU related.
-# https://gitlab.freedesktop.org/drm/intel/-/issues/2644
-igt@core_hotunplug@.*(hot|plug).*
+# *plug* subtests still fail and leave the
+# machine in a very bad state, causing coverage
+# loss for other tests. IOMMU related.
+igt@core_hotunplug@.*plug.*
# hangs several gens of hosts, and has no immediate fix
igt@device_reset@reset-bound
--
2.25.1
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2021-04-08 8:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-08 8:30 [Intel-gfx] [RFC PATCH 1/2] tests/core_hotunplug: Add perf health check Janusz Krzysztofik
2021-04-08 8:30 ` Janusz Krzysztofik [this message]
2021-04-14 9:52 ` [Intel-gfx] [RFC PATCH 2/2] intel-ci: Unblock core_hotunplug@*hot*bind* subtests Marcin Bernatowicz
2021-04-08 8:35 ` [Intel-gfx] [RFC PATCH 1/2] tests/core_hotunplug: Add perf health check Janusz Krzysztofik
2021-04-08 12:34 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for series starting with [RFC,1/2] " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2021-04-08 8:31 [Intel-gfx] [RFC PATCH 1/2] " Janusz Krzysztofik
2021-04-08 8:31 ` [Intel-gfx] [RFC PATCH 2/2] intel-ci: Unblock core_hotunplug@*hot*bind* subtests Janusz Krzysztofik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210408083009.22860-2-janusz.krzysztofik@linux.intel.com \
--to=janusz.krzysztofik@linux.intel.com \
--cc=igt-dev@lists.freedesktop.oef \
--cc=intel-gfx@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox