On Mon, Jan 31, 2022 at 07:00:57PM +0100, Erik Skultety wrote: > Another annoying thing in terms of test failure analysis is that TCK in its > current shape cannot save libvirt debug logs on a per-test basis and so a > massive dump is produced for the whole test run. This is very suboptimal, but > this can only be solved with libvirt admin API which can enable/modify/redirect > logs at runtime, however, the perl bindings are currently missings > -> I'm already working on adding the bindings to libvirt-perl and then we > need to teach TCK to use that feature IIUC you're suggesting that at the start of each test we re-configure the libvirtd.log to say "libvirt-this-test.log", so we can capture the logs per test ? If so, an easy way to achieve this would be to do 'truncate libvirtd.log' at the start of each test. I don't mind which way though. If we ever want ability to run tests concurrently though, we'll not be able to separate the logs at all. I guess we can worry about that another time though. 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 :|
