-
Notifications
You must be signed in to change notification settings - Fork 123
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/actionx compdat show error #5486
Conversation
Two data files get compared: one with ACTIONX and one with the same commands but without ACTIONX. For sequential runs, they produce the same output, but for parallel runs they don't, because the when the COMPDAT keyword is used in an ACTIONX, well connections get created there that are not known to the grid partitioner.
jenkins build this opm-tests=1199 please |
jenkins build this please |
Nice, thanks. On of the few occasions where a failing test is something good 😅 |
Last jenkins build used master and fails with
Let's try with the OPM/opm-tests#1199 |
jenkins build this opm-tests=1199 please |
ah yes, thanks! |
jenkins build this opm-tests=1199 please |
jenkins build this please |
jenkins build this opm-tests=1200 please |
It seems like it fails correctly now. |
Yes, I don't really know where this timeout came from .. when creating the previous test file, I used a somewhat older version of flow (possibly from last week, so July 24th 2024) and the test with 8 processes was failing because of the correct reason, yet today I ran that with a freshly compiled version and the program was also frozen at the same reportstep as on Jenkins. |
Closing this since #5488 has been merged |
No description provided.