-
Notifications
You must be signed in to change notification settings - Fork 2
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 #133
Comments
Nightly feedstock build failure for TileDB-Py%20Feedstock%20Testing at https://dev.azure.com/TileDB-Inc/CI/_build?definitionId=5&_a=summary |
It is the known |
Agreed. The tiledb-py-feedstock failures are the known However, the tiledb-feedstock win-64 build also failed. I restarted it
|
@teo-tsirpanis any idea what's going on with the windows build here? |
On first glance |
Agreed. Your comment jogged my memory. We've seen this before when the GitHub Actions image (also used by Azure) is updated. I'll investigate xref: #94 (comment), #104 (comment) |
Strangely however, both the last passing build on Sunday night and the failing build from Monday night used image version 20240811.1.0. |
I think I've figured it out. The last passing build used vs2022_win-64 19.40.33808-h753ab0a_2, and the failing builds used vs2022_win-64 19.41.34120-h72b6792_20. vs2022 19.41 has since been marked as broken (conda-forge/admin-requests#1056), so it should pass with a restart now. |
Ha. Can't win. The third attempt installed vs2022_win-64 19.40 (19.40.33808-h753ab0a_20), but then the image version was updated to 20240825.1.0, which updated Visual Studio from 17.10 to 17.11 (actions/runner-images@e01292a, actions/runner-images#10490) |
Last night's tiledb-feedstock win-64 build passed because it used image version 20240825.1.0 (Visual Studio 17.11) and installed vs2022_win-64 19.41. This was last night at 9:30 pm ET. However, exactly 12 hours later this morning at 9:30 am ET, two migration PRs to tiledb-feedstock failed because they used image version 20240811.1.0 (Visual Studio 17.10) and installed vs2022_win-64 19.41 (conda-forge/tiledb-feedstock#338, conda-forge/tiledb-feedstock#339) |
Nightly feedstock build failure for tiledbfeedstock_CI at https://dev.azure.com/TileDB-Inc/CI/_build?definitionId=4&_a=summary |
Nightly feedstock build failure for TileDB-Py%20Feedstock%20Testing at https://dev.azure.com/TileDB-Inc/CI/_build?definitionId=5&_a=summary |
Same Windows error apparently. |
Yes. It is super frustrating. As long as Azure keeps randomly flip-flopping between images that use either Visual Studio 17.10 or 17.11, there isn't much we can do. For more details see conda-forge/vc-feedstock#82 (comment) |
Nightly feedstock build failure for tiledbfeedstock_CI at https://dev.azure.com/TileDB-Inc/CI/_build?definitionId=4&_a=summary |
Nightly feedstock build failure for TileDB-Py%20Feedstock%20Testing at https://dev.azure.com/TileDB-Inc/CI/_build?definitionId=5&_a=summary |
The win-64 tiledb-feedstock build continues to fail because Azure is still using the outdated image version 20240811 |
I applied a workaround (conda-forge/admin-requests#1062 (comment)) to unblock the latest migration PRs (conda-forge/tiledb-feedstock#340). This should also fix the nightly build, that is, until Azure transitions to Visual Studio 17.11 (conda-forge/tiledb-feedstock#341) |
Nightly feedstock build failure for tiledbfeedstock_CI at https://dev.azure.com/TileDB-Inc/CI/_build?definitionId=4&_a=summary
The text was updated successfully, but these errors were encountered: