-
Notifications
You must be signed in to change notification settings - Fork 10
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
BUG -4294967296 #14
Comments
Do you have the possibility to share/link to your test data so that I can see if I can reproduce it? |
I recreated the |
Thank you! downloaded the data and ran with your command on my MacBook. I could not reproduce the bug. I ran both with head of master and head of develop (commit c0ac67c and commit 8313e9b, respectively) This is my call:
This is my output log of uLTRA:
|
My version of python (that executes uLTRA) is Python 3.8.2. |
I'm not surprised, it seems to be very random :/ |
ouch.. I wonder if it is because of slaMEM that uLTRA fails (as this is a package I have no control/understanding about). If |
From my point of view, it's not a big deal. |
I see :) let’s see if this happens for others and I'll revisit then. |
Hi Kristoffer,
During nf-core/isoseq test jobs, I randomly have a bug:
Here is the command used:
Re-running is enough to get the job done.
I never noticed this when I ran it locally.
The text was updated successfully, but these errors were encountered: