From: "Vudum, Lakshminarayana" <lakshminarayana.vudum@intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/vblank: Avoid storing a timestamp for the same frame twice (rev2)
Date: Thu, 18 Feb 2021 19:51:53 +0000 [thread overview]
Message-ID: <14c4e382b13f4832a234e3ddf918e22f@intel.com> (raw)
In-Reply-To: <YC6+XySefUEkPoKx@intel.com>
Re-reported.
-----Original Message-----
From: Ville Syrjälä <ville.syrjala@linux.intel.com>
Sent: Thursday, February 18, 2021 11:22 AM
To: intel-gfx@lists.freedesktop.org
Cc: Vudum, Lakshminarayana <lakshminarayana.vudum@intel.com>
Subject: Re: ✗ Fi.CI.BAT: failure for drm/vblank: Avoid storing a timestamp for the same frame twice (rev2)
On Thu, Feb 18, 2021 at 07:08:27PM -0000, Patchwork wrote:
> == Series Details ==
>
> Series: drm/vblank: Avoid storing a timestamp for the same frame twice (rev2)
> URL : https://patchwork.freedesktop.org/series/86672/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_9786 -> Patchwork_19701
> ====================================================
>
> Summary
> -------
>
> **FAILURE**
>
> Serious unknown changes coming with Patchwork_19701 absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_19701, 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/Patchwork_19701/index.html
>
> Possible new issues
> -------------------
>
> Here are the unknown changes that may have been introduced in Patchwork_19701:
>
> ### IGT changes ###
>
> #### Possible regressions ####
>
> * igt@gem_exec_suspend@basic-s0:
> - fi-cfl-8109u: [PASS][1] -> [INCOMPLETE][2]
> [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9786/fi-cfl-8109u/igt@gem_exec_suspend@basic-s0.html
> [2]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19701/fi-cfl-8109u/
> igt@gem_exec_suspend@basic-s0.html
Looks like the machine went AWOL during suspend. Seems unrelated to the patch at hand.
--
Ville Syrjälä
Intel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2021-02-18 19:51 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-04 2:04 [Intel-gfx] [PATCH] drm/vblank: Avoid storing a timestamp for the same frame twice Ville Syrjala
2021-02-04 3:12 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2021-02-04 5:44 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2021-02-04 15:32 ` [Intel-gfx] [PATCH] " Daniel Vetter
2021-02-04 15:55 ` Ville Syrjälä
2021-02-05 15:46 ` Daniel Vetter
2021-02-05 16:24 ` Ville Syrjälä
2021-02-05 21:19 ` Ville Syrjälä
2021-02-08 9:56 ` Daniel Vetter
2021-02-08 16:58 ` Ville Syrjälä
2021-02-08 17:43 ` Daniel Vetter
2021-02-08 18:05 ` Ville Syrjälä
2021-02-09 10:07 ` Daniel Vetter
2021-02-09 15:40 ` Ville Syrjälä
2021-02-09 16:44 ` Daniel Vetter
2021-02-18 16:03 ` [Intel-gfx] [PATCH v2] drm/vblank: Do not store a new vblank timestamp in drm_vblank_restore() Ville Syrjala
2021-02-18 16:10 ` Ville Syrjälä
2021-02-19 15:08 ` Daniel Vetter
2021-02-19 15:47 ` Ville Syrjälä
2021-02-18 19:08 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/vblank: Avoid storing a timestamp for the same frame twice (rev2) Patchwork
2021-02-18 19:22 ` Ville Syrjälä
2021-02-18 19:51 ` Vudum, Lakshminarayana [this message]
2021-02-18 19:29 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-02-18 20:58 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2021-02-21 4:18 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/vblank: Avoid storing a timestamp for the same frame twice (rev3) Patchwork
2021-02-21 5:41 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=14c4e382b13f4832a234e3ddf918e22f@intel.com \
--to=lakshminarayana.vudum@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ville.syrjala@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