Skip to content
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

Closed
matsko opened this issue Feb 14, 2018 · 2 comments
Labels
area: build & ci Related the build and CI infrastructure of the project freq1: low type: bug/fix
Milestone

Comments

@matsko
Copy link
Contributor

matsko commented Feb 14, 2018

When travis runs this error pops up:

   creating: /home/travis/.chrome/chromium/chrome-linux/resources/inspector/security_test_runner/
  inflating: /home/travis/.chrome/chromium/chrome-linux/resources/inspector/security_test_runner/security_test_runner_module.js  
/home/travis/build/angular/angular/scripts/ci/install-chromium.sh: line 82: LATEST_CHROMIUM_VERSION: unbound variable

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.

@IgorMinar
Copy link
Contributor

can you capture why it's failing now? the next caretaker will not know when it's safe to restore.

@vicb 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
@ngbot ngbot bot modified the milestones: needsTriage, Backlog Feb 26, 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
@matsko matsko closed this as completed in efb453c Aug 24, 2018
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
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 13, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area: build & ci Related the build and CI infrastructure of the project freq1: low type: bug/fix
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants