-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Latest Windows runner broke our builds #11691
Comments
Hi @Galkon ,Thank you for bringing this issue to our attention. We will look into this issue and will update you after investigating. |
also broken the CUDA installation: Jimver/cuda-toolkit#382. |
Hi @Galkon - Could you please share a sample workflow preferably with a repo where the issue can be reproduced? Hi @thxCode - From the failure message it is evident that the maximum allowable execution time has surpassed. Kindly optimize your workflow to keep it within the limit. |
Hello subir0071 - regarding broken CUDA install it fails due to maximum allowable execution time has surpassed indeed. But this is not a cause, but a consequence. Recently, CUDA installers of recent versions started to stuck forever on install. This didn't happened with previous runner image version. Steps to reproduce:
Probably alternatively could be tested by downloading |
Seems like CUDA VS integration fails to work with new VS version updated in #11591. Getting a lot of these if launched with
|
Issue that addresses bug with CUDA Toolkit: microsoft/STL#5282 Quote from it:
All recent versions of CUDA Toolkit (I think starting from 12.4.0 and up to latest 12.8.0). From my point of view reverting unstable/bugged VS version sounds reasonable until this issue will be resolved. But that's just my opinion. |
Thanks @N-Storm. Will keep this issue open for now. |
Description
The latest windows runner update here broke our builds. We cannot build one of our native windows dependencies, without any code changing in it for 7+ months.
Platforms affected
Runner images affected
Image version and build link
Private repo so can't share build link.
Failing with this visual studio version:
VS2022 (17.13.35818.85)
Is it regression?
Yes, last successful action:
Expected behavior
It should build and not randomly break perfectly functional c++ code that previously built without issues.
Actual behavior
Completely broken builds and unusable github actions.
Repro steps
I don't know how to reproduce in another repo.
The text was updated successfully, but these errors were encountered: