From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 102242] [CI] assert(level < 128) failed for igt@pm_rpm@sysfs-read
Date: Fri, 01 Sep 2017 11:05:22 +0000 [thread overview]
Message-ID: <bug-102242-502-zKz4EePIOX@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-102242-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1066 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=102242
Jari Tahvanainen <jari.tahvanainen@intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
QA Contact|intel-gfx-bugs@lists.freede |
|sktop.org |
Assignee|intel-gfx-bugs@lists.freede |dri-devel@lists.freedesktop
|sktop.org |.org
Component|DRM/Intel |IGT
--- Comment #6 from Jari Tahvanainen <jari.tahvanainen@intel.com> ---
Tested-by/SKL: I see the same improvement (FAIL -> SUCCESS) with igt+series
(https://patchwork.freedesktop.org/series/29141/) used on latest drm-tip kernel
drm-tip: "2017y-08m-30d-08h-12m-34s UTC integration manifest".
Looping ./pm_rpm --r sysfs-read thousand times resulted all
Subtest sysfs-read: SUCCESS (0,1..s).
Moving to IGT component since fixing is done there...
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2761 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:[~2017-09-01 11:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-102242-502@http.bugs.freedesktop.org/>
2017-09-01 11:05 ` bugzilla-daemon [this message]
2017-09-06 18:07 ` [Bug 102242] [CI] assert(level < 128) failed for igt@pm_rpm@sysfs-read bugzilla-daemon
2017-09-07 7:48 ` 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-102242-502-zKz4EePIOX@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