From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 108073] [CI][SHARDS] igt@gem_cpu_reloc@full - incomplete
Date: Mon, 26 Nov 2018 20:54:19 +0000 [thread overview]
Message-ID: <bug-108073-502-F8G3yZEzsO@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-108073-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1118 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=108073
Chris Wilson <chris@chris-wilson.co.uk> changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|normal |blocker
Priority|high |highest
--- Comment #2 from Chris Wilson <chris@chris-wilson.co.uk> ---
Looking further, it's quite a serious bug.
<7>[ 268.714297] [IGT] gem_cpu_reloc: executing
<7>[ 268.789099] [IGT] gem_cpu_reloc: starting subtest full
yet
[30/79] ( 882s left) gem_cpu_reloc (full)
Child refuses to die. Aborting.
Warning: Cannot open result directory 30
Starting subtest: full
Timeout. Killing the current test with SIGTERM.
Timeout. Killing the current test with SIGKILL.
Closing watchdogs
Closing watchdogs
Done.
So it tried to kill the child before any timeout, even before it began
executing the subtest, i.e <70ms. And closed the watchdogs twice.
Fork() gone astray?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2590 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 prev parent reply other threads:[~2018-11-26 20:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-108073-502@http.bugs.freedesktop.org/>
2018-11-21 20:52 ` [Bug 108073] [CI][SHARDS] igt@gem_cpu_reloc@full - incomplete bugzilla-daemon
2018-11-26 20:54 ` bugzilla-daemon [this message]
2018-11-27 9:41 ` bugzilla-daemon
2018-11-27 9:43 ` bugzilla-daemon
2019-02-19 8:21 ` 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-108073-502-F8G3yZEzsO@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