From: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: <intel-xe@lists.freedesktop.org>, <ryszard.knop@intel.com>,
<ewelina.musial@intel.com>
Subject: Re: ✓ CI.BAT: success for Reapply "drm/xe/gsc: define GSC FW for LNL"
Date: Wed, 3 Jul 2024 09:38:54 -0700 [thread overview]
Message-ID: <11752a39-1aa0-4140-bc26-15283f045607@intel.com> (raw)
In-Reply-To: <ct6pqzwxnhlmgkal5yjbaaukl7kcshlg2ifhjiodxu464o4xth@6lnkhu7lrwck>
On 7/2/2024 11:02 AM, Lucas De Marchi wrote:
> On Tue, Jul 02, 2024 at 09:25:31AM GMT, Daniele Ceraolo Spurio wrote:
>>
>>
>> On 7/2/2024 7:29 AM, Lucas De Marchi wrote:
>>> On Tue, Jul 02, 2024 at 01:01:28AM GMT, Patchwork wrote:
>>>> == Series Details ==
>>>>
>>>> Series: Reapply "drm/xe/gsc: define GSC FW for LNL"
>>>> URL : https://patchwork.freedesktop.org/series/135623/
>>>> State : success
>>>>
>>>> == Summary ==
>>>>
>>>> CI Bug Log - changes from
>>>> xe-1542-886eeb6d89b58f914ee5045fcac54b59a73d8299_BAT ->
>>>> xe-pw-135623v1_BAT
>>>> ====================================================
>>>>
>>>> Summary
>>>> -------
>>>>
>>>> **SUCCESS**
>>>>
>>>> No regressions found.
>>>>
>>>>
>>>>
>>>> Participating hosts (5 -> 4)
>>>> ------------------------------
>>>>
>>>> Missing (1): bat-lnl-1
>>>
>>> I guess it didn't really work. +Ryszard +Ewelina: Can we promote LNL to
>>> be considered "a reliable machine from the CI POV" so we don't have
>>> "CI.BAT: success" when LNL execution is missing? Or is there any other
>>> reason why we report success in this case?
>>
>> Damn. I can't repro the issue anymore with this WA applied and even
>> in CI we weren't seeing it when I sent it for testing before:
>> https://patchwork.freedesktop.org/series/134099/ . I did 3 runs in
>> that case and none of them hit the problem.
>>
>> I've triggered another run to see if we get any better logs.
>
> this change should NOT make the machine "go missing" really. Actually no
> change to xe-only should really make a machine not have any log at
> all....
>
> I believe it was a very unfortunate coincidence and there must be a
> network issue or the like... but we can't consider success when we don't
> have a report for LNL. Particularly for this patch since LNL is
> the only affected platform.
>
> "try again" in patchwork sounds good for now.
It died again, but this time we got some logs. It died during an fbdev
test, which makes me think this is due to the display side of the WA
still being missing. I'll try again to repro locally and if I can't I'll
send a patch to move the FB out of stolen and see what happens.
Daniele
>
> thanks
> Lucas De Marchi
>
>>
>> Daniele
>>
>>>
>>> thanks
>>> Lucas De Marchi
>>
next prev parent reply other threads:[~2024-07-03 16:39 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-02 0:11 [PATCH] Reapply "drm/xe/gsc: define GSC FW for LNL" Daniele Ceraolo Spurio
2024-07-02 0:16 ` ✓ CI.Patch_applied: success for " Patchwork
2024-07-02 0:17 ` ✗ CI.checkpatch: warning " Patchwork
2024-07-02 0:18 ` ✓ CI.KUnit: success " Patchwork
2024-07-02 0:30 ` ✓ CI.Build: " Patchwork
2024-07-02 0:32 ` ✓ CI.Hooks: " Patchwork
2024-07-02 0:34 ` ✓ CI.checksparse: " Patchwork
2024-07-02 1:01 ` ✓ CI.BAT: " Patchwork
2024-07-02 14:29 ` Lucas De Marchi
2024-07-02 16:25 ` Daniele Ceraolo Spurio
2024-07-02 18:02 ` Lucas De Marchi
2024-07-03 16:38 ` Daniele Ceraolo Spurio [this message]
2024-07-03 20:22 ` Lucas De Marchi
2024-07-04 13:29 ` Ville Syrjälä
2024-07-08 22:59 ` Lucas De Marchi
2024-07-02 2:15 ` ✗ CI.FULL: failure " Patchwork
2024-07-03 11:30 ` ✓ CI.Patch_applied: success for Reapply "drm/xe/gsc: define GSC FW for LNL" (rev2) Patchwork
2024-07-03 11:30 ` ✗ CI.checkpatch: warning " Patchwork
2024-07-03 11:32 ` ✓ CI.KUnit: success " Patchwork
2024-07-03 11:43 ` ✓ CI.Build: " Patchwork
2024-07-03 11:46 ` ✓ CI.Hooks: " Patchwork
2024-07-03 11:47 ` ✓ CI.checksparse: " Patchwork
2024-07-03 12:13 ` ✓ CI.BAT: " Patchwork
2024-07-03 14:01 ` ✗ CI.FULL: failure " Patchwork
2024-07-18 14:05 ` ✓ CI.Patch_applied: success for Reapply "drm/xe/gsc: define GSC FW for LNL" (rev3) Patchwork
2024-07-18 14:06 ` ✗ CI.checkpatch: warning " Patchwork
2024-07-18 14:07 ` ✓ CI.KUnit: success " Patchwork
2024-07-18 14:19 ` ✓ CI.Build: " Patchwork
2024-07-18 14:21 ` ✓ CI.Hooks: " Patchwork
2024-07-18 14:23 ` ✓ CI.checksparse: " Patchwork
2024-07-18 14:46 ` ✗ CI.BAT: failure " Patchwork
2024-07-18 15:15 ` Daniele Ceraolo Spurio
2024-07-18 16:42 ` ✓ CI.Patch_applied: success for Reapply "drm/xe/gsc: define GSC FW for LNL" (rev4) Patchwork
2024-07-18 16:43 ` ✗ CI.checkpatch: warning " Patchwork
2024-07-18 16:44 ` ✓ CI.KUnit: success " Patchwork
2024-07-18 16:56 ` ✓ CI.Build: " Patchwork
2024-07-18 16:58 ` ✓ CI.Hooks: " Patchwork
2024-07-18 16:59 ` ✓ CI.checksparse: " Patchwork
2024-07-18 17:20 ` ✓ CI.BAT: " Patchwork
2024-07-18 19:59 ` Lucas De Marchi
2024-07-18 20:28 ` ✗ CI.FULL: failure for Reapply "drm/xe/gsc: define GSC FW for LNL" (rev3) Patchwork
2024-07-18 23:49 ` ✗ CI.FULL: failure for Reapply "drm/xe/gsc: define GSC FW for LNL" (rev4) 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=11752a39-1aa0-4140-bc26-15283f045607@intel.com \
--to=daniele.ceraolospurio@intel.com \
--cc=ewelina.musial@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=ryszard.knop@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 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.