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 (rev3)
Date: Fri, 7 May 2021 13:09:20 +0200 [thread overview]
Message-ID: <84dce7f8-bd93-6a51-9c40-b50b24744cde@redhat.com> (raw)
In-Reply-To: <162031509542.15692.3870747553948271057@emeril.freedesktop.org>
Hi,
On 5/6/21 5:31 PM, Patchwork wrote:
> *Patch Details*
> *Series:* drm + usb-type-c: Add support for out-of-band hotplug notification (rev3)
> *URL:* https://patchwork.freedesktop.org/series/89604/ <https://patchwork.freedesktop.org/series/89604/>
> *State:* failure
> *Details:* https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20068/index.html <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20068/index.html>
>
>
> CI Bug Log - changes from CI_DRM_10049_full -> Patchwork_20068_full
>
>
> Summary
>
> *FAILURE*
>
> Serious unknown changes coming with Patchwork_20068_full absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_20068_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_20068_full:
>
>
> Piglit changes
>
>
> Possible regressions
>
> * shaders@glsl-fs-texturecube-2 (NEW):
> o pig-skl-6260u: NOTRUN -> INCOMPLETE <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20068/pig-skl-6260u/shaders@glsl-fs-texturecube-2.html> +4 similar issues
This seems to be another false-positive as mentioned already this series does
not touch any 3d rendering related code (it only touches modesetting code).
Regards,
Hans
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2021-05-07 11:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-05 16:24 [Intel-gfx] [PATCH 0/8] drm + usb-type-c: Add support for out-of-band hotplug notification (v3) Hans de Goede
2021-05-05 16:24 ` [Intel-gfx] [PATCH 1/8] drm/connector: Give connector sysfs devices there own device_type Hans de Goede
2021-05-05 16:24 ` [Intel-gfx] [PATCH 2/8] drm/connector: Add a fwnode pointer to drm_connector and register with ACPI (v2) Hans de Goede
2021-05-05 16:24 ` [Intel-gfx] [PATCH 3/8] drm/connector: Add drm_connector_find_by_fwnode() function (v2) Hans de Goede
2021-05-05 16:24 ` [Intel-gfx] [PATCH 4/8] drm/connector: Add support for out-of-band hotplug notification (v3) Hans de Goede
2021-05-05 16:24 ` [Intel-gfx] [PATCH 5/8] drm/i915: Associate ACPI connector nodes with connector entries (v2) Hans de Goede
2021-05-05 16:24 ` [Intel-gfx] [PATCH 6/8] drm/i915/dp: Add support for out-of-bound hotplug events Hans de Goede
2021-05-05 16:24 ` [Intel-gfx] [PATCH 7/8] usb: typec: altmodes/displayport: Make dp_altmode_notify() more generic Hans de Goede
2021-05-11 6:55 ` Heikki Krogerus
2021-05-05 16:24 ` [Intel-gfx] [PATCH 8/8] usb: typec: altmodes/displayport: Notify drm subsys of hotplug events Hans de Goede
2021-05-11 6:56 ` Heikki Krogerus
2021-05-05 16:38 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm + usb-type-c: Add support for out-of-band hotplug notification (rev3) Patchwork
2021-05-05 17:04 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-05-05 19:14 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2021-05-06 8:53 ` Hans de Goede
2021-05-06 15:31 ` Patchwork
2021-05-07 11:09 ` Hans de Goede [this message]
2021-05-11 7:05 ` [Intel-gfx] [PATCH 0/8] drm + usb-type-c: Add support for out-of-band hotplug notification (v3) Heikki Krogerus
2021-05-21 11:41 ` Heikki Krogerus
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=84dce7f8-bd93-6a51-9c40-b50b24744cde@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