Nighly feedstock build failed about conda-forge-nightly-controller

[github-actions]

Nightly feedstock build failure for TileDB-Py%20Feedstock%20Testing at https://dev.azure.com/TileDB-Inc/CI/_build?definitionId=5&_a=summary

[jdblischak]

The failure yesterday was due to a spurious test failure on an osx-64 variant. We get this test failure quite often. My understanding is that the problem is due to the fact that the first iteration fails to finish within the 200ms deadline. A workaround I found is to increase the deadline eg @hypothesis.settings(deadline=300)

=========================== short test summary info ============================
FAILED tiledb/tests/test_multi_index-hp.py::TestMultiIndexPropertySparse::test_multi_index_two_way_query - hypothesis.errors.Flaky: Hypothesis test_multi_index_two_way_query(self=<tests.test_multi_index-hp.TestMultiIndexPropertySparse object at 0x13395d930>, order='U', ranges=[(0, 1)], sparse_array_1d='/var/folders/24/8k48jl6d249_n_qfxwsl6xvm0000gn/T/tiledb-disktestcasevw08m_fd/tmpf1tc5bb7') produces unreliable results: Falsified on the first call but did not on a subsequent one
Falsifying example: test_multi_index_two_way_query(
    self=<tests.test_multi_index-hp.TestMultiIndexPropertySparse object at 0x13395d930>,

You can reproduce this example by temporarily adding @reproduce_failure('6.97.1', b'AAIBAQAAAAABAA==') as a decorator on your test case
FAILED tiledb/tests/test_multi_index-hp.py::TestMultiIndexPropertySparse::test_multi_index_inputs - hypothesis.errors.Flaky: Hypothesis test_multi_index_inputs(self=<tests.test_multi_index-hp.TestMultiIndexPropertySparse object at 0x13395f8e0>, sparse_array_1d='/var/folders/24/8k48jl6d249_n_qfxwsl6xvm0000gn/T/tiledb-disktestcasevw08m_fd/tmpf1tc5bb7', ind=([-1],)) produces unreliable results: Falsified on the first call but did not on a subsequent one
Falsifying example: test_multi_index_inputs(
    self=<tests.test_multi_index-hp.TestMultiIndexPropertySparse object at 0x13395f8e0>,
    sparse_array_1d='/var/folders/24/8k48jl6d249_n_qfxwsl6xvm0000gn/T/tiledb-disktestcasevw08m_fd/tmpf1tc5bb7',
    ind=([-1],),
)
Unreliable test timings! On an initial run, this test took 266.46ms, which exceeded the deadline of 200.00ms, but on a subsequent run it took 16.43 ms, which did not. If you expect this sort of variability in your test timings, consider turning deadlines off for this test by setting deadline=None.

You can reproduce this example by temporarily adding @reproduce_failure('6.97.1', b'AAICAAEAAwA=') as a decorator on your test case
== 2 failed, 504 passed, 1 skipped, 7 xfailed, 1 xpassed in 520.18s (0:08:40) ==
WARNING: Tests failed for tiledb-py-0.25.1.dev2.2024_01_27-py310h6435cfe_0.conda - moving package to /Users/runner/miniforge3/conda-bld/broken
TESTS FAILED: tiledb-py-0.25.1.dev2.2024_01_27-py310h6435cfe_0.conda

[jdblischak]

The failure today was simply a connection timeout when setting up the build for an osx-arm64 variant

[jdblischak]

I sent a PR upstream to remove the arbitrary deadline for the flaky tests TileDB-Inc/TileDB-Py#1894

[jdblischak]

Both passed on restart