-
Notifications
You must be signed in to change notification settings - Fork 2
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
Nightly feedstock build failed #151
Comments
Nightly feedstock build failure for TileDB-Py%20Feedstock%20Testing at https://dev.azure.com/TileDB-Inc/CI/_build?definitionId=5&_a=summary |
1 similar comment
Nightly feedstock build failure for TileDB-Py%20Feedstock%20Testing at https://dev.azure.com/TileDB-Inc/CI/_build?definitionId=5&_a=summary |
Starting with the nightly build on Friday, Nov 15th, there is a test failure only for the linux-aarch64 builds: =========================== short test summary info ============================
FAILED tiledb/tests/test_schema_evolution.py::test_schema_evolution_drop_fixed_attribute_and_add_back_as_var_sized - AssertionError:
Arrays are not equal
Mismatched elements: 10 / 10 (100%)
ACTUAL: array([b'', b'', b'', b'', b'', b'', b'', b'', b'', b''], dtype=object)
DESIRED: array([b'\x80', b'\x80', b'\x80', b'\x80', b'\x80', b'\x80', b'\x80',
b'\x80', b'\x80', b'\x80'], dtype='|S1')
== 1 failed, 526 passed, 2 skipped, 7 xfailed, 1 xpassed in 766.48s (0:12:46) ==
WARNING: Tests failed for tiledb-py-0.32.5.2024_11_15-py39h697c32b_0.conda - moving package to /home/conda/feedstock_root/build_artifacts/broken |
The failing test was added on Friday in TileDB-Inc/TileDB-Py#2083. @kounelisagis could you please investigate why this new test only fails on linux-aarch64? |
Strange that this check is OS-dependent. Does this mean that the data in the TileDB array differ depending on the OS, or is it just a representation issue? I believe it’s the latter. In any case, I don’t think this is a deeper issue; it seems to be a matter of modifying the assertion. I will investigate further tomorrow and make a fix in a PR. cc: @bekadavis9 |
Nightly feedstock build failure for TileDB-Py%20Feedstock%20Testing at https://dev.azure.com/TileDB-Inc/CI/_build?definitionId=5&_a=summary |
All builds fail because of this: TileDB-Inc/TileDB-Py#2111 (comment) |
This test gets skipped in TileDB-Py CI. From a quick look the behavior exhibited in |
Nightly feedstock build failure for TileDB-Py%20Feedstock%20Testing at https://dev.azure.com/TileDB-Inc/CI/_build?definitionId=5&_a=summary |
Now we're back to only the linux-aarch64 test failures that originally opened this Issue. Though unclear if the deprecated functions problem has been fixed or not, since we haven't yet merged #152 to always remove the deprecated functions. |
Nightly feedstock build failure for TileDB-Py%20Feedstock%20Testing at https://dev.azure.com/TileDB-Inc/CI/_build?definitionId=5&_a=summary |
1 similar comment
Nightly feedstock build failure for TileDB-Py%20Feedstock%20Testing at https://dev.azure.com/TileDB-Inc/CI/_build?definitionId=5&_a=summary |
Nightly feedstock build failure for TileDB-Py%20Feedstock%20Testing at https://dev.azure.com/TileDB-Inc/CI/_build?definitionId=5&_a=summary |
2 similar comments
Nightly feedstock build failure for TileDB-Py%20Feedstock%20Testing at https://dev.azure.com/TileDB-Inc/CI/_build?definitionId=5&_a=summary |
Nightly feedstock build failure for TileDB-Py%20Feedstock%20Testing at https://dev.azure.com/TileDB-Inc/CI/_build?definitionId=5&_a=summary |
@kounelisagis the linux-aarch64 tiledb-py-feedstock builds continue to fail the test |
Nightly feedstock build failure for TileDB-Py%20Feedstock%20Testing at https://dev.azure.com/TileDB-Inc/CI/_build?definitionId=5&_a=summary |
3 similar comments
Nightly feedstock build failure for TileDB-Py%20Feedstock%20Testing at https://dev.azure.com/TileDB-Inc/CI/_build?definitionId=5&_a=summary |
Nightly feedstock build failure for TileDB-Py%20Feedstock%20Testing at https://dev.azure.com/TileDB-Inc/CI/_build?definitionId=5&_a=summary |
Nightly feedstock build failure for TileDB-Py%20Feedstock%20Testing at https://dev.azure.com/TileDB-Inc/CI/_build?definitionId=5&_a=summary |
Nightly feedstock build failure for TileDB-Py%20Feedstock%20Testing at https://dev.azure.com/TileDB-Inc/CI/_build?definitionId=5&_a=summary |
2 similar comments
Nightly feedstock build failure for TileDB-Py%20Feedstock%20Testing at https://dev.azure.com/TileDB-Inc/CI/_build?definitionId=5&_a=summary |
Nightly feedstock build failure for TileDB-Py%20Feedstock%20Testing at https://dev.azure.com/TileDB-Inc/CI/_build?definitionId=5&_a=summary |
Nightly feedstock build failure for TileDB-Py%20Feedstock%20Testing at https://dev.azure.com/TileDB-Inc/CI/_build?definitionId=5&_a=summary |
There appears to be multiple issues:
|
The py313-specific solver errors were indeed due to #154. I didn't realize that the official name doesn't end in |
Also figured out the source of the |
Nightly feedstock build failure for TileDB-Py%20Feedstock%20Testing at https://dev.azure.com/TileDB-Inc/CI/_build?definitionId=5&_a=summary |
Nightlies are still a mess:
|
Nightly feedstock build failure for TileDB-Py%20Feedstock%20Testing at https://dev.azure.com/TileDB-Inc/CI/_build?definitionId=5&_a=summary |
After adding back the py312 build (#156), there are at least a reduced number of problems. Current build status:
|
Nightly feedstock build failure for TileDB-Py%20Feedstock%20Testing at https://dev.azure.com/TileDB-Inc/CI/_build?definitionId=5&_a=summary |
5 similar comments
Nightly feedstock build failure for TileDB-Py%20Feedstock%20Testing at https://dev.azure.com/TileDB-Inc/CI/_build?definitionId=5&_a=summary |
Nightly feedstock build failure for TileDB-Py%20Feedstock%20Testing at https://dev.azure.com/TileDB-Inc/CI/_build?definitionId=5&_a=summary |
Nightly feedstock build failure for TileDB-Py%20Feedstock%20Testing at https://dev.azure.com/TileDB-Inc/CI/_build?definitionId=5&_a=summary |
Nightly feedstock build failure for TileDB-Py%20Feedstock%20Testing at https://dev.azure.com/TileDB-Inc/CI/_build?definitionId=5&_a=summary |
Nightly feedstock build failure for TileDB-Py%20Feedstock%20Testing at https://dev.azure.com/TileDB-Inc/CI/_build?definitionId=5&_a=summary |
Nightly feedstock build failure for TileDB-Py%20Feedstock%20Testing at https://dev.azure.com/TileDB-Inc/CI/_build?definitionId=5&_a=summary |
Frustratingly the new failures from last night are because conda-build is now using the pin from - package tiledb-2.26.2-hedb9d39_0 is excluded by strict repo priority |
Nightly feedstock build failure for TileDB-Py%20Feedstock%20Testing at https://dev.azure.com/TileDB-Inc/CI/_build?definitionId=5&_a=summary |
I fixed this problem this morning with #158 To test it, I manually triggered a tiledb-py job from main, which then pushed to tiledb-py-feedstock (TileDB-Inc/tiledb-py-feedstock@afa8182). The builds are installing the nightly tiledb conda binary 2.27.0.2024_12_12. |
Nightly feedstock build failure for tiledbfeedstock_CI at https://dev.azure.com/TileDB-Inc/CI/_build?definitionId=4&_a=summary |
Nightly feedstock build failure for TileDB-Py%20Feedstock%20Testing at https://dev.azure.com/TileDB-Inc/CI/_build?definitionId=5&_a=summary |
Strange. The new tiledb-feedstock failures for osx-64 and win-64 were both download failures. And the centralized nightlies also suffered from download failures (TileDB-Inc/centralized-tiledb-nightlies#30). Is some central service experience a degradation? |
I'm closing this Issue since it has gotten too long and covered too many different errors. Note that we've started getting passing linux-aarch64 builds only because I skipped the failing test in conda-forge/tiledb-py-feedstock@b820944 in order to release TileDB-Py 0.33.0 (conda-forge/tiledb-py-feedstock#249). The hope is to fix this in a future 0.33.1 release. |
Nightly feedstock build failure for TileDB-Py%20Feedstock%20Testing at https://dev.azure.com/TileDB-Inc/CI/_build?definitionId=5&_a=summary
https://app.shortcut.com/tiledb-inc/story/59851
The text was updated successfully, but these errors were encountered: