-
Notifications
You must be signed in to change notification settings - Fork 849
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
Improve unit tests #2391
Open
guusbertens
wants to merge
10
commits into
su2code:develop
Choose a base branch
from
guusbertens:develop
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+16
−9
Open
Improve unit tests #2391
Changes from 3 commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
c2a668e
Update to Meson 0.64.1.
82abcad
UnitTests: make Meson copy required drg files to build dir
9e0549e
UnitTests: do not install tests
faca833
Merge branch 'develop' into develop
Cristopher-Morales 2d31d2b
Merge branch 'develop' into develop
bigfooted 598e23d
Merge branch 'develop' into develop
bigfooted 8382186
Merge branch 'develop' into develop
Cristopher-Morales c648c5f
Merge branch 'develop' into develop
Cristopher-Morales b9cf11b
Merge branch 'develop' into develop
Cristopher-Morales e11d90a
Merge branch 'develop' into develop
Cristopher-Morales File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Submodule meson
updated
1389 files
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
We would need to change the regression workflow to find the unit test binaries somewhere else. It's simpler if you add a meson option to skip installing them by default, and then we can install them in the regression test script.
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.
Thanks! I'll have a look!
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.
But... The documentation indicates the unit tests should be run from within the build dir (https://su2code.github.io/docs_v7/Running-Unit-Tests/). Shouldn't the regressions test script do the same, then?
(I'm not an SU2 pro... Maybe the regression test script tests for more and/or other things, which would invalidate the above.)
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.
I see, there are multiple tests being run:
The former currently relies on hardcoded paths in the source tree, which typically only work in the build container and test container. The hardcoded paths break the unit tests in any other situation.
My patches remove the hardcoded paths, and instead tell Meson to move the files to the build tree. This makes the unit tests work as documented.
Of course, the files can be installed as well. The test_driver then needs to be run from the right dir, or needs to have correct paths hardcoded into it. In the latter case, the documentation needs an update: only run the tests after installing.
So, there are three options:
3 and 4 would break things like EasyBuild, that assume tests are run before installation, and require an update to the documentation.
2 seems like the right option.
What do you think?
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.
Option 2 would require a change to the
compileSU2.sh
script. I doubt that that will be reflected anytime soon, which results in the tests failing until the container is updated.@pcarruscag I think options 3 above is what you suggested, but would still either break the documented way to run unit tests (
ninja -C builddir test
), or require one to specify a workdir inregression.yml
, which seems impossible.What is the intention of tests? Should they be run before installing, to ensure one doesn't install a broken binary, or should they be run after installing?
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.
Hi, Guus,
All tests that are not unit tests are run after installation/compilation, and are there mainly to make sure that developers do not break existing functionality during development. The tests all represent very small 'real' testcases that are solved, and we compare the output with the known and stored output.
The unit tests are special because they involve testing for correctness of specific c++ functions that we have, so they involve the compilation of a small cpp file that calls the specific function.
So the unit tests have to know where the header files are, the rest of the tests only have to know where the executable is. Hope that helps.