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
While fixing the heat CB pipeline, it became clear that some random time, the process opened by perun to monitor the hardware "does not run", meaning that the process is started, and is marked as alive, but the function passed to it as an argument never start running.
This only happened when the decomposition benchmarks were activated, and only 1 in 10 times, approximately. Mostly when running the benchmarks on CPU, but it happened once on GPU's.
Partially handled by #151, where the perun will exit gracefully if it detects this happening.
The text was updated successfully, but these errors were encountered:
While fixing the heat CB pipeline, it became clear that some random time, the process opened by perun to monitor the hardware "does not run", meaning that the process is started, and is marked as alive, but the function passed to it as an argument never start running.
This only happened when the decomposition benchmarks were activated, and only 1 in 10 times, approximately. Mostly when running the benchmarks on CPU, but it happened once on GPU's.
Partially handled by #151, where the perun will exit gracefully if it detects this happening.
The text was updated successfully, but these errors were encountered: