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 from "process.exit" to "exit" #7327

Merged
merged 5 commits into from
Mar 19, 2019
Merged

Move from "process.exit" to "exit" #7327

merged 5 commits into from
Mar 19, 2019

Conversation

JLHwung
Copy link
Contributor

@JLHwung JLHwung commented Nov 5, 2018

Summary

Follow up to #5313.

Test plan

Test failure seems unrelated.

@facebook-github-bot
Copy link
Contributor

Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. In order for us to review and merge your code, please sign up at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need the corporate CLA signed.

If you have received this in error or have any questions, please contact us at cla@fb.com. Thanks!

@facebook-github-bot
Copy link
Contributor

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks!

@SimenB SimenB requested a review from mjesun November 5, 2018 23:25
@SimenB
Copy link
Member

SimenB commented Mar 18, 2019

@JLHwung hey, could you rebase this? 🙏

@JLHwung
Copy link
Contributor Author

JLHwung commented Mar 19, 2019

@SimenB Rebased and thanks for reminder. Nearly forgot this patch. 🤦‍♂️

@SimenB SimenB merged commit e3bc4f5 into jestjs:master Mar 19, 2019
SimenB added a commit that referenced this pull request Mar 19, 2019
@SimenB
Copy link
Member

SimenB commented Mar 19, 2019

This seems to break node 6, not sure why... I reverted for now, do you think you can open up a new PR and check that node 6 passes?

@JLHwung
Copy link
Contributor Author

JLHwung commented Mar 20, 2019

This seems to break node 6, not sure why... I reverted for now, do you think you can open up a new PR and check that node 6 passes?

Hmm, interesting. I will investigate the issue later this day. According to CircleCI, test also breaks on Node.js 11 for the same reason of Node.js 6. I doubt that if the exit package introduces memory leak.

@SimenB
Copy link
Member

SimenB commented Mar 20, 2019

that one's unrelated

@github-actions
Copy link

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 11, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants