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
{{ message }}
This repository has been archived by the owner on Aug 15, 2024. It is now read-only.
When the last psom job fails, the pipeline execution sometimes return success du to a racing condition related to the garbage collector.
The best solution it seems it to create a PIPE.exit_code when the PIPE.lock is deleted. (but what should be the ret status when the PIPE.lock is manually removed? "2", maybe "128" ?
To flush the nfs cache in at directory, to most straightforward method is to do "ls /dir/to/flush/nfs"
The text was updated successfully, but these errors were encountered:
When the last psom job fails, the pipeline execution sometimes return success du to a racing condition related to the garbage collector.
The best solution it seems it to create a PIPE.exit_code when the PIPE.lock is deleted. (but what should be the ret status when the PIPE.lock is manually removed? "2", maybe "128" ?
To flush the nfs cache in at directory, to most straightforward method is to do "ls /dir/to/flush/nfs"
The text was updated successfully, but these errors were encountered: