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

Devicelab tests fail due to running on arm64 bots #101861

Closed
keyonghan opened this issue Apr 13, 2022 · 4 comments
Closed

Devicelab tests fail due to running on arm64 bots #101861

keyonghan opened this issue Apr 13, 2022 · 4 comments
Assignees
Labels
team-infra Owned by Infrastructure team

Comments

@keyonghan
Copy link
Contributor

https://chrome-internal-review.googlesource.com/c/infradata/config/+/4673717 enabled several arm64 bots in prod, and devicelab tests are scheduled to run on these bots, causing infra failures.

These bots are expected to run only arm64 tests validated in staging.

We need to enforce mac model for existing builders.

@keyonghan keyonghan added this to New in Infra Ticket Queue via automation Apr 13, 2022
@keyonghan keyonghan added the team-infra Owned by Infrastructure team label Apr 13, 2022
@keyonghan
Copy link
Contributor Author

I tried ssh to these bots to quarantine, but somehow hit:

ssh flutter@flutter-devicelab-mac-42.mtv.corp.google.com
F0413 12:50:19.015105   66936 helper.go:392] Failed to initialize session: upgrading to websocket: bad status
kex_exchange_identification: Connection closed by remote host

@keyonghan
Copy link
Contributor Author

@keyonghan
Copy link
Contributor Author

DeviceLab tests have been switched to use os+cpu, instead of mac_model, and all tests have explicitly specified the correct dimensions. Closing.

Infra Ticket Queue automation moved this from In progress to Done Apr 18, 2022
@github-actions
Copy link

github-actions bot commented May 2, 2022

This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 2, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
team-infra Owned by Infrastructure team
Projects
No open projects
Development

No branches or pull requests

1 participant