From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: piglit discussion list <piglit@lists.freedesktop.org>,
Daniel Vetter <daniel.vetter@intel.com>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
jari.tahvanainen@intel.com
Subject: Re: [PATCH] tests/igt: dmesg noise is a kernel failure
Date: Thu, 6 Oct 2016 12:33:04 +0300 [thread overview]
Message-ID: <20161006093304.GI4329@intel.com> (raw)
In-Reply-To: <20161006090717.23527-1-daniel.vetter@ffwll.ch>
On Thu, Oct 06, 2016 at 11:07:17AM +0200, Daniel Vetter wrote:
> At least when testing the kernel. In normal programs pretty much all
> the dmesg noise would simply be replaced by debug asserts, but in the
> kernel we try rely hard to not fall over minor inconsistencies.
>
> Still for CI purposes there's not really a difference, hence don't
> treat it as such.
>
> Motivated since once again I've seen a statistics where this was split
> up, and then a reduction of "failures" (but in reality just trading
> them in for more "warnings") praised as success.
>
> Cc: jari.tahvanainen@intel.com
> Cc: Petri Latvala <petri.latvala@intel.com>
> Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
> ---
> tests/igt.py | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/tests/igt.py b/tests/igt.py
> index 7ebb03646b50..473027b76936 100644
> --- a/tests/igt.py
> +++ b/tests/igt.py
> @@ -53,6 +53,7 @@ def check_environment():
>
> """
> debugfs_path = "/sys/kernel/debug/dri"
> +
> if os.getuid() != 0:
> raise exceptions.PiglitInternalError(
> "Test Environment check: not root!")
> @@ -123,6 +124,10 @@ class IGTTest(Test):
> else:
> self.result.result = 'fail'
>
> + # all dmesg noise is considered a test failure when testing the kernel
> + if self.result.dmesg
> + self.result.result = 'fail'
Hmm. So now all errors will look the same? I think I'm usually more
interested in the dmesg warns, so this would perhaps make it harder for
me to spot them. Not sure I like that.
> +
>
> def list_tests(listname):
> """Parse igt test list and return them as a list."""
> --
> 2.9.3
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-10-06 9:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-06 9:07 [PATCH] tests/igt: dmesg noise is a kernel failure Daniel Vetter
2016-10-06 9:16 ` Chris Wilson
[not found] ` <20161006091629.GI22676-aII6DKEyn0pWYbfKqPwjAkR8Iwp7RQ6xAL8bYrjMMd8@public.gmane.org>
2016-10-07 7:02 ` [Intel-gfx] " Daniel Vetter
2016-10-06 9:33 ` Ville Syrjälä [this message]
[not found] ` <20161006090717.23527-1-daniel.vetter-/w4YWyX8dFk@public.gmane.org>
2016-10-06 18:25 ` Dylan Baker
-- strict thread matches above, loose matches on Subject: below --
2016-10-07 7:06 Daniel Vetter
2016-10-07 7:12 ` Chris Wilson
2016-10-07 7:59 ` Tahvanainen, Jari
2016-10-07 8:43 ` Ville Syrjälä
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=20161006093304.GI4329@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jari.tahvanainen@intel.com \
--cc=piglit@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.