| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
There was a problem hiding this comment.
Feel free to merge with or without tim's suggestion.
It may make sense to add some machinery in image_comparison to check whether it's overwriting itself? (not in a "controlled" case like here after the PR when the same file is listed twice, but rather in a case where it doesn't expect such an overwrite and is likely due to parametrization) Not sure how complex this would be to implement, and therefore whether it's worth the trouble...
Sorry, something went wrong.
Since parametrizing the test allows it to run in parallel, this makes it flaky, as one process can overwrite the test result image of another. Our standard way for dealing with tests that use the same baseline image is to pass duplicate filenames to `image_comparison`, because that is serialized.
…656-on-v3.2.x Backport PR #16656 on branch v3.2.x (Make test_imagegrid_cbar_mode_edge less flaky.)
| Back | FazBrowse Home | New Git URL |
PR Summary
Since parametrizing the test allows it to run in parallel, this makes it flaky, as one process can overwrite the test result image of another.
Our standard way for dealing with tests that use the same baseline image is to pass duplicate filenames to image_comparison, because that is serialized.
PR Checklist