Patch Details
Series:series starting with [i-g-t,1/6] tests/kms_invalid_dotclock: Rename to kms_invalid_mode
URL:https://patchwork.freedesktop.org/series/94768/
State:failure
Details:https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6233/index.html

CI Bug Log - changes from CI_DRM_10598 -> IGTPW_6233

Summary

FAILURE

Serious unknown changes coming with IGTPW_6233 absolutely need to be
verified manually.

If you think the reported changes have nothing to do with the changes
introduced in IGTPW_6233, please notify your bug team to allow them
to document this new failure mode, which will reduce false positives in CI.

External URL: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6233/index.html

Possible new issues

Here are the unknown changes that may have been introduced in IGTPW_6233:

IGT changes

Possible regressions

Known issues

Here are the changes found in IGTPW_6233 that come from known issues:

IGT changes

Issues hit

Possible fixes

Warnings

{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).

Participating hosts (37 -> 34)

Missing (3): fi-bsw-cyan fi-cfl-8109u fi-bdw-samus

Build changes

CI-20190529: 20190529
CI_DRM_10598: 5b7e720d97fd94cf081daec8f9d09753cfbe1c31 @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_6233: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6233/index.html
IGT_6211: 7b275b3eb17ddf6e7c5b7b9ba359b7f5345a5311 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git

== Testlist changes ==

+igt@kms_invalid_mode@bad-hsync-end
+igt@kms_invalid_mode@bad-hsync-start
+igt@kms_invalid_mode@bad-htotal
+igt@kms_invalid_mode@bad-vsync-end
+igt@kms_invalid_mode@bad-vsync-start
+igt@kms_invalid_mode@bad-vtotal
+igt@kms_invalid_mode@clock-too-high
+igt@kms_invalid_mode@int-max-clock
+igt@kms_invalid_mode@uint-max-clock
+igt@kms_invalid_mode@zero-clock
+igt@kms_invalid_mode@zero-hdisplay
+igt@kms_invalid_mode@zero-vdisplay
-igt@kms_invalid_dotclock