Skip to content
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

failed with exit code 132 #43

Open
stemangiola opened this issue Apr 14, 2021 · 2 comments
Open

failed with exit code 132 #43

stemangiola opened this issue Apr 14, 2021 · 2 comments

Comments

@stemangiola
Copy link

stemangiola commented Apr 14, 2021

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.

@btovar
Copy link
Member

btovar commented Apr 14, 2021

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?

@stemangiola
Copy link
Author

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants