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
When the user works with a job (reads logs, attaches to it, etc) which is finished for some reasons, neuro just stops, without any indication of the reason of job's termination. If it is an exception in the Python code, there is a chance to see a traceback in the logs or the attach output, but if it was cancelled or terminated by the OOM Killer, it just stops. You need to use neuro status to get details.
When the user works with a job (reads logs, attaches to it, etc) which is finished for some reasons,
neuro
just stops, without any indication of the reason of job's termination. If it is an exception in the Python code, there is a chance to see a traceback in the logs or the attach output, but if it was cancelled or terminated by the OOM Killer, it just stops. You need to useneuro status
to get details.We need to print details of the job termination, at least when it was failed or cancelled.
neuro run
neuro logs
neuro attach
neuro exec
neuro port-forward
The text was updated successfully, but these errors were encountered: