You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
gaspi_allreduce doesn't affect the state vector in case of an error.
If i use a barrier returning a timeout before allreduce (given example), gaspi_allreduce returns an error. If their is no barrier called before gaspi_allreduce the applications pends forever.
Either way, the state vector doesn't change.
Also, the standard says in case of an error gaspi_allrduce returns GASPI_ERROR not a GPI2 specific error code.
gaspi_allreduce doesn't affect the state vector in case of an error.
If i use a barrier returning a timeout before allreduce (given example), gaspi_allreduce returns an error. If their is no barrier called before gaspi_allreduce the applications pends forever.
Either way, the state vector doesn't change.
Also, the standard says in case of an error gaspi_allrduce returns GASPI_ERROR not a GPI2 specific error code.
used branch: next
Example:
state_vec_3.cpp.txt
output (8 processes):
2 = 0
3 = 0
4 = 0
5 = 0
6 = 0
7 = 0
0 = 0
time out
0 -> healthy
1 -> healthy
2 -> healthy
3 -> healthy
4 -> healthy
5 -> healthy
6 -> healthy
7 -> healthy
The text was updated successfully, but these errors were encountered: