-
Notifications
You must be signed in to change notification settings - Fork 93
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
Sporadic failures of Parquet segarray_write
test with gasnet
#2268
Comments
Had conversation with @bmcdonald3 documenting here for awareness. @pierce314159 and I were unable to replicate the issue. We will continue to monitor this to hopefully determine what is causing it. |
I believe I located the issue causing this. While working Issue #2493, I discovered that there is an issue when a locale has no values being written. In |
I corrected the first layer here, but it appears that there are more issues occurring that are related. |
Through testing I am able to replicate issue with 3 locales running this test. However, based on the error I am seeing it appears to be an allocation error. I am working to track this down, but it is proving rather tricky to locate. |
…st with gasnet (#2534) * Final correction for issue. Error is resolved, code still requires cleanup. * Final updates to prevent memory allocation errors. * Clean up * Removing prints from test. Adding comments for early outs. * Removing prints
Describe the bug
This failure:
popped up on nightly testing. I am able to reproduce this issue on 16 locales, but it appears to only show up about once in every 100 trials.
To Reproduce
pytest.ini
to run with 4 or more locales (not sure if this is necessary, but I couldn't reproduce with 2 locales, but could with 16; fairly confident anything 4 or over would work based on the type of failure and what we've seen here in the past)test_segarray_write
to run a large number of trials (I seem to catch this about 1 in every 100 runs)python3 -m pytest tests/parquet_test.py -k "test_segarray_write"
to run just this testThe text was updated successfully, but these errors were encountered: