From: Daniel Vetter <daniel@ffwll.ch>
To: "Souza, Jose" <jose.souza@intel.com>
Cc: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] ✗ Fi.CI.IGT: failure for tests/kms_concurrent: Allow the test to proceed with fewer planes
Date: Wed, 3 Apr 2019 10:36:41 +0200 [thread overview]
Message-ID: <20190403083641.GS2665@phenom.ffwll.local> (raw)
In-Reply-To: <7a9ff86851ab310059172ed16c8131f67d92f208.camel@intel.com>
On Wed, Apr 03, 2019 at 12:28:12AM +0000, Souza, Jose wrote:
> On Tue, 2019-04-02 at 21:21 +0000, Patchwork wrote:
> > == Series Details ==
> >
> > Series: tests/kms_concurrent: Allow the test to proceed with fewer
> > planes
> > URL : https://patchwork.freedesktop.org/series/58872/
> > State : failure
> >
> > == Summary ==
> >
> > CI Bug Log - changes from IGT_4920_full -> IGTPW_2760_full
> > ====================================================
> >
> > Summary
> > -------
> >
> > **FAILURE**
> >
> > Serious unknown changes coming with IGTPW_2760_full absolutely need
> > to be
> > verified manually.
> >
> > If you think the reported changes have nothing to do with the
> > changes
> > introduced in IGTPW_2760_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://patchwork.freedesktop.org/api/1.0/series/58872/revisions/1/mbox/
> >
> > Possible new issues
> > -------------------
> >
> > Here are the unknown changes that may have been introduced in
> > IGTPW_2760_full:
> >
> > ### IGT changes ###
> >
> > #### Possible regressions ####
> >
> > * igt@kms_vblank@pipe-b-ts-continuation-modeset:
> > - shard-kbl: PASS -> DMESG-FAIL
>
> Not related at all.
>
> Patch pushed.
See my reply, I think we now have a test gap. Can you pls fill that again?
I know there's a pile of pressure, but that's no good reason to rush
stuff.
Thanks, Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-04-03 8:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-02 13:08 [igt-dev] [PATCH i-g-t] tests/kms_concurrent: Allow the test to proceed with fewer planes Ville Syrjala
2019-04-02 14:01 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2019-04-02 17:49 ` [igt-dev] [PATCH i-g-t] " Souza, Jose
2019-04-02 21:21 ` [igt-dev] ✗ Fi.CI.IGT: failure for " Patchwork
2019-04-03 0:28 ` Souza, Jose
2019-04-03 8:36 ` Daniel Vetter [this message]
2019-04-03 8:48 ` Daniel Vetter
2019-04-03 8:35 ` [igt-dev] [PATCH i-g-t] " Daniel Vetter
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=20190403083641.GS2665@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=igt-dev@lists.freedesktop.org \
--cc=jose.souza@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