-
Notifications
You must be signed in to change notification settings - Fork 1
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 centralized nightlies job failed on Tuesday (2024-07-09) #14
Comments
The centralized nightlies job failed on Tuesday (2024-07-09) in run 9867069920 |
Oops. I forgot to close this Issue yesterday. The original failure from last week was a spurious error when uploading an artifact. It has passed ever since then. |
Last night's failure was due to the recent update to the xref: TileDB-Inc/TileDB#5026, TileDB-Inc/conda-forge-nightly-controller#108, TileDB-Inc/TileDB-R#727, TileDB-Inc/TileDB-Py#1975 |
The centralized nightlies job failed on Wednesday (2024-07-10) in run 9884378480 |
Still failing due to the |
Fix pending in TileDB-Inc/TileDB#5179 |
The centralized nightlies job failed on Thursday (2024-07-11) in run 9901331468 |
The centralized nightlies job failed on Friday (2024-07-12) in run 9916513178 |
The centralized nightlies job failed on Saturday (2024-07-13) in run 9924615480 |
The centralized nightlies job failed on Sunday (2024-07-14) in run 9932722986 |
The centralized nightlies job failed on Monday (2024-07-15) in run 9949626990 |
The centralized nightlies job failed on Tuesday (2024-07-16) in run 9967040160 |
Last night libtiledb failed due to a spurious download failure. Restarted |
The centralized nightlies job failed on Wednesday (2024-07-17) in run 9967040160 |
While the libtiledb failure last night was spurious, most of the client builds are now failing. I suspect it is related to the recent removal of deprecated APIs in TileDB-Inc/TileDB#5146 I'm seeing similar error messages to those in other nightly builds |
The centralized nightlies job failed on Wednesday (2024-07-17) in run 9984394452 |
The centralized nightlies job failed on Thursday (2024-07-18) in run 10001437480 |
The centralized nightlies job failed on Friday (2024-07-19) in run 10016749877 |
The centralized nightlies job failed on Saturday (2024-07-20) in run 10024869559 |
The centralized nightlies job failed on Sunday (2024-07-21) in run 10033500413 |
TileDB-Py and libtiledbvcf continue to fail due to the use of deprecated APIs. The tests for tiledbsoma-r sometimes pass and sometimes segfault. Unclear if this is spurious or not. Will have to keep monitoring |
The centralized nightlies job failed on Monday (2024-07-22) in run 10051518578 |
The centralized nightlies job failed on Tuesday (2024-07-23) in run 10069345493 |
The centralized nightlies job failed on Wednesday (2024-07-24) in run 10087006106 |
The centralized nightlies job failed on Thursday (2024-07-25) in run 10104559745 |
The TileDB-Py error about However, there are still errors that are failing the build:
The error appears related to pybind11. @teo-tsirpanis do you have any ideas what could be causing this? |
Apparently one API was missed in TileDB-Inc/TileDB-Py#1958, c.c. @kounelisagis. |
The centralized nightlies job failed on Friday (2024-07-26) in run 10120050775 |
Oh my goodness, another one? 😩 |
Do we have to remove all instances of https://github.com/TileDB-Inc/TileDB-Py/blob/e29bf7301c44df9c8086c83a66deaf3c9089e12d/tiledb/cc/array.cc#L124 cc: @kounelisagis |
The centralized nightlies job failed on Saturday (2024-07-27) in run 10128189890 |
The centralized nightlies job failed on Sunday (2024-07-28) in run 10136948012 |
The centralized nightlies job failed on Monday (2024-07-29) in run 10154979104 |
The centralized nightlies job failed on Tuesday (2024-07-30) in run 10172798362 |
The centralized nightlies job failed on Wednesday (2024-07-31) in run 10190812724 |
The centralized nightlies job failed on Thursday (2024-08-01) in run 10208863772 |
The centralized nightlies job failed on Friday (2024-08-02) in run 10224480159 |
The centralized nightlies job failed on Saturday (2024-08-03) in run 10232732546 |
The centralized nightlies job failed on Sunday (2024-08-04) in run 10241445902 |
For Python, should we do something similar to this TileDB-Inc/conda-forge-nightly-controller#122 @jdblischak? |
The centralized nightlies job failed on Monday (2024-08-05) in run 10259108970 |
The centralized nightlies job failed on Tuesday (2024-08-06) in run 10276973841 |
The centralized nightlies job failed on Wednesday (2024-08-07) in run 10294780430 |
It's been a bit of a roller coaster ride, but things are settling down. 3 days ago there were 4 failings builds: But last night only TileDB-Py failed. As @kounelisagis suggested above (https://github.com/jdblischak/centralized-tiledb-nightlies/issues/14#issuecomment-2268942904), I'll try addressing this with The libtiledbvcf build was fixed by TileDB-Inc/TileDB-VCF#753 and TileDB-Inc/TileDB-VCF#755 Unclear why TileDB-Go is passing now. 3 days ago it was clearly failing due to using deprecated APIs (see test failure below). However, while there have been recent commits both to TileDB-Go and TileDB, none appear related to these particular deprecated APIs.
Also unclear why TileDB-R is passing now. Maybe the previous error was spurious. There have been no recent upstream commits.
|
TileDB-Py build fixed by ec5ce1f (build). Thanks @kounelisagis! xref: TileDB-Inc/TileDB-Py#2023, TileDB-Inc/conda-forge-nightly-controller#122 |
The centralized nightlies job failed on Tuesday (2024-07-02) in run 9770774146
The text was updated successfully, but these errors were encountered: