-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Logs miss-displaying processing of SLURM variables #115
Comments
This is what I see when doing this:
That doesn't seem so bad? Admittedly it says 'Using 0 variables', but the last line has 'Launched Slurm job'. |
I think the problem is that it doesn't specify that it's selecting 0 variables to process locally, and there might be more used in the slurm job. We could probably improve the logs in general by printing the names of all the variables that were selected, which would be particularly useful with |
Yes, the phrase 'Using 0 variables' was what generated the confusion today. |
OK, got it. I'm hoping to work on logs today (if other stuff doesn't get in the way, as it often does) |
This should now show up as:
Are we happy enough with that message to close this issue? |
As James commented, is it possible to print the names of the variables being used? both locally and in slurm. |
CC @bermudei
Related to #100 , when e.g.
reprocessing --match (slurm variable)
the logs do not indicate that the job started to run but instead display that no match was found.This might lead to the user running several jobs by mistake.
The text was updated successfully, but these errors were encountered: