Nicholas Piggin <[email protected]> writes: > These seem to be quite solid, including on several gitlab CI runs. > Enabling them should help catch breakage in future. > > And update the powernv comment -- gitlab isn't the problem, there are > known gaps in implementation. > > Signed-off-by: Nicholas Piggin <[email protected]>
Tested-by: Alex Bennée <[email protected]> Reviewed-by: Alex Bennée <[email protected]> > --- > tests/avocado/reverse_debugging.py | 9 +-------- > 1 file changed, 1 insertion(+), 8 deletions(-) > > diff --git a/tests/avocado/reverse_debugging.py > b/tests/avocado/reverse_debugging.py > index 92855a02a5..8fe76ff921 100644 > --- a/tests/avocado/reverse_debugging.py > +++ b/tests/avocado/reverse_debugging.py > @@ -223,9 +223,6 @@ class ReverseDebugging_AArch64(ReverseDebugging): > > REG_PC = 32 > > - # unidentified gitlab timeout problem > - @skipUnless(os.getenv('QEMU_TEST_FLAKY_TESTS'), 'Test is unstable on > GitLab') > - > def test_aarch64_virt(self): > """ > :avocado: tags=arch:aarch64 > @@ -248,14 +245,10 @@ class ReverseDebugging_ppc64(ReverseDebugging): > > REG_PC = 0x40 > > - # unidentified gitlab timeout problem > - @skipUnless(os.getenv('QEMU_TEST_FLAKY_TESTS'), 'Test is unstable on > GitLab') > - > def test_ppc64_pseries(self): > """ > :avocado: tags=arch:ppc64 > :avocado: tags=machine:pseries > - :avocado: tags=flaky > """ > # SLOF branches back to its entry point, which causes this test > # to take the 'hit a breakpoint again' path. That's not a problem, > @@ -264,7 +257,7 @@ def test_ppc64_pseries(self): > self.reverse_debugging() > > # See https://gitlab.com/qemu-project/qemu/-/issues/1992 > - @skipUnless(os.getenv('QEMU_TEST_FLAKY_TESTS'), 'Test is unstable on > GitLab') > + @skipUnless(os.getenv('QEMU_TEST_FLAKY_TESTS'), 'powernv migration > support is incomplete so rr debugging is flaky') > > def test_ppc64_powernv(self): > """ -- Alex Bennée Virtualisation Tech Lead @ Linaro
