From: Petri Latvala <petri.latvala@intel.com>
To: Tejas Upadhyay <tejaskumarx.surendrakumar.upadhyay@intel.com>
Cc: igt-dev@lists.freedesktop.org, hariom.pandey@intel.com
Subject: Re: [igt-dev] [i-g-t] test/i915/basic-wide-active: set max relocation limit
Date: Wed, 7 Apr 2021 10:42:59 +0300 [thread overview]
Message-ID: <YG1igzvUPT41npFD@platvala-desk.ger.corp.intel.com> (raw)
In-Reply-To: <20210407030952.44288-1-tejaskumarx.surendrakumar.upadhyay@intel.com>
On Wed, Apr 07, 2021 at 08:39:52AM +0530, Tejas Upadhyay wrote:
> practically its highly unlike to get as many relocations which
> basic-wide-active test is testing thus setting and adjusting
> max limit and count to avoid failures on legacy platforms like KBL.
The previous such patch against gem_exec_reloc had an unaddressed
objection and it was still merged. If you don't agree with the
objection, you still need to explain how in your view it's not valid.
This commit message quite clearly says the purpose of this patch is to
ignore failures, improving passrate metrics instead of driver
health. The same objection to this patch applies as far as I can see,
so nak on this.
--
Petri Latvala
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2021-04-07 7:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-07 3:09 [igt-dev] [i-g-t] test/i915/basic-wide-active: set max relocation limit Tejas Upadhyay
2021-04-07 4:02 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2021-04-07 5:00 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2021-04-07 7:42 ` Petri Latvala [this message]
2021-04-07 8:29 ` [igt-dev] [i-g-t] " Surendrakumar Upadhyay, TejaskumarX
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=YG1igzvUPT41npFD@platvala-desk.ger.corp.intel.com \
--to=petri.latvala@intel.com \
--cc=hariom.pandey@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=tejaskumarx.surendrakumar.upadhyay@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.