Skip to content

feat(console): show running model batches - #6102

Open
Vamsi-klu wants to merge 1 commit into
SQLMesh:mainfrom
Vamsi-klu:feat/5904-running-batch-output
Open

Vamsi-klu wants to merge 1 commit into
SQLMesh:mainfrom
Vamsi-klu:feat/5904-running-batch-output

Conversation

@Vamsi-klu

Copy link
Copy Markdown

Description

Print a durable Running row when each model evaluation batch starts, using the same aligned batch, model, interval, and status columns as completion output. This keeps long-running batches visible in CI, cron, and other captured logs.

The change adds a backward-compatible per-batch console hook, preserves existing console implementations and audit-only behavior, and reports terminal Failed and zero-duration states correctly.

Fixes #5904

Test Plan

  • make fast-test
    • 2,636 passed, 4 skipped
    • 5 isolated tests passed
    • 1 registry-isolation test passed
    • 161 dialect-isolated tests passed
  • .venv/bin/pytest -q tests/core/test_console.py tests/core/test_scheduler.py — 37 passed
  • .venv/bin/pytest -q tests/cli/test_cli.py::test_run_dev — 2 passed
  • Targeted Ruff, Ruff format, and Mypy checks for all changed files — passed

Checklist

  • I have run make style and fixed any issues
  • I have added tests for my changes (if applicable)
  • All existing tests pass (make fast-test)
  • My commits are signed off (git commit -s) per the DCO

Signed-off-by: Vamsi-klu <nrvamsi13@gmail.com>
@Vamsi-klu

Copy link
Copy Markdown
Author

@treysp @izeigerman — could you review this? It touches console evaluation progress and scheduler batch lifecycle paths you have substantial recent ownership of.

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

Successfully merging this pull request may close these issues.

Feature Request(CLI): print "Running" batch line when model evaluation starts (not only on completion)

1 participant