public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Vudum, Lakshminarayana" <lakshminarayana.vudum@intel.com>
To: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx]  ✗ Fi.CI.IGT: failure for drm/i915: Start disabling pread/pwrite ioctl's for future platforms
Date: Mon, 25 Jan 2021 02:36:18 +0000	[thread overview]
Message-ID: <a2aa6cd4a23042b7928b3dbfd62582fb@intel.com> (raw)
In-Reply-To: <87a6sxlwl3.wl-ashutosh.dixit@intel.com>

Re-reported.

-----Original Message-----
From: Dixit, Ashutosh <ashutosh.dixit@intel.com> 
Sent: Sunday, January 24, 2021 3:55 PM
To: intel-gfx@lists.freedesktop.org; Vudum, Lakshminarayana <lakshminarayana.vudum@intel.com>
Subject: Re: ✗ Fi.CI.IGT: failure for drm/i915: Start disabling pread/pwrite ioctl's for future platforms

On Sat, 23 Jan 2021 05:05:02 -0800, Patchwork wrote:
>
> [1  <text/plain; utf-8 (7bit)>]
> [2  <text/html; utf-8 (7bit)>]
> Project List - Patchwork
>
> Patch Details
>
>  Series:  drm/i915: Start disabling pread/pwrite ioctl's for future 
> platforms
>  URL:  https://patchwork.freedesktop.org/series/86199/
>  State:  failure
>  Details:  
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19470/index.html
>
> CI Bug Log - changes from CI_DRM_9671_full -> Patchwork_19470_full
>
> Summary
>
> FAILURE
>
> Serious unknown changes coming with Patchwork_19470_full absolutely 
> need to be verified manually.
>
> If you think the reported changes have nothing to do with the changes 
> introduced in Patchwork_19470_full, please notify your bug team to 
> allow them to document this new failure mode, which will reduce false positives in CI.
>
> Possible new issues
>
> Here are the unknown changes that may have been introduced in Patchwork_19470_full:
>
> IGT changes
>
> Possible regressions
>
> * igt@kms_sequence@queue-busy:
>
>  * shard-skl: PASS -> FAIL

This is a unrelated failure and a false positive, the patch should not have any effect on this platform.

Seeing a few igt@kms_sequence bugs in gitlab but maybe the signature for this one is a little different. Thanks.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2021-01-25  2:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-22 22:40 [Intel-gfx] [PATCH 0/1] drm/i915: Start disabling pread/pwrite ioctl's for future platforms Ashutosh Dixit
2021-01-22 22:40 ` [Intel-gfx] [PATCH 1/1] " Ashutosh Dixit
2021-03-10 21:37   ` Jason Ekstrand
2021-01-23  2:36 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2021-01-23 13:05 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2021-01-24 23:54   ` Dixit, Ashutosh
2021-01-25  2:36     ` Vudum, Lakshminarayana [this message]
2021-01-25  2:35 ` [Intel-gfx] ✓ Fi.CI.IGT: success " Patchwork
2021-03-11 20:20 ` [Intel-gfx] [PATCH 0/1]drm/i915: Disable pread/pwrite ioctl's for future platforms (v2) Jason Ekstrand
2021-03-11 20:20   ` [Intel-gfx] [PATCH 1/1] drm/i915: " Jason Ekstrand
2021-03-12  3:28     ` Dixit, Ashutosh
2021-03-12 11:37       ` Maarten Lankhorst

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=a2aa6cd4a23042b7928b3dbfd62582fb@intel.com \
    --to=lakshminarayana.vudum@intel.com \
    --cc=ashutosh.dixit@intel.com \
    --cc=intel-gfx@lists.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