Skip to content

bpeek output sometimes not immediately available causing job checks to fail #4

@rokroskar

Description

@rokroskar

if the job output has not been synchronized yet in the temprorary output files by the scheduler, the bpeek command will fail even though the job has started -- catch this failure in the output and react appropriately

Metadata

Metadata

Assignees

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions