-
-
Notifications
You must be signed in to change notification settings - Fork 8.6k
test: enable gc tests #13272
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
base: main
Are you sure you want to change the base?
test: enable gc tests #13272
Conversation
WalkthroughThe test configuration file was updated to modify the way test worker processes are spawned. The worker pool type was changed from using threads to using forks. Additionally, new pool options were specified for the forked workers, particularly adding an execution argument to expose the garbage collector. No other configuration settings or public interfaces were altered. Changes
Poem
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
⏰ Context from checks skipped due to timeout of 90000ms (3)
✨ Finishing Touches
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
Size ReportBundles
Usages
|
@vue/compiler-core
@vue/compiler-dom
@vue/compiler-sfc
@vue/compiler-ssr
@vue/reactivity
@vue/runtime-core
@vue/runtime-dom
@vue/server-renderer
@vue/shared
vue
@vue/compat
commit: |
reactivity/gc tests were being skipped because vitest was running without gc exposed
reactivity/gc tests were being skipped because vitest was running without gc exposed.
One test is currently failing but passed by unnoticed because of this.
CC @johnsoncodehk
Summary by CodeRabbit