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

[check_swatinit] Tests fail on RHEL8 builds #669

Closed
andreas-el opened this issue Feb 26, 2024 · 5 comments
Closed

[check_swatinit] Tests fail on RHEL8 builds #669

andreas-el opened this issue Feb 26, 2024 · 5 comments
Labels
help wanted Extra attention is needed

Comments

@andreas-el
Copy link
Contributor

andreas-el commented Feb 26, 2024

Update:

The tests are now skipped instead:

SKIPPED [2] tests/test_check_swatinit_simulators.py:287: Test require flow dev version
SKIPPED [2] tests/test_check_swatinit_simulators.py:338: Test require flow dev version
SKIPPED [2] tests/test_check_swatinit_simulators.py:482: Test require flow dev version
SKIPPED [2] tests/test_check_swatinit_simulators.py:573: Test require flow dev version
SKIPPED [2] tests/test_check_swatinit_simulators.py:606: Test require flow dev version

Subscript tests for check_swatinit fails during komodo bleeding builds using python 3.8:
https://github.com/equinor/komodo-releases/actions/runs/8041838251/job/21963435048

As a sidenote, these also fails for python version 3.11
https://github.com/equinor/komodo-releases/actions/runs/8041838251/job/21962580908

FAILED tests/test_check_swatinit_simulators.py::test_swatinit_1_far_above_contact[flow] - assert False
 +  where False = <function isclose at 0x7f2ae5d8a700>(0.1, 1)
 +    where <function isclose at 0x7f2ae5d8a700> = np.isclose
FAILED tests/test_check_swatinit_simulators.py::test_swatinit_1_slightly_above_contact[flow] - assert False
 +  where False = <function isclose at 0x7f2ae5d8a700>(0.88782424, 1)
 +    where <function isclose at 0x7f2ae5d8a700> = np.isclose
FAILED tests/test_check_swatinit_simulators.py::test_swatinit_less_than_1_below_contact_neg_pc[flow] - assert False
 +  where False = <function isclose at 0x7f2ae5d8a700>(0.7906856, 1.0)
 +    where <function isclose at 0x7f2ae5d8a700> = np.isclose
FAILED tests/test_check_swatinit_simulators.py::test_swu_equal_swatinit[flow] - assert False
 +  where False = <function isclose at 0x7f2ae5d8a700>(0.5152699, 0.9)
 +    where <function isclose at 0x7f2ae5d8a700> = np.isclose
FAILED tests/test_check_swatinit_simulators.py::test_swu_lessthan_swatinit[flow] - assert False
 +  where False = <function isclose at 0x7f2ae5d8a700>(0.46336114, 0.9)
 +    where <function isclose at 0x7f2ae5d8a700> = np.isclose
= 5 failed, 781 passed, 19 skipped, 1 xfailed, 1 xpassed, 1 warning in 190.71s (0:03:10) =
@andreas-el andreas-el added bug Something isn't working help wanted Extra attention is needed labels Feb 26, 2024
@andreas-el andreas-el added this to SCOUT Feb 26, 2024
@sondreso
Copy link
Collaborator

Note that all of these run flow, which is using a different version on RHEL7 and RHEL8

@sondreso sondreso removed the bug Something isn't working label Feb 26, 2024
@larsevj
Copy link
Contributor

larsevj commented Feb 26, 2024

All of these tests check for different values depending on if you are running ecl or opm-flow. With opm-flow for rhel8 it seems like the output is more similar to the values expected from eclipse. So if you for these 5 tests check for exactly the same output for ecl and opm-flow (rhel8) you only get 3 failing test, and the numerical differences for these 3 tests are:

where False = <function isclose at 0x7fee5b8abf30>(0.5152699, 0.5151365333333333)
where False = <function isclose at 0x7fee5b8abf30>(0.7906856, 0.7915066)
where False = <function isclose at 0x7fee5b8abf30>(0.46336114, 0.4632444666666667)

@alifbe
Copy link
Collaborator

alifbe commented Feb 27, 2024

@larsevj You are right. I think all 5 tests will pass if we are using the same criteria with Eclipse

But it's interesting that only RHEL8 has converging results. The RHEL7 seems to give the same "old" result.

@alifbe
Copy link
Collaborator

alifbe commented Feb 28, 2024

flowdaily RHEL7 build was updated yesterday and now give a more consistent result.

We will update the test value accordingly. But the challenge is official flow which is used for GitHub action test will not be updated until April.

@andreas-el andreas-el changed the title [check_swatinit] Tests fail on RHEL8 builds [check_swatinit] Tests ~~fail~~ skipped on RHEL8 builds Mar 4, 2024
@andreas-el andreas-el changed the title [check_swatinit] Tests ~~fail~~ skipped on RHEL8 builds [check_swatinit] Tests fail on RHEL8 builds Mar 4, 2024
@alifbe
Copy link
Collaborator

alifbe commented Mar 5, 2024

Solved in #672

@alifbe alifbe closed this as completed Mar 5, 2024
@github-project-automation github-project-automation bot moved this to Done in SCOUT Mar 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
Archived in project
Development

No branches or pull requests

4 participants