From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 110580] [CI][BAT] igt@.* - skip - Chamelium ports not enabled
Date: Mon, 04 Nov 2019 13:18:06 +0000 [thread overview]
Message-ID: <bug-110580-502-UFrVsji0zm@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-110580-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1196 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=110580
Arek Hiler <arkadiusz.hiler@intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
QA Contact|intel-gfx-bugs@lists.freede |
|sktop.org |
Component|DRM/Intel |IGT
Assignee|intel-gfx-bugs@lists.freede |dri-devel@lists.freedesktop
|sktop.org |.org
--- Comment #61 from Arek Hiler <arkadiusz.hiler@intel.com> ---
Seems like the only way to get this under control is to make sure that
chamelium ports are plugged at the beginning of each test using displays.
This will add a lot of execution time:
1. XMLRPC calls + reprobing connectors
2. waiting for network to be up after suspend can take multiple seconds
This would only affect [idle runs] as we don't have Chamelium connected to any
of the shards (so it's a nop there), so it may be worth a shot.
Moving to IGT.
[idle runs]: https://intel-gfx-ci.01.org/#idle-runs
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2823 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 parent reply other threads:[~2019-11-04 13:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-110580-502@http.bugs.freedesktop.org/>
2019-11-04 13:18 ` bugzilla-daemon [this message]
2019-11-08 9:45 ` [Bug 110580] [CI][BAT] igt@.* - skip - Chamelium ports not enabled 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-110580-502-UFrVsji0zm@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