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

Occasionally failing tests #191

Open
3 of 11 tasks
msimberg opened this issue Apr 12, 2022 · 3 comments
Open
3 of 11 tasks

Occasionally failing tests #191

msimberg opened this issue Apr 12, 2022 · 3 comments
Assignees
Labels
effort: 3 A few days of work. effort: 4 A few weeks of work. priority: medium This should be done sooner or later. type: bug

Comments

@msimberg
Copy link
Contributor

msimberg commented Apr 12, 2022

This issue is meant to collect the names of failing tests together with links to the failures for investigation. This is a long-running issue and will likely not be closed by one or only a few PRs.

@msimberg msimberg moved this to Backlog in pika planning board Apr 12, 2022
This was referenced Apr 26, 2022
@msimberg msimberg added effort: 3 A few days of work. effort: 4 A few weeks of work. priority: medium This should be done sooner or later. type: bug labels May 4, 2022
@msimberg msimberg added this to the 0.6.0 milestone Jun 3, 2022
@msimberg msimberg moved this from Backlog to Todo in pika planning board Jun 3, 2022
@msimberg
Copy link
Contributor Author

msimberg commented Jun 3, 2022

I will attempt to look at the std_thread_scheduler failure for 0.6.0.

@msimberg msimberg self-assigned this Jun 3, 2022
bors bot added a commit that referenced this issue Jun 8, 2022
250: Attempt to wait for detached thread to finish in `std_thread_scheduler_test` r=msimberg a=msimberg

I think this fixes part of #191 (the `std_thread_scheduler_test` failures). The sender is still discarded immediately so that part is still somewhat tested, but we attempt to wait for the detached `std::thread` to avoid having it possibly start after exiting main.

Co-authored-by: Mikael Simberg <mikael.simberg@iki.fi>
@msimberg msimberg removed this from the 0.6.0 milestone Jun 23, 2022
@msimberg msimberg added this to the 0.7.0 milestone Jul 7, 2022
@msimberg msimberg removed this from the 0.7.0 milestone Jul 19, 2022
bors bot added a commit that referenced this issue Sep 29, 2022
395: Re-enable release builds on Jenkins r=msimberg a=msimberg

Half-depends on #67 (i.e. should go in afterwards).

Fixes #382.

This may end up increasing the failure rate of #191 to something that is no longer sustainable. With this we also have to be a lot more mindful not to spam `bors try/merge` since the used node hours will at least double. Draft because of the above reasons.

Co-authored-by: Mikael Simberg <mikael.simberg@iki.fi>
@msimberg msimberg added this to the 0.11.0 milestone Nov 3, 2022
@msimberg msimberg modified the milestones: 0.11.0, 0.12.0 Dec 5, 2022
bors bot added a commit that referenced this issue Jan 30, 2023
579: Disable `std_thread_scheduler_test` on macOS CI r=msimberg a=msimberg

It fails frequently and is listed on #191.

Co-authored-by: Mikael Simberg <mikael.simberg@iki.fi>
bors bot added a commit that referenced this issue Jan 30, 2023
579: Disable `std_thread_scheduler_test` on macOS CI and reduce parallelism on arm64 CircleCI configuration r=msimberg a=msimberg

`std_thread_scheduler_test` fails frequently and is listed on #191. I'm attempting to reduce parallelism for tests on the `arm64` configuration to see if it reduces timeouts on the `condition_variable2` test. One of the timed tests fails, which may indicate oversubscription (since we haven't seen it fail on other configurations).

Co-authored-by: Mikael Simberg <mikael.simberg@iki.fi>
@msimberg msimberg modified the milestones: 0.12.0, 0.13.0 Jan 31, 2023
bors bot added a commit that referenced this issue Jan 31, 2023
579: Disable `std_thread_scheduler_test` on macOS CI and reduce parallelism on arm64 CircleCI configuration r=msimberg a=msimberg

`std_thread_scheduler_test` fails frequently and is listed on #191. I'm attempting to reduce parallelism for tests on the `arm64` configuration to see if it reduces timeouts on the `condition_variable2` test. One of the timed tests fails, which may indicate oversubscription (since we haven't seen it fail on other configurations).

580: Update atomics feature test to correctly use fallback test with libatomic r=msimberg a=msimberg

Attempts to fix #576.

The regular atomics test already had a fallback to use `libatomic`, but because the `REQUIRED` flag was set the default test fails immediately and never lets the fallback test run. This adds another flag `NOT_REQUIRED` which overrides `REQUIRED` and is used in the default atomics tests (the fallback test still uses plain `REQUIRED` if requested by the caller).

Co-authored-by: Mikael Simberg <mikael.simberg@iki.fi>
bors bot added a commit that referenced this issue Jan 31, 2023
579: Disable `std_thread_scheduler_test` on macOS CI and reduce parallelism on arm64 CircleCI configuration r=msimberg a=msimberg

`std_thread_scheduler_test` fails frequently and is listed on #191. I'm attempting to reduce parallelism for tests on the `arm64` configuration to see if it reduces timeouts on the `condition_variable2` test. One of the timed tests fails, which may indicate oversubscription (since we haven't seen it fail on other configurations).

Co-authored-by: Mikael Simberg <mikael.simberg@iki.fi>
@aurianer aurianer modified the milestones: 0.13.0, 0.14.0 Mar 8, 2023
@msimberg
Copy link
Contributor Author

These are some of the more frequently failing tests on CDash: https://cdash.cscs.ch/testOverview.php?project=pika&date=2023-01-31&group=28.

@aurianer
Copy link
Contributor

aurianer commented Nov 3, 2023

ARCHIVE (bugs solved):

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
effort: 3 A few days of work. effort: 4 A few weeks of work. priority: medium This should be done sooner or later. type: bug
Projects
Development

No branches or pull requests

2 participants