-
Notifications
You must be signed in to change notification settings - Fork 114
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
parameters to extend drsdtcon #4097
Conversation
jenkins build this opm-models=902 opm-simulators=5418 please |
The test failures are in the opm-models blackoil models i.e. they dont use opmcommon stuff. Adding a enableConvectiveMixing flag and make the convectiveMixingModule depent on this flag is the best way IMO to solve this. (ala what is done for the rest of the blackoilmodules) |
jenkins build this opm-models=902 opm-simulators=5418 please |
5 similar comments
jenkins build this opm-models=902 opm-simulators=5418 please |
jenkins build this opm-models=902 opm-simulators=5418 please |
jenkins build this opm-models=902 opm-simulators=5418 please |
jenkins build this opm-models=902 opm-simulators=5418 please |
jenkins build this opm-models=902 opm-simulators=5418 please |
jenkins build this please |
jenkins build this opm-models=902 opm-simulators=5418 please |
Thanks. The test failure in the DRSDTCON test is expected. I have manually checked the results and they are ok. To be on the safe side I will run a benchmark to check the performance. After that this can be merged. |
benchmark please opm-models=902 opm-simulators=5418 |
Benchmark result overview:
FAILED RUNS: View result details @ https://www.ytelses.com/opm/?page=result&id=2524 |
Did I do something wrong when I called benchmark? |
benchmark opm-models=902 opm-simulators=5418 please |
benchmark please opm-models=902 opm-simulators=5418 |
Benchmark result overview:
FAILED RUNS: View result details @ https://www.ytelses.com/opm/?page=result&id=2526 |
@akva2 Do I do something wrong when calling benchmark? |
i'm not responsible for the benchmark support but i cannot see anything wrong as such. but the PR is also red, are you sure this actually builds? One guess would be that the trigger builds the PR branches rather than the PR branches pulled into the respective masters so maybe you should rebase the PR's ? |
I was unsure about the syntax to call benchmark across multiple repos. "benchmark please opm-models=902 opm-simulators=5418" Will this work. Or do I need to add please in the end. |
i believe your syntax is correct, although I must point out that whoever implemented it did not understand the practical role of the please in the trigger structure (ie it's there to have an end anchor). I have never seen the scripts behind the trigger so I can't really help other than my faint memory seeing that structure work before. |
jenkins build this opm-models=902 opm-simulators=5418 please |
Benchmark result overview:
FAILED RUNS: View result details @ https://www.ytelses.com/opm/?page=result&id=2528 |
I have tested Norne and drogon and smeaheia and they all run fine (i.e. no changes in results and performance) locally. |
I will try to merge this step by step. First opm-common. |
jenkins build this please |
connected to opm-models (OPM/opm-models#902) and opm-simulators (OPM/opm-simulators#5418)