All of lore.kernel.org
 help / color / mirror / Atom feed
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 lib/igt_core: Ensure subtest result is skip if all dynamic subtests skip
Date: Thu, 16 Dec 2021 07:27:57 +0000	[thread overview]
Message-ID: <a518d822f75f47d1a6541fcdf9592659@intel.com> (raw)
In-Reply-To: <YbreHoq9/14yCQCL@platvala-desk.ger.corp.intel.com>

We have an existing bug for the regression, updated the filter to include the test
https://gitlab.freedesktop.org/drm/intel/-/issues/3778
igt@gem_exec_endless@dispatch@.* - incomplete - Per-test timeout exceeded. Killing the current test with SIGQUIT.

Lakshmi.
-----Original Message-----
From: Latvala, Petri <petri.latvala@intel.com> 
Sent: Wednesday, December 15, 2021 10:35 PM
To: igt-dev@lists.freedesktop.org; Vudum, Lakshminarayana <lakshminarayana.vudum@intel.com>
Subject: Re: [igt-dev] ✗ Fi.CI.IGT: failure for lib/igt_core: Ensure subtest result is skip if all dynamic subtests skip

On Wed, Dec 15, 2021 at 01:48:07PM +0000, Patchwork wrote:
> == Series Details ==
> 
> Series: lib/igt_core: Ensure subtest result is skip if all dynamic subtests skip
> URL   : https://patchwork.freedesktop.org/series/98053/
> State : failure
> 
> == Summary ==
> 
> CI Bug Log - changes from IGT_6309_full -> IGTPW_6496_full 
> ====================================================
> 
> Summary
> -------
> 
>   **FAILURE**
> 
>   Serious unknown changes coming with IGTPW_6496_full absolutely need to be
>   verified manually.
>   
>   If you think the reported changes have nothing to do with the changes
>   introduced in IGTPW_6496_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_6496/index.html
> 
> Participating hosts (7 -> 7)
> ------------------------------
> 
>   No changes in participating hosts
> 
> Possible new issues
> -------------------
> 
>   Here are the unknown changes that may have been introduced in IGTPW_6496_full:
> 
> ### IGT changes ###
> 
> #### Possible regressions ####
> 
>   * igt@gem_exec_endless@dispatch@vcs1:
>     - shard-tglb:         [PASS][1] -> [INCOMPLETE][2]
>    [1]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6309/shard-tglb7/igt@gem_exec_endless@dispatch@vcs1.html
>    [2]: 
> https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6496/shard-tglb2/igt@ge
> m_exec_endless@dispatch@vcs1.html
> 
>   

Lakshmi, false positive here.



--
Petri Latvala

  reply	other threads:[~2021-12-16  7:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-15 10:35 [igt-dev] [PATCH i-g-t] lib/igt_core: Ensure subtest result is skip if all dynamic subtests skip Petri Latvala
2021-12-15 11:33 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2021-12-15 13:48 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2021-12-16  6:35   ` Petri Latvala
2021-12-16  7:27     ` Vudum, Lakshminarayana [this message]
2021-12-15 14:31 ` [igt-dev] [PATCH i-g-t] " Dixit, Ashutosh
2021-12-16  6:37   ` Petri Latvala
2021-12-16  7:20 ` [igt-dev] ✓ Fi.CI.IGT: success for " 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=a518d822f75f47d1a6541fcdf9592659@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 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.