Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: "Zbigniew Kempczyński" <zbigniew.kempczynski@intel.com>
Cc: <igt-dev@lists.freedesktop.org>,
	Christoph Manszewski <christoph.manszewski@intel.com>
Subject: Re: [PATCH i-g-t] scripts/test_list: Drop logging out list of not compiled tests
Date: Mon, 23 Sep 2024 09:35:34 -0700	[thread overview]
Message-ID: <85zfny5nvt.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <20240923080520.39559-1-zbigniew.kempczynski@intel.com>

On Mon, 23 Sep 2024 01:05:20 -0700, Zbigniew Kempczyński wrote:
>
> Logging out of not compiled tests looks like warning what is confusing.
> Get rid of this printing to keep building steps clear.
>
> Signed-off-by: Zbigniew Kempczyński <zbigniew.kempczynski@intel.com>
> Cc: Ashutosh Dixit <ashutosh.dixit@intel.com>
> Cc: Christoph Manszewski <christoph.manszewski@intel.com>

Reviewed-by: Ashutosh Dixit <ashutosh.dixit@intel.com>

> ---
>  scripts/test_list.py | 2 --
>  1 file changed, 2 deletions(-)
>
> diff --git a/scripts/test_list.py b/scripts/test_list.py
> index 40b6b7829b..867d284003 100644
> --- a/scripts/test_list.py
> +++ b/scripts/test_list.py
> @@ -1196,8 +1196,6 @@ class TestList:
>          run_subtests = set(self.get_testlist())
>
>          not_compiled = set(self.get_not_compiled())
> -        for test_basename in not_compiled:
> -            print(f"INFO: Found documentation for '{test_basename}' but no binary")
>
>          # Compare sets
>
> --
> 2.34.1
>

  reply	other threads:[~2024-09-23 16:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-23  8:05 [PATCH i-g-t] scripts/test_list: Drop logging out list of not compiled tests Zbigniew Kempczyński
2024-09-23 16:35 ` Dixit, Ashutosh [this message]
2024-09-25 22:01 ` ✗ Fi.CI.BAT: failure for " 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=85zfny5nvt.wl-ashutosh.dixit@intel.com \
    --to=ashutosh.dixit@intel.com \
    --cc=christoph.manszewski@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=zbigniew.kempczynski@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