-
Notifications
You must be signed in to change notification settings - Fork 1
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
Address thread-safety issues by removing backtrace logger #147
Conversation
7c81cc3
to
2872071
Compare
We keep running into |
@@ -1,115 +1,3 @@ | |||
# We only run clang-13 on 20.04 (and whatever ships on its libc), the other compilers run on 22.04 | |||
# unfortunately we have to duplicate the postprocessing steps | |||
FROM ubuntu:20.04 AS base-ubuntu20 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
drop ubuntu 20
@@ -226,16 +114,6 @@ ENTRYPOINT ["/usr/bin/entrypoint"] | |||
|
|||
# ---------------------------------------------------------------------------------------------------------------- | |||
|
|||
# 20.04 for clang-13 | |||
FROM base-ubuntu20 AS clang-13-ubuntu20 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
kept clang-13
with ubuntu 22
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice! Thanks for adding the test coverage.
The logger maintained a history for logging a backtrace in case of errors, this wasn't thread-safe, rather costly and currently unused so we've decided to remove it.
Fixes #139
This is an alternative to #140 to avoid introducing locks
Before:
After: