-
Notifications
You must be signed in to change notification settings - Fork 33
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 Sunday (2024-09-29) #2075
Comments
The nightly build with earliest supported numpy job failed on Sunday (2024-09-29) in run 11089884523 |
Both failed jobs were related to |
The nightly build job failed on Friday (2024-10-04) in run 11174316176 |
1 similar comment
The nightly build job failed on Friday (2024-10-04) in run 11174316176 |
The nightly build with earliest supported numpy job failed on Friday (2024-10-04) in run 11174316176 |
The nightly build job failed on Saturday (2024-10-05) in run 11190619867 |
1 similar comment
The nightly build job failed on Saturday (2024-10-05) in run 11190619867 |
The nightly build with earliest supported numpy job failed on Saturday (2024-10-05) in run 11190619867 |
The nightly build job failed on Sunday (2024-10-06) in run 11199130785 |
1 similar comment
The nightly build job failed on Sunday (2024-10-06) in run 11199130785 |
The nightly build with earliest supported numpy job failed on Sunday (2024-10-06) in run 11199130785 |
The nightly build job failed on Monday (2024-10-07) in run 11209033615 |
1 similar comment
The nightly build job failed on Monday (2024-10-07) in run 11209033615 |
The nightly build with earliest supported numpy job failed on Monday (2024-10-07) in run 11209033615 |
The nightly build job failed on Tuesday (2024-10-08) in run 11228931833 |
1 similar comment
The nightly build job failed on Tuesday (2024-10-08) in run 11228931833 |
The nightly build with earliest supported numpy job failed on Tuesday (2024-10-08) in run 11228931833 |
The nightly build job failed on Wednesday (2024-10-09) in run 11248595774 |
1 similar comment
The nightly build job failed on Wednesday (2024-10-09) in run 11248595774 |
The nightly build with earliest supported numpy job failed on Wednesday (2024-10-09) in run 11248595774 |
The nightly build job failed on Thursday (2024-10-10) in run 11267784095 |
1 similar comment
The nightly build job failed on Thursday (2024-10-10) in run 11267784095 |
The nightly build with earliest supported numpy job failed on Thursday (2024-10-10) in run 11267784095 |
The nightly build job failed on Monday (2024-10-14) in run 11321329322 |
The nightly build with earliest supported numpy job failed on Tuesday (2024-10-15) in run 11339636658 |
The nightly build with earliest supported numpy job failed on Thursday (2024-10-17) in run 11378701272 |
Except for errors coming from
An example is: https://github.com/TileDB-Inc/TileDB-Py/actions/runs/11378701272/job/31654942639 and some from I will investigate this. |
this one and https://github.com/TileDB-Inc/TileDB-Py/actions/runs/11321329322/job/31480234054 look like a core issue? For the context ones, I think we need to move them to a subprocess to make sure no other tiledb operations have happened. |
|
The nightly build with earliest supported numpy job failed on Friday (2024-10-18) in run 11397798114 |
The nightly build job failed on Monday (2024-10-21) in run 11433574610 |
The nightly build with earliest supported numpy job failed on Tuesday (2024-10-22) in run 11453608764 |
The nightly build with earliest supported numpy job failed on Saturday (2024-10-26) in run 11529122363 |
The nightly build job failed on Sunday (2024-09-29) in run 11089884523
The text was updated successfully, but these errors were encountered: