Improve Travis CI configuration. #44
Closed
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
added 30 commits
September 21, 2017 16:30
-Make the API and ABI for emulator easily parameterizable -Do not install emulator hardcoded in install step -Remove installation of support repo that is unnecessary after google maven repo. -Start emulator in before_script
akeeaggarwal
referenced
this pull request
Jan 30, 2024
… they can be customized Resolves #3492 PiperOrigin-RevId: 590915421
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.
-Removes unnecessary packages that were being installed before having the Google Maven Repository.
-Splits Travis CI builds into separate jobs, one containing unit tests only and the rest containing instrumentation tests. This helps keep lint and unit test results separate from other checks and improves performance.
-Makes sure unit test jobs do not bring up any emulators.
-Makes sure instrumentation test jobs don't run any unit tests.
-Adds 3 environments to run tests in, android-16, android-19 and android-21.
-- Each of these environments installs its dependencies dynamically, so the build takes the least amount of time installing stuff
Notice SnackBarTest is flaky, but fails often in android-21, and AppBarWithCollapsingToolbarTest.testPinnedToolbarWithMargins fails constantly on all three targets.
This is not the case with internal tools, so these failures have to be debugged manually in external configurations.