documentation
sign in→

project test

Run the project locally to verify it works before uploading.

squadron project test [dir] [-e KEY=val] [-r | -c] [--skip-limits]

Arguments:

  • dir: Project directory. If omitted, the CLI searches up from the current directory through parent directories for the nearest project manifest.

Options:

  • -e, --env: Set an environment variable (repeatable). These are merged with the env vars in the manifest's [job] section; if the same key appears in both, the -e value wins.
  • -r, --rebuild: Re-run the build script on top of the previous build image, even if nothing changed.
  • -c, --clean: Discard all cached build layers and start from a fresh base image.
  • --skip-limits: Disable memory and PID limits on the container. By default the container gets exactly the memory its manifest asks for, plus a cap of 4096 processes, the same treatment a job gets on the daemon. Passing this flag lets the container use as much of your machine as it wants, which is useful for finding out how much a job really needs, but it means a local run no longer tells you whether the job will survive on the fleet. /dev/shm stays sized to memory either way.

--rebuild and --clean cannot be used together.

Output location:

Artifacts are saved to .squadron/tests/<YY-MM-DD_HH-MM-SS>/ using your local time.

Examples:

squadron project test
squadron project test -e MODEL=resnet -e EPOCHS=5
squadron project test --skip-limits
squadron project test --clean