From: Petri Latvala <adrinael@adrinael.net>
To: Mark Yacoub <markyacoub@chromium.org>
Cc: igt-dev@lists.freedesktop.org, "Vudum,
Lakshminarayana" <lakshminarayana.vudum@intel.com>
Subject: Re: [igt-dev] ✗ Fi.CI.BAT: failure for Chamelium: Get Chamelium Logs on RPC failure.
Date: Fri, 3 Feb 2023 12:10:50 +0200 [thread overview]
Message-ID: <Y9zdqjsQEO3+UKX5@adrinael.net> (raw)
In-Reply-To: <CAJUqKUoRGa8=Som60+OyieGFjNKObq06_XQSWq=zS8BpntZhrg@mail.gmail.com>
On Wed, Feb 01, 2023 at 04:02:35PM -0500, Mark Yacoub wrote:
> Hi Lakshminarayana, the failure seems unrelated - can we get a rerun please?
The failure is very related. The failure is:
"GetChameleondLogs" is not supported
You need to check with chamelium_supports_method whether
GetChameleondLogs is there. Btw, what chameleond version does that
need?
--
Petri Latvala
>
> On Wed, Feb 1, 2023 at 1:49 PM Patchwork <patchwork@emeril.freedesktop.org>
> wrote:
>
> > *Patch Details*
> > *Series:* Chamelium: Get Chamelium Logs on RPC failure.
> > *URL:* https://patchwork.freedesktop.org/series/113567/
> > *State:* failure
> > *Details:* https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8428/index.html CI
> > Bug Log - changes from CI_DRM_12680 -> IGTPW_8428 Summary
> >
> > *FAILURE*
> >
> > Serious unknown changes coming with IGTPW_8428 absolutely need to be
> > verified manually.
> >
> > If you think the reported changes have nothing to do with the changes
> > introduced in IGTPW_8428, please notify your bug team to allow them
> > to document this new failure mode, which will reduce false positives in CI.
> >
> > External URL:
> > https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8428/index.html
> > Participating hosts (26 -> 25)
> >
> > Missing (1): fi-snb-2520m
> > Possible new issues
> >
> > Here are the unknown changes that may have been introduced in IGTPW_8428:
> > IGT changes Possible regressions
> >
> > - igt@kms_chamelium_frames@hdmi-crc-fast:
> > - fi-kbl-7567u: PASS
> > <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12680/fi-kbl-7567u/igt@kms_chamelium_frames@hdmi-crc-fast.html>
> > -> FAIL
> > <https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8428/fi-kbl-7567u/igt@kms_chamelium_frames@hdmi-crc-fast.html>
> > +3 similar issues
> >
> > Warnings
> >
> > - igt@kms_chamelium_hpd@vga-hpd-fast:
> > - fi-kbl-7567u: SKIP
> > <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12680/fi-kbl-7567u/igt@kms_chamelium_hpd@vga-hpd-fast.html>
> > (fdo#109271 <https://bugs.freedesktop.org/show_bug.cgi?id=109271>)
> > -> FAIL
> > <https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8428/fi-kbl-7567u/igt@kms_chamelium_hpd@vga-hpd-fast.html>
> > +4 similar issues
> >
> > Known issues
> >
> > Here are the changes found in IGTPW_8428 that come from known issues:
> > IGT changes Issues hit
> >
> > - igt@i915_selftest@live@gt_heartbeat:
> > - fi-glk-j4005: PASS
> > <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12680/fi-glk-j4005/igt@i915_selftest@live@gt_heartbeat.html>
> > -> DMESG-FAIL
> > <https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8428/fi-glk-j4005/igt@i915_selftest@live@gt_heartbeat.html>
> > (i915#5334 <https://gitlab.freedesktop.org/drm/intel/issues/5334>)
> >
> > Possible fixes
> >
> > - igt@i915_selftest@live@migrate:
> > - {bat-dg2-11}: DMESG-WARN
> > <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12680/bat-dg2-11/igt@i915_selftest@live@migrate.html>
> > (i915#7699 <https://gitlab.freedesktop.org/drm/intel/issues/7699>)
> > -> PASS
> > <https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8428/bat-dg2-11/igt@i915_selftest@live@migrate.html>
> >
> > {name}: This element is suppressed. This means it is ignored when computing
> > the status of the difference (SUCCESS, WARNING, or FAILURE).
> > Build changes
> >
> > - CI: CI-20190529 -> None
> > - IGT: IGT_7143 -> IGTPW_8428
> >
> > CI-20190529: 20190529
> > CI_DRM_12680: 06086656e6f03cbcbb4b99273734a7943e923fc9 @ git://
> > anongit.freedesktop.org/gfx-ci/linux
> > IGTPW_8428: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8428/index.html
> > IGT_7143: c7b12dcc460fc2348e1fa7f4dcb791bb82e29e44 @
> > https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
> >
next prev parent reply other threads:[~2023-02-03 10:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 18:12 [igt-dev] [PATCH] Chamelium: Get Chamelium Logs on RPC failure Mark Yacoub
2023-02-01 18:24 ` [igt-dev] ✗ GitLab.Pipeline: warning for " Patchwork
2023-02-01 18:49 ` [igt-dev] ✗ Fi.CI.BAT: failure " Patchwork
2023-02-01 21:02 ` Mark Yacoub
2023-02-03 10:10 ` Petri Latvala [this message]
2023-02-03 16:59 ` Mark Yacoub
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=Y9zdqjsQEO3+UKX5@adrinael.net \
--to=adrinael@adrinael.net \
--cc=igt-dev@lists.freedesktop.org \
--cc=lakshminarayana.vudum@intel.com \
--cc=markyacoub@chromium.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