From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: Tomi Sarvela <tomi.p.sarvela@intel.com>
Subject: Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: Per-crtc/connector DRRS debugfs (rev2)
Date: Mon, 3 Oct 2022 11:37:41 +0300 [thread overview]
Message-ID: <YzqfVR8RjL06e20Y@intel.com> (raw)
In-Reply-To: <166466659715.32391.15847655821384807172@emeril.freedesktop.org>
On Sat, Oct 01, 2022 at 11:23:17PM -0000, Patchwork wrote:
> * igt@gem_exec_balancer@parallel-balancer:
> - shard-iclb: [PASS][58] -> [SKIP][59] ([i915#4525])
> [58]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12204/shard-iclb2/igt@gem_exec_balancer@parallel-balancer.html
> [59]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109175v2/shard-iclb5/igt@gem_exec_balancer@parallel-balancer.html
shard-iclb skips most DRRS tests, but does execute a few which is
weird.
I spot checked a few of he logs and saw at least three different panels
being used:
1. using preferred EDID fixed mode: "2560x1440": 60 241750 2560 2608 2640 2720 1440 1443 1448 1481 0x48 0xa
2. using preferred EDID fixed mode: "1920x1080": 60 141000 1920 1936 1952 2104 1080 1083 1097 1116 0x48 0xa
3. using preferred EDID fixed mode: "1920x1080": 60 138780 1920 1966 1996 2080 1080 1082 1086 1112 0x48 0xa
using alternate EDID fixed mode: "1920x1080": 40 92520 1920 1966 1996 2080 1080 1082 1086 1112 0x40 0xa
So the DRRS tests were only executed when they ended up on machine with
panel 3.
Having different panels between the machines in the shard pool is not
great. We can get all kinds of pingpongs depending on how tests get
scheduled to individual machines.
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2022-10-03 8:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-01 18:25 [Intel-gfx] [PATCH v2 0/4] drm/i915: Per-crtc/connector DRRS debugfs Ville Syrjala
2022-10-01 18:25 ` [Intel-gfx] [PATCH v2 1/4] drm/i915: Move DRRS debugfs next to the implementation Ville Syrjala
2022-10-01 18:25 ` [Intel-gfx] [PATCH v2 2/4] drm/i915: Make the DRRS debugfs contents more consistent Ville Syrjala
2022-10-01 18:25 ` [Intel-gfx] [PATCH v2 3/4] drm/i915: Make DRRS debugfs per-crtc/connector Ville Syrjala
2022-10-01 18:25 ` [Intel-gfx] [PATCH v2 4/4] drm/i915: Fix locking in DRRS debugfs Ville Syrjala
2022-10-01 19:02 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: Per-crtc/connector DRRS debugfs (rev2) Patchwork
2022-10-01 19:26 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-10-01 23:23 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-10-03 8:37 ` Ville Syrjälä [this message]
2022-10-03 8:44 ` Sarvela, Tomi P
2022-10-03 8:48 ` Ville Syrjälä
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=YzqfVR8RjL06e20Y@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=tomi.p.sarvela@intel.com \
/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