From: Sebastian Brzezinka <sebastian.brzezinka@intel.com>
To: Kamil Konieczny <kamil.konieczny@linux.intel.com>,
<igt-dev@lists.freedesktop.org>
Cc: Ewelina Musial <ewelina.musial@intel.com>,
Lucas De Marchi <lucas.demarchi@intel.com>,
Ryszard Knop <ryszard.knop@intel.com>,
"Krzysztof Karas" <krzysztof.karas@intel.com>,
Petri Latvala <adrinael@adrinael.net>
Subject: Re: [PATCH i-g-t v5] runner: Parse results harder
Date: Thu, 6 Mar 2025 09:16:57 +0000 [thread overview]
Message-ID: <D892JDK00AAD.2NMTT2TJIHFBO@intel.com> (raw)
In-Reply-To: <20250305193137.295162-1-kamil.konieczny@linux.intel.com>
Hi Kamil
On Wed Mar 5, 2025 at 7:31 PM UTC, Kamil Konieczny wrote:
> Sometimes an error happens in kernel or in test that leaves
> output files in corrupted or incorrect state. While runner or
> resume will just move on to executing next test, when generating
> results it could end up with no results.json
>
> Try processing outputs a little more persistently and use any
> output file left there, even if only dmesg.txt. Also, when no
> useful output files were present, instead of breaking out add
> notrun.
>
> Inform about processing results for each test so a problem
> could be spotted more easily.
>
> v2: removed ')' from 'notrun\n)' (Kamil)
> using bool var, added more prints about errors (Ryszard)
> v3: reused open_for_reading, removed bool var (Krzysztof)
> closing only positive fds[] in close_outputs(), checking
> file sizes also if all opens succeeded (Kamil)
> v4: reverting to v2 and addresing review comments (Krzysztof)
> closing only already opened file, drop early return when empty
> output files as this changes run status (Kamil)
> v5: reverting to returning false after any out/err/dmesg output
> is missing, simplified later checks and printed logs, fixed
> closing outputs (Kamil)
>
> Cc: Ewelina Musial <ewelina.musial@intel.com>
> Cc: Lucas De Marchi <lucas.demarchi@intel.com>
> Cc: Ryszard Knop <ryszard.knop@intel.com>
> Cc: Krzysztof Karas <krzysztof.karas@intel.com>
> Cc: Petri Latvala <adrinael@adrinael.net>
> Signed-off-by: Kamil Konieczny <kamil.konieczny@linux.intel.com>
> ---
> For results checks compile igt with runner and then run
> meson test -C build
>
> runner/executor.c | 34 +++++++++++++++++++++++++-
> runner/executor.h | 2 ++
> runner/resultgen.c | 61 ++++++++++++++++++++++++++++++++++------------
> 3 files changed, 81 insertions(+), 16 deletions(-)
>
> diff --git a/runner/executor.c b/runner/executor.c
> index 2abb18732..6cfe523a2 100644
> --- a/runner/executor.c
> +++ b/runner/executor.c
> @@ -576,15 +576,47 @@ bool open_output_files(int dirfd, int *fds, bool write)
> return true;
> }
>
> +/**
> + * open_output_files_rdonly:
> + * @dirfd: fd of output directory with err.txt, dmesg.txt and other files
> + * @fds: array for fd's of opened output files
> + *
> + * Tries to open output files in read-only mode and saves file descriptors
> + * in fds arrray.
%s/arrray/array
LGTM
Reviewed-by: Sebastian Brzezinka <sebastian.brzezinka@intel.com>
--
Best regards,
Sebastian
next prev parent reply other threads:[~2025-03-06 9:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 19:31 [PATCH i-g-t v5] runner: Parse results harder Kamil Konieczny
2025-03-06 7:42 ` ✓ Xe.CI.BAT: success for runner: Parse results harder (rev5) Patchwork
2025-03-06 8:01 ` ✓ i915.CI.BAT: " Patchwork
2025-03-06 9:16 ` Sebastian Brzezinka [this message]
2025-03-06 10:31 ` ✗ i915.CI.Full: failure " Patchwork
2025-03-06 10:47 ` Kamil Konieczny
2025-03-06 14:32 ` [PATCH i-g-t v5] runner: Parse results harder Krzysztof Karas
2025-03-06 15:31 ` ✗ Xe.CI.Full: failure for runner: Parse results harder (rev5) Patchwork
2025-03-06 17:27 ` Kamil Konieczny
2025-03-12 9:14 ` [PATCH i-g-t v5] runner: Parse results harder Krzysztof Karas
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=D892JDK00AAD.2NMTT2TJIHFBO@intel.com \
--to=sebastian.brzezinka@intel.com \
--cc=adrinael@adrinael.net \
--cc=ewelina.musial@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=kamil.konieczny@linux.intel.com \
--cc=krzysztof.karas@intel.com \
--cc=lucas.demarchi@intel.com \
--cc=ryszard.knop@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