From: Petri Latvala <petri.latvala@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: Petri Latvala <petri.latvala@intel.com>
Subject: [igt-dev] [PATCH i-g-t v2 2/2] intel-ci: Adjust pipe-specific blacklisting
Date: Thu, 17 Oct 2019 12:21:37 +0300 [thread overview]
Message-ID: <20191017092137.28967-1-petri.latvala@intel.com> (raw)
In-Reply-To: <20191017091713.25456-2-petri.latvala@intel.com>
Blacklist pipes E and F usage even when the subtest name ends in
pipe-x.
Signed-off-by: Petri Latvala <petri.latvala@intel.com>
Cc: Martin Peres <martin.peres@linux.intel.com>
---
tests/intel-ci/blacklist.txt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tests/intel-ci/blacklist.txt b/tests/intel-ci/blacklist.txt
index 734fa40a..4d1813e5 100644
--- a/tests/intel-ci/blacklist.txt
+++ b/tests/intel-ci/blacklist.txt
@@ -106,5 +106,5 @@ igt@i915_suspend@shrink
###############################################
# pipe-e, pipe-f no current HW support
###############################################
-igt@.*@.*pipe-e-.*
-igt@.*@.*pipe-f-.*
+igt@.*@.*pipe-e($|-.*)
+igt@.*@.*pipe-f($|-.*)
--
2.19.1
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-10-17 9:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-17 9:17 [igt-dev] [PATCH i-g-t 1/2] kms_busy: Rename tests so pipe-specific subtests are blacklistable Petri Latvala
2019-10-17 9:17 ` [igt-dev] [PATCH i-g-t 2/2] intel-ci: Adjust pipe-specific blacklisting Petri Latvala
2019-10-17 9:21 ` Petri Latvala [this message]
2019-11-07 14:45 ` Arkadiusz Hiler
2019-11-07 14:54 ` Arkadiusz Hiler
2019-10-17 9:41 ` [igt-dev] ✗ GitLab.Pipeline: warning for series starting with [i-g-t,1/2] kms_busy: Rename tests so pipe-specific subtests are blacklistable (rev2) Patchwork
2019-10-17 10:00 ` [igt-dev] ✗ Fi.CI.BAT: failure " Patchwork
2019-10-20 10:51 ` [igt-dev] ✗ GitLab.Pipeline: warning for series starting with [i-g-t,1/2] kms_busy: Rename tests so pipe-specific subtests are blacklistable (rev3) Patchwork
2019-10-20 11:08 ` [igt-dev] ✗ Fi.CI.BAT: failure " Patchwork
2019-10-21 11:42 ` [igt-dev] ✗ GitLab.Pipeline: warning for series starting with [i-g-t,1/2] kms_busy: Rename tests so pipe-specific subtests are blacklistable (rev4) Patchwork
2019-10-21 12:17 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2019-10-21 15:22 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2019-11-07 14:45 ` [igt-dev] [PATCH i-g-t 1/2] kms_busy: Rename tests so pipe-specific subtests are blacklistable Arkadiusz Hiler
2019-11-11 11:31 ` [igt-dev] ✗ Fi.CI.IGT: failure for series starting with [i-g-t,1/2] kms_busy: Rename tests so pipe-specific subtests are blacklistable (rev4) Patchwork
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=20191017092137.28967-1-petri.latvala@intel.com \
--to=petri.latvala@intel.com \
--cc=igt-dev@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