-
Notifications
You must be signed in to change notification settings - Fork 13.3k
std: Update jemalloc version #30434
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
std: Update jemalloc version #30434
Conversation
(rust_highfive has picked a reviewer for you, use r? to override) |
I... forget the reason that this bounced in the past, and it may have been fixed upstream, so I figured we should try again. |
@bors: r+ Let's refresh our memories. |
📌 Commit aed7997 has been approved by |
⌛ Testing commit aed7997 with merge 8f431fa... |
💔 Test failed - auto-linux-64-nopt-t |
@bors: retry On Dec 19, 2015, 09:07 -0500, [email protected], wrote:
|
⌛ Testing commit aed7997 with merge a692b0d... |
💔 Test failed - auto-win-gnu-32-nopt-t |
@bors retry |
⌛ Testing commit aed7997 with merge aa1075c... |
💔 Test failed - auto-win-gnu-32-nopt-t |
Both bot failures failed with the error code |
aed7997
to
c0b868e
Compare
@bors: r+ c0b868e133744dd0d23849671d818f5dcefe25ad |
⌛ Testing commit c0b868e with merge 980c216... |
💔 Test failed - auto-win-gnu-64-opt |
It's been awhile since we last updated jemalloc, and there's likely some bugs that have been fixed since the last version we're using, so let's try to update again.
c0b868e
to
9929c24
Compare
We're currently passing |
It's been awhile since we last updated jemalloc, and there's likely some bugs that have been fixed since the last version we're using, so let's try to update again.
🌴 |
We've been seeing a lot of timeouts in tests on the bots and investigation ended pointing to jemalloc/jemalloc#315 as the culprit. Unfortunately it looks like that doesn't seem to have a fix on the way soon, so let's temporarily downgrade back to the previous version of jemalloc we were using (where rust-lang#30434 was the most recent upgrade)
We've been seeing a lot of timeouts in tests on the bots and investigation ended pointing to jemalloc/jemalloc#315 as the culprit. Unfortunately it looks like that doesn't seem to have a fix on the way soon, so let's temporarily downgrade back to the previous version of jemalloc we were using (where #30434 was the most recent upgrade)
It's been awhile since we last updated jemalloc, and there's likely some bugs
that have been fixed since the last version we're using, so let's try to update
again.