I guess this also is the reason why unity8.shell.tests.test_lock_screen.TestLockscreen.test_passphrase_screen_wrong_password hangs?
If one runs phablet-test-run -n unity8, it seems to hang eternally at a password screen, and also that ^ test individually does not complete even with a failure (unlike test_can_unlock_passphrase_screen which properly fails). That makes testing unity8 hard since the tests need to be executed one at a time which is slow compared to whole suite run.
I guess this also is the reason why unity8. shell.tests. test_lock_ screen. TestLockscreen. test_passphrase _screen_ wrong_password hangs?
If one runs phablet-test-run -n unity8, it seems to hang eternally at a password screen, and also that ^ test individually does not complete even with a failure (unlike test_can_ unlock_ passphrase_ screen which properly fails). That makes testing unity8 hard since the tests need to be executed one at a time which is slow compared to whole suite run.