Bug 100313

Summary:	[BAT][BYT] igt@gem_exec_basic@gtt-default timed out on fi-byt-j1900 in CI
Product:	DRI	Reporter:	Martin Peres <martin.peres>
Component:	DRM/Intel	Assignee:	Intel GFX Bugs mailing list <intel-gfx-bugs>
Status:	CLOSED DUPLICATE	QA Contact:	Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity:	normal
Priority:	highest	CC:	intel-gfx-bugs
Version:	DRI git
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:	BYT	i915 features:	GEM/execlists

Description Martin Peres 2017-03-22 08:31:30 UTC

The machine got completely hung while running this test. Nothing interesting in the logs other than that.

Here are the raw results: https://intel-gfx-ci.01.org/CI/CI_DRM_2384/fi-byt-j1900/igt@gem_exec_basic@gtt-default.html

And here are the igt logs, showing that the CI system failed to connect to the machine to stop the job: https://intel-gfx-ci.01.org/CI/CI_DRM_2384/fi-byt-j1900/igt.log

Comment 1 Jani Saarinen 2017-03-22 09:28:00 UTC

just documenting. Still seen:
https://intel-gfx-ci.01.org/CI/CI_DRM_2384/fi-byt-j1900/igt@gem_exec_basic@gtt-default.html

Comment 2 Martin Peres 2017-03-23 10:00:20 UTC

Raising the priority, because it reduces our code coverage. It only happened once though :s

Comment 3 Jani Saarinen 2017-03-28 12:48:37 UTC

just document that also gem_exec_basic@gtt-bsd incompleted (fdo#100429)

Comment 4 Martin Peres 2017-03-29 08:13:15 UTC

Same symptoms on igt@gem_busy@basic-busy-default (CI_DRM_2421) and igt@gem_exec_store@basic-vebox (CI_DRM_2418).

Links: 
 - https://intel-gfx-ci.01.org/CI/CI_DRM_2418/fi-byt-j1900/igt@gem_exec_store@basic-vebox.html
 - https://intel-gfx-ci.01.org/CI/CI_DRM_2421/fi-byt-j1900/igt@gem_busy@basic-busy-default.html

Comment 5 Mika Kuoppala 2017-04-05 11:08:24 UTC


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

Comment 6 Ricardo 2017-06-27 15:20:05 UTC

original issue is solved and now closing - Cleaning our bug BD from resolved

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.