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_m... which is after the patch was merged.