-
Notifications
You must be signed in to change notification settings - Fork 13.3k
[WIP-test run] switch rustc allocator to mimalloc #64495
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
Conversation
…malloc from being enabled
@bors: try |
@gnzlbg: 🔑 Insufficient privileges: not in try users |
@bors try |
⌛ Trying commit 111e3f8 with merge 606331a2236eca07e80368668ab5c7b97d68c300... |
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
💔 Test failed - checks-azure |
The mimalloc maintainers were finally able to reproduce our segfaults, so i'm closing this again since no progress can happen here until those issues are resolved. @Mark-Simulacrum there is currently a big barrier of entry to debug rustc issues. I think it would be worth documenting how to run rustc build locally in the exact same way that CI does (e.g. using docker as @mati865 explains microsoft/mimalloc#77 ). Also, when running a test fails, there is no easy way to debug it in the same conditions that CI has, and e.g., just launch gdb/lldb/valgrind/etc. on the test. One currently gets the CLI invocation for the command that fails, but this does not includes all the environment variables required to run that command correctly, see this comment: microsoft/mimalloc#77 (comment) |
Now that daanx figured out what was happening in microsoft/mimalloc#77 (comment) , is it worth retrying? |
I think it is. A new test run has been opened in #81782 |
Follow up to #62340 . Disables secure mode.
r? @mati865