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>,
	"martin.peres@linux.intel.com" <martin.peres@linux.intel.com>
Subject: Re: [igt-dev] ✗ Fi.CI.BAT: failure for Use C11 atomics (rev4)
Date: Tue, 25 Jun 2019 07:19:08 +0000	[thread overview]
Message-ID: <dff274af6a2292782bba179e2be2f213e74a85ff.camel@intel.com> (raw)
In-Reply-To: <20190624165920.1473.47292@emeril.freedesktop.org>

On Mon, 2019-06-24 at 16:59 +0000, Patchwork wrote:
> == Series Details ==
> 
> Series: Use C11 atomics (rev4)
> URL   : https://patchwork.freedesktop.org/series/62048/
> State : failure
> 
> == Summary ==
> 
> CI Bug Log - changes from CI_DRM_6336 -> IGTPW_3194
> ====================================================
> 
> Summary
> -------
> 
>   **FAILURE**
> 
>   Serious unknown changes coming with IGTPW_3194 absolutely need to be
>   verified manually.
>   
>   If you think the reported changes have nothing to do with the changes
>   introduced in IGTPW_3194, 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/4/mbox/
> 
> Possible new issues
> -------------------
> 
>   Here are the unknown changes that may have been introduced in IGTPW_3194:
> 
> ### IGT changes ###
> 
> #### Possible regressions ####
> 
>   * igt@core_auth@basic-auth:
>     - fi-blb-e6850:       [PASS][1] -> [DMESG-WARN][2]
>    [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6336/fi-blb-e6850/igt@core_auth@basic-auth.html
>    [2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3194/fi-blb-e6850/igt@core_auth@basic-auth.html
> 

Cc Martin

> Known issues
> ------------
> 
>   Here are the changes found in IGTPW_3194 that come from known issues:
> 
> ### IGT changes ###
> 
> #### Issues hit ####
> 
>   * igt@gem_pwrite@basic:
>     - fi-icl-u3:          [PASS][3] -> [DMESG-WARN][4] ([fdo#107724])
>    [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6336/fi-icl-u3/igt@gem_pwrite@basic.html
>    [4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3194/fi-icl-u3/igt@gem_pwrite@basic.html
> 
>   
> #### Possible fixes ####
> 
>   * igt@kms_chamelium@hdmi-hpd-fast:
>     - fi-kbl-7500u:       [FAIL][5] ([fdo#109485]) -> [PASS][6]
>    [5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6336/fi-kbl-7500u/igt@kms_chamelium@hdmi-hpd-fast.html
>    [6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3194/fi-kbl-7500u/igt@kms_chamelium@hdmi-hpd-fast.html
> 
>   * igt@kms_frontbuffer_tracking@basic:
>     - fi-hsw-peppy:       [DMESG-WARN][7] ([fdo#102614]) -> [PASS][8]
>    [7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6336/fi-hsw-peppy/igt@kms_frontbuffer_tracking@basic.html
>    [8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3194/fi-hsw-peppy/igt@kms_frontbuffer_tracking@basic.html
> 
>   
>   [fdo#102614]: https://bugs.freedesktop.org/show_bug.cgi?id=102614
>   [fdo#107724]: https://bugs.freedesktop.org/show_bug.cgi?id=107724
>   [fdo#109485]: https://bugs.freedesktop.org/show_bug.cgi?id=109485
> 
> 
> Participating hosts (49 -> 43)
> ------------------------------
> 
>   Additional (2): fi-icl-dsi fi-icl-u2 
>   Missing    (8): fi-kbl-soraka fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-icl-y fi-byt-clapper fi-bdw-samus 
> 
> 
> Build changes
> -------------
> 
>   * IGT: IGT_5066 -> IGTPW_3194
> 
>   CI_DRM_6336: 1c47064d13b90ef8b25cfa4066fb433809bf6ff5 @ git://anongit.freedesktop.org/gfx-ci/linux
>   IGTPW_3194: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3194/
>   IGT_5066: a6f5cc854efb4b7dfed7f0a2c1039a9ddd1a35a5 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
> 
> == Logs ==
> 
> For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3194/
> _______________________________________________
> 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-25  7:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-24 16:22 [igt-dev] [PATCH i-g-t v4 0/4] Use C11 atomics Guillaume Tucker
2019-06-24 16:22 ` [igt-dev] [PATCH i-g-t v4 1/4] meson: add libatomic dependency Guillaume Tucker
2019-06-24 16:22 ` [igt-dev] [PATCH i-g-t v4 2/4] gitlab-ci: add libatomic to docker images Guillaume Tucker
2019-06-25 10:48   ` Ser, Simon
2019-06-24 16:22 ` [igt-dev] [PATCH i-g-t v4 3/4] i915/gem_create: use atomic_* instead of __sync_* Guillaume Tucker
2019-06-24 16:22 ` [igt-dev] [PATCH i-g-t v4 4/4] tests/sw_sync: " Guillaume Tucker
2019-06-24 16:59 ` [igt-dev] ✗ Fi.CI.BAT: failure for Use C11 atomics (rev4) Patchwork
2019-06-25  7:19   ` Ser, Simon [this message]
2019-06-25  8:55     ` Guillaume Tucker
2019-06-25  8:06 ` [igt-dev] ✓ Fi.CI.BAT: success for Use C11 atomics (rev5) Patchwork
2019-06-25  9:16 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2019-06-25 10:54 ` [igt-dev] [PATCH i-g-t v4 0/4] Use C11 atomics Ser, Simon
2019-06-25 13:04   ` [Intel-gfx] " Guillaume Tucker

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=dff274af6a2292782bba179e2be2f213e74a85ff.camel@intel.com \
    --to=simon.ser@intel.com \
    --cc=guillaume.tucker@collabora.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=martin.peres@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