From: Hans de Goede <hdegoede@redhat.com>
To: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm + usb-type-c: Add support for out-of-band hotplug notification (v4 resend)
Date: Wed, 18 Aug 2021 21:54:28 +0200 [thread overview]
Message-ID: <b1f7c3b2-2dd7-791b-bcaa-615f3d55bdf5@redhat.com> (raw)
In-Reply-To: <162924530163.16675.12698639172189836634@emeril.freedesktop.org>
Hi,
On 8/18/21 2:08 AM, Patchwork wrote:
> *Patch Details*
> *Series:* drm + usb-type-c: Add support for out-of-band hotplug notification (v4 resend)
> *URL:* https://patchwork.freedesktop.org/series/93762/ <https://patchwork.freedesktop.org/series/93762/>
> *State:* failure
> *Details:* https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20838/index.html <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20838/index.html>
>
>
> CI Bug Log - changes from CI_DRM_10491_full -> Patchwork_20838_full
>
>
> Summary
>
> *FAILURE*
>
> Serious unknown changes coming with Patchwork_20838_full absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_20838_full, please notify your bug team to allow them
> to document this new failure mode, which will reduce false positives in CI.
>
>
> Possible new issues
>
> Here are the unknown changes that may have been introduced in Patchwork_20838_full:
>
>
> IGT changes
>
>
> Possible regressions
>
> *
>
> igt@i915_pm_backlight@bad-brightness:
>
> o shard-iclb: PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10491/shard-iclb4/igt@i915_pm_backlight@bad-brightness.html> -> INCOMPLETE <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20838/shard-iclb4/igt@i915_pm_backlight@bad-brightness.html>
> *
>
> igt@sysfs_heartbeat_interval@mixed@vcs0:
>
> o shard-skl: PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10491/shard-skl2/igt@sysfs_heartbeat_interval@mixed@vcs0.html> -> WARN <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20838/shard-skl9/igt@sysfs_heartbeat_interval@mixed@vcs0.html>
I believe that these both are false-positives. This patch-set has little to
do with either test; and this is a rebased (with no changes) resend of
a version which did pass CI before.
Regards,
Hans
next prev parent reply other threads:[~2021-08-18 19:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-17 21:51 [Intel-gfx] [PATCH 0/8] drm + usb-type-c: Add support for out-of-band hotplug notification (v4 resend) Hans de Goede
2021-08-17 21:51 ` [Intel-gfx] [PATCH 1/8] drm/connector: Give connector sysfs devices there own device_type Hans de Goede
2021-08-18 21:35 ` Lyude Paul
2021-08-17 21:51 ` [Intel-gfx] [PATCH 2/8] drm/connector: Add a fwnode pointer to drm_connector and register with ACPI (v2) Hans de Goede
2021-08-17 21:51 ` [Intel-gfx] [PATCH 3/8] drm/connector: Add drm_connector_find_by_fwnode() function (v3) Hans de Goede
2021-08-17 21:51 ` [Intel-gfx] [PATCH 4/8] drm/connector: Add support for out-of-band hotplug notification (v3) Hans de Goede
2021-08-17 21:51 ` [Intel-gfx] [PATCH 5/8] drm/i915: Associate ACPI connector nodes with connector entries (v2) Hans de Goede
2025-05-23 9:28 ` Jani Nikula
2025-05-23 14:52 ` Heikki Krogerus
2025-05-26 10:24 ` Jani Nikula
2021-08-17 21:51 ` [Intel-gfx] [PATCH 6/8] drm/i915/dp: Add support for out-of-bound hotplug events Hans de Goede
2021-08-17 21:52 ` [Intel-gfx] [PATCH 7/8] usb: typec: altmodes/displayport: Make dp_altmode_notify() more generic Hans de Goede
2021-08-17 21:52 ` [Intel-gfx] [PATCH 8/8] usb: typec: altmodes/displayport: Notify drm subsys of hotplug events Hans de Goede
2021-09-16 3:20 ` Stephen Boyd
2021-09-16 13:17 ` Hans de Goede
2021-09-24 23:29 ` Stephen Boyd
2021-08-17 22:08 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm + usb-type-c: Add support for out-of-band hotplug notification (v4 resend) Patchwork
2021-08-17 22:35 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-08-18 0:08 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2021-08-18 19:54 ` Hans de Goede [this message]
2021-08-18 22:03 ` [Intel-gfx] [PATCH 0/8] " Lyude Paul
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b1f7c3b2-2dd7-791b-bcaa-615f3d55bdf5@redhat.com \
--to=hdegoede@redhat.com \
--cc=intel-gfx@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox