All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Intel-gfx@lists.freedesktop.org,
	Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Subject: Re: [PATCH] drm/i915/selftests: Log test and subtest names for easier debugging
Date: Tue, 20 Nov 2018 18:10:30 +0000	[thread overview]
Message-ID: <154273743050.11623.12150286322017112708@skylake-alporthouse-com> (raw)
In-Reply-To: <d13f8c12-f26f-ff15-ab60-cc556cb6af5d@linux.intel.com>

Quoting Tvrtko Ursulin (2018-11-20 17:58:33)
> 
> On 20/11/2018 17:33, Chris Wilson wrote:
> > Quoting Tvrtko Ursulin (2018-11-20 17:28:39)
> >> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> >>
> >> Since pr_debug is not printed by default, change both test and subtest
> >> log messages to pr_info so they are always logged.
> > 
> > I just use the trace... As when the test fails we say which subtest
> > failed, and hopefully include more details in the error message, and
> > recent history is in the trace dumped when considered relevant.
> 
> Fair. My thinking was simply to leave more breadcrumbs if the machine 
> died in the middle of a subtest.

Thinking more about it, the easiest option would be to actually enable
pr_debug, iirc a config option.

However, the only time we don't get breadcrumbs is if the machine
spontaneously combusts, which we are told is a mere figment of our
imagination.  Most often I wonder if we simply do not get the death
throes - adding logging won't help if we don't capture it. For the true
spontaneous combustion, it's pretty random and all I can think of
suggesting are more sanity checks to try and catch inconsistencies early.
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2018-11-20 18:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-20 17:28 [PATCH] drm/i915/selftests: Log test and subtest names for easier debugging Tvrtko Ursulin
2018-11-20 17:33 ` Chris Wilson
2018-11-20 17:58   ` Tvrtko Ursulin
2018-11-20 18:10     ` Chris Wilson [this message]
2018-11-20 18:18       ` Tvrtko Ursulin
2018-11-20 18:24         ` Chris Wilson
2018-11-21  9:02         ` Tvrtko Ursulin
2018-11-21  9:33           ` Chris Wilson
2018-11-21  9:43             ` Tvrtko Ursulin
2018-11-20 18:03 ` ✓ Fi.CI.BAT: success for " Patchwork
2018-11-21  4:06 ` ✓ 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=154273743050.11623.12150286322017112708@skylake-alporthouse-com \
    --to=chris@chris-wilson.co.uk \
    --cc=Intel-gfx@lists.freedesktop.org \
    --cc=tvrtko.ursulin@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 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.