Skip to content

Conversation

@therault
Copy link
Contributor

  • Make sure the parsec context is started only after the taskpool is created as the taskpool will register active message handlers for the first time via the user-triggered option in PTG
  • Correctly compute the number of local tasks instead of assuming a run at a given world size; compute that number on all ranks and check that all ranks have a correct value
  • have all MPI rank return the same return code for consistency
  • Free the taskpool when it's not used anymore to remove assertion.

 - Make sure the parsec context is started only after the taskpool
   is created as the taskpool will register active message handlers
   for the first time via the user-triggered option in PTG
 - Correctly compute the number of local tasks instead of assuming
   a run at a given world size; compute that number on all ranks
   and check that all ranks have a correct value
 - have all MPI rank return the same return code for consistency
 - Free the taskpool when it's not used anymore to remove assertion.
@therault therault requested a review from a team as a code owner July 12, 2024 20:06
@bosilca
Copy link
Contributor

bosilca commented Sep 9, 2024

This is breaking existing capabilities. The termination detection capability should work in all cases, not only when then context is started after the taskpool creation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants