-
Notifications
You must be signed in to change notification settings - Fork 241
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
RuntimeError: Cannot store message argument of type <enum 'BatchJobExitReason'>: BatchJobExitReason.MEMLIMIT #4321
Comments
I think the problem is here: Lines 206 to 207 in 332eeed
|
This should fix #4321. It could probably use a test.
* Allow for subclasses of base types in messages This should fix #4321. It could probably use a test. * Add a test for enums in bus log files * Actually start tuple * Fix test to actually write to file * Fix enum to be IntEnum so it isinstance int
Thank you @adamnovak ! As far as you know, should Cactus be compatible with the master branch of toil ? |
I believe it should; we have a CI test in Toil that does an integration test against Cactus, so we know when we make a breaking change, and I don't recall any since the last release. |
Super, thanks, I'll give it a try |
Hello,
I'm running Cactus on a LSF farm, and a bunch of jobs consumed more memory than they had requested, and got killed by LSF ("MEMLIMIT")
This resulted in Cactus/toil failing with this error:
Job ID 9986865 was not the only one to fail with error 130 at the same time, but it's the last one in the log before the stack-trace. Here is its report:
I'm using the official Docker image of Cactus v2.4.0, converted to Singularity. This is toil 5.8.0, according to their changelog.
┆Issue is synchronized with this Jira Story
┆Issue Number: TOIL-1264
The text was updated successfully, but these errors were encountered: