public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Martin Peres <martin.peres@linux.intel.com>
To: Petri Latvala <petri.latvala@intel.com>, igt-dev@lists.freedesktop.org
Cc: 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:38:52 +0200	[thread overview]
Message-ID: <cd539f54-df4c-a5f4-67b6-22c2b760bf70@linux.intel.com> (raw)
In-Reply-To: <20200220125207.16423-2-petri.latvala@intel.com>

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.

Martin
> 
> Signed-off-by: Petri Latvala <petri.latvala@intel.com>
> Cc: Tomi Sarvela <tomi.p.sarvela@intel.com>
> ---
>  tests/intel-ci/blacklist.txt          | 5 -----
>  tests/intel-ci/fast-feedback.testlist | 4 ++++
>  2 files changed, 4 insertions(+), 5 deletions(-)
> 
> diff --git a/tests/intel-ci/blacklist.txt b/tests/intel-ci/blacklist.txt
> index 51d0417c..390e4fa0 100644
> --- a/tests/intel-ci/blacklist.txt
> +++ b/tests/intel-ci/blacklist.txt
> @@ -1,10 +1,5 @@
>  igt@meta_test(@.*)?
>  ###############################################
> -# Kernel selftests (run separately)
> -###############################################
> -igt@i915_selftest(@.*)?
> -igt@drm_mm(@.*)?
> -###############################################
>  # Handle module reloads with great care!
>  #
>  # Reloading a module is more likely to leave
> diff --git a/tests/intel-ci/fast-feedback.testlist b/tests/intel-ci/fast-feedback.testlist
> index 1b00485e..b41fb4a0 100644
> --- a/tests/intel-ci/fast-feedback.testlist
> +++ b/tests/intel-ci/fast-feedback.testlist
> @@ -171,3 +171,7 @@ igt@vgem_basic@sysfs
>  igt@vgem_basic@unload
>  igt@i915_module_load@reload
>  igt@i915_pm_rpm@module-reload
> +
> +# Kernel selftests
> +igt@i915_selftest@live
> +igt@dmabuf@all
> 
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  reply	other threads:[~2020-02-27 11:38 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 [this message]
2020-02-27 11:46     ` Petri Latvala
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=cd539f54-df4c-a5f4-67b6-22c2b760bf70@linux.intel.com \
    --to=martin.peres@linux.intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=petri.latvala@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