From: Patchwork <patchwork@emeril.freedesktop.org>
To: Nischala Yelchuri <nischala.yelchuri@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: [igt-dev] ✗ Fi.CI.BAT: failure for tests/kms_cursor_legacy: Add missing munmap
Date: Fri, 01 Mar 2019 19:53:38 -0000 [thread overview]
Message-ID: <20190301195338.18741.59945@emeril.freedesktop.org> (raw)
In-Reply-To: <20190301194900.78123-1-nischala.yelchuri@intel.com>
== Series Details ==
Series: tests/kms_cursor_legacy: Add missing munmap
URL : https://patchwork.freedesktop.org/series/57438/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_5680 -> IGTPW_2543
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with IGTPW_2543 absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in IGTPW_2543, 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/57438/revisions/1/mbox/
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in IGTPW_2543:
### IGT changes ###
#### Possible regressions ####
* igt@gem_exec_suspend@basic-s4-devices:
- fi-bsw-kefka: PASS -> DMESG-WARN
* igt@runner@aborted:
- fi-bsw-kefka: NOTRUN -> FAIL
Known issues
------------
Here are the changes found in IGTPW_2543 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_ctx_create@basic-files:
- fi-gdg-551: NOTRUN -> SKIP [fdo#109271] +106
* igt@gem_exec_suspend@basic-s3:
- fi-blb-e6850: PASS -> INCOMPLETE [fdo#107718]
* igt@i915_selftest@live_execlists:
- fi-apl-guc: PASS -> DMESG-WARN [fdo#108622]
* igt@kms_busy@basic-flip-c:
- fi-gdg-551: NOTRUN -> SKIP [fdo#109271] / [fdo#109278]
* igt@runner@aborted:
- fi-apl-guc: NOTRUN -> FAIL [fdo#108622] / [fdo#109720] / [fdo#109799]
[fdo#107718]: https://bugs.freedesktop.org/show_bug.cgi?id=107718
[fdo#108622]: https://bugs.freedesktop.org/show_bug.cgi?id=108622
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109278]: https://bugs.freedesktop.org/show_bug.cgi?id=109278
[fdo#109720]: https://bugs.freedesktop.org/show_bug.cgi?id=109720
[fdo#109799]: https://bugs.freedesktop.org/show_bug.cgi?id=109799
Participating hosts (43 -> 39)
------------------------------
Additional (1): fi-gdg-551
Missing (5): fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-icl-y
Build changes
-------------
* IGT: IGT_4866 -> IGTPW_2543
CI_DRM_5680: 348fd7b7fa6584957fa6a5143058b3fbb319806b @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_2543: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_2543/
IGT_4866: 189956af183c245eb237b3be4fa22953ec93bbe0 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_2543/
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
prev parent reply other threads:[~2019-03-01 19:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-01 19:49 [igt-dev] [PATCH] tests/kms_cursor_legacy: Add missing munmap Nischala Yelchuri
2019-03-01 19:17 ` Chris Wilson
2019-03-01 19:53 ` Patchwork [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=20190301195338.18741.59945@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=igt-dev@lists.freedesktop.org \
--cc=nischala.yelchuri@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