Bug #11563
Git over HTTPS scenario is fragile
Start date:
2016-07-14
Due date:
% Done:
100%
Description
While Bug #10444 has successfully tackled most of the Git scenarios, the one testing Git over HTTPS has still exposed some false positives that were most probably due to the way Git handles HTTP, in particular over a bad Internet connection, or when Tor has not really bootstrapped correctly (see Bug #10238).
Subtasks
History
#1 Updated by bertagaz 2016-07-14 04:10:29
- Description updated
#2 Updated by bertagaz 2016-07-14 04:11:09
- Feature Branch set to test/10444-git-over-https-is-fragile
#3 Updated by intrigeri 2016-07-14 17:29:27
> Feature Branch set to test/10444-git-over-https-is-fragile
It would be nice if the branch name had the correct ticket number embedded, if you don’t mind renaming it.
#4 Updated by intrigeri 2016-07-21 08:53:22
- related to
Bug #10444: Git tests are fragile added
#5 Updated by anonym 2016-09-20 16:53:57
- Target version changed from Tails_2.6 to Tails_2.7
#6 Updated by bertagaz 2016-09-22 05:32:55
- Target version changed from Tails_2.7 to 284
#7 Updated by anonym 2016-11-25 10:57:01
- Target version changed from 284 to Tails 2.10
#8 Updated by intrigeri 2016-12-18 09:58:54
- Target version deleted (
Tails 2.10)
#9 Updated by intrigeri 2019-08-30 13:18:26
- Status changed from Confirmed to In Progress
Applied in changeset commit:tails|4d8b0bba02de43f25c930cb82983aba72b1a6aeb.
#10 Updated by intrigeri 2019-08-30 13:28:50
- Status changed from In Progress to Needs Validation
- Assignee changed from bertagaz to hefee
- Target version set to Tails_4.0
- Feature Branch changed from test/10444-git-over-https-is-fragile to https://salsa.debian.org/tails-team/tails/merge_requests/33
#11 Updated by Anonymous 2019-08-30 14:18:59
- Status changed from Needs Validation to Resolved
- % Done changed from 0 to 100
Applied in changeset commit:tails|a7ca22afb536e8936727d1e681baa6140cc95f37.