Skip to content
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

Reintroduce debuginfod deadlock workaround #635

Merged

Conversation

godlygeek
Copy link
Contributor

While switching from referencing the system debuginfod client library to vendoring our own copy of it, I removed a hack that turns out to still be required for some libc versions, because I incorrectly thought it only applied to the case when debuginfod was being loaded with dlopen.

Closes #634

While switching from referencing the system debuginfod client library to
vendoring our own copy of it, I removed a hack that turns out to still
be required for some libc versions, because I incorrectly thought it
only applied to the case when debuginfod was being loaded with `dlopen`.

Signed-off-by: Matt Wozniski <[email protected]>
See changelog for more details.

Signed-off-by: Matt Wozniski <[email protected]>
@godlygeek godlygeek self-assigned this Jun 24, 2024
@codecov-commenter
Copy link

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 93.02%. Comparing base (41248ed) to head (af85883).
Report is 90 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #635      +/-   ##
==========================================
+ Coverage   92.55%   93.02%   +0.47%     
==========================================
  Files          91       94       +3     
  Lines       11304    11412     +108     
  Branches     1581     2089     +508     
==========================================
+ Hits        10462    10616     +154     
+ Misses        837      796      -41     
+ Partials        5        0       -5     
Flag Coverage Δ
cpp 93.02% <100.00%> (+7.08%) ⬆️
python_and_cython 93.02% <100.00%> (-2.70%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@godlygeek
Copy link
Contributor Author

@ZeroIntensity confirmed for me that the wheels built by this CI run do in fact fix #634.

@pablogsal pablogsal enabled auto-merge (rebase) June 24, 2024 10:19
@pablogsal pablogsal merged commit 08e4cc6 into bloomberg:main Jun 24, 2024
19 of 20 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

memray flamegraph hangs on files generated with --native
3 participants