Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Naladala Ramanaidu <ramanaidu.naladala@intel.com>,
	igt-dev@lists.freedesktop.org
Cc: pranay.samala@intel.com,
	Naladala Ramanaidu <ramanaidu.naladala@intel.com>,
	"Syrjala, Ville" <ville.syrjala@intel.com>,
	"Saarinen, Jani" <jani.saarinen@intel.com>
Subject: Re: [PATCH i-g-t v1 1/2] tests/kms_plane_scaling: Reduce debug log level in CI for scaling tests
Date: Thu, 06 Nov 2025 15:09:08 +0200	[thread overview]
Message-ID: <191a8b272532dbd8de15b380b583de718a37e44f@intel.com> (raw)
In-Reply-To: <20251106092204.1505129-2-ramanaidu.naladala@intel.com>

On Thu, 06 Nov 2025, Naladala Ramanaidu <ramanaidu.naladala@intel.com> wrote:
> Reduce excessive logging in CI environments when multiple outputs
> are connected. It prevents CI runners from exceeding disk usage
> limits.

So how do we debug issues when there are no KMD debug logs? This can't
be the go-to solution in the long run.

Moreover, update_debug_mask_if_ci() doesn't even log the actual mask
being switched to.


BR,
Jani.


>
> Signed-off-by: Naladala Ramanaidu <ramanaidu.naladala@intel.com>
> ---
>  tests/kms_plane_scaling.c | 5 +++++
>  1 file changed, 5 insertions(+)
>
> diff --git a/tests/kms_plane_scaling.c b/tests/kms_plane_scaling.c
> index 63d35d76b..34c8f8a64 100644
> --- a/tests/kms_plane_scaling.c
> +++ b/tests/kms_plane_scaling.c
> @@ -32,6 +32,7 @@
>  
>  #include "igt.h"
>  #include "igt_vec.h"
> +#include "igt_sysfs.h"
>  #include <math.h>
>  
>  /**
> @@ -1358,11 +1359,15 @@ igt_main_args("", long_opts, help_str, opt_handler, &data)
>  		data.devid = is_intel_device(data.drm_fd) ?
>  			intel_get_drm_devid(data.drm_fd) : 0;
>  		igt_require(data.display.is_atomic);
> +		igt_install_exit_handler(igt_drm_debug_mask_reset_exit_handler);
>  	}
>  
>  	igt_subtest_group {
>  		igt_output_t *output;
>  
> +		if (igt_get_connected_output_count(&data.display) > 1)
> +			update_debug_mask_if_ci(DRM_UT_DRIVER | DRM_UT_CORE);
> +
>  		for (int index = 0; index < ARRAY_SIZE(scaler_with_pixel_format_tests); index++) {
>  			igt_describe(scaler_with_pixel_format_tests[index].describe);
>  			igt_subtest_with_dynamic(scaler_with_pixel_format_tests[index].name) {

-- 
Jani Nikula, Intel

  parent reply	other threads:[~2025-11-06 13:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-06  9:22 [PATCH i-g-t v1 0/2] Limit debug logging in CI for scaling tests Naladala Ramanaidu
2025-11-06  9:22 ` [PATCH i-g-t v1 1/2] tests/kms_plane_scaling: Reduce debug log level " Naladala Ramanaidu
2025-11-06 12:59   ` Samala, Pranay
2025-11-06 13:09   ` Jani Nikula [this message]
2025-11-07 13:54     ` Ville Syrjälä
2025-11-07 16:10       ` Naladala, Ramanaidu
2025-11-07 20:34         ` Kamil Konieczny
2025-11-06  9:22 ` [PATCH i-g-t v1 2/2] HAX patch do not merge Naladala Ramanaidu
2025-11-06 19:29 ` ✗ Xe.CI.BAT: failure for Limit debug logging in CI for scaling tests Patchwork
2025-11-06 20:30 ` ✗ i915.CI.BAT: " Patchwork
2025-11-07 17:02 ` ✗ Xe.CI.Full: " 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=191a8b272532dbd8de15b380b583de718a37e44f@intel.com \
    --to=jani.nikula@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=jani.saarinen@intel.com \
    --cc=pranay.samala@intel.com \
    --cc=ramanaidu.naladala@intel.com \
    --cc=ville.syrjala@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