-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Visual tests don't seem to run on Travis #2838
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
Comments
@lionel- I think I have figured out the problem. I believe it is in these lines in the vdiffr code: This code causes vdiffr to silently (from within CRAN check) skip tests when the system freetype library is too old. The freetype version on Travis is 2.5.2, hence that condition is satisfied. On our local machines we have more recent versions of freetype and thus we never notice the problem. I have made a PR to test this hypothesis for the ggplot2 repo (#2841), but I've seen the same problem already in one of my own repos: https://travis-ci.org/wilkelab/cowplot/builds/417734551 I think the freetype version test in vdiffr should be removed since vdiffr now uses a defined version anyways. This raises another issue, though: If vdiffr for whatever reason decides to skip tests while on Travis then we don't get notified and may assume everything is fine when actually nothing is tested. Maybe there needs to be a strict mode that treats skipped tests as errors, and that mode should then be enabled on Travis. |
As expected (https://travis-ci.org/tidyverse/ggplot2/jobs/417736237):
|
Thanks to your help diagnosing the vdiffr issue the tests are now run again on Travis @clauswilke! Unfortunately it seems many visual tests have not been updated because of the silent skipping. As I'm not familiar with all the recent changes I'm not sure whether the failures reflect actual bugs or (more likely) figures that should simply be updated. Could you take a look based on current master please? |
@lionel- Thanks for taking care of this so quickly! I'm aware of the broken visual tests, that's what prompted me to look into Travis in the first place. I opened an issue a few days ago: #2824 The broken tests are due to changes in secondary axis code (those are all fine) and changes in the scales package (those are sufficiently different that I don't feel comfortable to approve without a second set of eyes). I think @hadley and/or @dpseidel need to take a look. Issue #2824 contains a few example images. |
This old issue has been automatically locked. If you believe you have found a related problem, please file a new issue (with reprex) and link to this issue. https://reprex.tidyverse.org/ |
From all I can tell, visual tests don't run on Travis. I have three lines of evidence:
In PR make preserve = "single" more robust in position_dodge(). #2813, I ran a build with and without a change in the visual test reference images. Both builds succeeded on Travis. Only one succeeded on my local install.
Numerous visual tests seem to have changed with the latest version of scales (Visual tests fail with scales 1.0 #2824), but no Travis build fails because of this.
I can't remember when was the last time that I had a Travis build fail because of a failed visual test. Yet in my local install it's quite common that visual tests fail on occasion, and generally for valid reasons (something small has changed in the plot).
cc @lionel-
The text was updated successfully, but these errors were encountered: