-
Notifications
You must be signed in to change notification settings - Fork 353
WIP: Debug windows CI for YAC coupling #691
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
WIP: Debug windows CI for YAC coupling #691
Conversation
…mpi-handshake as fallback if working without YAC.
This reverts commit 994152c.
ffea4c9 to
a2b3c1b
Compare
218b773 to
996331f
Compare
|
I reduced the diff to a minimum compared to https://github.com/ElmerCSC/elmerfem/tree/devel @ f6798c3 and the test |
|
@raback we would need output from the Windows runner to identify the issue. Don't merge, if fixed, since this is just a dummy PR to get rid of failing windows testing |
|
Looking at recent CI runs for the @tzwinger: Which kind of output are you looking for. If tests fail, the step "re-run tests" lists the directory content of the affected tests and the content of the |
|
@mmuetzel that is what @raback reported on that issue #682 (comment) |
|
Thanks for clarifying. So, is there anything missing in this PR? Or can it be closed? |
|
Well, we still have no real clue why this one test appears to have latency in writing the TEST_PASSED file (as suggested by @raback as the cause of it to fail in a random way) |
|
Maybe, @raback was looking at a different CI run than the one here. Copying the output to stderr and stdout here in case it is difficult to find in the CI logs: |
|
Thanx for the attention to the issue! Nothing to merge anymore. |
I open this PR to trigger the CI pipeline since I do not have access to a Windows machine for local testing.
I try to find the reason for the test
6 - Contactfailing in #682 @ ac2d8cb