Feature #8477
config/chroot_local-hooks/10-tbb: please retry a failed download
0%
Description
When building Tails, config/chroot_local-hooks/10-tbb fetches all current TBB binaries. If any of these download fails, the build hangs. It should retry the failed download at least one instead
Subtasks
Related issues
| Related to Tails - Feature #15864: Make onboarding of new developers easier | In Progress | 2018-08-30 | |
| Blocks Tails - Feature #16209: Core work: Foundations Team | Confirmed |
History
#1 Updated by BitingBird 2014-12-24 02:00:37
- Status changed from New to Confirmed
#2 Updated by intrigeri 2014-12-24 11:53:39
> When building Tails, config/chroot_local-hooks/10-tbb fetches all current TBB
> binaries. If any of these download fails, the build hangs. It should retry the failed
> download at least one instead
If that can be solved by adding --retry <num> to the curl command-line, fine with me.
Otherwise, I’m not convinced it is worth making the code more complex, given this would be inconsistent with all the other pieces of our build system code, that don’t retry upon failure. I kind of see why this one is a bit different (one has less chances to have it cached already than e.g. the Debian packages), but still: the time saved by retrying vs. restarting a build from scratch is about 3-10 minutes, so well…
#3 Updated by intrigeri 2014-12-24 12:03:08
- Priority changed from Normal to Low
#4 Updated by intrigeri 2019-04-08 13:38:58
- related to Feature #15864: Make onboarding of new developers easier added
#5 Updated by intrigeri 2019-12-15 08:35:59
- blocks Feature #16209: Core work: Foundations Team added
#6 Updated by intrigeri 2019-12-15 08:38:34
- Priority changed from Low to Normal
We’ve seen weird download failures when building Tails for the first time with a brand new Tor Browser version. This has wasted release manager’s time a few times already. I’m bumping priority of this ticket and I’ve put it on the FT’s plate, because we need to make the release process more robust and less stressful.