-
Notifications
You must be signed in to change notification settings - Fork 32
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
[INFRA] Some e2e tests fail on Chrome and Edge browsers when run with GitHub Actions #1933
Comments
ℹ️ I have just reproduced the issue locally with Chrome 101.0.4951.41 (Official build) 64 bits on Ubuntu 20.04.4 LTS by running a test with the local error:
GitHub Actions error (according to the image release notes, with Chrome 100):
|
Thanks to process-analytics/github-actions-playground#78, I have been able to get the actual versions of chrome and edge macOS: not implemented for now Here are information on
|
ℹ️ New environment detected today
google-chrome-stable Version: 101.0.4951.54-1
Google Chrome 101.0.4951.54 Google LLC 20220504 |
At that time, we weren't using the browsers installed in the GitHub runners. Chrome and Edge was installed prior running tests. This should change with #2355 |
Starting from 2022-04-27T14:54:28Z (detected in #1929), some visual tests on Chrome involving labels are not passing anymore. All OS are affected.
Starting from 2022-04-29T13:21:03Z (detected in #1934), the same occurs with the Edge browser!
The failure may be related to a GitHub Actions environment change.
Environment information for the Chrome issue
Information taken from #1929 runs.
macos-11 OK - run logs
On
2022-04-26T16:51:57Z
Browsers listed in the image Readme
macos-11 KO - run logs
On
2022-04-27T14:54:28Z
Browsers listed in the image Readme
The virtual environment image changed from 20220419.3 to 20220424.1.
The provisioner changed, from 1.0.0.0-main-20220406-1 to 1.0.0.0-main-20220421-1
ubuntu-20.04 OK - run logs
On
2022-04-26T16:51:57
Browsers listed in the image Readme
ubuntu-20.04 KO - run logs
On
2022-04-27T14:54:56Z
This is the exact same virtual environment image. Only the provisioner changed, from 1.0.0.0-main-20220406-1 to 1.0.0.0-main-20220421-1
windows-2019 OK - run logs
On
2022-04-26T16:52Z
Browsers listed in the image Readme
windows-2019 KO - run logs
On `2022-04-27T15:03:57Z
This is the exact same virtual environment image. Only the provisioner changed, from 1.0.0.0-main-20220406-1 to 1.0.0.0-main-20220421-1
Environment information for the Edge issue
Working, in #1929, on
2022-04-27T14:55:21Z
Browsers listed in the image Readme
not working, in #1934, on
2022-04-29T13:34:54Z
This is the exact same virtual environment image and the exact same environment provisioner.
The text was updated successfully, but these errors were encountered: