Created attachment 108156 [details] dmesg ==System Environment== -------------------------- Regression: Yes. It's a igt regression bug. Non-working platforms: BDW ==kernel== -------------------------- origin/drm-intel-nightly: 8d1dbeed28a28ecf964769bf089503f0c90ffdaa(fails) drm-intel-nightly: 2014y-10m-19d-14h-54m-38s UTC integration manifest origin/drm-intel-next-queued: 6476486cb3570d3662e4a3870b884e75d35d1072(fails) drm/i915: Document that mmap forwarding is discouraged origin/drm-intel-fixes: bfe01a5ba2490f299e1d2d5508cbbbadd897bbe9(fails) Linux 3.17 ==Bug detailed description== igt/kms_force_connector fails There has another bug 82230 about this case. Output: root@x-bdw05:/GFX/Test/Intel_gpu_tools/intel-gpu-tools/tests# ./kms_force_connector IGT-Version: 1.8-gbba1cd0 (x86_64) (Linux: 3.18.0-rc1_drm-intel-nightly_f2bcbc_20141021+ x86_64) Test requirement not met in function main, file kms_force_connector.c:58: Test requirement: vga_connector ==Reproduce steps== ---------------------------- 1. ./kms_force_connector ==Bisect results== ---------------------------- Bisect shows: e11b7100c9c8d4e74a4d4439b1519ea50741fda5 is the first bad commit commit e11b7100c9c8d4e74a4d4439b1519ea50741fda5 Author: Thomas Wood <thomas.wood@intel.com> AuthorDate: Thu Oct 9 16:44:12 2014 +0100 Commit: Thomas Wood <thomas.wood@intel.com> CommitDate: Wed Oct 15 11:01:37 2014 +0100 tests/kms_force_connect: skip if a VGA connector is not available v2: rename "connector" to "vga_connector" to improve the skip message (Chris Wilson) Suggested-by: Paulo Zanoni <paulo.r.zanoni@intel.com> Signed-off-by: Thomas Wood <thomas.wood@intel.com>
Why is this labeled as a regression? As far as I understand, we went from FAIL to SKIP. And on this specific case, it' s expected: this test will SKIP unless the machine has a VGA connector attached.
If it is skipping it doesn't look like a bug for me either.
Verified.
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.