You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The directory /gpfs/alpine/proj-shared/gen119/bsql_shared/logs_ucx_1060213 did not exist prior to launching the job.
Steps/Code to reproduce bug
Launch BlazingSQL on a sufficient number of workers to trigger the race condition, set LOG to the above directory (and make sure it doesn't exist yet), and set the following environment variables
Describe the bug
Running on 90 workers, I get the following error
The directory
/gpfs/alpine/proj-shared/gen119/bsql_shared/logs_ucx_1060213
did not exist prior to launching the job.Steps/Code to reproduce bug
Launch BlazingSQL on a sufficient number of workers to trigger the race condition, set LOG to the above directory (and make sure it doesn't exist yet), and set the following environment variables
Expected behavior
The directory should be silently created if it doesn't exist yet.
Environment details
Please run and paste the output of the
print_env.sh
script here, to gather any other relevant environment detailsAdditional context
Suspected source of the issue
in
pyblazing/apiv2/context.py
This should intercept the
FileExistsError
and then silently return (instead of usingos.path.exists
, which results in a race condition).The text was updated successfully, but these errors were encountered: