Summary: | [all]igt/gem_concurrent_blit takes 42 hrs | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | DRI | Reporter: | lu hua <huax.lu> | ||||||||
Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||||
Status: | CLOSED FIXED | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||||
Severity: | normal | ||||||||||
Priority: | medium | CC: | intel-gfx-bugs | ||||||||
Version: | unspecified | ||||||||||
Hardware: | All | ||||||||||
OS: | Linux (All) | ||||||||||
Whiteboard: | |||||||||||
i915 platform: | i915 features: | ||||||||||
Attachments: |
|
Description
lu hua
2015-03-09 07:56:24 UTC
Created attachment 114148 [details]
test log
It has 3780 sub cases on the latest igt. commit 7763349a9a878ca58de4fb559edcbf81040da07b Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Thu Mar 26 08:11:43 2015 +0000 igt/gem_concurrent_blit: Separate out the combinatorial explosion Apparently nobody else likes testing and debugging GEM coherency issues. However, this also means that QA is skipping these vital tests. Split out a set of canaries into igt/gem_concurrent_blit and keep the rest in igt/gem_concurrent_all. Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=89497 Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> I will run full gem_concurrent_all subcases. Test on SNB with the latest -nightly kernel, 75 cases take 3 hr, 3780 cases will take 151 hr. Test on HSW with the latest -fixes kernel, 96 cases take 6hr45m(some case cause system hang, so takes more time than SNB), 3780 cases will take 265 hr. Created attachment 114752 [details]
75 cases test log on SNB
If you don't want to run all the test cases, don't run all the test cases! You complained about there being too many, so gem_concurrent_blit now only has a select few at the expense of not being complete. gem_concurrent_blit has 168 subcases, they take 42 minutes on BSW. Close it. Closing old verified. |
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.