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

Fix Windows CI failures #3806

Open
aymanhab opened this issue Jun 10, 2024 · 8 comments · Fixed by #3810
Open

Fix Windows CI failures #3806

aymanhab opened this issue Jun 10, 2024 · 8 comments · Fixed by #3810
Assignees

Comments

@aymanhab
Copy link
Member

No description provided.

@nickbianco
Copy link
Member

This thread may be useful: actions/runner-images#10004

@nickbianco
Copy link
Member

nickbianco commented Jun 11, 2024

The Windows 2019 builds were failing due to an issue with compiling Catch2 (linker error). There's another issue on that repo also reporting issues with Catch2; not a linker error, but worth monitoring.

Based on that thread, it seems like they did not properly update the VCruntime shipped with the Windows runner images. Other projects have come up with workarounds in their CI scripts that we might be able to adopt, e.g.: https://github.com/ECP-WarpX/impactx/pull/633/files.

@nickbianco
Copy link
Member

I'm testing the workaround on #3807, but supposedly the issue was fixed in the runners, so I'm also re-running the Windows builds on #3796 without the workaround to see what happens.

@aymanhab
Copy link
Member Author

Thanks @nickbianco I wouldn't try workarounds to roll back later since it appears they're rolling out a fix on their side and too many projects were affected. As long as one of our windows environments is functional we can afford to wait I think. My main concern would be if there's an issue linking executables built with earlier vc versions which may be problematic for dependencies but will wait for the dust to settle if this comes up.

@nickbianco
Copy link
Member

nickbianco commented Jun 12, 2024

It looks like the Windows runners have been updated. The C++ tests are passing, but the Matlab tests are still failing with a link error:

java.lang.UnsatisfiedLinkError: D:\a\opensim-core\opensim-core\build\Release\osimJavaJNI.dll: A dynamic link library (DLL) initialization routine failed

I'm seeing this on #3796.

@nickbianco
Copy link
Member

New issue related to Java bindings failures: actions/runner-images#10055.

@nickbianco nickbianco changed the title Fix or remove visual studio 2019 from ci Fix Windows CI failures Jun 14, 2024
@nickbianco nickbianco reopened this Jun 19, 2024
@aymanhab
Copy link
Member Author

@nickbianco This seems rather flaky, same runner version passes all java tests on other runs. Is that the reason for reopening?

@nickbianco
Copy link
Member

The issue closed automatically after I merged that PR, which I didn't intend. The PR is more of a temporary patch, and I was thinking we keep this issue open until Microsoft gets their act together.

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

Successfully merging a pull request may close this issue.

2 participants