Remove C++ dependency from thread state#108
Conversation
ac90a7e to
b2548b3
Compare
Signed-off-by: Gideon Sebastian Geier <gideon.sebastian.geier@huawei.com>
Signed-off-by: Gideon Sebastian Geier <gideon.sebastian.geier@huawei.com>
b2548b3 to
c3ee667
Compare
Signed-off-by: Gideon Sebastian Geier <gideon.sebastian.geier@huawei.com>
db7
left a comment
There was a problem hiding this comment.
LGTM. I think this is a good improvement. It removes one potential source of problems.
|
There's just one problem left to solve: apparently, this uncovers a race between the first trace entry and file creation and the attribute constructor that calls the cleanup. At least the pipeline seems to show that: For now, the pipeline just passes, because I disabled the cleanup. I assume it is a race, because I don't have this issue on my machine. However, it could be also deterministically first alloc/trace entry, constructor and cleanup, and then the remaining tracing. |
I will try to reproduce on my side. |
I couldnt reproduce on my Ubuntu system |
|
I ran once the pipeline without changes to confirm it's not because github changed the runners #110. And I made the current change no longer be triggered by no longer calling |
|
070e188 'fixed' it: disabling the cleanup in the pipeline, but this can't be the solution |
Ok, if that was the change than I really cannot reproduce it. |
6cee6ef to
2ff0287
Compare
Signed-off-by: Diogo Behrens <db7@sdf.org>
b4c4497 to
9d730ba
Compare
Signed-off-by: Diogo Behrens <db7@sdf.org>
Signed-off-by: Diogo Behrens <db7@sdf.org>
58fc021 to
c090e34
Compare
Summary
Verification