All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Petri Latvala <petri.latvala@intel.com>,
	Tvrtko Ursulin <tursulin@ursulin.net>
Cc: igt-dev@lists.freedesktop.org,
	Tomi Sarvela <tomi.p.sarvela@intel.com>,
	Intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH i-g-t v2] tests/perf_pmu: Handle CPU hotplug failures better
Date: Fri, 02 Mar 2018 11:32:26 +0000	[thread overview]
Message-ID: <151999034674.32001.17684398035555526277@mail.alporthouse.com> (raw)
In-Reply-To: <20180302111219.wjas3yhqqbafc4ju@platvala-desk.ger.corp.intel.com>

Quoting Petri Latvala (2018-03-02 11:12:19)
> On Wed, Feb 28, 2018 at 10:05:55AM +0000, Tvrtko Ursulin wrote:
> > +/**
> > + * igt_fatal_error:
> > + *
> > + * Stop test execution or optionally, if the IGT_REBOOT_ON_FATAL_ERROR
> > + * environment variable is set, reboot the machine.
> > + *
> > + * Since out test runner (piglit) does support fatal test exit codes, we
> > + * implement the default behaviour by waiting endlessly.
> > + */
> > +void  __attribute__((noreturn)) igt_fatal_error(void)
> > +{
> > +     if (igt_check_boolean_env_var("IGT_REBOOT_ON_FATAL_ERROR", false)) {
> > +             igt_warn("FATAL ERROR - REBOOTING");
> > +             igt_sysrq_reboot();
> > +     } else {
> > +             igt_warn("FATAL ERROR");
> > +             for (;;)
> > +                     sleep(60);

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

WARNING: multiple messages have this Message-ID (diff)
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Petri Latvala <petri.latvala@intel.com>,
	Tvrtko Ursulin <tursulin@ursulin.net>
Cc: igt-dev@lists.freedesktop.org,
	Tomi Sarvela <tomi.p.sarvela@intel.com>,
	Intel-gfx@lists.freedesktop.org,
	Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t v2] tests/perf_pmu: Handle CPU hotplug failures better
Date: Fri, 02 Mar 2018 11:32:26 +0000	[thread overview]
Message-ID: <151999034674.32001.17684398035555526277@mail.alporthouse.com> (raw)
In-Reply-To: <20180302111219.wjas3yhqqbafc4ju@platvala-desk.ger.corp.intel.com>

Quoting Petri Latvala (2018-03-02 11:12:19)
> On Wed, Feb 28, 2018 at 10:05:55AM +0000, Tvrtko Ursulin wrote:
> > +/**
> > + * igt_fatal_error:
> > + *
> > + * Stop test execution or optionally, if the IGT_REBOOT_ON_FATAL_ERROR
> > + * environment variable is set, reboot the machine.
> > + *
> > + * Since out test runner (piglit) does support fatal test exit codes, we
> > + * implement the default behaviour by waiting endlessly.
> > + */
> > +void  __attribute__((noreturn)) igt_fatal_error(void)
> > +{
> > +     if (igt_check_boolean_env_var("IGT_REBOOT_ON_FATAL_ERROR", false)) {
> > +             igt_warn("FATAL ERROR - REBOOTING");
> > +             igt_sysrq_reboot();
> > +     } else {
> > +             igt_warn("FATAL ERROR");
> > +             for (;;)
> > +                     sleep(60);

s/sleep/pause/
-Chris
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  parent reply	other threads:[~2018-03-02 11:32 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-23 11:34 [PATCH i-g-t] tests/perf_pmu: Handle CPU hotplug failures better Tvrtko Ursulin
2018-02-23 11:34 ` [Intel-gfx] " Tvrtko Ursulin
2018-02-23 11:58 ` [igt-dev] " Petri Latvala
2018-02-23 11:58   ` Petri Latvala
2018-02-23 14:20   ` Tvrtko Ursulin
2018-02-23 14:20     ` [igt-dev] [Intel-gfx] " Tvrtko Ursulin
2018-02-26 10:03     ` [igt-dev] " Petri Latvala
2018-02-26 10:03       ` [igt-dev] [Intel-gfx] " Petri Latvala
2018-02-26 10:14       ` [igt-dev] " Tomi Sarvela
2018-02-26 10:14         ` [Intel-gfx] " Tomi Sarvela
2018-02-28 10:05         ` [PATCH i-g-t v2] " Tvrtko Ursulin
2018-02-28 10:05           ` [igt-dev] " Tvrtko Ursulin
2018-03-02 11:12           ` Petri Latvala
2018-03-02 11:12             ` [Intel-gfx] " Petri Latvala
2018-03-02 11:28             ` [PATCH i-g-t v3] " Tvrtko Ursulin
2018-03-02 11:28               ` [igt-dev] " Tvrtko Ursulin
2018-03-02 11:39               ` [PATCH i-g-t v4] " Tvrtko Ursulin
2018-03-02 11:39                 ` [igt-dev] " Tvrtko Ursulin
2018-03-02 11:42                 ` Chris Wilson
2018-03-02 11:42                   ` [igt-dev] " Chris Wilson
2018-03-02 11:55                   ` [PATCH i-g-t v5] " Tvrtko Ursulin
2018-03-02 11:55                     ` [igt-dev] " Tvrtko Ursulin
2018-03-02 11:32             ` Chris Wilson [this message]
2018-03-02 11:32               ` [igt-dev] [PATCH i-g-t v2] " Chris Wilson
2018-03-02 20:16             ` [igt-dev] ✓ Fi.CI.BAT: success for tests/perf_pmu: Handle CPU hotplug failures better (rev5) Patchwork
2018-03-02 23:33             ` [igt-dev] ✗ Fi.CI.IGT: warning " Patchwork
2018-02-23 12:37 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/perf_pmu: Handle CPU hotplug failures better Patchwork
2018-02-23 15:34 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2018-02-28 11:54 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/perf_pmu: Handle CPU hotplug failures better (rev2) Patchwork
2018-02-28 14:50 ` [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=151999034674.32001.17684398035555526277@mail.alporthouse.com \
    --to=chris@chris-wilson.co.uk \
    --cc=Intel-gfx@lists.freedesktop.org \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=petri.latvala@intel.com \
    --cc=tomi.p.sarvela@intel.com \
    --cc=tursulin@ursulin.net \
    /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.