public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Petri Latvala <petri.latvala@intel.com>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] ✗ Fi.CI.IGT: failure for i915/perf_pmu: Compare semaphore and busy measurements (rev2)
Date: Mon, 30 Sep 2019 12:39:42 +0300	[thread overview]
Message-ID: <20190930093942.GF4019@platvala-desk.ger.corp.intel.com> (raw)
In-Reply-To: <89abc668-3005-0e68-631b-b5c4c38e749e@linux.intel.com>

On Thu, Sep 26, 2019 at 09:20:23AM +0100, Tvrtko Ursulin wrote:
> 
> On 26/09/2019 01:13, Patchwork wrote:
> > == Series Details ==
> > 
> > Series: i915/perf_pmu: Compare semaphore and busy measurements (rev2)
> > URL   : https://patchwork.freedesktop.org/series/67183/
> > State : failure
> > 
> > == Summary ==
> > 
> > CI Bug Log - changes from CI_DRM_6954_full -> IGTPW_3498_full
> > ====================================================
> > 
> > Summary
> > -------
> > 
> >    **FAILURE**
> > 
> >    Serious unknown changes coming with IGTPW_3498_full absolutely need to be
> >    verified manually.
> >    If you think the reported changes have nothing to do with the changes
> >    introduced in IGTPW_3498_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/67183/revisions/2/mbox/
> > 
> > Possible new issues
> > -------------------
> > 
> >    Here are the unknown changes that may have been introduced in IGTPW_3498_full:
> > 
> > ### IGT changes ###
> > 
> > #### Possible regressions ####
> > 
> >    * igt@i915_pm_sseu@full-enable:
> >      - shard-glk:          [PASS][1] -> [FAIL][2]
> >     [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6954/shard-glk1/igt@i915_pm_sseu@full-enable.html
> >     [2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3498/shard-glk5/igt@i915_pm_sseu@full-enable.html
> > 
> > New tests
> > ---------
> > 
> >    New tests have been introduced between CI_DRM_6954_full and IGTPW_3498_full:
> > 
> > ### New IGT tests (6) ###
> > 
> >    * igt@perf_pmu@semaphore-busy-bcs0:
> >      - Statuses : 4 pass(s) 2 skip(s)
> >      - Exec time: [0.0, 6.18] s
> > 
> >    * igt@perf_pmu@semaphore-busy-rcs0:
> >      - Statuses : 4 pass(s) 2 skip(s)
> >      - Exec time: [0.0, 6.21] s
> > 
> >    * igt@perf_pmu@semaphore-busy-vcs0:
> >      - Statuses : 4 pass(s) 2 skip(s)
> >      - Exec time: [0.0, 6.17] s
> > 
> >    * igt@perf_pmu@semaphore-busy-vcs1:
> >      - Statuses : 2 pass(s)
> >      - Exec time: [6.16, 6.18] s
> > 
> >    * igt@perf_pmu@semaphore-busy-vcs2:
> >      - Statuses :
> >      - Exec time: [None] s
> 
> Is this odd?

No such test semaphore-busy-vcs2. It exists only when you
--list-subtests, when executing IGT now uses engine discovery and
doesn't really have that subtest.


> 
> Also..
> 
> [snip]
> 
> > 
> > == Logs ==
> > 
> > For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3498/
> 
> ... I don't see the new tests in HTML?


https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3498/shards-all.html?testfilter=perf_pmu@semaphore-busy

You have to select "shards all" from the view menu up top, the default
view is "issues only".


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

      reply	other threads:[~2019-09-30  9:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-24 22:01 [igt-dev] [PATCH i-g-t] i915/perf_pmu: Compare semaphore and busy measurements Chris Wilson
2019-09-24 22:27 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2019-09-24 22:31 ` [igt-dev] ✗ GitLab.Pipeline: warning " Patchwork
2019-09-25  8:36 ` [igt-dev] [Intel-gfx] [PATCH i-g-t] " Tvrtko Ursulin
2019-09-25  9:23 ` [igt-dev] [PATCH i-g-t v2] " Chris Wilson
2019-09-25  9:27   ` [Intel-gfx] " Tvrtko Ursulin
2019-09-25  9:51 ` [igt-dev] ✗ GitLab.Pipeline: warning for i915/perf_pmu: Compare semaphore and busy measurements (rev2) Patchwork
2019-09-25  9:58 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2019-09-25 17:06 ` [igt-dev] ✓ Fi.CI.IGT: success for i915/perf_pmu: Compare semaphore and busy measurements Patchwork
2019-09-26  0:13 ` [igt-dev] ✗ Fi.CI.IGT: failure for i915/perf_pmu: Compare semaphore and busy measurements (rev2) Patchwork
2019-09-26  8:20   ` Tvrtko Ursulin
2019-09-30  9:39     ` Petri Latvala [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=20190930093942.GF4019@platvala-desk.ger.corp.intel.com \
    --to=petri.latvala@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=tvrtko.ursulin@linux.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