Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kamil Konieczny <kamil.konieczny@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Cc: Kamil Konieczny <kamil.konieczny@linux.intel.com>,
	Ewelina Musial <ewelina.musial@intel.com>,
	Ryszard Knop <ryszard.knop@intel.com>,
	Vitaly Prosyak <vitaly.prosyak@amd.com>
Subject: [PATCH i-g-t RFC v1 0/2] runner: create results incrementally
Date: Mon, 20 Jul 2026 18:15:24 +0200	[thread overview]
Message-ID: <20260720161526.64709-1-kamil.konieczny@linux.intel.com> (raw)

Create results incementally during run, e.g. after each test end
its execution create results.json up to last one executed.

One caveat is that it will still not hold last one at which
sudden reboot happens, for example after a kernel panic.

In such cases there is still a need for calling igt_results to
collect all data.

Cc: Ewelina Musial <ewelina.musial@intel.com>
Cc: Ryszard Knop <ryszard.knop@intel.com>
Cc: Vitaly Prosyak <vitaly.prosyak@amd.com>

Kamil Konieczny (2):
  runner: Create results after each tests end
  runner: Create new option for incremental results

 runner/executor.c  | 57 ++++++++++++++++++++++++++++++++++++++++++----
 runner/resultgen.c |  6 ++++-
 runner/settings.c  |  8 +++++++
 runner/settings.h  |  1 +
 4 files changed, 67 insertions(+), 5 deletions(-)

-- 
2.54.0


             reply	other threads:[~2026-07-20 16:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-20 16:15 Kamil Konieczny [this message]
2026-07-20 16:15 ` [PATCH i-g-t v1 1/2] runner: Create results after each tests end Kamil Konieczny
2026-07-21 13:17   ` [i-g-t,v1,1/2] " Knop, Ryszard
2026-07-20 16:15 ` [PATCH i-g-t v1 2/2] runner: Create new option for incremental results Kamil Konieczny
2026-07-21 13:20   ` [i-g-t,v1,2/2] " Knop, Ryszard
2026-07-21 22:20 ` [PATCH i-g-t RFC v1 0/2] runner: create results incrementally Gustavo Sousa

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=20260720161526.64709-1-kamil.konieczny@linux.intel.com \
    --to=kamil.konieczny@linux.intel.com \
    --cc=ewelina.musial@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=ryszard.knop@intel.com \
    --cc=vitaly.prosyak@amd.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