public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Leah Rumancik <leah.rumancik@gmail.com>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH] check: use /var/tmp instead of /tmp
Date: Mon, 12 Dec 2022 18:53:27 -0800	[thread overview]
Message-ID: <Y5fpJ168rNwwrfhI@magnolia> (raw)
In-Reply-To: <Y5fb5viJh8Q7bVH0@google.com>

On Mon, Dec 12, 2022 at 05:56:54PM -0800, Leah Rumancik wrote:
> On Mon, Dec 12, 2022 at 03:18:49PM -0800, Darrick J. Wong wrote:
> > On Mon, Dec 12, 2022 at 03:06:46PM -0800, Leah Rumancik wrote:
> > > With the results recorded in /tmp, a crashing test results in a loss
> > > of all prior test runs. Instead, record results in /var/tmp so that
> > > it is possible to recover results from completed tests.
> > 
> > RESULT_BASE=/some/stable/storage ./check <args> ?
> 
> So I am interested in the passing test results in addition to the
> failed/skipped tests. I thought just the non-passing tests stored
> artifacts here, is there some way to also tell which tests passed for
> tests that don't write to .full? I was hoping to just grab the xml
> file that is being generated by _make_testcase_report as it also
> has the test runtimes which would be nice to have.

Oh, right, I forgot that the reporting only runs at the end of the
section, which means that (short of invading the fstests internal state)
there's no means to figure out where fstests was when it died, even if
you pointed RESULT_BASE at some nfs mount or something.

Does this help?

--D

From: Darrick J. Wong <djwong@kernel.org>
Subject: [PATCH] check: generate section reports between tests

Generate the section report between tests so that the summary report
always reflects the outcome of the most recent test.  This is useful for
fstests status reporting, for people who anxiously await results.

Signed-off-by: Darrick J. Wong <djwong@kernel.org>
---
 check |   10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/check b/check
index d2e5129620..997547247f 100755
--- a/check
+++ b/check
@@ -841,6 +841,16 @@ function run_section()
 		fi
 		seqres="$REPORT_DIR/$seqnum"
 
+		# Generate the entire section report with whatever test results
+		# we have so far.  Leave the $sect_time parameter empty so that
+		# it's a little more obvious that this test run is incomplete.
+		if $do_report; then
+			local sect_now=`_wallclock`
+			_make_section_report "$section" "${#try[*]}" \
+					     "${#bad[*]}" "${#notrun[*]}" \
+					     "" &> /dev/null
+		fi
+
 		mkdir -p $RESULT_DIR
 		rm -f ${RESULT_DIR}/require_scratch*
 		rm -f ${RESULT_DIR}/require_test*

  reply	other threads:[~2022-12-13  2:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-12 23:06 [PATCH] check: use /var/tmp instead of /tmp Leah Rumancik
2022-12-12 23:18 ` Darrick J. Wong
2022-12-13  1:56   ` Leah Rumancik
2022-12-13  2:53     ` Darrick J. Wong [this message]
2022-12-14 19:56       ` Leah Rumancik

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=Y5fpJ168rNwwrfhI@magnolia \
    --to=djwong@kernel.org \
    --cc=fstests@vger.kernel.org \
    --cc=leah.rumancik@gmail.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