New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Restore install-chromium.sh
version checking once https://omahaproxy.appspot.com/all
is back
#22231
Labels
Milestone
Comments
matsko
added a commit
to matsko/angular
that referenced
this issue
Feb 14, 2018
matsko
added a commit
to matsko/angular
that referenced
this issue
Feb 14, 2018
can you capture why it's failing now? the next caretaker will not know when it's safe to restore. |
matsko
added a commit
that referenced
this issue
Feb 14, 2018
matsko
added a commit
that referenced
this issue
Feb 14, 2018
vicb
added
area: build & ci
Related the build and CI infrastructure of the project
type: bug/fix
freq1: low
severity3: broken
labels
Feb 15, 2018
jbogarthyde
pushed a commit
to jbogarthyde/angular
that referenced
this issue
Feb 23, 2018
smdunn
pushed a commit
to smdunn/angular
that referenced
this issue
Feb 28, 2018
leo6104
pushed a commit
to leo6104/angular
that referenced
this issue
Mar 25, 2018
gkalpak
added a commit
to gkalpak/angular
that referenced
this issue
Aug 21, 2018
Now that https://omahaproxy.appspot.com/all is back up, we can restore the check for newer available version of Chromium. Fixes angular#22231
gkalpak
added a commit
to gkalpak/angular
that referenced
this issue
Aug 22, 2018
Now that https://omahaproxy.appspot.com/all is back up, we can restore the check for newer available version of Chromium. Fixes angular#22231
gkalpak
added a commit
to gkalpak/angular
that referenced
this issue
Aug 23, 2018
Now that https://omahaproxy.appspot.com/all is back up, we can restore the check for newer available version of Chromium. Fixes angular#22231
gkalpak
added a commit
to gkalpak/angular
that referenced
this issue
Aug 25, 2018
Now that https://omahaproxy.appspot.com/all is back up, we can restore the check for newer available version of Chromium. Fixes angular#22231 PR Close angular#25602
mhevery
pushed a commit
that referenced
this issue
Sep 5, 2018
Now that https://omahaproxy.appspot.com/all is back up, we can restore the check for newer available version of Chromium. Fixes #22231 PR Close #25602 PR Close #25669
FrederikSchlemmer
pushed a commit
to FrederikSchlemmer/angular
that referenced
this issue
Jan 3, 2019
Now that https://omahaproxy.appspot.com/all is back up, we can restore the check for newer available version of Chromium. Fixes angular#22231 PR Close angular#25602
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
When travis runs this error pops up:
And it's due to https://omahaproxy.appspot.com/all being unresponsive.
Once that page is working again. We can uncomment and close this issue.
The text was updated successfully, but these errors were encountered: