You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In #63511, we added a clock drift check using the Date: of http://detectportal.firefox.com/success.txt as reference. However, the reply is extremely unreliable recently (?), so we can't use it to detect any drift at all.
$ date -u; curl -fs --head http://detectportal.firefox.com/success.txt | grep DateThu Nov 12 10:49:23 UTC 2020Date: Wed, 11 Nov 2020 12:48:07 GMT
$ date -u; curl -fs --head http://detectportal.firefox.com/success.txt | grep DateThu Nov 12 10:49:27 UTC 2020Date: Thu, 12 Nov 2020 00:26:09 GMT
$ date -u; curl -fs --head http://detectportal.firefox.com/success.txt | grep DateThu Nov 12 10:49:30 UTC 2020Date: Wed, 11 Nov 2020 12:48:07 GMT
$ date -u; curl -fs --head http://detectportal.firefox.com/success.txt | grep DateThu Nov 12 10:49:32 UTC 2020Date: Thu, 12 Nov 2020 00:26:09 GMT
The text was updated successfully, but these errors were encountered:
kennytm
added
T-infra
Relevant to the infrastructure team, which will review and decide on the PR/issue.
C-bug
Category: This is a bug.
labels
Nov 12, 2020
kennytm
changed the title
Choose a more reliable network clock source
Choose a more reliable network clock source for the CI
Nov 12, 2020
In #63511, we added a clock drift check using the Date: of
http://detectportal.firefox.com/success.txt
as reference. However, the reply is extremely unreliable recently (?), so we can't use it to detect any drift at all.The text was updated successfully, but these errors were encountered: