From: Katarzyna Dec <katarzyna.dec@intel.com>
To: Daniel Vetter <daniel@ffwll.ch>, Chris Wilson <chris@chris-wilson.co.uk>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t 1/2] lib: Defer application of igt_fixture results
Date: Mon, 28 Jan 2019 17:05:24 +0100 [thread overview]
Message-ID: <20190128160524.GA5997@kdec5-desk.ger.corp.intel.com> (raw)
In-Reply-To: <20181129171741.GO21184@phenom.ffwll.local>
On Thu, Nov 29, 2018 at 06:17:41PM +0100, Daniel Vetter wrote:
> On Thu, Nov 29, 2018 at 06:16:48PM +0100, Daniel Vetter wrote:
> > On Wed, Nov 28, 2018 at 10:52:30PM +0000, Chris Wilson wrote:
> > > If an igt_fixture causes an independent subgroup to fail/skip and that
> > > subgroup is not part of the execution set (--run-subtest) as no subtests
> > > themselves failed or skipped, it should not count towards the overall
> > > test exitcode.
> > >
> > > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=108891
> > > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> >
> > I'm honestly a bit lost on what's going on here. Could you please write a
> > new library testcase for this one here, as demonstrator? For stuff like
> > this I really want to lock behaviour down with compile-time testcases.
>
> Forgot to add: They're in lib/tests/
> -Daniel
Looks like this issue is observed when running single subtest, e.g.:
gem_busy --r busy-render
Code prepared by Chris doesn't help with all issues I am observing, but at least
I see the direction to follow.
I will debug the issue more and let you know.
Kasia :)
> --
> 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
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
prev parent reply other threads:[~2019-01-28 16:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-28 22:52 [igt-dev] [PATCH i-g-t 1/2] lib: Defer application of igt_fixture results Chris Wilson
2018-11-28 22:52 ` [igt-dev] [PATCH i-g-t 2/2] lib: Only require we have i915.reset module parameter for allow-hang Chris Wilson
2018-11-29 1:25 ` [igt-dev] ✗ Fi.CI.BAT: failure for series starting with [i-g-t,1/2] lib: Defer application of igt_fixture results Patchwork
2018-11-29 17:16 ` [igt-dev] [PATCH i-g-t 1/2] " Daniel Vetter
2018-11-29 17:17 ` Daniel Vetter
2019-01-28 16:05 ` Katarzyna Dec [this message]
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=20190128160524.GA5997@kdec5-desk.ger.corp.intel.com \
--to=katarzyna.dec@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniel@ffwll.ch \
--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