Emulator test matrix in "Feat/add docker testing" #68
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…nd, waiting for another job to complete takes a while
|
Thanks for the good work. I see the issues with timeouts - I've decided to use just one value in the matrix for now, but I'll keep this branch as a reference |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hey,
I've added some emulators, but mind you that the whole test framework is flaky.
/sdcard may or may not be a good place for test file creation. I would do that in /data/local/tmp, but that also may not be available on all devices.
Ubuntu only has a single fuse version, so we can't add that to the test matrix. There's fuse3, but we would need support in adbfs before we test it.
Haven't looked into testing arm64 on macos yet.