-
Notifications
You must be signed in to change notification settings - Fork 767
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
Missing buildjet Emulator network #7210
Conversation
ac8ce1c
to
7952439
Compare
955ac8d
to
ad8786d
Compare
7952439
to
35b1ba3
Compare
ad8786d
to
1db0ef4
Compare
b03d43a
to
aee2c71
Compare
1db0ef4
to
3f83afb
Compare
aee2c71
to
21ba60e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for looking into this!
21ba60e
to
2f9c5f5
Compare
2f9c5f5
to
34b3c6c
Compare
…n the buildjet runner - updates max workers to match available resources - re-enables previously failing test
34b3c6c
to
2e4ca1d
Compare
~/.android/adb* | ||
key: avd-${{ matrix.api-level }} | ||
|
||
- name: create AVD and generate snapshot for caching |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
caching the AVD is causing strange problems for the playstore
emulator image where the expected AVD path changes between runs
PANIC: Broken AVD system path. Check your ANDROID_SDK_ROOT value [/usr/local/lib/android/sdk]!
Creating a new AVD image each run fixes the problem but does mean the initial start time becomes slower
Kudos, SonarCloud Quality Gate passed! |
Type of change
Content
Fixes the
CantVerifyTest
failing when running on the buildjet github action runner, the cause seems to be related to the emulator not having access to the wider network, which meant the initial matrix.org requests would timeout.For reasons unknown to me, switching the emulator image to use the play store version ensures that the outside network is accessible.
Motivation and context
To re-enable an ignored test
Screenshots / GIFs
No production code changes
Tests
Run on the CI!
Tested devices