build: migrate unit tests to GitHub Actions #1870
Merged
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
mantariksh
requested review from
karrui,
liangyuanruo,
chowyiyin,
seaerchin,
tshuli and
yong-jie
karrui
approved these changes
May 12, 2021
yong-jie
approved these changes
May 12, 2021
Merged
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.
Problem
Unit tests on Travis CI have been intermittently failing due to memory issues with Jest. It does not seem like the issue is with the tests themselves, since running
jest --logHeapUsageshows that the memory usage does not increase consistently as more tests pass. This suggests that the memory limitation is with Travis.Part of #1864
Solution
This PR migrates only the frontend and backend unit tests to GitHub Actions (GA) to test whether the tests pass consistently. If they do, we can consider migrating the entire CI pipeline to GA.