public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Qu Wenruo <quwenruo.btrfs@gmx.com>, Qu Wenruo <wqu@suse.com>,
	linux-btrfs@vger.kernel.org, fstests@vger.kernel.org
Subject: Re: [PATCH] fstests: report: add arch and kernel version info into testsuite attributes
Date: Mon, 19 Dec 2022 19:00:00 -0500	[thread overview]
Message-ID: <Y6D7AK6bY5PHGzds@mit.edu> (raw)
In-Reply-To: <Y6D4TT9Ids8RerEf@magnolia>

For what it's worth, here is how I add properties to the xunit file.
I do it after the fact using a tiny python script:

https://github.com/tytso/xfstests-bld/blob/master/test-appliance/files/usr/local/bin/update_properties_xunit

This way I can dump a lot of interesting information about the test
run into the XML file.  (See attached for the beginning of a
results.xml file generated by gce-xfstests.)

I also have a handy script which allows me to run separate file system
configs in separate VM's, and then combine the xunuit files together:

https://github.com/tytso/xfstests-bld/blob/master/test-appliance/files/usr/local/bin/merge_xunit
https://github.com/tytso/xfstests-bld/blob/master/test-appliance/files/usr/local/bin/combine_xunit

I'm a **big** fan of this approach, since it allows me to take about
24 hours worth of test runs, shard them across 12 different VM's, so
that it akes about 2.5 hours of wall clock time to do a full ext4 test
run.

After all, cloud VM time is cheap; software engineering time is
expensive.  :-)

					- Ted
					
<?xml version="1.0" encoding="utf-8"?>
<testsuite name="xfstests" failures="6" skipped="160" tests="1045" time="14724" hostname="xfstests-ltm-
20220825074228-aa" timestamp="2022-08-25T11:55:34">


        <properties>


                <property name="CMDLINE" value="--instance-name xfstests-ltm-20220825074228-aa --gce-zo
ne us-west1-a --gs-bucket gce-xfstests --kernel gs://gce-xfstests/kernel.deb --bucket-subdir results --
no-email -c xfs/4k -g auto --local-ssd-nvme --image-project gce-xfstests"/>
                <property name="FSTESTIMG" value="gce-xfstests/xfstests-202208242313"/>
                <property name="FSTESTPRJ" value="gce-xfstests"/>
                <property name="KERNEL" value="kernel   6.0.0-rc2-xfstests #756 SMP PREEMPT_DYNAMIC Mon
 Aug 22 22:04:33 EDT 2022 x86_64"/>
                <property name="FSTESTVER" value="blktests      4e07b0c (Fri, 15 Jul 2022 14:40:03 +090
0)"/>
                <property name="FSTESTVER" value="fio           fio-3.31 (Tue, 9 Aug 2022 14:41:25 -060
0)"/>
                <property name="FSTESTVER" value="fsverity      v1.5 (Sun, 6 Feb 2022 10:59:13 -0800)"/
>
                <property name="FSTESTVER" value="ima-evm-utils v1.3.2 (Wed, 28 Oct 2020 13:18:08 -0400
)"/>
                <property name="FSTESTVER" value="nvme-cli      v1.16 (Thu, 11 Nov 2021 13:09:06 -0800)
"/>
                <property name="FSTESTVER" value="quota         v4.05-43-gd2256ac (Fri, 17 Sep 2021 14:
04:16 +0200)"/>
                <property name="FSTESTVER" value="util-linux    v2.38.1 (Thu, 4 Aug 2022 11:06:21 +0200
)"/>
                <property name="FSTESTVER" value="xfsprogs      v5.19.0 (Fri, 12 Aug 2022 13:45:01 -050
0)"/>
                <property name="FSTESTVER" value="xfstests-bld  bb566bcf (Wed, 24 Aug 2022 23:07:24 -04
00)"/>
                <property name="FSTESTVER" value="xfstests      v2022.08.21-8-g289f50f8b (Sun, 21 Aug 2
022 15:21:34 -0400)"/>
                <property name="FSTESTVER" value="zz_build-distro       bullseye"/>
                <property name="FSTESTCFG" value="xfs/4k"/>
                <property name="FSTESTSET" value="-g auto"/>
                <property name="FSTESTEXC" value=""/>
                <property name="FSTESTOPT" value="aex"/>
                <property name="MNTOPTS" value=""/>
                <property name="CPUS" value="2"/>
                <property name="MEM" value="7680"/>
                <property name="DMI_MEM" value="7680 MB (Max capacity)"/>
                <property name="GCE ID" value="8073487017178750853"/>
                <property name="MACHINE TYPE" value="n1-standard-2"/>
                <property name="TESTRUNID" value="ltm-20220825074228-aa"/>
                <property name="TESTCFG" value="xfs/4k"/>
        </properties>


      reply	other threads:[~2022-12-20  0:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-16  7:05 [PATCH] fstests: report: add arch and kernel version info into testsuite attributes Qu Wenruo
2022-12-19 17:57 ` Darrick J. Wong
2022-12-19 22:30   ` Qu Wenruo
2022-12-19 23:48     ` Darrick J. Wong
2022-12-20  0:00       ` Theodore Ts'o [this message]

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=Y6D7AK6bY5PHGzds@mit.edu \
    --to=tytso@mit.edu \
    --cc=djwong@kernel.org \
    --cc=fstests@vger.kernel.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=quwenruo.btrfs@gmx.com \
    --cc=wqu@suse.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