On Tue, Jan 14, 2020 at 09:33:45PM +0200, Maxim Levitsky wrote: > This allows more tests to be able to have same output on both qcow2 luks > encrypted images > and raw luks images > > Signed-off-by: Maxim Levitsky <mlevi...@redhat.com> > --- > tests/qemu-iotests/087.out | 6 +++--- > tests/qemu-iotests/134.out | 2 +- > tests/qemu-iotests/158.out | 4 ++-- > tests/qemu-iotests/188.out | 2 +- > tests/qemu-iotests/189.out | 4 ++-- > tests/qemu-iotests/198.out | 4 ++-- > tests/qemu-iotests/common.filter | 6 ++++-- > 7 files changed, 15 insertions(+), 13 deletions(-) > > diff --git a/tests/qemu-iotests/087.out b/tests/qemu-iotests/087.out > index 2d92ea847b..b61ba638af 100644 > --- a/tests/qemu-iotests/087.out > +++ b/tests/qemu-iotests/087.out > @@ -34,7 +34,7 @@ QMP_VERSION 1> > === Encrypted image QCow === > > -Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=134217728 encryption=on > encrypt.key-secret=sec0 > +Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=134217728 encryption=on
I'm not convinced about this - it feels like this is throwing away relevant info to be validated about the test scenario Can you give more info about the scenario this benefits us in ? Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
