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 kubernetes and docker and parsl workflow currently outputs logging statements to the terminal that communicate a lot of information, including the number active tasks, active slots, connected workers, etc . These statements include DEBUG level logging, so this results in a constant stream of output that is hard to search through. An easy solution to this would be to configure parsl to output these logging statements to a file instead. Parsl has this functionality, like using parsl.set_file_logger() or setting up logging settings like in this stack overflow post. Note that this logging is different than the viz workflow logging, which is already set up to write to a log.log file.
The text was updated successfully, but these errors were encountered:
The kubernetes and docker and parsl workflow currently outputs logging statements to the terminal that communicate a lot of information, including the number active tasks, active slots, connected workers, etc . These statements include DEBUG level logging, so this results in a constant stream of output that is hard to search through. An easy solution to this would be to configure parsl to output these logging statements to a file instead. Parsl has this functionality, like using parsl.set_file_logger() or setting up logging settings like in this stack overflow post. Note that this logging is different than the viz workflow logging, which is already set up to write to a
log.log
file.The text was updated successfully, but these errors were encountered: