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

CI testbed #144

Open
3 tasks
dfuchsgruber opened this issue Aug 30, 2024 · 0 comments
Open
3 tasks

CI testbed #144

dfuchsgruber opened this issue Aug 30, 2024 · 0 comments

Comments

@dfuchsgruber
Copy link
Contributor

dfuchsgruber commented Aug 30, 2024

This issue serves to track CI test cases we should include to seml.

  • Source Code Stashing: Test that the experiment actually uses the stashed source code. Proposal: Add experiments, then change the source code to include a raise RuntimeError(...) statement, then run the code and check that all experiments are COMPLETED eventually.
  • Test that experiments_per_job actually runs code in parallel: Devise a python script with wait times as dummy and ensure that they start roughly synchronised by checking their outputs.
  • Ensure that the src layout is correctly supported by source code stashing (how?)

Add further test cases when you encounter weird behaviour that needs to be fixed.

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