-
Notifications
You must be signed in to change notification settings - Fork 278
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 test_pr_1905.py for native 2019msvc64 (#2108) #2112
Fix test_pr_1905.py for native 2019msvc64 (#2108) #2112
Conversation
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.
Tested on my Windows PC and it works 👏
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.
Beautiful fix, @postscript-dev.
Codecov Report
@@ Coverage Diff @@
## main #2112 +/- ##
=======================================
Coverage 63.80% 63.80%
=======================================
Files 96 96
Lines 19171 19171
Branches 9772 9772
=======================================
Hits 12232 12232
Misses 4658 4658
Partials 2281 2281 Continue to review full report at Codecov.
|
@piponazo: Last year, I noticed a problem related to this issue that I think is worth mentioning. The Exiv2 mechanism to create tag webpages from the source code is only run when we publish the website. This means that when we make changes, the CI will not catch any errors for us. To create the webpages is simple.
The build instructions are missing from README.md but I plan to add them. If you have the time, could you look at the CI? |
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.
Can we keep test/data
for input data and use test/data/test_reference_files
for reference output?
I think it would be a good idea to write this down in the wiki or in the test/README document to give instructions to people about some of the practices we have been discussing lately about writting tests.
@postscript-dev whenever you create the PR with the instructions, please do it in the main repository and I'll happily try to adapt our CI jobs to make this run on every PR. |
Closes #2108.