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

Unable to fork in Msys2 #2154

Closed
pavelkryukov opened this issue Mar 13, 2018 · 4 comments
Closed

Unable to fork in Msys2 #2154

pavelkryukov opened this issue Mar 13, 2018 · 4 comments

Comments

@pavelkryukov
Copy link

Hi

We experience random errors in forks occurred during msys64 builds today:

      1 [main] make 2196 fork: child -1 - forked process 3928 died unexpectedly, retry 0, exit code 0xC0000005, errno 11
make[2]: fork: Resource temporarily unavailable

Examples:
https://ci.appveyor.com/project/miptilab/mipt-mips/branch/master/job/2qhqnwr2qmyg8ma4
https://ci.appveyor.com/project/miptilab/mipt-mips/branch/master/job/uhee74ex7hexa5dv

@IlyaFinkelshteyn IlyaFinkelshteyn added this to the next-images-update milestone Mar 14, 2018
@IlyaFinkelshteyn
Copy link
Contributor

@pavelkryukov this can be connected to recent build worker images update which includes MSYS2 updates.

As a temporary workaround please try to use Previous Visual Studio 2017 image.

Let us know if this help, but even if yes, do not close the issue, we need to root cause and fix it (or have a workaround) it before next build worker image update (when current image becomes "Previous").

pavelkryukov added a commit to MIPT-ILab/mipt-mips that referenced this issue Mar 14, 2018
@pavelkryukov
Copy link
Author

Thanks, it helps.

@FeodorFitsner FeodorFitsner removed this from the next-images-update milestone Mar 30, 2018
@pavelkryukov
Copy link
Author

I still see the failure in new image. Additionally, I noticed that it does not happen if "build" is set to "msvc", only "g++" builds are failing (we use MSys in both)

@pavelkryukov
Copy link
Author

Fixed in the image of last week

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