Bug 92320 - [BSW] piglit tests intermittently/randomly fail when running concurrently
Summary: [BSW] piglit tests intermittently/randomly fail when running concurrently
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: git
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Mark Janes
QA Contact: Intel 3D Bugs Mailing List
Depends on:
Reported: 2015-10-06 18:55 UTC by Mark Janes
Modified: 2019-09-25 18:54 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

disable fast clear (807 bytes, text/plain)
2015-10-13 22:23 UTC, Mark Janes

Description Mark Janes 2015-10-06 18:55:52 UTC
On linux 4.2.0, random piglit failures occur when running concurrently.

Changing to serial execution eliminates the failures, leaving aside the occasional gpu hang.

This behavior needs more investigation to verify that 
 * the list of failures is indeed unstable/random
 * disabling tests has no effect on the failures.
Comment 1 Mark Janes 2015-10-12 17:12:47 UTC
confirmed flaky tests:

Comment 2 Mark Janes 2015-10-12 19:24:20 UTC
additional flaky test:

Comment 3 Mark Janes 2015-10-13 22:23:51 UTC
Created attachment 118862 [details]
disable fast clear
Comment 4 Mark Janes 2015-10-13 22:24:21 UTC
attached patch resolves instability by disabling fast clear.
Comment 5 Ben Widawsky 2015-10-14 03:25:14 UTC
The attached patch should only disable MSAA compression, not single sample fast clears.
Comment 6 Ben Widawsky 2015-10-15 22:25:17 UTC
I ran piglit in a loop 8 times and got these intermittent failures (excludes glsl-routing):

spec/arb_texture_multisample/texelfetch fs sampler2dms 4 1x130-501x130
Comment 7 Ben Widawsky 2015-10-22 18:34:22 UTC
Assigning to Mark to cleanup and send the patch.
Comment 8 Mark Janes 2015-10-23 22:50:31 UTC
In testing my patch, I found that intermittent failures persisted.  sigh.
Comment 9 Mark Janes 2015-11-11 18:19:22 UTC
I updated to Linux 4.3 and saw no improvement to this behavior.
Comment 10 Denis 2019-03-13 12:01:20 UTC
hi Mark, could you please review my results and confirm them?
My configuration:
Kernel - 4.20.14-200
OS - Fedora 29
Mesa - 18.3.4 (system, from repository)
GPU - HD Graphics 400 (Braswell)

passed in CI
didn't find locally

./depthstencil-render-miplevels 1024 ds=z24_s8 -auto 
passed locally and in CI

passed in CI
didn't find test locally

didn't find in CI
./ext_framebuffer_multisample-multisample-blit 4 color -auto
ran 100 times in a loop - passed locally

passed in CI
didn't find locally

passed in CI
didn't find locally

passed in CI
didn't find locally

passed in CI
didn't find locally

To summarize, looks like most of the tests are stable now. And I didn't find in CI this one - ext_framebuffer_multisample.multisample-blit.4.color, maybe it was disabled?
Comment 11 Mark Janes 2019-03-13 15:29:44 UTC
Mesa i965 CI is not a useful tool for investigating this bug.  Sadly, we punted on this issue 4 years ago, and I have to re-execute all bsw tests that fail at the end of a CI run, to verify that they did not fail due to this bug.

So every BSW failure reported by CI has in fact failed *twice* in the run.

My expectation is that the platform is not properly enabled, leading to these instabilities.  See comment 6 in bug 108787.  Perhaps there is some workaround missing, in addition to the mishandled resource constraint that Ken describes.

BSW has less customer relevance than even SNB, because it did not sell well.  As far as I know, Intel CI is the only source of bugs for the platform, because no one else has them.  I'd love for the bugs to get fixed, but they should probably be prioritized lower than the bugs that are known to impact customers (eg 104778).
Comment 12 GitLab Migration User 2019-09-25 18:54:49 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/1497.

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.