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
We need to replace ${TASKORDER} with ${RSTRNT_TASKORDER} in scripts rstraint-sync-set and rstraint-sync-block to avoid sync issue between systems in a multihost recipe set.
The ${TASKODER} will be NULL in rstrnt-sync-set if you don't specify -t to overide the task/test order. So when in a mulihost recipe set with multiple tasks using same STATE, there would be sync issues in those tasks except the first one that uses the STATE.
For example, each task uses "rstraint-sync-set -t foo" and "rstrnt-sync-block -t foo" in a recipe, then there will be multiple same _foo states in a recipe where all other tasks will have sync issue except the first task.
The text was updated successfully, but these errors were encountered:
We need to replace ${TASKORDER} with ${RSTRNT_TASKORDER} in scripts rstraint-sync-set and rstraint-sync-block to avoid sync issue between systems in a multihost recipe set.
The ${TASKODER} will be NULL in rstrnt-sync-set if you don't specify -t to overide the task/test order. So when in a mulihost recipe set with multiple tasks using same STATE, there would be sync issues in those tasks except the first one that uses the STATE.
For example, each task uses "rstraint-sync-set -t foo" and "rstrnt-sync-block -t foo" in a recipe, then there will be multiple same _foo states in a recipe where all other tasks will have sync issue except the first task.
The text was updated successfully, but these errors were encountered: