Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: "Musial, Ewelina" <ewelina.musial@intel.com>,
	Patchwork <patchwork@emeril.freedesktop.org>,
	LGCI Bug Filing <lgci.bug.filing@intel.com>,
	"Grabski, Mateusz" <mateusz.grabski@intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>
Subject: Re: ✓ Fi.CI.BAT: success for drm/i915: BXT/GLK per-lane vswing and PHY reg cleanup (rev3)
Date: Fri, 19 Apr 2024 19:56:53 +0300	[thread overview]
Message-ID: <ZiKiVQ0WHfRCi2pY@intel.com> (raw)
In-Reply-To: <87cyqlwy72.fsf@intel.com>

On Fri, Apr 19, 2024 at 11:31:29AM +0300, Jani Nikula wrote:
> 
> Got the results in the middle of the night; Ville, please merge. :)

Unfortunately GLK was AWOL at the time, so we didn't actually test
anything :( I've hit the retest button for good measure.

> 
> BR,
> Jani.
> 
> On Fri, 19 Apr 2024, "Musial, Ewelina" <ewelina.musial@intel.com> wrote:
> > + @Grabski, Mateusz please check it 
> >
> > Thanks,
> > Ewelina
> >
> > -----Original Message-----
> > From: Jani Nikula <jani.nikula@linux.intel.com> 
> > Sent: Thursday, April 18, 2024 6:41 PM
> > To: Patchwork <patchwork@emeril.freedesktop.org>; Ville Syrjala <ville.syrjala@linux.intel.com>; LGCI Bug Filing <lgci.bug.filing@intel.com>
> > Cc: intel-gfx@lists.freedesktop.org
> > Subject: Re: ✓ Fi.CI.BAT: success for drm/i915: BXT/GLK per-lane vswing and PHY reg cleanup (rev3)
> >
> > On Wed, 17 Apr 2024, Patchwork <patchwork@emeril.freedesktop.org> wrote:
> >> == Series Details ==
> >>
> >> Series: drm/i915: BXT/GLK per-lane vswing and PHY reg cleanup (rev3)
> >> URL   : https://patchwork.freedesktop.org/series/132390/
> >> State : success
> >>
> >> == Summary ==
> >>
> >> CI Bug Log - changes from CI_DRM_14597 -> Patchwork_132390v3 
> >> ====================================================
> >>
> >> Summary
> >> -------
> >>
> >>   **SUCCESS**
> >>
> >>   No regressions found.
> >>
> >>   External URL: 
> >> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_132390v3/index.html
> >
> > What happened here? BAT passed, but there are no IGT results, and the shards queue is empty?
> >
> > BR,
> > Jani.
> >
> >
> >>
> >> Participating hosts (38 -> 32)
> >> ------------------------------
> >>
> >>   Missing    (6): bat-dg1-7 fi-snb-2520m fi-glk-j4005 fi-kbl-8809g bat-dg2-11 bat-arls-3 
> >>
> >> Known issues
> >> ------------
> >>
> >>   Here are the changes found in Patchwork_132390v3 that come from known issues:
> >>
> >> ### IGT changes ###
> >>
> >> #### Issues hit ####
> >>
> >>   * igt@i915_selftest@live@gem:
> >>     - bat-dg2-9:          [PASS][1] -> [ABORT][2] ([i915#10366])
> >>    [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_14597/bat-dg2-9/igt@i915_selftest@live@gem.html
> >>    [2]: 
> >> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_132390v3/bat-dg2-9/
> >> igt@i915_selftest@live@gem.html
> >>
> >>   
> >>   [i915#10366]: https://gitlab.freedesktop.org/drm/intel/issues/10366
> >>
> >>
> >> Build changes
> >> -------------
> >>
> >>   * Linux: CI_DRM_14597 -> Patchwork_132390v3
> >>
> >>   CI-20190529: 20190529
> >>   CI_DRM_14597: 64a20aacb61e4ce6d8a0b3dc6e4bff72e316ffa3 @ git://anongit.freedesktop.org/gfx-ci/linux
> >>   IGT_7810: 189483744e9ff56ea573e07a049c5365404c7ecb @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
> >>   Patchwork_132390v3: 64a20aacb61e4ce6d8a0b3dc6e4bff72e316ffa3 @ 
> >> git://anongit.freedesktop.org/gfx-ci/linux
> >>
> >> == Logs ==
> >>
> >> For more details see: 
> >> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_132390v3/index.html
> >
> > --
> > Jani Nikula, Intel
> 
> -- 
> Jani Nikula, Intel

-- 
Ville Syrjälä
Intel

  reply	other threads:[~2024-04-19 16:57 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-12 17:58 [PATCH 0/8] drm/i915: BXT/GLK per-lane vswing and PHY reg cleanup Ville Syrjala
2024-04-12 17:58 ` [PATCH 1/8] drm/i915/dpio: Clean up bxt/glk PHY registers Ville Syrjala
2024-04-12 17:58 ` [PATCH 2/8] drm/i915/dpio: Add per-lane PHY TX register definitons for bxt/glk Ville Syrjala
2024-04-15 12:35   ` Jani Nikula
2024-04-15 23:12   ` kernel test robot
2024-04-16  0:28   ` kernel test robot
2024-04-17 15:12   ` [PATCH v2 " Ville Syrjala
2024-04-12 17:58 ` [PATCH 3/8] drm/i915/dpio: Extract bxt_dpio_phy_regs.h Ville Syrjala
2024-04-16  1:41   ` kernel test robot
2024-04-17 15:12   ` [PATCH v2 " Ville Syrjala
2024-04-12 17:58 ` [PATCH 4/8] drm/i915/dpio: Introdude bxt_ddi_phy_rmw_grp() Ville Syrjala
2024-04-15 12:36   ` Jani Nikula
2024-04-12 17:58 ` [PATCH 5/8] drm/i915/dpio: Use intel_de_rmw() for BXT DPIO latency optim setup Ville Syrjala
2024-04-12 17:58 ` [PATCH 6/8] drm/i915/dpio: s/ddi/dpio/ for bxt/glk PHY stuff Ville Syrjala
2024-04-15 12:39   ` Jani Nikula
2024-04-17 13:04     ` Ville Syrjälä
2024-04-12 17:58 ` [PATCH 7/8] drm/i915/dpio: Program bxt/glk PHY TX registers per-lane Ville Syrjala
2024-04-12 17:58 ` [PATCH 8/8] drm/i915: Enable per-lane DP drive settings for bxt/glk Ville Syrjala
2024-04-15 12:34 ` [PATCH 0/8] drm/i915: BXT/GLK per-lane vswing and PHY reg cleanup Jani Nikula
2024-04-15 14:29 ` ✗ Fi.CI.BUILD: failure for " Patchwork
2024-04-17 18:07 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: BXT/GLK per-lane vswing and PHY reg cleanup (rev3) Patchwork
2024-04-17 18:07 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-04-17 18:22 ` ✓ Fi.CI.BAT: success " Patchwork
2024-04-18 16:40   ` Jani Nikula
2024-04-19  5:37     ` Musial, Ewelina
2024-04-19  8:31       ` Jani Nikula
2024-04-19 16:56         ` Ville Syrjälä [this message]
2024-04-18 23:34 ` ✓ Fi.CI.IGT: " Patchwork
2024-04-19 17:54 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: BXT/GLK per-lane vswing and PHY reg cleanup (rev4) Patchwork
2024-04-19 17:54 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-04-19 18:00 ` ✓ Fi.CI.BAT: success " Patchwork
2024-04-20  1:40 ` ✗ 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=ZiKiVQ0WHfRCi2pY@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=ewelina.musial@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=lgci.bug.filing@intel.com \
    --cc=mateusz.grabski@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