-
Notifications
You must be signed in to change notification settings - Fork 65
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
C:\MinGW\msys\1.0\bin\bash The system cannot find the path specified. #3893
Comments
I aborted an image update in progress to try to remedy this. Let me know if you are still seeing this failure. |
New builds are working now. Thanks! |
Going to deploy a new image today that hopefully addresses the issue. Let me know if the issue recurs. |
This should be fixed now on both |
Can confirm, the builds are working fine for the last few days. Thanks! |
Hi @OwenMcDonnell , we got this problem again today: https://ci.appveyor.com/project/blp/ovs/builds/48647442 |
I Will be working on a fix for this in the coming days. In the meantime please use |
It may take a few days for AppVeyor to fix their broken images [1], use the 'Previous' version of the image for now to unblock CI. We'll need to revert this once the issue is fixed. [1] appveyor/ci#3893 Signed-off-by: Ilya Maximets <[email protected]> Signed-off-by: 0-day Robot <[email protected]>
It may take a few days for AppVeyor to fix their broken images [1], use the 'Previous' version of the image for now to unblock CI. We'll need to revert this once the issue is fixed. [1] appveyor/ci#3893 Acked-by: Alin Gabriel Serdean <[email protected]> Acked-by: Eelco Chaudron <[email protected]> Signed-off-by: Ilya Maximets <[email protected]>
@igsilya can you confirm this is working again with current image? |
@OwenMcDonnell , seems to be working so far: https://ci.appveyor.com/project/igsilya/ovs/builds/48705167 |
@igsilya Not sure if you're subscribed to Appveyor's technical newsletter or not, but with the latest update we've also announced the end of support for MinGW 32 bit v.5.3.0 at the next image update. At that time, you'll still be able to run builds with |
@OwenMcDonnell thanks for the heads up! I'm not an expert in our windows build myself, but I know we link with some 32-bit libraries, so maybe some other adjustments will be needed. We'll look into that. Closing this issue for now as the new image appears to be working fine. Thanks again! |
Can you please also fix the VS 2022 image? It has the same issue (the C:\MinGW folder is empty). Note: I don't see a reference in https://www.appveyor.com/updates/2023/12/03/ that MinGW is (to be) removed and https://www.appveyor.com/docs/windows-images-software/#mingw-msys-cygwin also list that to be available. When it is removed: how long will it stay available in the "Previous" images (I guess until the next update) and how long with the others (pre 2019)? |
It may take a few days for AppVeyor to fix their broken images [1], use the 'Previous' version of the image for now to unblock CI. We'll need to revert this once the issue is fixed. [1] appveyor/ci#3893 Acked-by: Alin Gabriel Serdean <[email protected]> Acked-by: Eelco Chaudron <[email protected]> Signed-off-by: Ilya Maximets <[email protected]>
The builds started failing a few hours ago. Visual Studio 2019 image seem to miss the msys installation:
Example: https://ci.appveyor.com/project/igsilya/ovs/build/job/1s49rn253o7apswo
The text was updated successfully, but these errors were encountered: