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

[tests] infrastructure for automatic pytest of babs-submit and babs-status #113

Open
zhao-cy opened this issue Jul 10, 2023 · 0 comments
Open

Comments

@zhao-cy
Copy link
Collaborator

zhao-cy commented Jul 10, 2023

Currently we are trying to figure out feasible infrastructure for testing out babs-submit and babs-status automatically. These two programs require interactions w/ the clusters. We hope to be able to run pytest of babs-submit and babs-status in an automatical and controlled way and even on CircleCI.

Current ways we could think of:

  1. emulator of cluster job scheduler system.
  • Challenge 1: find one for SGE and one for Slurm.
  • Challenge 2: install everything, including this emulator, and also singularity, python, datalad, etc in one Docker image, so that we can test it on CircleCI.
  • Challenge 3: how to control this emulator to get the job status we want?
  1. Just to use current real clusters.
  • Challenge 1: how to control our clusters to get the job status we want?
  1. job scheduler "replier": a simple Python package that returns printed messages we usually get from qstat (SGE) or squeue (Slurm) when checking job status.
  • Challenge 1: we implement it (it might turn out to be not that complex!)
  • Advantage 1: We have full control on the messages it returns / job statuses
  • Advantage 2: We can design different versions of SGE or Slurm clusters, to add support for a specific cluster which has specific returned messages
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