From: "Vudum, Lakshminarayana" <lakshminarayana.vudum@intel.com>
To: "Latvala, Petri" <petri.latvala@intel.com>,
"igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] ✗ Fi.CI.IGT: failure for runner: Only claim the test was killed if it was killed
Date: Thu, 6 Aug 2020 16:37:10 +0000 [thread overview]
Message-ID: <52b02c58f20f49e0a076a2c63e72752b@intel.com> (raw)
In-Reply-To: <20200806083801.GW20883@platvala-desk.ger.corp.intel.com>
Re-reported.
-----Original Message-----
From: Latvala, Petri <petri.latvala@intel.com>
Sent: Thursday, August 6, 2020 1:38 AM
To: igt-dev@lists.freedesktop.org; Vudum, Lakshminarayana <lakshminarayana.vudum@intel.com>
Subject: Re: ✗ Fi.CI.IGT: failure for runner: Only claim the test was killed if it was killed
On Wed, Aug 05, 2020 at 04:26:30PM +0000, Patchwork wrote:
> == Series Details ==
>
> Series: runner: Only claim the test was killed if it was killed
> URL : https://patchwork.freedesktop.org/series/80284/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from IGT_5759_full -> IGTPW_4853_full
> ====================================================
>
> Summary
> -------
>
> **FAILURE**
>
> Serious unknown changes coming with IGTPW_4853_full absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in IGTPW_4853_full, 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_4853/index.html
>
> Possible new issues
> -------------------
>
> Here are the unknown changes that may have been introduced in IGTPW_4853_full:
>
> ### IGT changes ###
>
> #### Possible regressions ####
>
> * igt@i915_selftest@mock:
> - shard-glk: NOTRUN -> [FAIL][1]
> [1]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4853/shard-glk9/igt@i915_selftest@mock.html
> - shard-iclb: NOTRUN -> [FAIL][2]
> [2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4853/shard-iclb5/igt@i915_selftest@mock.html
> - shard-hsw: NOTRUN -> [FAIL][3]
> [3]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4853/shard-hsw2/igt@i915_selftest@mock.html
> - shard-kbl: NOTRUN -> [FAIL][4]
> [4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4853/shard-kbl4/igt@i915_selftest@mock.html
> - shard-snb: NOTRUN -> [FAIL][5]
> [5]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4853/shard-snb6/igt@i915_selftest@mock.html
> - shard-tglb: NOTRUN -> [FAIL][6]
> [6]:
> https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4853/shard-tglb7/igt@i9
> 15_selftest@mock.html
Well that was a scary result, but turns out all of these are false failures. Lakshmi, ^
--
Petri Latvala
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2020-08-06 16:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-05 10:59 [igt-dev] [PATCH i-g-t] runner: Only claim the test was killed if it was killed Petri Latvala
2020-08-05 12:13 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2020-08-05 14:01 ` [igt-dev] [PATCH i-g-t] " Lukasz Fiedorowicz
2020-08-05 16:26 ` [igt-dev] ✗ Fi.CI.IGT: failure for " Patchwork
2020-08-06 8:38 ` Petri Latvala
2020-08-06 16:37 ` Vudum, Lakshminarayana [this message]
2020-08-06 15:44 ` [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=52b02c58f20f49e0a076a2c63e72752b@intel.com \
--to=lakshminarayana.vudum@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=petri.latvala@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