-
-
Notifications
You must be signed in to change notification settings - Fork 220
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] issue 1637 #1720
base: master
Are you sure you want to change the base?
[FIX] issue 1637 #1720
Conversation
Do you need help moving forward @t-h2o ? |
yes, I am not familiar with F3D testing framework. My goal is to test that no-config is set to 1:
For that, I run this command f3d --no-render --config=config_build --no-config --verbose In
My result for lines to add into # Test that --no-config set no-config value to 1
f3d_test(NAME TestNoConfigWithConfig ARGS --no-config --config=config_build --verbose REGEXP "'no-config' = '1'" NO_BASELINE) |
Please let me know if you need another review @t-h2o :) |
Hi @mwestphal, I have these two unanswered comments: |
This looks correct to me |
I have answered your questions :) |
Do you need help moving forward @t-h2o ? |
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.
missing TestNoConfigWithConfig
@@ -1049,6 +1049,9 @@ f3d_test(NAME TestConfigFileQuiet DATA nonExistentFile.vtp CONFIG ${F3D_SOURCE_D | |||
# Test no file with config file | |||
f3d_test(NAME TestNoFileConfigFile CONFIG ${F3D_SOURCE_DIR}/testing/configs/verbose.json ARGS --verbose REGEXP "No files to load provided" NO_BASELINE) | |||
|
|||
# Test that --no-config set no-config value to 1 | |||
f3d_test(NAME TestNoConfigWithConfig ARGS --no-config --config=config_build --verbose REGEXP "'no-config' = '1'" NO_BASELINE) |
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.
instead of testing the verbosity of no-config, how about opening a file a taking a screenshot ? This way we ensure the config_build is not taken into account
Looks like a few console test are failing, can you check them locally ? |
You actually just need to update the baselines :) |
--dry-run flag set variable dryRun avoid to read config
in case dry-run or no-render is true, we do not read the configuration file from f3d --help: [...] --dry-run [=<bool>(=1)] Do not read the configuration file (default: false) --no-render [=<bool>(=1)] Do not read the configuration file (default: false) [...]
find . -name "*\.cxx" -exec sed -i 's/dry-run/no-config/g' {} \;
find . -name "*\.cxx" -exec sed -i 's/dryRun/noConfig/g' {} \;
find . -name "*\.txt" -exec sed -i 's/--dry-run/--no-config/g' {} \;
find . -name "*\.h" -exec sed -i 's/dry-run/no-config/g' {} \; find . -name "*\.md" -exec sed -i 's/dry-run/no-config/g' {} \; find . -name "*\.txt" -exec sed -i 's/DryRun/NoRender/g' {} \;
test it with ctest -R NoConfigWithConfig
What do you mean by update the baselines? |
I mean that your change has an impact on some test that had an incorrect baseline because of the dry run issue. You can run these test locally and recover the baseline |
You can look in the CI results to see which test are impacted. |
Fix the dry run flag
TODO
--dry-run
flag set variabledryRun
avoid to read configapplication/testing/CMakeLists.txt