Open ccraddock opened 3 years ago
not only does this error not generate a crashfile, it doesn't show up in the pypeline.log file. So you wouldn't see it unless you are watching CPAC's output in the terminal.i have time this week to discuss with y'all if that will help.
Describe the bug There are certain exceptions that occur during QC functions that do not result in crashfiles being generated and cause the parent process to hang.
Here is an example of one such exception:
These nodes appear to hang in the scheduler and once enough of them accumulate the pipeline reaches a standstill. My pipeline has been stuck with the following message for over an hour:
To Reproduce Steps to reproduce the behavior:
Expected behavior The exception should result in a crashfile being generated and should be cleared from the scheduler.
Versions
Additional context
config_files.zip