-
Notifications
You must be signed in to change notification settings - Fork 61
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
Parralelization fail #9
Comments
Also the parrelization fail warnings are 13 seconds apart but cite timeout limits that are 1200/2400/4800 seconds apart? |
Usually this is something wrong with the input. Try adding method="serial" to the wb initializer. This will run calls serially without multiprocessing, so you will see where the code crashes. The fail warnings come as soon as the parallelization fails. The timeout limits are doubled on each attempt. |
thanks that helped me figure it out!
…On Sun, Feb 11, 2018 at 3:08 AM anttttti ***@***.***> wrote:
Usually this is something wrong with the input. Try adding method="serial"
to the wb initializer. This will run call serially without multiprocessing,
so you will see where the code crashes.
The fail warnings come as soon as the parallelization fails. The timeout
limits are doubled on each attempt.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#9 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFw9Yd8-eym89CbnCM2o4h5sxaOz12hKks5tTp_zgaJpZM4SBKVB>
.
|
Any idea how to fix? Has just started happening without changing code. Thought this was from running too many kernels at once but even if I run one kernel I get this error....
From kaggle script environment
The text was updated successfully, but these errors were encountered: