intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com>
To: Marcin Bernatowicz <marcin.bernatowicz@linux.intel.com>,
	 igt-dev@lists.freedesktop.org
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH i-g-t] tests/core_hotunplug: Reduce debug noise on stdout
Date: Thu, 21 Jan 2021 09:48:17 +0100	[thread overview]
Message-ID: <7c9e9e4545e7195f8f96ff352548eee63d6c3c7d.camel@linux.intel.com> (raw)
In-Reply-To: <7ac828ba904e3fc4153f5aa8041bfcf79128407b.camel@linux.intel.com>

On Tue, 2021-01-19 at 12:08 +0100, Marcin Bernatowicz wrote:
> On Tue, 2021-01-19 at 09:42 +0100, Janusz Krzysztofik wrote:
> > Since igt_fixture sections are processed unconditionally regardless
> > of
> > which subtest has been requested, they can now emit a lot of
> > unrelated
> > debug messages which can make the picture less clear.  Avoid emitting
> > those messages from outside igt_subtest sections.
> > 
> > Move device close status prerequisite checks from igt_fixture
> > sections
> > into subtest execution paths.  For simplicity, pass any device close
> > errors, including those from health checks, to next sections via a
> > single .fd.drm data structure field.
> > 
> > Moreover, postpone initial device health check until first actually
> > selected subtest is started.  In order to let that subtest skip on
> > unsuccessful initial health check, not fail, move the decision
> > whether
> > to fail or skip on error from the health check helper to its users.
> > 
> > Signed-off-by: Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com
> > ...
> Reviewed-by: Marcin Bernatowicz <marcin.bernatowicz@linux.intel.com>

Thank you Marcin.

CI results with no false positives finally collected after a few re-
runs, so pushed.

Thanks,
Janusz

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      reply	other threads:[~2021-01-21  8:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-19  8:42 [Intel-gfx] [PATCH i-g-t] tests/core_hotunplug: Reduce debug noise on stdout Janusz Krzysztofik
2021-01-19 11:08 ` Marcin Bernatowicz
2021-01-21  8:48   ` Janusz Krzysztofik [this message]

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=7c9e9e4545e7195f8f96ff352548eee63d6c3c7d.camel@linux.intel.com \
    --to=janusz.krzysztofik@linux.intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=marcin.bernatowicz@linux.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;
as well as URLs for NNTP newsgroup(s).