chore: introduce chromium-tip-of-tree-headless-shell#33964
chore: introduce chromium-tip-of-tree-headless-shell#33964mxschmitt merged 2 commits intomicrosoft:mainfrom
Conversation
4ff4cdd to
6ceac06
Compare
This comment has been minimized.
This comment has been minimized.
| headlessShellBrowser.revision = revision; | ||
| headlessShellBrowser.browserVersion = browserVersion; | ||
| } else if (browserName === 'chromium-tip-of-tree') { | ||
| const tipOfTreeBrowser = await browsersJSON.browsers.find(b => b.name === 'chromium-tip-of-tree-headless-shell'); |
There was a problem hiding this comment.
Why can't we just use version of chromium-tip-of-tree, we don't expect these two to ever diverge, do we?
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Test results for "tests 1"10 failed 7 flaky37129 passed, 646 skipped Merge workflow run. |
Test results for "tests others"1 flaky21293 passed, 509 skipped Merge workflow run. |
Test results for "tests 2"1 fatal errors, not part of any test 93 flaky262979 passed, 10099 skipped Merge workflow run. |
Motivation: This helps us to find out about upstream headless_shell regressions before they appear in the Beta channel.
I was considering doing the same pattern like we do for chromium (auto use headless-shell) but this doesn't work here since
chromium-tip-of-treeis already a channel. Lets keep it how it is and do the manual opt-in.