From: Patchwork <patchwork@emeril.freedesktop.org>
To: Simon Ser <simon.ser@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: [igt-dev] ✗ Fi.CI.BAT: failure for lib/igt_chamelium: wait for worker thread to finish
Date: Wed, 05 Jun 2019 11:51:13 -0000 [thread overview]
Message-ID: <20190605115113.10842.66238@emeril.freedesktop.org> (raw)
In-Reply-To: <20190605103627.32526-1-simon.ser@intel.com>
== Series Details ==
Series: lib/igt_chamelium: wait for worker thread to finish
URL : https://patchwork.freedesktop.org/series/61648/
State : failure
== Summary ==
CI Bug Log - changes from IGT_5039 -> IGTPW_3115
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with IGTPW_3115 absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in IGTPW_3115, 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/61648/revisions/1/mbox/
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in IGTPW_3115:
### IGT changes ###
#### Possible regressions ####
* igt@i915_module_load@reload-with-fault-injection:
- fi-icl-u3: [PASS][1] -> [WARN][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5039/fi-icl-u3/igt@i915_module_load@reload-with-fault-injection.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3115/fi-icl-u3/igt@i915_module_load@reload-with-fault-injection.html
* igt@i915_selftest@live_contexts:
- fi-icl-u3: [PASS][3] -> [SKIP][4] +18 similar issues
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5039/fi-icl-u3/igt@i915_selftest@live_contexts.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3115/fi-icl-u3/igt@i915_selftest@live_contexts.html
* igt@i915_selftest@live_hangcheck:
- fi-kbl-7567u: [PASS][5] -> [DMESG-FAIL][6]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5039/fi-kbl-7567u/igt@i915_selftest@live_hangcheck.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3115/fi-kbl-7567u/igt@i915_selftest@live_hangcheck.html
#### Suppressed ####
The following results come from untrusted machines, tests, or statuses.
They do not affect the overall result.
* {igt@i915_selftest@live_blt}:
- fi-icl-u3: [PASS][7] -> [SKIP][8] +2 similar issues
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5039/fi-icl-u3/igt@i915_selftest@live_blt.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3115/fi-icl-u3/igt@i915_selftest@live_blt.html
Known issues
------------
Here are the changes found in IGTPW_3115 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@i915_module_load@reload-no-display:
- fi-icl-u3: [PASS][9] -> [DMESG-WARN][10] ([fdo#107724])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5039/fi-icl-u3/igt@i915_module_load@reload-no-display.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3115/fi-icl-u3/igt@i915_module_load@reload-no-display.html
* igt@i915_selftest@live_requests:
- fi-icl-u3: [PASS][11] -> [SKIP][12] ([fdo#109644] / [fdo#110464])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5039/fi-icl-u3/igt@i915_selftest@live_requests.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3115/fi-icl-u3/igt@i915_selftest@live_requests.html
* igt@kms_frontbuffer_tracking@basic:
- fi-icl-u2: [PASS][13] -> [FAIL][14] ([fdo#103167])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5039/fi-icl-u2/igt@kms_frontbuffer_tracking@basic.html
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3115/fi-icl-u2/igt@kms_frontbuffer_tracking@basic.html
#### Possible fixes ####
* igt@core_auth@basic-auth:
- fi-icl-u3: [DMESG-WARN][15] ([fdo#107724]) -> [PASS][16]
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5039/fi-icl-u3/igt@core_auth@basic-auth.html
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3115/fi-icl-u3/igt@core_auth@basic-auth.html
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#103167]: https://bugs.freedesktop.org/show_bug.cgi?id=103167
[fdo#107724]: https://bugs.freedesktop.org/show_bug.cgi?id=107724
[fdo#109644]: https://bugs.freedesktop.org/show_bug.cgi?id=109644
[fdo#110464]: https://bugs.freedesktop.org/show_bug.cgi?id=110464
Participating hosts (55 -> 45)
------------------------------
Missing (10): fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-ctg-p8600 fi-gdg-551 fi-kbl-7560u fi-byt-clapper fi-bdw-samus fi-kbl-r
Build changes
-------------
* IGT: IGT_5039 -> IGTPW_3115
CI_DRM_6194: 10a75edfc43885387e1e9e2bc50f9678e9bf59d6 @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_3115: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3115/
IGT_5039: 2d4f470bba1cb51ed116fb80b170f717c6294714 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3115/
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-06-05 11:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 10:36 [igt-dev] [PATCH i-g-t] lib/igt_chamelium: wait for worker thread to finish Simon Ser
2019-06-05 11:51 ` Patchwork [this message]
2019-06-05 12:03 ` [igt-dev] ✗ Fi.CI.BAT: failure for " Ser, Simon
2019-06-05 15:47 ` [igt-dev] [PATCH i-g-t] " Arkadiusz Hiler
2019-06-05 16:44 ` [igt-dev] ✗ Fi.CI.BAT: failure for lib/igt_chamelium: wait for worker thread to finish (rev2) Patchwork
2019-06-06 7:05 ` Ser, Simon
2019-06-06 13:50 ` [igt-dev] ✓ Fi.CI.BAT: success for lib/igt_chamelium: wait for worker thread to finish (rev3) Patchwork
2019-06-06 15:30 ` [igt-dev] ✓ Fi.CI.BAT: success for lib/igt_chamelium: wait for worker thread to finish (rev4) Patchwork
2019-06-08 16:21 ` [igt-dev] ✗ Fi.CI.IGT: failure for lib/igt_chamelium: wait for worker thread to finish (rev3) Patchwork
2019-06-08 22:38 ` [igt-dev] ✓ Fi.CI.IGT: success for lib/igt_chamelium: wait for worker thread to finish (rev4) 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=20190605115113.10842.66238@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=igt-dev@lists.freedesktop.org \
--cc=simon.ser@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