From: Petri Latvala <petri.latvala@intel.com>
To: Martin Peres <martin.peres@linux.intel.com>
Cc: igt-dev@lists.freedesktop.org, Tomi Sarvela <tomi.p.sarvela@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t 2/2] intel-ci: Kernel selftest changes to fast-feedback and blacklist
Date: Thu, 27 Feb 2020 13:46:15 +0200 [thread overview]
Message-ID: <20200227114615.GK3839@platvala-desk.ger.corp.intel.com> (raw)
In-Reply-To: <cd539f54-df4c-a5f4-67b6-22c2b760bf70@linux.intel.com>
On Thu, Feb 27, 2020 at 01:38:52PM +0200, Martin Peres wrote:
> On 2020-02-20 14:52, Petri Latvala wrote:
> > Now that selftest launchers are enumerable, we can control them with
> > fast-feedback.testlist and blacklist.txt. For now, apply the status
> > quo.
>
> This patch series will end up being a no-op on Intel CI since we were
> appending the selftests as part of BAT testing. With this change done,
> CI will be able to drop this extra test list, and simplify execution.
>
> I renamed the tests in cibuglog, so this patch series is:
>
> Acked-by: Martin Peres <martin.peres@linux.intel.com>
>
> And it is ready to merge from my PoV.
Merged, thanks.
--
Petri Latvala
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2020-02-27 11:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-20 12:52 [igt-dev] [PATCH i-g-t 1/2] lib: Update selftests to use dynamic subtests Petri Latvala
2020-02-20 12:52 ` [igt-dev] [PATCH i-g-t 2/2] intel-ci: Kernel selftest changes to fast-feedback and blacklist Petri Latvala
2020-02-27 11:38 ` Martin Peres
2020-02-27 11:46 ` Petri Latvala [this message]
2020-02-20 13:42 ` [igt-dev] ✗ GitLab.Pipeline: failure for series starting with [i-g-t,1/2] lib: Update selftests to use dynamic subtests Patchwork
2020-02-20 13:55 ` [igt-dev] ✗ Fi.CI.BAT: " Patchwork
2020-02-24 1:23 ` [igt-dev] ✗ Fi.CI.IGT: " 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=20200227114615.GK3839@platvala-desk.ger.corp.intel.com \
--to=petri.latvala@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=martin.peres@linux.intel.com \
--cc=tomi.p.sarvela@intel.com \
/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