From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 108763] [CI] Make IGT_runner exit with an error code != 0 when aborting
Date: Fri, 16 Nov 2018 14:06:39 +0000 [thread overview]
Message-ID: <bug-108763-502-KRKCMMP0dc@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-108763-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1013 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=108763
Martin Peres <martin.peres@free.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|intel-gfx-bugs@lists.freede |dri-devel@lists.freedesktop
|sktop.org |.org
QA Contact|intel-gfx-bugs@lists.freede |
|sktop.org |
Summary|[CI][SHARDS] shard-iclb6 |[CI] Make IGT_runner exit
|dies on boot without giving |with an error code != 0
|out its precious logs |when aborting
Component|DRM/Intel |IGT
--- Comment #1 from Martin Peres <martin.peres@free.fr> ---
Right now, our shards do not reboot after the kernel got tainted because it
cannot know if the execution of IGT went well or not.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2679 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next parent reply other threads:[~2018-11-16 14:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-108763-502@http.bugs.freedesktop.org/>
2018-11-16 14:06 ` bugzilla-daemon [this message]
2018-11-16 14:40 ` [Bug 108763] [CI] Make IGT_runner exit with an error code != 0 when aborting bugzilla-daemon
2018-11-20 12:06 ` bugzilla-daemon
2019-01-04 15:39 ` bugzilla-daemon
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=bug-108763-502-KRKCMMP0dc@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox