From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: igt-dev@lists.freedesktop.org,
Lakshminarayana Vudum <lakshminarayana.vudum@intel.com>
Subject: Re: [igt-dev] ✗ Fi.CI.IGT: failure for i915: Avoid set_domain -ENOMEM error with huge buffers
Date: Mon, 29 Mar 2021 22:44:11 -0700 [thread overview]
Message-ID: <87tuot19hw.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <161708206647.22471.13837189475686372810@emeril.freedesktop.org>
On Mon, 29 Mar 2021 22:27:46 -0700, Patchwork wrote:
>
> [1 <text/plain; utf-8 (7bit)>]
> [2 <text/html; utf-8 (quoted-printable)>]
> Project List - Patchwork
>
> Patch Details
>
> Series: i915: Avoid set_domain -ENOMEM error with huge buffers
> URL: https://patchwork.freedesktop.org/series/88561/
> State: failure
> Details: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5675/index.html
>
> CI Bug Log - changes from CI_DRM_9914_full -> IGTPW_5675_full
>
> Summary
>
> FAILURE
>
> Serious unknown changes coming with IGTPW_5675_full absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in IGTPW_5675_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_5675/index.html
>
> Possible new issues
>
> Here are the unknown changes that may have been introduced in IGTPW_5675_full:
>
> IGT changes
>
> Possible regressions
>
> * igt@perf@polling-parameterized:
>
> * shard-iclb: PASS -> SKIP
>
> * shard-tglb: PASS -> SKIP
This is false positive. This patch cannot affect this test. It can only
affect igt@prime_mmap and igt@gem_exec_params. Thanks.
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2021-03-30 5:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-30 3:50 [igt-dev] [PATCH i-g-t] i915: Avoid set_domain -ENOMEM error with huge buffers Ashutosh Dixit
2021-03-30 4:26 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2021-03-30 5:27 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2021-03-30 5:44 ` Dixit, Ashutosh [this message]
2021-03-30 18:06 ` Vudum, Lakshminarayana
2021-03-30 10:28 ` [igt-dev] [PATCH i-g-t] " Matthew Auld
2021-03-30 19:31 ` Dixit, Ashutosh
2021-03-31 9:02 ` Matthew Auld
2021-04-01 0:45 ` Dixit, Ashutosh
2021-04-01 12:49 ` Ruhl, Michael J
2021-04-01 19:25 ` Dixit, Ashutosh
2021-04-01 21:11 ` Ruhl, Michael J
2021-04-07 7:51 ` Daniel Vetter
2021-03-30 15:07 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2021-03-30 16:14 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2021-03-30 22:02 ` [igt-dev] [PATCH i-g-t] i915: Avoid set_domain -ENOMEM error with large objects Ashutosh Dixit
2021-03-31 7:52 ` [igt-dev] ✓ Fi.CI.BAT: success for i915: Avoid set_domain -ENOMEM error with huge buffers (rev2) Patchwork
2021-03-31 8:52 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2021-04-01 0:43 ` [igt-dev] [PATCH i-g-t] i915: Avoid set_domain -ENOMEM error with large objects Ashutosh Dixit
2021-04-01 10:22 ` [igt-dev] ✓ Fi.CI.BAT: success for i915: Avoid set_domain -ENOMEM error with huge buffers (rev3) Patchwork
2021-04-01 12:36 ` [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=87tuot19hw.wl-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=lakshminarayana.vudum@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