Skip to content

Enable debug MALLOC_CONF options on CI #2031

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

Merged
merged 2 commits into from
Dec 23, 2019
Merged

Conversation

jtgeibel
Copy link
Member

On top of the production configuration, this commit adds two options:

  • abort:true - most jemalloc warnings become fatal (opt.abort)
  • junk:true - both allocated and deallocated memory will be
    initialized to 0xa5. (opt.junk)

Combined with the existing abort_conf:true, this should be equivalent
to enabling the debug feature of jemallocator. We cannot enable
this feature in Cargo.toml because that would affect performance in
production.

r? @carols10cents

@jtgeibel
Copy link
Member Author

Hopefully #2027 (comment) was just a fluke. If not, this should make things worse I guess, lol. The tests run fine for me locally.

On top of the production configuration, this commit adds two options:

* `abort:true` - most jemalloc warnings become fatal ([opt.abort])
* `junk:true` - both allocated and deallocated memory will be
  initialized to 0xa5. ([opt.junk])

Combined with the existing `abort_conf:true`, this should be equivalent
to enabling the `debug` feature of `jemallocator`.  We cannot enable
this feature in `Cargo.toml` because that would affect performance in
production.

[opt.abort]: http://jemalloc.net/jemalloc.3.html#opt.abort
[opt.junk]: http://jemalloc.net/jemalloc.3.html#opt.junk
@carols10cents
Copy link
Member

LGTM! 🤷‍♀

@bors r+

@bors
Copy link
Contributor

bors commented Dec 23, 2019

📌 Commit 8cd03c7 has been approved by carols10cents

bors added a commit that referenced this pull request Dec 23, 2019
Enable debug MALLOC_CONF options on CI

On top of the production configuration, this commit adds two options:

* `abort:true` - most jemalloc warnings become fatal ([opt.abort])
* `junk:true` - both allocated and deallocated memory will be
  initialized to 0xa5. ([opt.junk])

Combined with the existing `abort_conf:true`, this should be equivalent
to enabling the `debug` feature of `jemallocator`.  We cannot enable
this feature in `Cargo.toml` because that would affect performance in
production.

[opt.abort]: http://jemalloc.net/jemalloc.3.html#opt.abort
[opt.junk]: http://jemalloc.net/jemalloc.3.html#opt.junk

r? @carols10cents
@bors
Copy link
Contributor

bors commented Dec 23, 2019

⌛ Testing commit 8cd03c7 with merge 79176c7...

@bors
Copy link
Contributor

bors commented Dec 23, 2019

☀️ Test successful - checks-travis
Approved by: carols10cents
Pushing 79176c7 to master...

@bors bors merged commit 8cd03c7 into rust-lang:master Dec 23, 2019
@jtgeibel jtgeibel deleted the ci/malloc_conf branch December 23, 2019 22:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants