From: "Teres Alexis, Alan Previn" <alan.previn.teres.alexis@intel.com>
To: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] ✗ Fi.CI.IGT: failure for lib/i915: Add a helper to read mmio registers via ioctl (rev4)
Date: Mon, 18 Sep 2023 17:16:58 +0000 [thread overview]
Message-ID: <8c6651a93ea343b776d0c82d1435eff95e4bd0e7.camel@intel.com> (raw)
In-Reply-To: <169485773482.10846.1205724611104113416@emeril.freedesktop.org>
On Sat, 2023-09-16 at 09:48 +0000, Patchwork wrote:
> Patch Details
alan:snip
> IGT changes
> Possible regressions
>
> * igt@i915_pm_freq_api@freq-suspend@gt0:
>
> * shard-dg2: PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13643/shard-dg2-3/igt@i915_pm_freq_api@freq-suspend@gt0.html> -> INCOMPLETE<https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9807/shard-dg2-7/igt@i915_pm_freq_api@freq-suspend@gt0.html> +1 other test incomplete
> * igt@i915_suspend@fence-restore-untiled:
>
> * shard-tglu: PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13643/shard-tglu-10/igt@i915_suspend@fence-restore-untiled.html> -> INCOMPLETE<https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9807/shard-tglu-9/igt@i915_suspend@fence-restore-untiled.html>
alan: i dont believe above issues are related - i checked to ensure that those tests are not calling into the new wrapper lib functions i added.
prev parent reply other threads:[~2023-09-18 17:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-15 20:40 [igt-dev] [PATCH i-g-t v5] lib/i915: Add a helper to read mmio registers via ioctl Alan Previn
2023-09-15 23:51 ` [igt-dev] ✓ Fi.CI.BAT: success for lib/i915: Add a helper to read mmio registers via ioctl (rev4) Patchwork
2023-09-16 1:24 ` [igt-dev] ✓ CI.xeBAT: " Patchwork
2023-09-16 9:48 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2023-09-18 17:16 ` Teres Alexis, Alan Previn [this message]
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=8c6651a93ea343b776d0c82d1435eff95e4bd0e7.camel@intel.com \
--to=alan.previn.teres.alexis@intel.com \
--cc=igt-dev@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