[wasm] Fix chrome update script to use 'chromium dash', instead of 'omahaproxy' #92436
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
.. omahaproxy. The older way to get versions hasn't been removed yet, to wait to see how stable this method is.
ghost
assigned 
|
Tagging subscribers to 'arch-wasm': @lewing Issue Details
|
radical
changed the title
|
/azp run runtime-wasm |
|
Azure Pipelines successfully started running 1 pipeline(s). |
radical
force-pushed
the
chrome-update-script
branch
from
1cccf32
to
bfc38ac
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
https://chromiumdash.appspot.comis the recommended way to get the chrome release versions now, instead ofhttp://omahaproxy.appspot.com. This PR updates the task to do that.