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

Sync issue between systems in a multihost recipe set when using rstraint-sync-set/rstraint-sync-block #305

Open
jijianwen opened this issue Nov 8, 2023 · 0 comments

Comments

@jijianwen
Copy link

jijianwen commented Nov 8, 2023

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.

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

No branches or pull requests

1 participant