Tor still sometimes fails to bootstrap in the test suite

It’s been noticed while reviewing Jenkins test suite runs failure in June (#12289 (closed)) that the TorBootstrapFailure exception still happens sometimes.

There are 3 possible reasons to it, I think: a) chutney/tor sometimes feels stupid; or b) our test suite sometimes fails to manage chutney properly; or c) some unrelated event on the system prevents them from doing their job.

Next steps to investigate this would be to:

1. look at the test suite debug log and
* double-check there’s no explanation for the tor bootstrap failure (that’s about (a) and (b))
* record the exact times when things went wrong
2. ensure we save the tor log from the Tails system when this happens, so we can see if that tor is stupid (a)
3. make the Journal persistent on isotesters so we can try to correlate such failures with system events ©.

Attachments

• 01_50_31_The_tor_process_should_be_confined_with_Seccomp.journal
• 02_18_48_Getting_a_DHCP_lease_with_a_manually_configured_NetworkManager_connection.journal
• 02_56_27_The_system_DNS_is_always_set_up_to_use_Tor_s_DNSPort.journal

Parent Task: #10288

Related issues

• Related to #10238 (closed)
• Related to #12411 (closed)
• Related to #12289 (closed)
• Related to #15799 (closed)
• Blocks #16209

Original created by @bertagaz on 13541 (Redmine)