Open stemangiola opened 3 years ago
Stefano, do you any logs or messages before that? Do you know which rule is failing with that message?
As I see it from the makeflow executable, that could only happen from a task that already finished. The code 132 in general (in linux, independent of makeflow) means that the task tried to execute an illegal instruction. Could it be that the task tried to execute in a node that was not correctly setup, and that result is now recoded in the makeflow's log? Do you get the same messages when starting the workflow from scratch?
Thanks,
I have printed standard error (I will do that next time first sorry)
caught illegal operation address 0x2b437ff1192d, cause 'illegal operand'
Something must have changed in the server. Thanks!
Hello,
I don't remember what is "failed with exit code 132".
It happens straight away, with the resources 60Gb 12cores on SLURM, those jobs before were working. The script is working interactively.