-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
feat: support --segfault-retry=3
#1854
Conversation
main() | ||
|
||
async function start(args: string[]) { | ||
const child = execa('node', [fileURLToPath(ENTRY), ...args], { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Doesn't it hurt performance for "--segfault-retry=1" that we always starts a child process? Shouldn't we just import ./cli.mjs
in this case?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hm, but we can't show useful error message that way 🤔
I guess it's ok for now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't count how many times we invoke vitest
in our test, but at the high level, it doesn't make CI time increase. Using this would allow us to provide information about the segfault reasoning and issue link.
Context: vitejs/vite#9508
Changes:
--segfault-retry
CLI flag andVITEST_SEGFAULT_RETRY
envCo-authored-by: tony19 tony19@users.noreply.github.com