Closed github-actions[bot] closed 4 months ago
The centralized nightlies job failed on Saturday (2024-05-04) in run 8954953554
The centralized nightlies job failed on Sunday (2024-05-05) in run 8963067275
Currently stuck:
TILEDB_S3=ON
), then the libtiledb tests stall during the new faketime tests (https://github.com/jdblischak/centralized-tiledb-nightlies/commit/476e1c258a67c83c6bd665a2e29771e877978df4)The centralized nightlies job failed on Monday (2024-05-06) in run 8978605753
The centralized nightlies job failed on Tuesday (2024-05-07) in run 8995099398
The centralized nightlies job failed on Wednesday (2024-05-08) in run 9011309089
Still only the S3 failure in the tiledbvcf-py test. Waiting on a resolution of https://github.com/TileDB-Inc/TileDB/issues/4956
The centralized nightlies job failed on Thursday (2024-05-09) in run 9026233897
The centralized nightlies job failed on Friday (2024-05-10) in run 9026233897
TileDB-Cloud-Py failed in last night's build. However, it was due to a download error while installing dependencies. I restarted it.
It passed but then failed to upload since the date has changed
The centralized nightlies job failed on Friday (2024-05-10) in run 9040328376
The centralized nightlies job failed on Saturday (2024-05-11) in run 9048110525
The centralized nightlies job failed on Sunday (2024-05-12) in run 9056194311
It's not currently possible to run the libtiledb unit tests with S3 support enabled without also configuring S3 credentials (https://github.com/TileDB-Inc/TileDB/issues/4956#issuecomment-2108535085), so I commented out these tests in https://github.com/jdblischak/centralized-tiledb-nightlies/commit/3febc7b5b1f60a92a13c9258d894495883305390 (passing build).
If this changes in the future, I can add back the libtiledb tests. But the point of this centralized nightly repo is to check combability of the downstream clients with the latest libtiledb, so testing them is more important than directly testing libtiledb itself (which is already done upstream).
The centralized nightlies job failed on Friday (2024-05-03) in run 8947208381