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
On Bebop, I think I am seeing cases where the output files indicate the job is done, but a short job.wait() is returning None, indicating that a final state has not yet been reached. Could this mean that job.wait() is caching an old scheduler status?
Yes, it is possible. The queue is not polled continuously, so it's entirely possible to have a delay between when the job finishes and when the status is updated.
The queue_polling_interval property in the executor config allows you to adjust the frequency with which the job status is updated.
Activity
hategan commentedon Mar 10, 2023
Let me guess: the
Nonestatus is in a different process than the one where the job was launched.It's because the status hasn't been updated yet.
j-woz commentedon Mar 10, 2023
This is the same Python process:
https://github.com/swift-lang/swift-t/blob/7186e7ffeeb358b22d08bc86371d815f5cd74948/turbine/code/scripts/submit/psij/turbine2psij.py#L189
hategan commentedon Mar 10, 2023
My bad. Sorry.
Yes, it is possible. The queue is not polled continuously, so it's entirely possible to have a delay between when the job finishes and when the status is updated.
The queue_polling_interval property in the executor config allows you to adjust the frequency with which the job status is updated.
j-woz commentedon Mar 10, 2023
Using queue_polling_interval works, PSI/J only returns None when not given enough time to poll.