Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Naladala, Ramanaidu" <Ramanaidu.naladala@intel.com>
To: <igt-dev@lists.freedesktop.org>
Subject: Re: FW: [PATCH i-g-t v2 1/2] tests/kms_atomic_transition: Use extended flag for local execution
Date: Mon, 11 Nov 2024 12:09:10 +0530	[thread overview]
Message-ID: <a9f3b691-9cc1-4e42-a70d-7391ebc82b6e@intel.com> (raw)
In-Reply-To: <PH7PR11MB6053D85677A7EDB6C2071357E7582@PH7PR11MB6053.namprd11.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 1949 bytes --]


On 11/11/2024 11:49 AM, Samala, Pranay wrote:
>
> -----Original Message-----
> From: Samala, Pranay<pranay.samala@intel.com> 
> Sent: Wednesday, November 6, 2024 2:49 PM
> To:igt-dev@lists.freedesktop.org
> Cc: B S, Karthik<karthik.b.s@intel.com>; Joshi, Kunal1<kunal1.joshi@intel.com>; Lattannavar, Sameer<sameer.lattannavar@intel.com>; Samala, Pranay<pranay.samala@intel.com>
> Subject: [PATCH i-g-t v2 1/2] tests/kms_atomic_transition: Use extended flag for local execution
>
> There is no need to reduce the debug log level for local executions.
> This flag is used to prevent the reduction of the debug log level in local environments, while it will lower the log level in CI environments.
>
> To avoid reducing the debug log level in local executions, the extended flag must be explicitly used.
>
> Signed-off-by: Pranay Samala<pranay.samala@intel.com>
> ---
>   tests/kms_atomic_transition.c | 16 +++++++++-------
>   1 file changed, 9 insertions(+), 7 deletions(-)
>
> diff --git a/tests/kms_atomic_transition.c b/tests/kms_atomic_transition.c index f4f8afc66..f11e846d8 100644
> --- a/tests/kms_atomic_transition.c
> +++ b/tests/kms_atomic_transition.c
> @@ -1189,13 +1189,15 @@ igt_main_args("", long_opts, help_str, opt_handler, &data)
>   		for_each_connected_output(&data.display, output)
>   			count++;
>   
> -		dir = igt_sysfs_drm_module_params_open();
> -		if (dir >= 0) {
> -			current_log_level = igt_drm_debug_level_get(dir);
> -			close(dir);
> -
> -			if (current_log_level > 10)
> -				igt_drm_debug_level_update(10);
> +		if (!data.extended) {
> +			dir = igt_sysfs_drm_module_params_open();
> +			if (dir >= 0) {
> +				current_log_level = igt_drm_debug_level_get(dir);
> +				close(dir);
> +
> +				if (current_log_level > 10)
> +					igt_drm_debug_level_update(10);
> +			}
>   		}
>   	}

LGTM,

Reviewed-by: Naladala Ramanaidu <ramanaidu.naladala@intel.com> 
<mailto:ramanaidu.naladala@intel.com>

>   
> --
> 2.34.1
>

[-- Attachment #2: Type: text/html, Size: 38643 bytes --]

  parent reply	other threads:[~2024-11-11  6:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-06  9:19 [PATCH i-g-t v2 1/2] tests/kms_atomic_transition: Use extended flag for local execution Pranay Samala
2024-11-06  9:19 ` [PATCH i-g-t v2 2/2] HAX: Do not merge Pranay Samala
2024-11-06 10:48 ` ✗ CI.xeBAT: failure for series starting with [i-g-t,v2,1/2] tests/kms_atomic_transition: Use extended flag for local execution Patchwork
2024-11-06 11:11 ` ✗ Fi.CI.BAT: " Patchwork
2024-11-07 12:02 ` ✗ CI.xeFULL: " Patchwork
     [not found] ` <PH7PR11MB6053D85677A7EDB6C2071357E7582@PH7PR11MB6053.namprd11.prod.outlook.com>
2024-11-11  6:39   ` Naladala, Ramanaidu [this message]
2024-11-12 11:37 ` ✓ Fi.CI.BAT: success " Patchwork
2024-11-12 14:20 ` ✗ Fi.CI.IGT: failure " 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=a9f3b691-9cc1-4e42-a70d-7391ebc82b6e@intel.com \
    --to=ramanaidu.naladala@intel.com \
    --cc=igt-dev@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