The nightly build job failed on Sunday (2024-09-29)

[github-actions]

The nightly build job failed on Sunday (2024-09-29) in run 11089884523

[github-actions]

The nightly build with earliest supported numpy job failed on Sunday (2024-09-29) in run 11089884523

[kounelisagis]

Both failed jobs were related to test_open_with_timestamp[False], which is known to fail frequently.

[github-actions]

The nightly build job failed on Friday (2024-10-04) in run 11174316176

[github-actions]

The nightly build job failed on Friday (2024-10-04) in run 11174316176

[github-actions]

The nightly build with earliest supported numpy job failed on Friday (2024-10-04) in run 11174316176

[github-actions]

The nightly build job failed on Saturday (2024-10-05) in run 11190619867

[github-actions]

The nightly build job failed on Saturday (2024-10-05) in run 11190619867

[github-actions]

The nightly build with earliest supported numpy job failed on Saturday (2024-10-05) in run 11190619867

[github-actions]

The nightly build job failed on Sunday (2024-10-06) in run 11199130785

[github-actions]

The nightly build job failed on Sunday (2024-10-06) in run 11199130785

[github-actions]

The nightly build with earliest supported numpy job failed on Sunday (2024-10-06) in run 11199130785

[github-actions]

The nightly build job failed on Monday (2024-10-07) in run 11209033615

[github-actions]

The nightly build job failed on Monday (2024-10-07) in run 11209033615

[github-actions]

The nightly build with earliest supported numpy job failed on Monday (2024-10-07) in run 11209033615

[github-actions]

The nightly build job failed on Tuesday (2024-10-08) in run 11228931833

[github-actions]

The nightly build job failed on Tuesday (2024-10-08) in run 11228931833

[github-actions]

The nightly build with earliest supported numpy job failed on Tuesday (2024-10-08) in run 11228931833

[github-actions]

The nightly build job failed on Wednesday (2024-10-09) in run 11248595774

[github-actions]

The nightly build job failed on Wednesday (2024-10-09) in run 11248595774

[github-actions]

The nightly build with earliest supported numpy job failed on Wednesday (2024-10-09) in run 11248595774

[github-actions]

The nightly build job failed on Thursday (2024-10-10) in run 11267784095

[github-actions]

The nightly build job failed on Thursday (2024-10-10) in run 11267784095

[github-actions]

The nightly build with earliest supported numpy job failed on Thursday (2024-10-10) in run 11267784095

[github-actions]

The nightly build job failed on Monday (2024-10-14) in run 11321329322

[github-actions]

The nightly build with earliest supported numpy job failed on Tuesday (2024-10-15) in run 11339636658

[github-actions]

The nightly build with earliest supported numpy job failed on Thursday (2024-10-17) in run 11378701272

[kounelisagis]

Except for errors coming from CloudTest::test_save_and_open_array_from_cloud and DenseArrayTest::test_open_with_timestamp[False] which were recently fixed, we are getting some random errors regarding:

• test_fork_ctx.py::test_warning_multiprocessing_with_default_ctx
• test_fork_ctx.py::test_warning_multiprocessing_with_ctx
• test_fork_ctx.py::test_no_warning_multiprocessing_without_ctx

An example is: https://github.com/TileDB-Inc/TileDB-Py/actions/runs/11378701272/job/31654942639

and some from TestMultiIndexPropertySparse.test_multi_index_two_way_query: https://github.com/TileDB-Inc/TileDB-Py/actions/runs/11339636658/job/31534761210

I will investigate this.

[ihnorton]

and some from TestMultiIndexPropertySparse.test_multi_index_two_way_query: https://github.com/TileDB-Inc/TileDB-Py/actions/runs/11339636658/job/31534761210

this one and https://github.com/TileDB-Inc/TileDB-Py/actions/runs/11321329322/job/31480234054 look like a core issue?

For the context ones, I think we need to move them to a subprocess to make sure no other tiledb operations have happened.

[kounelisagis]

this one and https://github.com/TileDB-Inc/TileDB-Py/actions/runs/11321329322/job/31480234054 look like a core issue?

For the context ones, I think we need to move them to a subprocess to make sure no other tiledb operations have happened.

https://app.shortcut.com/tiledb-inc/story/57975/move-tests-of-test-fork-ctx-py-to-a-subprocess-to-make-sure-no-other-tiledb-operations-have-happened

[github-actions]

The nightly build with earliest supported numpy job failed on Friday (2024-10-18) in run 11397798114

[github-actions]

The nightly build job failed on Monday (2024-10-21) in run 11433574610

[github-actions]

The nightly build with earliest supported numpy job failed on Tuesday (2024-10-22) in run 11453608764

[github-actions]

The nightly build with earliest supported numpy job failed on Saturday (2024-10-26) in run 11529122363