Bug #10288: Fix newly identified issues to make our test suite more robust and faster
"Tor Launcher uses all expected TBB shared libraries" is fragile
And the Tor Launcher uses all expected TBB shared libraries Command failed: find /usr/lib /lib -name "libnssutil3.so" error code: 1 stderr: find: `/lib/live/mount/overlay/var/tmp/systemd-private-9a29e2ac5e134767bdb750c1f0108468-systemd-hostnamed.service-23b1BY/tmp': No such file or directory . is not true. (ExecutionFailedInVM) ./features/support/helpers/vm_helper.rb:442:in `rescue in execute_successfully' ./features/support/helpers/vm_helper.rb:439:in `execute_successfully' ./features/step_definitions/browser.rb:145:in `block in xul_app_shared_lib_check' ./features/step_definitions/browser.rb:140:in `each' ./features/step_definitions/browser.rb:140:in `xul_app_shared_lib_check' ./features/step_definitions/browser.rb:166:in `/^the (.*) uses all expected TBB shared libraries$/' features/tor_bridges.feature:12:in `And the Tor Launcher uses all expected TBB shared libraries'
Revert "Test suite: mark tests that use Tor Launcher as fragile (refs: #11606)."
This reverts commit da26fc1d9399c8ae909f1b78a25fbbaa4fd35ca0.
Test suite: update reason why these tests are fragile (refs: #11606)
The step "the Tor Launcher uses all expected TBB shared libraries" step has
never failed on Jenkins in the last 2 months. But these scenarios
have failed a number of time due to "Tor is ready" failing, which I assume
is because of time sync' problems.