From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 103168] [CI] igt@prime_mmap_coherency@write - fail - Failed assertion: !(stale)
Date: Wed, 18 Oct 2017 13:58:40 +0000 [thread overview]
Message-ID: <bug-103168-502-TFrREcfnZl@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-103168-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1859 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=103168
Marta Löfstedt <marta.lofstedt@intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|FIXED |---
Status|RESOLVED |REOPENED
Summary|[CI] |[CI]
|igt@prime_mmap_coherency@[w |igt@prime_mmap_coherency@wr
|rite-and-fail|write] - fai |ite - fail - Failed
|- Failed assertion: |assertion: !(stale)
|!(!stale) |
--- Comment #4 from Marta Löfstedt <marta.lofstedt@intel.com> ---
(In reply to Chris Wilson from comment #3)
> Test removed in
>
> commit 22fdae38cbad3794a315bfd8d9fd833eba4a35dc
> Author: Chris Wilson <chris@chris-wilson.co.uk>
> Date: Wed Oct 11 10:51:22 2017 +0100
>
> igt/prime_mmap_coherency: Only assert correct usage of sync API
>
> Ignore the unexpected success when the CPU cache is randomly flushed
> that makes !llc appear to work without sync. It happens, the cpu cache
> is a fickle beast that we do not have sole control over. Instead limit
> the test to detect failures when the API is being adhered to.
>
I agree that:
igt@prime_mmap_coherency@write-and-fail
is skipped from CI_DRM_3254 on APL-shards. However, before I realized this I
had already filed igt@prime_mmap_coherency@write for GLK-shards on this bug.
The currently latest occurrence of igt@prime_mmap_coherency@write issue is on:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3256/shard-glkb3/igt@prime_mmap_coherency@write.html
which is after the patch was merged.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3755 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:[~2017-10-18 13:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-103168-502@http.bugs.freedesktop.org/>
2017-10-09 12:56 ` [Bug 103168] [CI] igt@prime_mmap_coherency@write-and-fail - fai - Failed assertion: !(!stale) bugzilla-daemon
2017-10-11 9:42 ` bugzilla-daemon
2017-10-11 9:42 ` bugzilla-daemon
2017-10-18 11:08 ` [Bug 103168] [CI] igt@prime_mmap_coherency@[write-and-fail|write] " bugzilla-daemon
2017-10-18 11:15 ` bugzilla-daemon
2017-10-18 13:58 ` bugzilla-daemon [this message]
2017-12-08 7:52 ` [Bug 103168] [CI] igt@prime_mmap_coherency@write - fail - Failed assertion: !(stale) bugzilla-daemon
2017-12-08 7:52 ` 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-103168-502-TFrREcfnZl@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