-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Update jemalloc to 4.5.0 #41861
Update jemalloc to 4.5.0 #41861
Conversation
r? @brson (rust_highfive has picked a reviewer for you, use r? to override) |
Thanks! Do you have a pointer to the commit for the disable-lazy-lock business? Or a pointer to the source which disables it on Windows today? (just curious) |
Apparently it involves multiple commits jemalloc/jemalloc#310 (comment) |
@bors: r+ Sounds great! |
📌 Commit 8f420b4 has been approved by |
…ichton Update jemalloc to 4.5.0 * pointing jemalloc submodule to the 4.5.0 HEAD + generated configure script * removed the now unnecessary extra config for windows. jemalloc is now much better at configuring itself overall. Let's see what the CI think.
I believe that this has caused the failure of #41872 (maybe an interaction with #41863?):
|
I'm looking into it. |
Once we merge rust-lang/jemalloc#18 I'll update the submodule reference here. |
@bors r- |
8f420b4
to
65d0be3
Compare
Submodule updated. Shall we give it another shot? |
@bors r=alexcrichton |
📌 Commit 65d0be3 has been approved by |
⌛ Testing commit 65d0be3 with merge 583c025... |
💔 Test failed - status-travis |
Looks like 32-bit segfaults?
|
😞 How can I simulate this build locally? I tried to follow the CI setup but I got lost real quick. |
@alexcrichton Could you help out here? We should provide some instructions on how to use Rust's CI containers locally on the forge... |
I'm on my phone, but you should be able toodify one of the CI scripts to whitelist the machines you want to test on in a script somewhere and then push to this branch |
After posting that I tried running the container with Here's the output with
|
Ah yeah the README has some more info but looks like you found it. That's odd though that it failed to build, can you try blowing away local state, updating submodules, and trying again? |
@bors: retry
|
Bors is on a strike? |
Well, we had one PR take like 6 hours to test since I think a builder didn't start or was really slow (no clue why) and then the rollup I created failed, so... we're waiting :). See https://buildbot2.rust-lang.org/homu/queue/rust if you want to follow progress. |
I wasn't aware of that queue page, thanks! |
Update jemalloc to 4.5.0 * pointing jemalloc submodule to the 4.5.0 HEAD + generated configure script * removed the now unnecessary extra config for windows. jemalloc is now much better at configuring itself overall. Let's see what the CI think.
☀️ Test successful - status-appveyor, status-travis |
🎉 |
Unfortunately I think this causes a regression on OSX 10.12. @arthurprs would you be up for submitting a PR to revert? |
Will do. |
Update jemalloc to 4.5.0 Second try, including the fix for osx deadlock jemalloc/jemalloc#895. cc #41861 @alexcrichton @RalfJung
Let's see what the CI think.