Skip to content

Conversation

@maflcko
Copy link
Member

@maflcko maflcko commented Nov 6, 2023

No description provided.

@DrahtBot
Copy link
Contributor

DrahtBot commented Nov 6, 2023

The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.

Code Coverage

For detailed information about the code coverage, see the test coverage report.

Reviews

See the guideline for information on the review process.
A summary of reviews will appear here.

@maflcko maflcko changed the title Revert "suppressions: note that 'type:ClassName::MethodName' should be used" test: Revert "suppressions: note that 'type:ClassName::MethodName' should be used" Nov 6, 2023
@DrahtBot DrahtBot added the Tests label Nov 6, 2023
@maflcko maflcko closed this Nov 7, 2023
@maflcko maflcko deleted the 2311-test-supp- branch November 7, 2023 18:22
fanquake added a commit that referenced this pull request Nov 8, 2023
49d9532 fuzz: explicitly specify llvm-symbolizer path in runner (fanquake)

Pull request description:

  It's not completely clear to me why this needs to be explicitly specified in some environments, and not in others, while at the same time that `llvm-symbolizer` is already in PATH, but this has fixed the 2 issues outlined in #28147.

  Use `LLVM_SYMBOLIZER_PATH` as the env var, as that is somewhat also used inside LLVM, but not consistently, i.e it's checked for in the asan_symbolize script, but not in in the ubsan_symbolize script, or from in compiler-rt.

  Alternative to #28804.

ACKs for top commit:
  maflcko:
    lgtm ACK 49d9532

Tree-SHA512: c3d5bf1c3629793b342c70754a419b3c7a3cd39f800b9aa69ce3395cc2bf83b4d46f2b329974337b94b99573cd0b8600d3f147ed5c21387bf3812316570d1ee3
@bitcoin bitcoin locked and limited conversation to collaborators Nov 6, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants