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
The runner should check if the workers were launched successfully. In the current version, L2L does not notice if the worker failed immediately, e.g. due to an illegal combination in the srun command. The user will end up with a confusing error message which does not reflect the real reason behind the failure.
This is how I checked the status of the workers:
process=subprocess.Popen(...) # starting srun in the runner# ...exitcode=process.poll()
ifexitcodeisnotNone: # None would imply that it's runninglogger.info(str(process.stdout.read()))
logger.info(str(process.stderr.read()))
The text was updated successfully, but these errors were encountered:
The runner should check if the workers were launched successfully. In the current version, L2L does not notice if the worker failed immediately, e.g. due to an illegal combination in the srun command. The user will end up with a confusing error message which does not reflect the real reason behind the failure.
This is how I checked the status of the workers:
The text was updated successfully, but these errors were encountered: