From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: igt-dev@lists.freedesktop.org,
Patchwork <patchwork@emeril.freedesktop.org>,
Arjun Melkaveri <arjun.melkaveri@intel.com>
Subject: Re: [igt-dev] ✗ Fi.CI.IGT: failure for i915/gem_exec_nop:Adjusted test to utilize all available engines (rev8)
Date: Fri, 31 Jan 2020 10:15:03 +0000 [thread overview]
Message-ID: <0b4061f3-0ddd-ccc2-c66b-7b31e9d18709@linux.intel.com> (raw)
In-Reply-To: <158043903896.13120.1526700707979050531@emeril.freedesktop.org>
On 31/01/2020 02:50, Patchwork wrote:
> == Series Details ==
>
> Series: i915/gem_exec_nop:Adjusted test to utilize all available engines (rev8)
> URL : https://patchwork.freedesktop.org/series/72334/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from IGT_5396_full -> IGTPW_4023_full
> ====================================================
>
> Summary
> -------
>
> **FAILURE**
>
> Serious unknown changes coming with IGTPW_4023_full absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in IGTPW_4023_full, 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/IGTPW_4023/index.html
>
> Possible new issues
> -------------------
>
> Here are the unknown changes that may have been introduced in IGTPW_4023_full:
>
> ### IGT changes ###
>
> #### Possible regressions ####
>
> * igt@gem_partial_pwrite_pread@writes-after-reads:
> - shard-hsw: [PASS][1] -> [FAIL][2]
> [1]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5396/shard-hsw6/igt@gem_partial_pwrite_pread@writes-after-reads.html
> [2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4023/shard-hsw2/igt@gem_partial_pwrite_pread@writes-after-reads.html
Unrelated so pushed.
Regards,
Tvrtko
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
prev parent reply other threads:[~2020-01-31 10:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-29 3:26 [igt-dev] [PATCH V8] i915/gem_exec_nop:Adjusted test to utilize all available engines Arjun Melkaveri
2020-01-29 3:53 ` [igt-dev] ✗ GitLab.Pipeline: failure for i915/gem_exec_nop:Adjusted test to utilize all available engines (rev8) Patchwork
2020-01-29 4:05 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2020-01-29 10:15 ` [igt-dev] [PATCH V8] i915/gem_exec_nop:Adjusted test to utilize all available engines Tvrtko Ursulin
2020-01-31 2:50 ` [igt-dev] ✗ Fi.CI.IGT: failure for i915/gem_exec_nop:Adjusted test to utilize all available engines (rev8) Patchwork
2020-01-31 10:15 ` Tvrtko Ursulin [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=0b4061f3-0ddd-ccc2-c66b-7b31e9d18709@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=arjun.melkaveri@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=patchwork@emeril.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