| What | Removed | Added |
|---|---|---|
| Resolution | FIXED | --- |
| Status | RESOLVED | REOPENED |
| Summary | [CI] igt@prime_mmap_coherency@[write-and-fail|write] - fai - Failed assertion: !(!stale) | [CI] igt@prime_mmap_coherency@write - fail - Failed assertion: !(stale) |
Comment # 4
on bug 103168
from Marta Löfstedt
(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.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
