From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: John Harrison <john.c.harrison@intel.com>,
intel-gfx@lists.freedesktop.org,
Patchwork <patchwork@emeril.freedesktop.org>
Subject: Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for Improve anti-pre-emption w/a for compute workloads (rev8)
Date: Wed, 12 Oct 2022 14:54:40 +0100 [thread overview]
Message-ID: <e26c05b9-6480-dd0d-50f2-cb2374370f61@linux.intel.com> (raw)
In-Reply-To: <5682621a-d507-39f2-58e1-5a646d31adc9@intel.com>
On 10/10/2022 20:44, John Harrison wrote:
> On 10/6/2022 15:20, Patchwork wrote:
>> Project List - Patchwork *Patch Details*
>> *Series:* Improve anti-pre-emption w/a for compute workloads (rev8)
>> *URL:* https://patchwork.freedesktop.org/series/100428/
>> *State:* failure
>> *Details:*
>> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_100428v8/index.html
>>
>>
>> CI Bug Log - changes from CI_DRM_12223 -> Patchwork_100428v8
>>
>>
>> Summary
>>
>> *FAILURE*
>>
>> Serious unknown changes coming with Patchwork_100428v8 absolutely need
>> to be
>> verified manually.
>>
>> If you think the reported changes have nothing to do with the changes
>> introduced in Patchwork_100428v8, 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/Patchwork_100428v8/index.html
>>
>>
>> Participating hosts (42 -> 40)
>>
>> Missing (2): fi-ctg-p8600 fi-hsw-4200u
>>
>>
>> Possible new issues
>>
>> Here are the unknown changes that may have been introduced in
>> Patchwork_100428v8:
>>
>>
>> IGT changes
>>
>>
>> Possible regressions
>>
>> * igt@i915_selftest@live@migrate:
>> o fi-apl-guc: PASS
>> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12223/fi-apl-guc/igt@i915_selftest@live@migrate.html> -> INCOMPLETE <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_100428v8/fi-apl-guc/igt@i915_selftest@live@migrate.html>
>>
> The logs seems to suggest the test just stopped (with the actual dmesg0
> link being corrupted at the end). Seems likely there was a kernel panic
> followed by reboot. Given that this patch set is only affecting hang
> detection and recovery and the migrate test is not supposed to hit any
> hangs, it seems very unlikely this failure is related. Certainly, all
> previous revisions of this patch set did not any problems with the
> live@migrate test.
I happened in the past:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12221/fi-apl-guc/igt@i915_selftest@live@migrate.html
So I think you can ignore it.
Regards,
Tvrtko
next prev parent reply other threads:[~2022-10-12 13:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 21:38 [Intel-gfx] [PATCH v5 0/4] Improve anti-pre-emption w/a for compute workloads John.C.Harrison
2022-10-06 21:38 ` [Intel-gfx] [PATCH v5 1/4] drm/i915/guc: Limit scheduling properties to avoid overflow John.C.Harrison
2022-10-18 0:06 ` Ceraolo Spurio, Daniele
2022-10-06 21:38 ` [Intel-gfx] [PATCH v5 2/4] drm/i915: Fix compute pre-emption w/a to apply to compute engines John.C.Harrison
2022-10-06 21:38 ` [Intel-gfx] [PATCH v5 3/4] drm/i915: Make the heartbeat play nice with long pre-emption timeouts John.C.Harrison
2022-10-07 8:44 ` Tvrtko Ursulin
2022-10-06 21:38 ` [Intel-gfx] [PATCH v5 4/4] drm/i915: Improve long running compute w/a for GuC submission John.C.Harrison
2022-10-18 0:09 ` Ceraolo Spurio, Daniele
2022-10-06 21:57 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Improve anti-pre-emption w/a for compute workloads (rev8) Patchwork
2022-10-06 21:57 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-10-06 22:20 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2022-10-10 19:44 ` John Harrison
2022-10-12 13:54 ` Tvrtko Ursulin [this message]
2022-10-12 15:34 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Improve anti-pre-emption w/a for compute workloads (rev9) Patchwork
2022-10-12 15:34 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-10-12 15:54 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-10-12 23:55 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=e26c05b9-6480-dd0d-50f2-cb2374370f61@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=john.c.harrison@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