Test suite: the remote shell sometimes gets stuck leading to RemoteShell::Timeout
Relevant excerpt from the debug.log:
And I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled (failed) # features/step_definitions/common_steps.rb:280
execution expired (RemoteShell::Timeout)
./features/support/helpers/remote_shell.rb:56:in `read'
./features/support/helpers/remote_shell.rb:56:in `block (3 levels) in communicate'
./features/support/helpers/remote_shell.rb:55:in `block (2 levels) in communicate'
./features/support/helpers/remote_shell.rb:42:in `loop'
./features/support/helpers/remote_shell.rb:42:in `block in communicate'
./features/support/helpers/remote_shell.rb:37:in `communicate'
./features/support/helpers/remote_shell.rb:174:in `execute'
./features/support/helpers/remote_shell.rb:185:in `initialize'
./features/support/helpers/dogtail.rb:80:in `new'
./features/support/helpers/dogtail.rb:80:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/common_steps.rb:714:in `new'
./features/step_definitions/common_steps.rb:714:in `/^all notifications have disappeared$/'
./features/step_definitions/common_steps.rb:297:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/additional_software_packages.feature:35:in `And I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled'
What happened is that the gnome_shell = Dogtail::Application.new('gnome-shell')
command in step all notifications have disappeared
in common_steps.rb
(used to be on line 714 in the commit the above failure happened on, on current stable its on line 713) failed with RemoteShell::Timeout
.
During the subsequent test cleanup, the remote shell is also unresponsive, so we get no journal. The remote shell and Dogtail were responsive before in the same scenario though (e.g. in the Welcome Screen).
Failing test runs:
- https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4703/cucumber-html-reports/report-feature_6_4113196806.html
-
https://jenkins.tails.boum.org/job/test_Tails_ISO_20219-pipewire/14//cucumber-html-reports/overview-failures.html(cleaned up by Jenkins, not sure if it was the exact same error) - https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4727/cucumber-html-reports/report-feature_7_295607190.html
- https://jenkins.tails.boum.org/job/test_Tails_ISO_20280-fix-second-unlock-dialog/1//cucumber-html-reports/overview-failures.html
- https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4805/cucumber-html-reports/report-feature_7_295607190.html
Edited by segfault