Skip to content
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

Closed
igsilya opened this issue Oct 26, 2023 · 12 comments
Closed

C:\MinGW\msys\1.0\bin\bash The system cannot find the path specified. #3893

igsilya opened this issue Oct 26, 2023 · 12 comments

Comments

@igsilya
Copy link

igsilya commented Oct 26, 2023

The builds started failing a few hours ago. Visual Studio 2019 image seem to miss the msys installation:

C:\MinGW\msys\1.0\bin\bash -lc "echo \"C:/MinGW /mingw\" > /etc/fstab"
The system cannot find the path specified.
Command exited with code 1

Example: https://ci.appveyor.com/project/igsilya/ovs/build/job/1s49rn253o7apswo

@OwenMcDonnell
Copy link

I aborted an image update in progress to try to remedy this. Let me know if you are still seeing this failure.

@igsilya
Copy link
Author

igsilya commented Oct 26, 2023

New builds are working now. Thanks!
Will keep an eye on how they go.

@OwenMcDonnell
Copy link

Going to deploy a new image today that hopefully addresses the issue. Let me know if the issue recurs.

@OwenMcDonnell
Copy link

This should be fixed now on both Visual Studio 2019 and Visual Studio 2022 images.

@igsilya
Copy link
Author

igsilya commented Oct 31, 2023

Can confirm, the builds are working fine for the last few days. Thanks!

@igsilya igsilya closed this as completed Oct 31, 2023
@igsilya
Copy link
Author

igsilya commented Nov 30, 2023

Hi @OwenMcDonnell , we got this problem again today: https://ci.appveyor.com/project/blp/ovs/builds/48647442
Could you please take a look?

@igsilya igsilya reopened this Nov 30, 2023
@OwenMcDonnell
Copy link

I Will be working on a fix for this in the coming days. In the meantime please use Previous Visual Studio 2019 image.

ovsrobot pushed a commit to ovsrobot/ovs that referenced this issue Nov 30, 2023
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]>
igsilya added a commit to openvswitch/ovs that referenced this issue Dec 1, 2023
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]>
@OwenMcDonnell
Copy link

@igsilya can you confirm this is working again with current image?

@igsilya
Copy link
Author

igsilya commented Dec 7, 2023

@OwenMcDonnell
Copy link

@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 Previous Visual Studio 2019 image, but that then will be replaced at the next image update. At which point you'll have to switch to MinGW-w64 and MSYS2 or else run your own script to install the, now very old, MinGW 32 bit.
I'm not too familiar with development using these toolchains, but it seems that you may only need to update your builds to use C:\msys64\usr\bin\bash instead of C:\MinGW\msys\1.0\bin\bash.

@igsilya
Copy link
Author

igsilya commented Dec 8, 2023

@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!

@igsilya igsilya closed this as completed Dec 8, 2023
@GitMensch
Copy link
Contributor

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)?

roseoriorden pushed a commit to roseoriorden/ovs that referenced this issue Jul 1, 2024
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]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants