public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Petri Latvala <petri.latvala@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] ✓ Fi.CI.BAT: success for runner: Make sure output is  still collected when killing test due to taint
Date: Wed, 29 Jan 2020 15:39:27 +0200	[thread overview]
Message-ID: <20200129133927.GT25209@platvala-desk.ger.corp.intel.com> (raw)
In-Reply-To: <158030448468.11197.16540157364945457011@skylake-alporthouse-com>

On Wed, Jan 29, 2020 at 01:28:04PM +0000, Chris Wilson wrote:
> Quoting Petri Latvala (2020-01-29 13:24:49)
> > On Tue, Jan 28, 2020 at 03:56:11PM +0000, Chris Wilson wrote:
> > > Quoting Patchwork (2020-01-28 15:30:42)
> > > > == Series Details ==
> > > > 
> > > > Series: runner: Make sure output is still collected when killing test due to taint
> > > > URL   : https://patchwork.freedesktop.org/series/72657/
> > > > State : success
> > > > 
> > > > == Summary ==
> > > > 
> > > > CI Bug Log - changes from IGT_5394 -> IGTPW_4016
> > > > ====================================================
> > > > 
> > > > Summary
> > > > -------
> > > > 
> > > >   **WARNING**
> > > > 
> > > >   Minor unknown changes coming with IGTPW_4016 need to be verified
> > > >   manually.
> > > >   
> > > >   If you think the reported changes have nothing to do with the changes
> > > >   introduced in IGTPW_4016, 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_4016/index.html
> > > > 
> > > > Possible new issues
> > > > -------------------
> > > > 
> > > >   Here are the unknown changes that may have been introduced in IGTPW_4016:
> > > > 
> > > > ### IGT changes ###
> > > > 
> > > > #### Warnings ####
> > > > 
> > > >   * igt@gem_exec_suspend@basic-s3:
> > > >     - fi-cml-s:           [FAIL][1] ([fdo#103375]) -> [TIMEOUT][2]
> > > >    [1]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5394/fi-cml-s/igt@gem_exec_suspend@basic-s3.html
> > > >    [2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4016/fi-cml-s/igt@gem_exec_suspend@basic-s3.html
> > > 
> > > Incomplete or Timeout?
> > > 
> > > Starting subtest: basic-S3
> > > [160.045053] Killing the test because the kernel is tainted.
> > > [160.119964] Aborting: Kernel badly tainted (0x240) (check dmesg for details):
> > >       (0x200) TAINT_WARN: WARN_ON has happened.
> > > 
> > > I'd rather have stern purple than whimsical blue.
> > 
> > I can probably make that happen and it's almost going to be easy.
> > 
> > Do you mind if I do it in a followup patch though? I'd like to get
> > this in, the questions about incomplete output are increasing every
> > day...
> 
> Sure. Could we also ticking down earlier i.e. periodic taint checking?


A possibility, yes.


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

  reply	other threads:[~2020-01-29 13:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-28 11:48 [igt-dev] [PATCH i-g-t] runner: Make sure output is still collected when killing test due to taint Petri Latvala
2020-01-28 12:01 ` Chris Wilson
2020-01-28 15:30 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2020-01-28 15:56   ` Chris Wilson
2020-01-29 13:24     ` Petri Latvala
2020-01-29 13:28       ` Chris Wilson
2020-01-29 13:39         ` Petri Latvala [this message]
2020-01-29 22:06 ` [igt-dev] ✗ Fi.CI.IGT: failure " 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=20200129133927.GT25209@platvala-desk.ger.corp.intel.com \
    --to=petri.latvala@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