intrigeri (2020-07-31):
> I've looked at the logs you've sent me and unfortunately, this did not
> help me understand what's happening.
>
> Sharing the *.journal and Tor log artifacts could give us more clues,
> perhaps.
Full directory for that run shared in the tarball available at:
Hi,
Cyril Brulebois (2020-07-28):
>> | [2020-05-05 23:29:07] kibi: not an issue when running the VM separately
>> (on the same machine), not an issue when running the test suite on stretch
>> (different machine), not an issue on baremetal.
>> | [2020-05-05 23:29:22] kibi: I think a bug or
Cyril Brulebois (2020-07-28):
> This is hindering:
> - my general ability to test Tails;
> - my specific ability to check locally what failed in Jenkins, namely
>all of features/additional_software_packages.feature
>
> Looking at XMPP logs (I didn't check what's happening now) from May,
intrigeri (2020-07-28):
> That sounds annoying indeed! I'm happy to try to help. To do so, I'll
> need the debug log (saved as debug.log by the test suite).
Great, thanks.
In the meanwhile, I had cleaned up all temporary directories, rebooted
the machine, etc. to be extra sure. I've just
Hi,
Cyril Brulebois (2020-07-28):
> I had noticed this during earlier release preps, but didn't get to the
> bottom of it: with a buster system used exclusively for Tails purposes
> (so no fancy extra packages installed), I cannot get the test suite to
> get Tor bootstrapped:
That sounds
Hi,
I had noticed this during earlier release preps, but didn't get to the
bottom of it: with a buster system used exclusively for Tails purposes
(so no fancy extra packages installed), I cannot get the test suite to
get Tor bootstrapped:
| Step failed while creating checkpoint: Tor is ready
