public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Peres, Martin" <martin.peres@intel.com>
To: Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com>,
	"igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Cc: "Sarvela, Tomi P" <tomi.p.sarvela@intel.com>,
	"Vudum, Lakshminarayana" <lakshminarayana.vudum@intel.com>
Subject: Re: [igt-dev] ✗ Fi.CI.BAT: failure for lib: Fix device lists not cleaned up sufficiently before rescan (rev2)
Date: Mon, 6 Apr 2020 07:19:33 +0000	[thread overview]
Message-ID: <d6950fff3b974a558c815583a03fa5f1@intel.com> (raw)
In-Reply-To: f819d52f898aad0f67e2dbc5c0fee511c8ad49d2.camel@linux.intel.com

[-- Attachment #1: Type: text/plain, Size: 4329 bytes --]

+ Lakshmi

On 2020-04-03 16:34, Janusz Krzysztofik wrote:
> On Fri, 2020-04-03 at 13:29 +0000, Patchwork wrote:
>> == Series Details ==
>>
>> Series: lib: Fix device lists not cleaned up sufficiently before rescan (rev2)
>> URL   : https://patchwork.freedesktop.org/series/74929/
>> State : failure
>>
>> == Summary ==
>>
>> CI Bug Log - changes from IGT_5561 -> IGTPW_4401
>> ====================================================
>>
>> Summary
>> -------
>>
>>   **FAILURE**
>>
>>   Serious unknown changes coming with IGTPW_4401 absolutely need to be
>>   verified manually.
>>   
>>   If you think the reported changes have nothing to do with the changes
>>   introduced in IGTPW_4401, 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_4401/index.html
>>
>> Possible new issues
>> -------------------
>>
>>   Here are the unknown changes that may have been introduced in IGTPW_4401:
>>
>> ### IGT changes ###
>>
>> #### Possible regressions ####
>>
>>   * igt@i915_selftest@live@gt_pm:
>>     - fi-kbl-guc:         [PASS][1] -> [DMESG-FAIL][2]
>>    [1]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5561/fi-kbl-guc/igt@i915_selftest@live@gt_pm.html
>>    [2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4401/fi-kbl-guc/igt@i915_selftest@live@gt_pm.html
> 
> The change has nothing to do with selftests so that's a false positive.

Lakshmi, Janusz has found a false positive.

Can you look into it?

Thanks,
Martin

> 
> Thanks,
> Janusz
> 
>>
>>   
>> Known issues
>> ------------
>>
>>   Here are the changes found in IGTPW_4401 that come from known issues:
>>
>> ### IGT changes ###
>>
>> #### Issues hit ####
>>
>>   * igt@gem_tiled_fence_blits@basic:
>>     - fi-blb-e6850:       [PASS][3] -> [DMESG-WARN][4] ([i915#1612])
>>    [3]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5561/fi-blb-e6850/igt@gem_tiled_fence_blits@basic.html
>>    [4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4401/fi-blb-e6850/igt@gem_tiled_fence_blits@basic.html
>>
>>   * igt@kms_chamelium@dp-edid-read:
>>     - fi-kbl-7500u:       [PASS][5] -> [FAIL][6] ([i915#976])
>>    [5]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5561/fi-kbl-7500u/igt@kms_chamelium@dp-edid-read.html
>>    [6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4401/fi-kbl-7500u/igt@kms_chamelium@dp-edid-read.html
>>
>>   
>> #### Possible fixes ####
>>
>>   * {igt@gem_wait@busy@all}:
>>     - fi-byt-n2820:       [FAIL][7] -> [PASS][8]
>>    [7]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5561/fi-byt-n2820/igt@gem_wait@busy@all.html
>>    [8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4401/fi-byt-n2820/igt@gem_wait@busy@all.html
>>
>>   * igt@i915_selftest@live@execlists:
>>     - fi-kbl-r:           [INCOMPLETE][9] ([CI#80] / [i915#656]) -> [PASS][10]
>>    [9]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5561/fi-kbl-r/igt@i915_selftest@live@execlists.html
>>    [10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4401/fi-kbl-r/igt@i915_selftest@live@execlists.html
>>
>>   
>>   {name}: This element is suppressed. This means it is ignored when computing
>>           the status of the difference (SUCCESS, WARNING, or FAILURE).
>>
>>   [CI#80]: https://gitlab.freedesktop.org/gfx-ci/i915-infra/issues/80
>>   [i915#1612]: https://gitlab.freedesktop.org/drm/intel/issues/1612
>>   [i915#656]: https://gitlab.freedesktop.org/drm/intel/issues/656
>>   [i915#976]: https://gitlab.freedesktop.org/drm/intel/issues/976
>>
>>
>> Participating hosts (49 -> 45)
>> ------------------------------
>>
>>   Additional (2): fi-snb-2520m fi-bsw-n3050 
>>   Missing    (6): fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-byt-clapper fi-bdw-samus 
>>
>>
>> Build changes
>> -------------
>>
>>   * CI: CI-20190529 -> None
>>   * IGT: IGT_5561 -> IGTPW_4401
>>
>>   CI-20190529: 20190529
>>   CI_DRM_8244: 55348aac86bd6f0c4ce4d3d8a0e227f6a20a72f9 @ git://anongit.freedesktop.org/gfx-ci/linux
>>   IGTPW_4401: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4401/index.html
>>   IGT_5561: 860a72c190aa9246055f20ac87a02a26fe1842e8 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
>>
>> == Logs ==
>>
>> For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4401/index.html
> 
> 


[-- Attachment #2: pEpkey.asc --]
[-- Type: application/pgp-keys, Size: 1765 bytes --]

[-- Attachment #3: Type: text/plain, Size: 154 bytes --]

_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  reply	other threads:[~2020-04-06  7:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-03 11:47 [igt-dev] [PATCH i-g-t v2] lib: Fix device lists not cleaned up sufficiently before rescan Janusz Krzysztofik
2020-04-03 13:29 ` [igt-dev] ✗ Fi.CI.BAT: failure for lib: Fix device lists not cleaned up sufficiently before rescan (rev2) Patchwork
2020-04-03 13:34   ` Janusz Krzysztofik
2020-04-06  7:19     ` Peres, Martin [this message]
2020-04-03 14:06 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2020-04-03 19:25 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2020-04-06  9:36   ` Arkadiusz Hiler
2020-04-06  9:38     ` Vudum, Lakshminarayana
2020-04-06 11:33 ` [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=d6950fff3b974a558c815583a03fa5f1@intel.com \
    --to=martin.peres@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=janusz.krzysztofik@linux.intel.com \
    --cc=lakshminarayana.vudum@intel.com \
    --cc=tomi.p.sarvela@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox