Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Patchwork <patchwork@emeril.freedesktop.org>,
	LGCI Bug Filing <lgci.bug.filing@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: ✓ Fi.CI.BAT: success for drm/i915: nomodeset and i915.modeset cleanups (rev2)
Date: Thu, 29 Aug 2024 14:49:54 +0300	[thread overview]
Message-ID: <87r0a7wntp.fsf@intel.com> (raw)
In-Reply-To: <172485475830.827467.7681242890043675648@2413ebb6fbb6>

On Wed, 28 Aug 2024, Patchwork <patchwork@emeril.freedesktop.org> wrote:
> == Series Details ==
>
> Series: drm/i915: nomodeset and i915.modeset cleanups (rev2)
> URL   : https://patchwork.freedesktop.org/series/137909/
> State : success
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_15308 -> Patchwork_137909v2
> ====================================================
>
> Summary
> -------
>
>   **SUCCESS**
>
>   No regressions found.
>
>   External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_137909v2/index.html

BAT passed, but no shard results, and it's not in the queue either?

BR,
Jani.


>
> Participating hosts (39 -> 36)
> ------------------------------
>
>   Missing    (3): bat-dg2-11 fi-snb-2520m fi-kbl-8809g 
>
> Known issues
> ------------
>
>   Here are the changes found in Patchwork_137909v2 that come from known issues:
>
> ### IGT changes ###
>
> #### Warnings ####
>
>   * igt@fbdev@read:
>     - bat-arls-1:         [DMESG-WARN][1] ([i915#9157]) -> [DMESG-FAIL][2] ([i915#9157])
>    [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15308/bat-arls-1/igt@fbdev@read.html
>    [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_137909v2/bat-arls-1/igt@fbdev@read.html
>
>   
>   [i915#9157]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/9157
>
>
> Build changes
> -------------
>
>   * Linux: CI_DRM_15308 -> Patchwork_137909v2
>
>   CI-20190529: 20190529
>   CI_DRM_15308: 3d18c558b87ad1c2d6d59ea1c56603a01e84ab88 @ git://anongit.freedesktop.org/gfx-ci/linux
>   IGT_7993: 3b6b2d238e864ff1af9e33159d3bbf4b7f01d86d @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
>   Patchwork_137909v2: 3d18c558b87ad1c2d6d59ea1c56603a01e84ab88 @ git://anongit.freedesktop.org/gfx-ci/linux
>
> == Logs ==
>
> For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_137909v2/index.html

-- 
Jani Nikula, Intel

  reply	other threads:[~2024-08-29 11:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-28 11:19 [PATCH 0/2] drm/i915: nomodeset and i915.modeset cleanups Jani Nikula
2024-08-28 11:19 ` [PATCH 1/2] drm/i915: fail module probe on nomodeset and i915.modeset=0 Jani Nikula
2024-08-28 11:19 ` [PATCH 2/2] drm/i915: deprecate the i915.modeset module parameter Jani Nikula
2024-08-28 11:55 ` ✗ Fi.CI.BAT: failure for drm/i915: nomodeset and i915.modeset cleanups Patchwork
2024-08-28 12:42 ` [PATCH 0/2] " Daniel Vetter
2024-08-28 14:19 ` ✓ Fi.CI.BAT: success for drm/i915: nomodeset and i915.modeset cleanups (rev2) Patchwork
2024-08-29 11:49   ` Jani Nikula [this message]
2024-08-29 11:56     ` Musial, Ewelina
2024-08-29 12:48 ` ✗ Fi.CI.IGT: failure " Patchwork

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=87r0a7wntp.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=lgci.bug.filing@intel.com \
    --cc=patchwork@emeril.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