TileDB-Py
TileDB-Py copied to clipboard
`test_bytes_{numpy,df}` produces inconsistent results [Nightly GitHub Actions Build Fail on Sat, June 25th 2022]
See run for more details: https://github.com/TileDB-Inc/TileDB-Py/actions/runs/2559515605
https://github.com/TileDB-Inc/TileDB-Py/runs/7848372619?check_suite_focus=true
After adding some debug info, I'm about 98% sure this is https://github.com/HypothesisWorks/hypothesis/issues/2108
or https://github.com/HypothesisWorks/hypothesis/issues/3369
or similar.
Timing the test itself: the function body in the failing instance completely very quickly. So, barring something extremely spooky, the only place the time could be hiding is in the hypothesis setup for the function (draws are supposed to be excluded but the issues above demonstrate there still appear to be corner cases).
2022-08-31T16:37:36.8077280Z E ==== Python Stats ====
2022-08-31T16:37:36.8077470Z E
2022-08-31T16:37:36.8077690Z E py.core_read_query_initial_submit_time : 0.00177066
2022-08-31T16:37:36.8077970Z E py.core_read_query_total_time : 0.00264233
2022-08-31T16:37:36.8078220Z E py.getitem_time : 0.00834703
2022-08-31T16:37:36.8078820Z E py.getitem_time.add_ranges : 2.88486e-05
2022-08-31T16:37:36.8079110Z E py.getitem_time.buffer_conversion_time : 0.000364065
2022-08-31T16:37:36.8079400Z E py.getitem_time.pandas_index_update_time : 0.00194836
2022-08-31T16:37:36.8079650Z E py.query_retries_count : 0
2022-08-31T16:37:36.8079840Z E
2022-08-31T16:37:36.8080160Z E test_bytes_df time: -0.034787893295288086
https://dev.azure.com/TileDB-Inc/CI/_build/results?buildId=26098&view=logs&jobId=35cef1e0-4eee-51ec-0f39-f0ea4bef66f4&j=35cef1e0-4eee-51ec-0f39-f0ea4bef66f4&t=72073061-58b7-574e-3733-fc43fc034d6c