Skip to content
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

Closed
github-actions bot opened this issue Nov 16, 2024 · 47 comments
Closed

Nightly feedstock build failed #151

github-actions bot opened this issue Nov 16, 2024 · 47 comments

Comments

@github-actions
Copy link

github-actions bot commented Nov 16, 2024

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

Copy link
Author

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
Copy link
Author

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

@jdblischak
Copy link
Collaborator

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

@jdblischak
Copy link
Collaborator

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?

@kounelisagis
Copy link
Member

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

Copy link
Author

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

@kounelisagis
Copy link
Member

All builds fail because of this: TileDB-Inc/TileDB-Py#2111 (comment)
Expected - working on this.

@teo-tsirpanis
Copy link
Member

This test gets skipped in TileDB-Py CI. From a quick look the behavior exhibited in linux-aarch64 seems to be the correct one. 🤔

Copy link
Author

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

@jdblischak
Copy link
Collaborator

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.

Copy link
Author

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
Copy link
Author

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

Copy link
Author

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
Copy link
Author

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

Copy link
Author

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

@jdblischak
Copy link
Collaborator

@kounelisagis the linux-aarch64 tiledb-py-feedstock builds continue to fail the test test_schema_evolution.py::test_schema_evolution_drop_fixed_attribute_and_add_back_as_var_sized. Is there an associated story and/or PR for fixing this?

Copy link
Author

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
Copy link
Author

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

Copy link
Author

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

Copy link
Author

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

Copy link
Author

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
Copy link
Author

github-actions bot commented Dec 1, 2024

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

Copy link
Author

github-actions bot commented Dec 2, 2024

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

Copy link
Author

github-actions bot commented Dec 3, 2024

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

@jdblischak
Copy link
Collaborator

Well last night's tiledb-py-feedstock builds were a complete mess. I'm guessing that my recent PR #154 to explicitly limit the build variants to py39 and py312 played a role. I'll investigate now

@jdblischak
Copy link
Collaborator

There appears to be multiple issues:

  • passed:
    • linux-64 py39
  • └─ python 3.13.* *_cpython does not exist (perhaps a typo or a missing channel).
    • linux-64 py313
    • linux-aarch64 py313
    • osx-arm64 py313
  • FAILED tiledb/tests/test_schema_evolution.py::test_schema_evolution_drop_fixed_attribute_and_add_back_as_var_sized - AssertionError: Arrays are not equal
    • linux-aarch64 py39
  • libmambapy.bindings.specs.ParseError: Found invalid version predicate in "*.2024_12_02"
    • osx-64 py313
    • osx-64 py39
    • osx-arm64 py39
    • win-64 py313
    • win-64 py39

@jdblischak
Copy link
Collaborator

The py313-specific solver errors were indeed due to #154. I didn't realize that the official name doesn't end in cpython (like all the previous versions) but instead it is 3.13.* *_cp313. Good news is that this is easy to fix

https://github.com/TileDB-Inc/tiledb-py-feedstock/blob/4af4729bab7a80e46332e5bfbe24a6d4b2d52f98/.ci_support/migrations/python313.yaml#L37

@jdblischak
Copy link
Collaborator

Also figured out the source of the invalid version predicate error. The passing linux-64 py39 build installed mamba 1.5.1, but all the other builds installed the latest mamba 2.0.4, and mamba 2 doesn't support regex in version strings (mamba-org/mamba#3601 (comment)). And unfortunately I don't see any conda-forge.yml configuration option that controls the version of mamba that is installed for the feedstock builds.

Copy link
Author

github-actions bot commented Dec 4, 2024

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

@jdblischak
Copy link
Collaborator

Nightlies are still a mess:

  • passed:
    • linux-64 py39 (must be some solver reason why mamba 2 can't be installed in linux-64 with py39)
  • nothing provides _numpy_rc needed by numpy-2.0.0rc1-py310...
    • linux-64 py313
    • linux-aarch64 py313
    • osx-arm64 py313
  • FAILED tiledb/tests/test_schema_evolution.py::test_schema_evolution_drop_fixed_attribute_and_add_back_as_var_sized - AssertionError: Arrays are not equal
    • linux-aarch64 py39
  • libmambapy.bindings.specs.ParseError: Found invalid version predicate in "*.2024_12_02"
    • osx-64 py313
    • osx-64 py39
    • osx-arm64 py39
    • win-64 py313
    • win-64 py39

Copy link
Author

github-actions bot commented Dec 5, 2024

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

@jdblischak
Copy link
Collaborator

After adding back the py312 build (#156), there are at least a reduced number of problems. Current build status:

Copy link
Author

github-actions bot commented Dec 6, 2024

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
Copy link
Author

github-actions bot commented Dec 7, 2024

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

Copy link
Author

github-actions bot commented Dec 8, 2024

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

Copy link
Author

github-actions bot commented Dec 9, 2024

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

Copy link
Author

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

Copy link
Author

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

Copy link
Author

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

@jdblischak
Copy link
Collaborator

Frustratingly the new failures from last night are because conda-build is now using the pin from .ci_support (which is 2.26) because I removed the recipe pin in #157

- package tiledb-2.26.2-hedb9d39_0 is excluded by strict repo priority

Copy link
Author

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

@jdblischak
Copy link
Collaborator

Frustratingly the new failures from last night are because conda-build is now using the pin from .ci_support (which is 2.26) because I removed the recipe pin in #157

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.

Copy link
Author

Nightly feedstock build failure for tiledbfeedstock_CI at https://dev.azure.com/TileDB-Inc/CI/_build?definitionId=4&_a=summary

Copy link
Author

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

@jdblischak
Copy link
Collaborator

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?

@jdblischak
Copy link
Collaborator

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants