Create mock HPC system to test deferred execution#55
Merged
Conversation
The system just emulates deferred queue separate from SANE orchestration and handling very basic dependency staging. The two directories are used as trackers for queuing and completion. Job id is assigned based on order of arrival and is used to write out all tracked information. This meshes with the expectations of the `HPCHost` within SANE workflows.
Use mock HPC system to create a very rudimentary `HPCHost` class. It does not do any error checking or resource management and instead focuses on behavior of deferred execution.
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Create a very simple "HPC" system focused on behavior of dependency resolution and separate execution context from the
Orchestrator. The system still has enough capability to properly work with SANE and provide job IDs, state and status values, and execute Actions. It DOES NOT handle resource management.The test is a very simple execution of A->B actions. More tests can be developed later to test correctness of HPC-like behavior beyond dry-runs.