-
Notifications
You must be signed in to change notification settings - Fork 249
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 cotire build #6508
Fix Windows cotire build #6508
Conversation
Should be fixed if we compile it "manually" in the script
@@ -11,7 +11,7 @@ set CC=cl.exe | |||
set CXX=cl.exe | |||
|
|||
rem Set variables | |||
set KRATOS_BUILD_TYPE=Release | |||
set KRATOS_BUILD_TYPE=Debug |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is it worth updating appveyor?
I would not touch it any more
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In any case, lets keep things consistent, its just adding a couple of lines...
at the end of the build it says:
maybe thats why it cant find Kratos when trying to run the tests |
Nono, that's normal, it says that because prior to install we decided to delete the folder. Files get installed after, but at some point we also disable the messages. The problem is that the env variables defined in the previous stage are not available here. |
yay it works |
@GuillermoCasas there is a test in the SwimmingDEM app that uses the non-standard python module |
Yep, to slow, so... we are a little f*****. Either we increase the runtime for the test, or we compile in Release, and the latter is not an option because then we run out of memory in the machine (cof cof @loumalouomega templates cof cof). |
I try now without contact and in release. I mean, the problem with the templates is not precisely new... |
It runs out of memory at core level... |
oh ok |
Yep... |
@roigcarlo do you know which files are the problem? |
|
now it is able to build and also run the tests in a decent amount of time :D if fails overall because some tests are failing |
Tests are failing in Please take a look and fix those tests such that we can merge this :) |
@loumalouomega also the contact tests seem to crash in Win |
@KratosMultiphysics/technical-committee just as an idea, we could for now disable the failing apps, merge this PR and then add the apps back in separate PRs |
Agree |
For some reason links against StructuralMechanics???
Now it passes :D |
@philbucher Is there anything still blocking this PR? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To me this can/should go in now, none had any comments and the longer we wait the higher the chances are that some test will break
For the apps I disabled, the are still being compiled in Appveyor so nothing is lost on that end. We should fix the tests and add the apps back here asap though
The night CI that is failing is because there are some tests failing in the nightly suites, this is a known issue, and is being addressed constantly
Thanks for the efforts @HubertBalcerzak @roigcarlo
@philbucher Seems that windows nightly is mandatory so we cannot merge :S |
Hm interesting/strange |
now it should work once the CI has passed |
yep now you can merge |
Ok let's do it |
🎉 🎉 🎉 |
This allows building Kratos with cotire on windows