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

Fix shared_future_continuation_order regression test #6341

Merged
merged 1 commit into from
Sep 2, 2023

Conversation

Pansysk75
Copy link
Member

Fixes occasional failure of shared_future_continuation_order regression test.
If my understanding is correct, continuations are executed on newly spawned threads by default, which would not guarantee their order of execution. Launching with hpx::launch::sync should guarantee that no new thread is spawned, thus they are executed in sequence.
(@hkaiser We had fixed this in some PR in the past, but it seems it didn't make it into master)

@hkaiser hkaiser added this to the 1.10.0 milestone Sep 1, 2023
@Pansysk75 Pansysk75 force-pushed the fix_continuation_order_test branch from c4abeff to 7170d7d Compare September 1, 2023 20:16
Copy link
Member

@hkaiser hkaiser left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks!

@hkaiser
Copy link
Member

hkaiser commented Sep 2, 2023

bors merge

@bors
Copy link

bors bot commented Sep 2, 2023

Build succeeded!

The publicly hosted instance of bors-ng is deprecated and will go away soon.

If you want to self-host your own instance, instructions are here.
For more help, visit the forum.

If you want to switch to GitHub's built-in merge queue, visit their help page.

  • Bors

@Pansysk75 Pansysk75 merged commit 5457e19 into master Sep 2, 2023
17 of 18 checks passed
@Pansysk75 Pansysk75 deleted the fix_continuation_order_test branch September 2, 2023 14:49
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.

2 participants