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

Non-deterministic job execution #141

Closed
henricasanova opened this issue Feb 12, 2020 · 0 comments
Closed

Non-deterministic job execution #141

henricasanova opened this issue Feb 12, 2020 · 0 comments
Assignees
Labels
Milestone

Comments

@henricasanova
Copy link
Contributor

Because when creating a standard job the pre-file copies, post-file copies, and post file deletions are in sets of items, and the order depends on the memory allocation. So depending on the allocation (and perhaps from run to run), a job execution can differ, which is not great.

The idea would be to modify the API and replace these sets by vectors, so that there is a consistent order.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants