Bug 102066 - [BAT][BXT] igt@prime_vgem@basic-gtt failed
Summary: [BAT][BXT] igt@prime_vgem@basic-gtt failed
Status: CLOSED DUPLICATE of bug 102577
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: DRI git
Hardware: Other All
: high critical
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard: ReadyForDev
Keywords:
Depends on:
Blocks:
 
Reported: 2017-08-07 09:08 UTC by Martin Peres
Modified: 2017-09-07 20:20 UTC (History)
1 user (show)

See Also:
i915 platform: BXT
i915 features: GEM/Other

Attachments

Description Martin Peres 2017-08-07 09:08:19 UTC 
On CI_DRM_2924, the test igt@prime_vgem@basic-gtt failed on the machine fi-bxt-j4205:
	
(prime_vgem:4787) CRITICAL: Test assertion failure function test_gtt, file prime_vgem.c:241:
(prime_vgem:4787) CRITICAL: Failed assertion: ptr[1024*i] == i
(prime_vgem:4787) CRITICAL: error: -771 != 770
Subtest basic-gtt failed.

Full logs: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_2924/fi-bxt-j4205/igt@prime_vgem@basic-gtt.html
Comment 1 Chris Wilson 2017-08-07 09:12:31 UTC 
That's expected to fail as bxt is not as coherent as we advertised.
Comment 2 Martin Peres 2017-08-07 09:14:20 UTC 
(In reply to Chris Wilson from comment #1)
> That's expected to fail as bxt is not as coherent as we advertised.

Good to know, but this means this bug will stay open forever then. Are we OK with that?

Can we instead accept a certain amount of failures for this test for BXT, so as we can catch more dramatic regressions?
Comment 3 Chris Wilson 2017-08-07 09:35:10 UTC 
It's an expected failure for a certain class of machines. There is no mechanism within igt to mark those up, so we rely on filtering the results.
Comment 4 Jani Saarinen 2017-09-01 08:13:09 UTC 
Lets drop priority as seen yet only once:
failure rate of 1 / 96 runs (1 %)
Comment 5 Chris Wilson 2017-09-07 19:37:56 UTC 

*** This bug has been marked as a duplicate of bug 102577 ***

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.