-
Notifications
You must be signed in to change notification settings - Fork 16
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
The nightly build job failed on Tuesday (2024-07-09) #747
Comments
The nightly build job failed on Wednesday (2024-07-10) in run 9867467789 |
Nightly failure caused by removal of Other nightlies are also failing for the same reason (TileDB-Inc/conda-forge-nightly-controller#108, https://github.com/jdblischak/centralized-tiledb-nightlies/issues/14) |
The nightly build job failed on Wednesday (2024-07-10) in run 9884769007 |
Still failing due to the |
Fix pending in TileDB-Inc/TileDB#5179 |
The nightly build job failed on Thursday (2024-07-11) in run 9901719476 |
The nightly build job failed on Friday (2024-07-12) in run 9916791171 |
The nightly build job failed on Saturday (2024-07-13) in run 9924855664 |
The nightly build job failed on Monday (2024-07-15) in run 9933055676 |
The nightly build job failed on Tuesday (2024-07-16) in run 9950025355 |
The nightly build job failed on Wednesday (2024-07-17) in run 9967445139 |
There is a new error now. I think it was caused by the renaming of
|
Yes, VCF is using deprecated APIs that are now being removed from |
The nightly build job failed on Wednesday (2024-07-17) in run 9984800099 |
The nightly build job failed on Friday (2024-07-19) in run 10001849608 |
The nightly build job failed on Friday (2024-07-19) in run 10017037575 |
The nightly build job failed on Saturday (2024-07-20) in run 10025129401 |
The nightly build job failed on Sunday (2024-07-21) in run 10033892381 |
The nightly build job failed on Monday (2024-07-22) in run 10051950114 |
The nightly build job failed on Tuesday (2024-07-23) in run 10069751383 |
The nightly build job failed on Wednesday (2024-07-24) in run 10087413480 |
Is there a Shortcut Story to track this? |
The nightly build job failed on Thursday (2024-07-25) in run 10104974819 |
The nightly build job failed on Friday (2024-07-26) in run 10120341663 |
The nightly build job failed on Sunday (2024-07-28) in run 10128443495 |
The nightly build job failed on Sunday (2024-07-28) in run 10137339331 |
The nightly build job failed on Monday (2024-07-29) in run 10155388427 |
The nightly build job failed on Tuesday (2024-07-30) in run 10173302227 |
The nightly build job failed on Thursday (2024-08-01) in run 10191214289 |
The nightly build job failed on Thursday (2024-08-01) in run 10209259984 |
The nightly build job failed on Friday (2024-08-02) in run 10224770255 |
The nightly build job failed on Saturday (2024-08-03) in run 10232985196 |
The nightly build job failed on Sunday (2024-08-04) in run 10241833692 |
The nightly build job failed on Monday (2024-08-05) in run 10259517615 |
The nightly build job failed on Tuesday (2024-08-06) in run 10277377168 |
The nightly build job failed on Wednesday (2024-08-07) in run 10277377168 |
The @jdblischak have you seen this error in other builds? |
The nightly build job failed on Thursday (2024-08-08) in run 10295190928 |
Awesome! Thanks @awenocur!
@gspowley Yes, this is a known issue, but there is a workaround. I'll investigate. Also, TileDB-Py has migrated to using scikit-build-core, so the nightly script needs updating anyways. |
AFAIK this kind of issue happens when you run any code that imports
|
The nightly build job failed on Thursday (2024-08-08) in run 10312916306 |
@dudoslav thanks! I keep running into this again and again
Previously I had been using |
The nightly build job failed on Friday (2024-08-09) in run 10328445394 |
The nightly build job failed on Tuesday (2024-07-09) in run 9867467789
The text was updated successfully, but these errors were encountered: