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

Try reenabling glibc's tcache in CircleCI #281

Closed
msimberg opened this issue Jun 30, 2022 · 2 comments
Closed

Try reenabling glibc's tcache in CircleCI #281

msimberg opened this issue Jun 30, 2022 · 2 comments
Labels
effort: 2 A few hours of work. effort: 3 A few days of work. effort: 4 A few weeks of work. effort: 5 Who knows how long it'll take? This must be split into smaller tasks. priority: low Nice to have, but nobody is going to be sad if this is never done. type: bug
Milestone

Comments

@msimberg
Copy link
Contributor

msimberg commented Jun 30, 2022

Or attempt to create a reproducer and report bug upstream? Cf. #280.

@msimberg msimberg added effort: 2 A few hours of work. effort: 3 A few days of work. effort: 4 A few weeks of work. effort: 5 Who knows how long it'll take? This must be split into smaller tasks. priority: low Nice to have, but nobody is going to be sad if this is never done. type: bug labels Jun 30, 2022
@msimberg msimberg moved this to Backlog in pika planning board Jun 30, 2022
bors bot added a commit that referenced this issue Jun 30, 2022
280: Disable glibc's tcache temporarily in CircleCI r=msimberg a=msimberg

Temporarily testing to see if disabling glibc's tcache would reduce the error rate on the `std_thread_scheduler` test (see #250 (comment)). Cf. #281.

Co-authored-by: Mikael Simberg <mikael.simberg@iki.fi>
@msimberg
Copy link
Contributor Author

msimberg commented Jul 6, 2022

It seems like this may not have changed anything on CircleCI, so it should be reenabled and the issue looked at again...

@msimberg msimberg changed the title Try reenabling glibc's tcache in CircleCi Try reenabling glibc's tcache in CircleCI Jul 6, 2022
@msimberg
Copy link
Contributor Author

The option was removed in #776.

@github-project-automation github-project-automation bot moved this from Backlog to Done in pika planning board Feb 16, 2024
@msimberg msimberg added this to the 0.19.0 milestone Mar 7, 2024
@msimberg msimberg moved this from Done to Archive in pika planning board Mar 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
effort: 2 A few hours of work. effort: 3 A few days of work. effort: 4 A few weeks of work. effort: 5 Who knows how long it'll take? This must be split into smaller tasks. priority: low Nice to have, but nobody is going to be sad if this is never done. type: bug
Projects
Archived in project
Development

No branches or pull requests

1 participant