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

⬆ Upgrade Chromium 78 to 87 #151

Merged
merged 7 commits into from
Feb 1, 2021
Merged

⬆ Upgrade Chromium 78 to 87 #151

merged 7 commits into from
Feb 1, 2021

Conversation

wwilsman
Copy link
Contributor

@wwilsman wwilsman commented Jan 29, 2021

What is this?

This updates the version of Chromium downloaded and used by asset discovery to Chrome 87.0.4280, which matches the next version that will be used in Percy's own rendering environment.

With this specific version of Chromium, the revisions are varied across all platforms. To make finding these revisions easier than the manual process, I automated it with a script. I also removed the old release-notes script since this repo uses a release-drafting action.

If authenticated with GitHub, the script could be modified to search a range of several versions to find a close match that has only one revision across all platforms. It could also be improved with GitHub's GraphQL API to search for the tag in a single query rather than paginating all tags for the Chromium repo. But that can be a future improvement for the next update.

Two tests needed to be updated:

  1. A test in which the error message thrown by Chromium's Dev Tools Protocol has changed.
  2. A test which triggers a page crash by navigating to chrome://crash. Scripts are no longer allowed to navigate to URLs which crash the page, so a few private properties were un-privated in order to trigger a page crash by issuing a Page.crash command over CDP.

While fixing test 2, I updated some discovery logs as well

@wwilsman wwilsman added the ✨ enhancement New feature or request label Jan 29, 2021
@wwilsman wwilsman requested a review from Robdel12 January 29, 2021 17:00
Scripts can no longer navigate to the chrome crash screen to trigger a crash. Instead, private
properties were un-privated so the test can reach in to trigger a crash.
@wwilsman wwilsman force-pushed the ww/upgrade-chromium branch from 5894344 to 06a1a13 Compare February 1, 2021 17:26
Copy link
Contributor

@Robdel12 Robdel12 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🏁

"clean": "rm -rf packages/**/{dist,.nyc_output,coverage,oclif.manifest.json}",
"release-notes": "./scripts/release-notes",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

noice

@@ -8,6 +9,8 @@ export default class Network {
#intercepts = new Map();
#authentications = new Set();

log = logger('core:network');
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fuuuuuuuttttttttttuuureeeeeeeeeeeee

@Robdel12
Copy link
Contributor

Robdel12 commented Feb 1, 2021

  • Oh, what's this mean for the support tool's version of Chrome? Starts using 87? (discussed in slack)

@Robdel12
Copy link
Contributor

Robdel12 commented Feb 1, 2021

Fix your bootleg ⬆️ emoji? 😂

@wwilsman
Copy link
Contributor Author

wwilsman commented Feb 1, 2021

Fix your bootleg ⬆️ emoji? 😂

No, it just gets corrected in some places automatically 😆

@wwilsman wwilsman merged commit 19f0d05 into master Feb 1, 2021
@wwilsman wwilsman deleted the ww/upgrade-chromium branch February 1, 2021 19:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
✨ enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants