From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 110514] [CI][BAT] igt@* - skip - Test requirement: is_i915_device(fd) && has_known_intel_chipset(fd), Skip
Date: Fri, 26 Apr 2019 10:55:56 +0000 [thread overview]
Message-ID: <bug-110514-502-o1ck3FCg5X@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-110514-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 742 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=110514
--- Comment #18 from Martin Peres <martin.peres@free.fr> ---
(In reply to Petri Latvala from comment #13)
> (In reply to CI Bug Log from comment #8)
> > The CI Bug Log issue associated to this bug has been updated.
> >
> > ### New filters associated
> >
> > * CML: igt@*stolen* - skip - Test requirement:
> > gem_create__has_stolen_support(fd) && (gem_total_stolen_size(fd)
> > > 0), SKIP
>
>
> This one is a different issue, isn't it?
More info from Petri: this should be a separate bug as it uses an ioctl call to
get this information, so this bug has nothing to do with it.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1880 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-26 10:55 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-110514-502@http.bugs.freedesktop.org/>
2019-04-25 12:38 ` [Bug 110514] [CI][BAT] igt@* - skip - Test requirement: is_i915_device(fd) && has_known_intel_chipset(fd), Skip bugzilla-daemon
2019-04-25 12:40 ` bugzilla-daemon
2019-04-25 13:09 ` bugzilla-daemon
2019-04-26 6:07 ` bugzilla-daemon
2019-04-26 6:31 ` bugzilla-daemon
2019-04-26 6:34 ` bugzilla-daemon
2019-04-26 7:45 ` bugzilla-daemon
2019-04-26 8:52 ` bugzilla-daemon
2019-04-26 8:56 ` bugzilla-daemon
2019-04-26 9:02 ` bugzilla-daemon
2019-04-26 9:32 ` bugzilla-daemon
2019-04-26 10:20 ` bugzilla-daemon
2019-04-26 10:21 ` bugzilla-daemon
2019-04-26 10:46 ` bugzilla-daemon
2019-04-26 10:46 ` bugzilla-daemon
2019-04-26 10:47 ` bugzilla-daemon
2019-04-26 10:47 ` bugzilla-daemon
2019-04-26 10:55 ` bugzilla-daemon [this message]
2019-04-29 7:55 ` bugzilla-daemon
2019-04-29 7:58 ` bugzilla-daemon
2019-04-29 7:58 ` bugzilla-daemon
2019-04-29 8:17 ` bugzilla-daemon
2019-04-30 8:03 ` bugzilla-daemon
2019-04-30 8:09 ` bugzilla-daemon
2019-07-08 8:56 ` 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-110514-502-o1ck3FCg5X@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.