You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, we use a Kubernetes Job in order to execute the test notebooks. This Job spins up a Pod, runs the pytest suite included in tests, and exits with a status that depends on the tests' outcome.
After the Job has finished, we collect its logs and report them to the user. Of course this makes for a suboptimal UX, since the user might have to wait long before they learn about the outcome of their tests.
Goal
Stream the Job logs directly to the pytest output, providing real-time insight.
The text was updated successfully, but these errors were encountered:
Currently, we use a Kubernetes Job in order to execute the test notebooks. This Job spins up a Pod, runs the
pytest
suite included intests
, and exits with a status that depends on the tests' outcome.After the Job has finished, we collect its logs and report them to the user. Of course this makes for a suboptimal UX, since the user might have to wait long before they learn about the outcome of their tests.
Goal
Stream the Job logs directly to the
pytest
output, providing real-time insight.The text was updated successfully, but these errors were encountered: