Skip to content

Too many tests trigger a valgrind internal assertion about function size #4478

@brson

Description

@brson

I have a branch where, if I add one more #[test] to core then valgrind will abort with an internal assertion failure. I don't have the message here but the valgrind source indicates its a sanity check about function size. Presumably our test harness is generating a main function that is larger than anything valgrind expects to see in the real world.

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-frontendArea: Compiler frontend (errors, parsing and HIR)A-testsuiteArea: The testsuite used to check the correctness of rustc

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions