From: Antonio Argenziano <antonio.argenziano@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] ✗ Fi.CI.BAT: failure for i915/gem_exec_reloc: Add SIGINT injection
Date: Wed, 29 Jan 2020 16:03:36 -0800 [thread overview]
Message-ID: <2f8a0f92-c04a-7525-7e5d-28169f3ce256@intel.com> (raw)
In-Reply-To: <158034225189.14720.7645748499533857319@skylake-alporthouse-com>
On 29/01/20 15:57, Chris Wilson wrote:
> Quoting Antonio Argenziano (2020-01-29 23:55:05)
>>
>>
>> On 29/01/20 15:35, Patchwork wrote:
>>> == Series Details ==
>>>
>>> Series: i915/gem_exec_reloc: Add SIGINT injection
>>> URL : https://patchwork.freedesktop.org/series/72745/
>>> State : failure
>>>
>>> == Summary ==
>>>
>>> CI Bug Log - changes from IGT_5405 -> IGTPW_4036
>>> ====================================================
>>>
>>> Summary
>>> -------
>>>
>>> **FAILURE**
>>>
>>> Serious unknown changes coming with IGTPW_4036 absolutely need to be
>>> verified manually.
>>>
>>> If you think the reported changes have nothing to do with the changes
>>> introduced in IGTPW_4036, 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_4036/index.html
>>>
>>> Possible new issues
>>> -------------------
>>>
>>> Here are the unknown changes that may have been introduced in IGTPW_4036:
>>>
>>> ### IGT changes ###
>>>
>>> #### Possible regressions ####
>>>
>>> * igt@runner@aborted:
>>> - fi-bsw-nick: NOTRUN -> [FAIL][1]
>>> [1]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4036/fi-bsw-nick/igt@runner@aborted.html
>>
>> I doubt this was caused by this patch, can I merge?
>
> After you fix the lockdep. I've all 3 ready to push, just waiting to
> give the kernel pw a chance (because somewhere in the queue is the fix
> for the above).
Fair.
Antonio
> -Chris
>
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2020-01-30 0:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-29 22:24 [igt-dev] [PATCH i-g-t] i915/gem_exec_reloc: Add SIGINT injection Chris Wilson
2020-01-29 22:28 ` Antonio Argenziano
2020-01-29 23:35 ` [igt-dev] ✗ Fi.CI.BAT: failure for " Patchwork
2020-01-29 23:55 ` Antonio Argenziano
2020-01-29 23:57 ` Chris Wilson
2020-01-30 0:03 ` Antonio Argenziano [this message]
2020-01-30 10:32 ` Petri Latvala
2020-01-30 10:33 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2020-02-01 9:04 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2020-02-01 14:03 ` [igt-dev] ✓ Fi.CI.IGT: success " 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=2f8a0f92-c04a-7525-7e5d-28169f3ce256@intel.com \
--to=antonio.argenziano@intel.com \
--cc=chris@chris-wilson.co.uk \
--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