1:03 ` iotests: add testing shim for script-style python tests John Snow 1:03 ` block/backup: add 'always' bitmap sync policy John Snow 1:03 ` block/dirty-bitmap: add bdrv_dirty_bitmap_claim John Snow 1:03 ` hbitmap: enable merging across granularities John Snow 1:03 ` hbitmap: Fix merge when b is empty, and result is not an alias of a John Snow 1:03 ` block/backup: add 'never' policy to bitmap sync mode John Snow 1:03 ` block/backup: Add mirror sync mode 'bitmap' John Snow
1:03 ` qapi: add BitmapSyncMode enum John Snow 1:03 bitmaps: introduce 'bitmap' sync mode John Snow Thread overview: 53+ messages / expand mbox.gz Atom feed top Not even because of the test runner, but maybeĮven more so because it seems like better style to split the tests into > If this seems like a good change I will do that as a follow-up series > can be passed as a closure to the test runner. > Tests just need to be refactored to have a single point of entry so it > copy-paste in the future will get us the right paradigm. I should convert the others to opt-in to the new format so that > iotests.script_main() explicitly does clear up my confusion. > Oh, it doesn’t work (well, not automagically). > Googlefu are that bad), but it works and looks good, so have a > I don’t quite get how script_main() works (yes, both my Pythonfu and my
> 1 file changed, 26 insertions(+), 14 deletions(-) > default variables we can simply create an instance of the runner with > was no reason to create a class in an inner scope just to achieve > Two cleanup notes: debug was not actually used as a global, and there > Refactor the launcher shim into new and old style shims so that they > launcher, we don't turn on the debugger logging for these scripts > Because the new-style python tests don't use the iotests.main() test Subject: Re: iotests: add testing shim for script-style python testsĭate: Thu, 20:55:59 +0200 To: John Snow Kevin Wolf, Fam Zheng Wen Congyang , Re: iotests: add testing shim for script-style python tests - Max Reitz All of help / color / mirror / Atom feed From: Max Reitz
0 kommentar(er)
