From: Jani Nikula <jani.nikula@intel.com>
To: Gustavo Sousa <gustavo.sousa@intel.com>, intel-gfx@lists.freedesktop.org
Cc: Rodrigo Vivi <rodrigo.vivi@gmail.com>,
i915-ci-infra@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.BAT: failure for Miscelaneous fixes for display tracepoints (rev2)
Date: Fri, 04 Oct 2024 14:33:20 +0300 [thread overview]
Message-ID: <878qv4rtkv.fsf@intel.com> (raw)
In-Reply-To: <172804037058.2413.13969013073462156051@gjsousa-mobl2>
On Fri, 04 Oct 2024, Gustavo Sousa <gustavo.sousa@intel.com> wrote:
> Quoting Patchwork (2024-09-26 16:28:07-03:00)
>>#### Possible regressions ####
>>
>> * igt@i915_selftest@live:
>> - bat-mtlp-6: [PASS][1] -> [ABORT][2] +1 other test abort
>> [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15449/bat-mtlp-6/igt@i915_selftest@live.html
>> [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_137978v2/bat-mtlp-6/igt@i915_selftest@live.html
>
> This does not seem related to this series, which is only about
> tracepoints.
>
> Jani or Rodrigo, ack to merge this series without triggering a new CI
> cycle? I don't believe CI exercises tests that enable tracepoints. Or
> does it?
BAT *must* pass before merging, no exceptions.
Full shard run failures can be looked over when it's clear the series
didn't cause the failures.
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-10-04 11:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-23 19:02 [PATCH v2 0/5] Miscelaneous fixes for display tracepoints Gustavo Sousa
2024-09-23 19:02 ` [PATCH v2 1/5] drm/i915/display: Fix out-of-bounds access in pipe-related tracepoints Gustavo Sousa
2024-09-23 19:02 ` [PATCH v2 2/5] drm/i915/display: Zero-initialize frame/scanline counts in tracepoints Gustavo Sousa
2024-09-23 19:02 ` [PATCH v2 3/5] drm/i915/display: Store pipe name in trace events Gustavo Sousa
2024-09-23 19:02 ` [PATCH v2 4/5] drm/i915/display: Do not use ids from enum pipe in TP_printk() Gustavo Sousa
2024-09-23 19:02 ` [PATCH v2 5/5] drm/i915/display: Cover all possible pipes " Gustavo Sousa
2024-09-23 19:23 ` Ville Syrjälä
2024-09-23 20:06 ` Gustavo Sousa
2024-09-23 20:18 ` Ville Syrjälä
2024-09-23 20:47 ` Gustavo Sousa
2024-09-23 20:48 ` Gustavo Sousa
2024-09-23 21:08 ` Ville Syrjälä
2024-09-26 19:26 ` ✗ Fi.CI.CHECKPATCH: warning for Miscelaneous fixes for display tracepoints (rev2) Patchwork
2024-09-26 19:28 ` ✗ Fi.CI.BAT: failure " Patchwork
2024-10-04 11:12 ` Gustavo Sousa
2024-10-04 11:33 ` Jani Nikula [this message]
2024-10-04 11:43 ` Gustavo Sousa
2024-10-04 12:03 ` Saarinen, Jani
2024-10-04 12:09 ` Saarinen, Jani
2024-10-08 19:46 ` ✗ Fi.CI.CHECKPATCH: warning for Miscelaneous fixes for display tracepoints (rev3) Patchwork
2024-10-08 19:55 ` ✗ Fi.CI.BAT: 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=878qv4rtkv.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=gustavo.sousa@intel.com \
--cc=i915-ci-infra@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rodrigo.vivi@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.