public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Ser, Simon" <simon.ser@intel.com>
To: "guillaume.tucker@collabora.com" <guillaume.tucker@collabora.com>,
	"igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] ✗ Fi.CI.BAT: failure for Use C11 atomics (rev2)
Date: Wed, 19 Jun 2019 06:52:22 +0000	[thread overview]
Message-ID: <e5bc9ed973e846373469f508668a21b83c781d08.camel@intel.com> (raw)
In-Reply-To: <20190618133119.30455.98385@emeril.freedesktop.org>

On Tue, 2019-06-18 at 13:31 +0000, Patchwork wrote:
> == Series Details ==
> 
> Series: Use C11 atomics (rev2)
> URL   : https://patchwork.freedesktop.org/series/62048/
> State : failure
> 
> == Summary ==
> 
> CI Bug Log - changes from CI_DRM_6291 -> IGTPW_3170
> ====================================================
> 
> Summary
> -------
> 
>   **FAILURE**
> 
>   Serious unknown changes coming with IGTPW_3170 absolutely need to be
>   verified manually.
>   
>   If you think the reported changes have nothing to do with the changes
>   introduced in IGTPW_3170, 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/62048/revisions/2/mbox/
> 
> Possible new issues
> -------------------
> 
>   Here are the unknown changes that may have been introduced in IGTPW_3170:
> 
> ### IGT changes ###
> 
> #### Possible regressions ####
> 
>   * igt@i915_selftest@live_gem:
>     - fi-cfl-guc:         [PASS][1] -> [DMESG-WARN][2]
>    [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6291/fi-cfl-guc/igt@i915_selftest@live_gem.html
>    [2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3170/fi-cfl-guc/igt@i915_selftest@live_gem.html
> 
>   * igt@runner@aborted:
>     - fi-cfl-guc:         NOTRUN -> [FAIL][3]
>    [3]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3170/fi-cfl-guc/igt@runner@aborted.html

Seems unrelated. Feel free to click the "Test again" button on 
https://patchwork.freedesktop.org/series/62048/

>   
> Known issues
> ------------
> 
>   Here are the changes found in IGTPW_3170 that come from known issues:
> 
> ### IGT changes ###
> 
> #### Issues hit ####
> 
>   * igt@core_auth@basic-auth:
>     - fi-icl-u3:          [PASS][4] -> [DMESG-WARN][5] ([fdo#107724]) +1 similar issue
>    [4]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6291/fi-icl-u3/igt@core_auth@basic-auth.html
>    [5]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3170/fi-icl-u3/igt@core_auth@basic-auth.html
> 
>   * igt@gem_exec_suspend@basic-s3:
>     - fi-blb-e6850:       [PASS][6] -> [INCOMPLETE][7] ([fdo#107718])
>    [6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6291/fi-blb-e6850/igt@gem_exec_suspend@basic-s3.html
>    [7]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3170/fi-blb-e6850/igt@gem_exec_suspend@basic-s3.html
> 
>   * igt@kms_chamelium@hdmi-hpd-fast:
>     - fi-kbl-7500u:       [PASS][8] -> [FAIL][9] ([fdo#109485])
>    [8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6291/fi-kbl-7500u/igt@kms_chamelium@hdmi-hpd-fast.html
>    [9]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3170/fi-kbl-7500u/igt@kms_chamelium@hdmi-hpd-fast.html
> 
>   * igt@kms_cursor_legacy@basic-flip-after-cursor-varying-size:
>     - fi-icl-dsi:         [PASS][10] -> [DMESG-WARN][11] ([fdo#106107])
>    [10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6291/fi-icl-dsi/igt@kms_cursor_legacy@basic-flip-after-cursor-varying-size.html
>    [11]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3170/fi-icl-dsi/igt@kms_cursor_legacy@basic-flip-after-cursor-varying-size.html
> 
>   * igt@kms_frontbuffer_tracking@basic:
>     - fi-hsw-peppy:       [PASS][12] -> [DMESG-WARN][13] ([fdo#102614])
>    [12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6291/fi-hsw-peppy/igt@kms_frontbuffer_tracking@basic.html
>    [13]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3170/fi-hsw-peppy/igt@kms_frontbuffer_tracking@basic.html
> 
>   
> #### Possible fixes ####
> 
>   * igt@gem_mmap_gtt@basic-short:
>     - fi-icl-u3:          [DMESG-WARN][14] ([fdo#107724]) -> [PASS][15] +2 similar issues
>    [14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6291/fi-icl-u3/igt@gem_mmap_gtt@basic-short.html
>    [15]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3170/fi-icl-u3/igt@gem_mmap_gtt@basic-short.html
> 
>   * igt@prime_vgem@basic-wait-default:
>     - fi-icl-dsi:         [DMESG-WARN][16] ([fdo#106107]) -> [PASS][17]
>    [16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6291/fi-icl-dsi/igt@prime_vgem@basic-wait-default.html
>    [17]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3170/fi-icl-dsi/igt@prime_vgem@basic-wait-default.html
> 
>   
>   [fdo#102614]: https://bugs.freedesktop.org/show_bug.cgi?id=102614
>   [fdo#106107]: https://bugs.freedesktop.org/show_bug.cgi?id=106107
>   [fdo#107718]: https://bugs.freedesktop.org/show_bug.cgi?id=107718
>   [fdo#107724]: https://bugs.freedesktop.org/show_bug.cgi?id=107724
>   [fdo#109485]: https://bugs.freedesktop.org/show_bug.cgi?id=109485
> 
> 
> Participating hosts (48 -> 36)
> ------------------------------
> 
>   Missing    (12): fi-kbl-soraka fi-cml-u2 fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-icl-u2 fi-bsw-cyan fi-ctg-p8600 fi-icl-y fi-byt-clapper fi-bdw-samus fi-cml-u 
> 
> 
> Build changes
> -------------
> 
>   * IGT: IGT_5059 -> IGTPW_3170
> 
>   CI_DRM_6291: 30a8dd688b1e9b56df650976b5058da5022dcfb8 @ git://anongit.freedesktop.org/gfx-ci/linux
>   IGTPW_3170: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3170/
>   IGT_5059: 1f67ee0d09d6513f487f2be74aae9700e755258a @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
> 
> == Logs ==
> 
> For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3170/
> _______________________________________________
> 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

  reply	other threads:[~2019-06-19  6:52 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-18 12:27 [igt-dev] [PATCH i-g-t v3 0/4] Use C11 atomics Guillaume Tucker
2019-06-18 12:27 ` [Intel-gfx] [PATCH i-g-t v3 1/4] meson: add libatomic dependency Guillaume Tucker
2019-06-18 13:20   ` [igt-dev] " Ser, Simon
2019-06-18 13:59     ` Guillaume Tucker
2019-06-18 14:37       ` Ser, Simon
2019-06-18 16:03         ` Guillaume Tucker
2019-06-19  6:42           ` Ser, Simon
2019-06-19  7:24             ` Guillaume Tucker
2019-06-18 12:27 ` [igt-dev] [PATCH i-g-t v3 2/4] gitlab-ci: add libatomic to docker images Guillaume Tucker
2019-06-19  6:50   ` Ser, Simon
2019-06-19  8:09     ` Guillaume Tucker
2019-06-18 12:27 ` [igt-dev] [PATCH i-g-t v3 3/4] i915/gem_create: use atomic_* instead of __sync_* Guillaume Tucker
2019-06-18 12:27 ` [Intel-gfx] [PATCH i-g-t v3 4/4] tests/sw_sync: " Guillaume Tucker
2019-06-18 13:31 ` [igt-dev] ✗ Fi.CI.BAT: failure for Use C11 atomics (rev2) Patchwork
2019-06-19  6:52   ` Ser, Simon [this message]
2019-06-19  7:02     ` Saarinen, Jani
2019-06-19  7:32       ` Peres, Martin
2019-06-19  7:46         ` Guillaume Tucker
2019-06-19  8:05 ` [igt-dev] ✓ Fi.CI.BAT: success for Use C11 atomics (rev3) Patchwork
2019-06-19 21:21 ` [igt-dev] ✓ 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=e5bc9ed973e846373469f508668a21b83c781d08.camel@intel.com \
    --to=simon.ser@intel.com \
    --cc=guillaume.tucker@collabora.com \
    --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