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 started
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 annoying
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
|
Hi,
Having being responsible for a number of releases lately, I've been
automatically “subscribed” to any tickets I ever touched, even if only
to push back the target version (Redmine) / milestone (GitLab) to the
next release.
A bunch of such tickets were closed already, and aren't moving anymore
Hi,
Instead of building all IUKs serially on a single Jenkins worker, I've
developed a proof of concept to trigger them all in parallel, across all
workers. The downside is that it didn't seem obvious how to gather all
results, so I went for a downstream job; for 4.9, jobs are:
https://jenkins.t
