On Tue, Jan 09, 2024 at 10:00:17AM -0300, Fabiano Rosas wrote: > > Can we opt-out those broken tests using either your "since:" thing or > > anything similar? > > If it's something migration related, then yes. But there might be other > types of breakages that have nothing to do with migration. Our tests are > not resilent enough (nor they should) to detect when QEMU aborted for > other reasons. Think about the -audio issue: the old QEMU would just say > "there's no -audio option, abort" and that's a test failure of course.
I'm wondering whether we can more or less remedy that by running migration-test under the build-previous directory for cross-binary tests. We don't necessarily need to cross-test anything new happening anyway. IOW, we use both old QEMU / migration-test for "n-1", and we only use "n" for the new QEMU binary? -- Peter Xu
