Skip to content

[1.30 beta] Test suite of the jemalloc-ctl crate is failing #54478

Description

@emilyalbini

This is not a spurious failure (the test output is consistent between runs), but we need to investigate why this is happening.

Activity

  1. added this to the 1.30 milestone on Sep 22, 2018
  2. sfackler commented on Sep 23, 2018

    @sfackler
    Member

    Those errors seem to imply that global allocator registration may have broken?

  3. sfackler commented on Sep 23, 2018

    @sfackler
    Member

    It seems like it may specifically be a problem with rustdoc tests - a normal library test passes as expected.

  4. self-assigned this
    on Sep 27, 2018
  5. pnkfelix commented on Oct 8, 2018

    @pnkfelix
    Contributor

    Bisection over nightly builds indicates that bug was injected between nightly-2018-08-06-x86_64-unknown-linux-gnu (73c7873) and nightly-2018-08-14-x86_64-unknown-linux-gnu (d5a448b).

    In the details block are the bors commits from that range:

    Details

    % git log --author bors 73c7873..d5a448b --format=oneline

  6. pnkfelix commented on Oct 9, 2018

    @pnkfelix
    Contributor

    Okay I bisected this and identified the bug as being injected by #52993

  7. pnkfelix commented on Oct 9, 2018

    @pnkfelix
    Contributor

    Adding @alexcrichton to the assignee list in case they have some special insight into how best to address it. (But, as I noted on #52993, I am hoping we can get away with just undoing one small part of that PR, rather than backing out the whole thing, which seems like it might cause more trouble than it would resolve)

  8. added
    A-allocatorsArea: Custom and system allocators
    T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.
    T-libs-api[DEPRECATED; DO NOT USE]
    on Oct 9, 2018
  9. pnkfelix commented on Oct 9, 2018

    @pnkfelix
    Contributor

    (also, tagging with both T-compiler and T-libs for now, though either team is free to untag the other if they want to take responsibility for resolving this.)

  10. 13 remaining items

  11. emilyalbini commented on Oct 18, 2018

    @emilyalbini
    MemberAuthor

    Fixed and backported, should work in the next beta release.

  12. pnkfelix commented on Oct 19, 2018

    @pnkfelix
    Contributor

    I hate to ask, but: @pietroalbini , I think we still need a regression test, right?

  13. emilyalbini commented on Oct 19, 2018

    @emilyalbini
    MemberAuthor

    Ugh, there was no regression test in that PR.

  14. added
    E-needs-testCall for participation: An issue has been fixed and does not reproduce, but no test has been added.
    on Oct 19, 2018
  15. pnkfelix commented on Oct 19, 2018

    @pnkfelix
    Contributor

    (But the lack of a regression test does not need to block the release, of course)

  16. emilyalbini commented on Oct 19, 2018

    @emilyalbini
    MemberAuthor

    Manually checked the issue is actually fixed, just to be sure.

  17. added a commit that references this issue on Oct 25, 2018
  18. added a commit that references this issue on Oct 25, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

A-allocatorsArea: Custom and system allocatorsC-bugCategory: This is a bug.E-needs-testCall for participation: An issue has been fixed and does not reproduce, but no test has been added.T-rustdocRelevant to the rustdoc team, which will review and decide on the PR/issue.regression-from-stable-to-betaPerformance or correctness regression from stable to beta.

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions