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

Move coverage to GitHub actions #10898

Merged

Conversation

JLHwung
Copy link
Contributor

@JLHwung JLHwung commented Dec 20, 2019

Q                       A
Fixed Issues? ENOMEM: not enough memory, stat /home/circleci/babel/packages/just/click/the/rerun/button
Tests Added + Pass? Yes
License MIT

This PR moves the coverage report job to GitHub Actions. The ENOMEM error should be alleviated because

CPU RAM
GitHub 2 core 7GB
CircleCI 2 core 4GB

Merge tips:
Please add CODECOV_TOKEN to the Settings > Secrets after merging to master. See https://github.com/codecov/codecov-action#usage

@JLHwung JLHwung added the PR: Internal 🏠 A type of pull request used for our changelog categories label Dec 20, 2019
IS_PUBLISH=true make build-standalone
# data for a JS file that's several megabytes large is bound to fail. Here,
# we just run the babel-standalone test separately.
yarn jest "\-standalone/test"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since this is just for coverage, maybe we can avoid testing standalone here?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The standalone is only tested on the coverage job in the CI, we have skipped the test on other executors.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh then maybe we should test it separately? I don't really see how it fits in the coverage tests.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah but standalone will rely on building and installing all the dependencies, I think we can test it here to save redundant machine hours.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok fair

@JLHwung JLHwung force-pushed the move-coverage-test-to-github-actions branch from a6b4865 to 6b47be7 Compare December 20, 2019 02:55
@JLHwung JLHwung marked this pull request as ready for review December 20, 2019 03:02
@nicolo-ribaudo nicolo-ribaudo merged commit c5cfc83 into babel:master Dec 20, 2019
@nicolo-ribaudo nicolo-ribaudo deleted the move-coverage-test-to-github-actions branch December 20, 2019 20:32
@github-actions github-actions bot added the outdated A closed issue/PR that is archived due to age. Recommended to make a new issue label Mar 21, 2020
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 21, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
outdated A closed issue/PR that is archived due to age. Recommended to make a new issue PR: Internal 🏠 A type of pull request used for our changelog categories
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants