Skip to content

Feature: add concore run to start a built study from the CLI #682

Open

Description

@yadavchiragg

Problem: the CLI covers init, build, validate, inspect, status, watch and stop, but starting a study still means cd-ing into the output folder and running ./run (or run.bat) by hand. There is also no clean way to run a study from a script or CI and know when it finished.

Proposal: a concore run <study_dir> command with:

  • --build to run the study's build script first,
  • --wait to wait until every node exits, using the pid files that POSIX/macOS run scripts already write; Ctrl+C stops only that study (not every concore process like concore stop),
  • --timeout <seconds> (with --wait) to stop a study that runs too long,
  • exit codes 0 / 124 (timeout) / 130 (interrupted) / the failing script's exit code.

Docker and Windows builds do not record pids, so there --wait only starts the study and prints a warning. --wait reports when nodes exit, not whether they succeeded.

I have a working implementation with tests and docs, which I'm opening as a PR together with this issue. I'm happy to change the design, rename options, or close it if you'd prefer a different direction.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions