From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 110313] [CI][SHARDS] igt@kms_lease@lease-uevent - fail - Failed assertion: igt_lease_change_detected(uevent_monitor, 1)
Date: Thu, 25 Apr 2019 08:08:39 +0000 [thread overview]
Message-ID: <bug-110313-502-M9TXyS1Hza@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-110313-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 695 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=110313
--- Comment #4 from Daniel Vetter <daniel@ffwll.ch> ---
(In reply to Arek Hiler from comment #3)
> This seems like a test deficiency. We are polling on udev monitor FD in
> anticipation of an events. According the the log linked in the previous
> comments we get EAGAIN (11), but we do not retry.
We already retry when we get EAGAIN, but then eventually give up. So the EAGAIN
errno is kinda expected.
The timeout right now is 1 second, which really should be enough to deliver an
uevent. Maybe the box is totally overloaded or something like that.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1692 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-04-25 8:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-110313-502@http.bugs.freedesktop.org/>
2019-04-15 12:31 ` [Bug 110313] [CI][SHARDS] igt@kms_lease@lease-uevent - fail - Failed assertion: igt_lease_change_detected(uevent_monitor, 1) bugzilla-daemon
2019-04-25 8:08 ` bugzilla-daemon [this message]
2019-06-07 11:05 ` bugzilla-daemon
2019-06-10 5:43 ` bugzilla-daemon
2019-11-12 7:40 ` 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-110313-502-M9TXyS1Hza@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;
as well as URLs for NNTP newsgroup(s).