qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Peter Xu <peterx@redhat.com>
Cc: qemu-devel@nongnu.org, Fabiano Rosas <farosas@suse.de>
Subject: Re: [PATCH v2 3/4] tests/functional: Test with scripts/vmstate-static-checker.py
Date: Thu, 22 May 2025 20:08:44 +0200	[thread overview]
Message-ID: <2f83dee7-6bfc-435e-8392-2236b98cbcfe@redhat.com> (raw)
In-Reply-To: <aC820hzwtrFBV9oq@x1.local>

On 22/05/2025 16.38, Peter Xu wrote:
> On Thu, May 22, 2025 at 03:37:55PM +0200, Thomas Huth wrote:
> 
> [...]
> 
>> +    def test_vmstate(self):
>> +        target_machine = {
>> +            'aarch64': 'virt-7.2',
>> +            'm68k': 'virt-7.2',
>> +            'ppc64': 'pseries-7.2',
>> +            's390x': 's390-ccw-virtio-7.2',
>> +            'x86_64': 'pc-q35-7.2',
>> +        }
>> +        self.set_machine(target_machine[self.arch])
>> +
>> +        # Run QEMU to get the current vmstate json file:
>> +        dst_json = self.scratch_file('dest.json')
>> +        self.log.info('Dumping vmstate from ' + self.qemu_bin)
>> +        cp = subprocess.run([self.qemu_bin, '-nodefaults',
>> +                             '-M', target_machine[self.arch],
>> +                             '-dump-vmstate', dst_json],
>> +                            stdout=subprocess.PIPE,
>> +                            stderr=subprocess.STDOUT,
>> +                            text=True)
>> +        if cp.returncode != 0:
>> +            self.fail('Running QEMU failed:\n' + cp.stdout)
>> +        if cp.stdout:
>> +            self.log.info('QEMU output: ' + cp.stdout)
>> +
>> +        # Check whether the old vmstate json file is still compatible:
>> +        src_json = self.data_file('..', 'data', 'vmstate-static-checker',
>> +                                  self.arch,
>> +                                  target_machine[self.arch] + '.json')
>> +        self.log.info('Comparing vmstate with ' + src_json)
>> +        cp = self.run_vmstate_checker(src_json, dst_json)
>> +        if cp.returncode != 0:
>> +            self.fail('Running vmstate-static-checker failed:\n' + cp.stdout)
> 
> Would false positives happen here?  Would it fail "make check" and CI, even
> if the change was intended?

Yes. In that case, the quick fix is to remove the problematic piece from the 
7.2 json files. Or we could try to improve the vmstate-static-checker 
script. At least we now notice it immediately, not only after a long delay 
until someone runs the script manually again.

But yes, this can be confusing for the who runs into this problem for the 
first time. I guess I should at least add some friendly words here with 
instructions what has to be done?

  Thomas


>> +        if cp.stdout:
>> +            self.log.warning('vmstate-static-checker output: ' + cp.stdout)
>> +
>> +
>> +if __name__ == '__main__':
>> +    QemuSystemTest.main()
>> -- 
>> 2.49.0
>>
> 



  reply	other threads:[~2025-05-22 18:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-22 13:37 [PATCH v2 0/4] tests/functional: Test with scripts/vmstate-static-checker.py Thomas Huth
2025-05-22 13:37 ` [PATCH v2 1/4] tests: Move the old vmstate-static-checker files to tests/data/ Thomas Huth
2025-05-22 14:35   ` Peter Xu
2025-05-22 13:37 ` [PATCH v2 2/4] tests/data/vmstate-static-checker: Add dump files from QEMU 7.2.17 Thomas Huth
2025-05-22 14:35   ` Peter Xu
2025-05-22 13:37 ` [PATCH v2 3/4] tests/functional: Test with scripts/vmstate-static-checker.py Thomas Huth
2025-05-22 14:38   ` Peter Xu
2025-05-22 18:08     ` Thomas Huth [this message]
2025-05-26 13:52       ` Peter Xu
2025-05-22 13:37 ` [PATCH v2 4/4] tests/functional/test_vmstate: Test whether the checker script works as expected Thomas Huth
2025-05-22 14:40   ` Peter Xu
2025-05-22 18:12     ` Thomas Huth
2025-05-26 13:47       ` Peter Xu

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=2f83dee7-6bfc-435e-8392-2236b98cbcfe@redhat.com \
    --to=thuth@redhat.com \
    --cc=farosas@suse.de \
    --cc=peterx@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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;
as well as URLs for NNTP newsgroup(s).