[Intel-gfx] ✗ Fi.CI.IGT: failure for drm: connector firmware nodes

[Tvrtko Ursulin]

On 27/03/2019 15:38, Heikki Krogerus wrote:
> Hi Jani,
> 
> On Tue, Mar 26, 2019 at 03:16:29PM +0000, Saarinen, Jani wrote:
>>> -----Original Message-----
>>> From: Intel-gfx [mailto:intel-gfx-bounces at lists.freedesktop.org] On Behalf Of Heikki
>>> Krogerus
>>> Sent: tiistai 26. maaliskuuta 2019 10.32
>>> To: intel-gfx at lists.freedesktop.org
>>> Subject: Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm: connector firmware nodes
>>>
>>> On Mon, Mar 25, 2019 at 08:57:44PM -0000, Patchwork wrote:
>>>> == Series Details ==
>>>>
>>>> Series: drm: connector firmware nodes
>>>> URL   : https://patchwork.freedesktop.org/series/58531/
>>>> State : failure
>>>>
>>>> == Summary ==
>>>>
>>>> CI Bug Log - changes from CI_DRM_5810_full -> Patchwork_12592_full
>>>> ====================================================
>>>>
>>>> Summary
>>>> -------
>>>>
>>>>    **FAILURE**
>>>>
>>>>    Serious unknown changes coming with Patchwork_12592_full absolutely need to
>>> be
>>>>    verified manually.
>>>>
>>>>    If you think the reported changes have nothing to do with the changes
>>>>    introduced in Patchwork_12592_full, please notify your bug team to allow them
>>>>    to document this new failure mode, which will reduce false positives in CI.
>>>>
>>>>
>>>>
>>>> Possible new issues
>>>> -------------------
>>>>
>>>>    Here are the unknown changes that may have been introduced in
>>> Patchwork_12592_full:
>>>>
>>>> ### IGT changes ###
>>>>
>>>> #### Possible regressions ####
>>>>
>>>>    * igt at perf_pmu@idle-no-semaphores-bcs0:
>>>>      - shard-iclb:         PASS -> INCOMPLETE
>>>
>>>
>>> I have not idea what this is about? Is there something I need to do?
>> Do you see from logs if relevant to your patche(s) ?
> 
> Sorry, but I can't really say, as I don't know how to interpret the
> logs. I don't understand what that test is doing.
> 
> I'm assuming this log shows the failure:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_12592/shard-iclb8/run7.log
> 
> The failure happens when running test (I'm guessing):
> "[30/82] (859s left) gem_tiled_swapping (non-threaded)"
> 
> In the log there is a line that says:
> "FATAL: Unable to delete script file /tmp/jenkins7657231043286309557.sh"
> 
> That certainly does not sound like anything that these patches would
> affect, but since I really have no idea what the test is doing, I
> can't really be sure.

gem_tiled_swapping caused OOM killer to trigger which first killed the 
test, then killed java, and then CI put the blame on 
igt at perf_pmu@idle-no-semaphores-bcs0 which AFAICS did not even get to run.

Regards,

Tvrtko