-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Only run test_recursive_call() in CI
#12568
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?
Conversation
Deploying pydantic-docs with
|
| Latest commit: |
fe7b52e
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://a1102f94.pydantic-docs.pages.dev |
| Branch Preview URL: | https://vp-debug-recursive-test.pydantic-docs.pages.dev |
CodSpeed Performance ReportMerging #12568 will improve performances by 5.8%Comparing Summary
Benchmarks breakdown
|
|
Can you explain again the conditions under which you get it to fail? Maybe I can fix this without needing to disable it from local testing (which IMO makes it easy for development to miss fixing the test). |
Setting the recursion limit to >= 750 on my end will create the segfault. I discussed this with Matthew, and he told me Rust doesn't have any guarantee of providing a correct "stack overflow" message (see rust-lang/rust#79935 (comment)), so my assumption is that on my end, it overflows on the Rust side with a lower limit (around 750) than the Python one I have (1000). |
Change Summary
Related issue number
Checklist