Skip to content

README.md

Latest commit

 

History

History
56 lines (38 loc) · 1.95 KB

README.md

File metadata and controls

56 lines (38 loc) · 1.95 KB
Raw

MESATest

Command line tool for running the MESA test suite and uploading results to MESATestHub

I'll flesh this out later, but ideally you should install via

gem install mesa_test

Then learn about the available commands via

mesa_test help

For an individual command, call help with an argument:

mesa_test help install

Authenticating

Generate an API key for your computer on its page on MESATestHub, then run mesa_test setup and paste it when asked (or export MESATESTHUB_API_KEY). Email and password still work if you'd rather not use a key.

Letting MESATestHub choose what to test

mesa_test install_and_test best

asks MESATestHub for the commit that most needs testing, builds it, and then runs tests one at a time in the order (and modes, e.g. full inlists for [ci optional] commits) it asks for, submitting each as it finishes. To just see what it would pick:

mesa_test request_work

On a cluster, where the build and the tests are separate jobs:

mesa_test install best || exit   # exits 3 if nothing needs testing
mesa_test submit --empty         # report the build
# ...then array jobs, one per test:
mesa_test test $N

install records the run modes it chose (FPE checks, optional inlists, convergence) in the work directory's testhub.yml, so the test jobs pick them up without extra flags.

Run modes

--skip-optional / --no-skip-optional, --fpe / --no-fpe, and --converge / --no-converge control MESA's MESA_SKIP_OPTIONAL, MESA_FPE_CHECKS_ON, and MESA_TEST_SUITE_RESOLUTION_FACTOR.

  • With best: they say what this computer is willing to run when a commit asks for it. Defaults come from capabilities in your config (set by mesa_test setup).
  • Otherwise: they set the mode directly. Anything you leave unset comes from what install recorded, then from your shell.
  • FPE checks are compiled in, so they are fixed when MESA is installed.