igt@gem_streaming_writes@batch-gtt igt@gem_streaming_writes@batch-reverse-gtt igt@gem_streaming_writes@batch-reverse-wc igt@gem_streaming_writes@batch-wc igt@gem_streaming_writes@cpu igt@gem_streaming_writes@cpu-sync igt@gem_streaming_writes@gtt igt@gem_streaming_writes@gtt-sync igt@gem_streaming_writes@wc igt@gem_streaming_writes@wc-sync eg: http://intel-gfx-ci.fi.intel.com/archive/results/CI_IGT_test/igt@gem_streaming_writes@batch-gtt.html
Reopening since it looks like this is not yet fix (still some test failures) nittin.rituraj@gmail.com, can you elaborate the reason why you think this is fixed?
What test failures? Don't confuse an incomplete (this bug) with a failure or a CI enforced timeout.
(In reply to Chris Wilson from comment #2) > What test failures? Don't confuse an incomplete (this bug) with a failure or > a CI enforced timeout. First of all, bug must not be closed w/o any explanation or justification. This is what it is happening here. Then this is correct that we have still various issue types linked to these test runs (not just going to the example that Jani is pointing out: batch-gtt) and to be accurate, avoid confusion, I agree with you, "Incomplete" state must be clearly defined to not misinterpret results.
Assuming that these incompletes were the irq bugs fixed about the same time as these were filed.
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.