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

Edge Chromium has incompatible browser & driver versions on Azure #17403

Closed
Hexcles opened this issue Jun 19, 2019 · 5 comments
Closed

Edge Chromium has incompatible browser & driver versions on Azure #17403

Hexcles opened this issue Jun 19, 2019 · 5 comments
Assignees

Comments

@Hexcles
Copy link
Member

Hexcles commented Jun 19, 2019

Currently, Edge Chromium isn't running any tests on Azure because:

SessionNotCreatedException: session not created (500): session not created: Microsoft Edge version must be 75

For reference, we use the latest dev channel of Edge Chromium on Azure:

Supposedly the problem is in install_webdriver:

url = "https://az813057.vo.msecnd.net/webdriver/msedgedriver_%s/msedgedriver.exe" % platform

I'm not sure which EdgeDriver version this URL points to, but apparently the URL doesn't contain version/channel information so it's guaranteed that this won't always work.

For now, I'll be passing --disable-build-check to EdgeDriver (similar to #16448), assuming that the underlying version check is the same as ChromeDriver.

@Hexcles
Copy link
Member Author

Hexcles commented Jun 19, 2019

cc @mustjab

@foolip
Copy link
Member

foolip commented Jun 20, 2019

@Hexcles I've merged your quickfix, and will rename the bad runs we got on wpt.fyi so far. Before this is closed, can you check if any more trickled in?

@mustjab I'll go ahead and assign this to you, is that OK?

@foolip
Copy link
Member

foolip commented Jun 20, 2019

https://wpt.fyi/results/?run_id=242900005 was good again, so there aren't any more runs to rename. (I renamed them to brokenedge.)

@stephenmcgruer
Copy link
Contributor

@mustjab was this fixed by #17540 ?

@mustjab
Copy link
Contributor

mustjab commented Dec 3, 2019

@stephenmcgruer Yes, should be fixed now with that change and #20023 , let me know if you still see this fail.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants