| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
There was a problem hiding this comment.
Could we do a hash check here to make sure that we get an uncorrupted file?
Sorry, something went wrong.
There was a problem hiding this comment.
Good idea.
Sorry, something went wrong.
|
👍 |
Sorry, something went wrong.
There was a problem hiding this comment.
Does that mean I can't run tests without this specific freetype installed?
Sorry, something went wrong.
There was a problem hiding this comment.
Is it feasible to allow running the tests, just giving a big warning and marking all image comparisons as known-fail? That would still let people run the other tests, or look at the results of single image-comparison tests manually, while not leading them to think the test results are canonical.
Sorry, something went wrong.
There was a problem hiding this comment.
@QuLogic: You don't need a specific version of freetype installed. You need to build matplotlib with the special "local_freetype" option, which will download and build against a particular version of freetype for you.
@jkseppan: Maybe a warning is the right thing to do -- but knownfail doesn't always communicate "the test run you just ran should give you very little confidence that anything is working" which is really the situation we would have here. What about a warning + real failures?
Sorry, something went wrong.
There was a problem hiding this comment.
Warning + failures makes sense to me.
Sorry, something went wrong.
|
The experiment in #5307 shows that there are now no text differences, even on Linux vs. Mac. There are other sorts of differences that happen when you turn the tolerance all the way down to 0, however, that I'm now trying to get to the bottom of. Some of it appears to just be random number effects that we've never noticed before with the higher tolerances. |
Sorry, something went wrong.
|
BTW, which tests were different, out of curiosity? Is it mostly Linux vs Mac or even between Linux distros? |
Sorry, something went wrong.
|
They mostly seem to be differences from one run to the next (all other things being equal). Some things just need an explicit random seed. The others are caused by a very deep and long standing bug in the test runner -- it's possible to write a test returning multiple figures all using the same output filename. Race conditions abound! I hope to have a test for that soon. |
Sorry, something went wrong.
|
Sorry, I meant which tests prompted this PR specifically? |
Sorry, something went wrong.
|
Oh -- different versions of Freetype have always been a problem since we've had our test suite. It's the whole reason we do "fuzzy" rather than exact matching. But the goal here is to nail down the version of Freetype such that we can do exact matching (and catch more bugs that way). |
Sorry, something went wrong.
|
OK, I'd just like to know whether FreeType eventually stabilized and we could drop this once all the older distros were EOL, or whether it's a more cross-platform issue. In testing Cartopy, I've never run into anything caused by Freetype and not changes in matplotlib, so perhaps we are all running new (or close) enough versions that it does not trigger anything. |
Sorry, something went wrong.
|
Freetype has stabilized somewhat in recent years, but we ran into this as recently as 2014 the last time. The cross-platform and cross-distro issues still exist though -- it can be compiled with different hinting settings etc. and this is an attempt to normalize that. |
Sorry, something went wrong.
|
@QuLogic: Just as an example that this is still a live problem, see #5305. @zLbZ generated a new set of images on Debian testing, and the version of Ubuntu on Travis (I think it's 12.04, maybe 14.04), with freetype 2.6.0 and 2.4.8 respectively, mismatched the images by as much as 20% (notably, these are text-heavy images). |
Sorry, something went wrong.
|
#5307 is now passing (except for some PEP8 stuff), so I'm convinced this approach to use a fixed version of freetype is sound. This is ready for final review. |
Sorry, something went wrong.
|
Ah, I had forgotten about all the configurable hinting settings in FreeType; those are quite likely to cause a sizeable difference (even if mostly imperceptible). |
Sorry, something went wrong.
There was a problem hiding this comment.
The tense here is different from most of the rest of the file (though it's not all totally the same.)
Sorry, something went wrong.
|
Is there any particular reason to use Freetype '2.5.2' According to http://www.freetype.org/ several security fixes has gone in since. It seems better to me to use 2.5.5 or 2.6.1? |
Sorry, something went wrong.
|
@jenshnielsen: I started with the version that is currently on Travis, and the version many (but not all) of the current images were created with, in an attempt to avoid updating too many of the images. Alternatively, we could just move to the latest and start fresh, but that will add more stuff to the repository. |
Sorry, something went wrong.
|
AFAIK the version on Travis is 2.4.8 from https://travis-ci.org/matplotlib/matplotlib/jobs/87692893 freetype: yes [version 2.4.8] We could upgrade Travis from the existing 12.04 image to the "new" beta 14.04 images to get 2.5.2 This is of cause slightly more complicated because the versions in ubuntu have backported some of the security fixes from 2.5.x |
Sorry, something went wrong.
|
@jenshnielsen: Ah -- that was my bad -- I just just for what 14.04 had rather than what Travis was actually using. Maybe it would be best to put this at the latest now just for longevity -- the idea should be to rarely, if ever, update this again, except for zero-visible-changes security updates. |
Sorry, something went wrong.
|
@QuLogic: I've addressed all of your minor points in the latest commits here. |
Sorry, something went wrong.
|
So, I think before merging, we should have a discussion about which version of Freetype to use here. I could be persuaded either way, I think. |
Sorry, something went wrong.
|
Rebased. |
Sorry, something went wrong.
|
Things look good to me. Just waiting for Travis to go green. |
Sorry, something went wrong.
Use a specific version of Freetype for testing
Use a specific version of Freetype for testing
|
The plan is to backport this to 2.0.x right? In that case feel free to merge #5413 |
Sorry, something went wrong.
|
Yes. This should be merged to 2.0.x. I'll do that. |
Sorry, something went wrong.
Use a specific version of Freetype for testing
|
Cherry-picked to 2.0.x as d730481 |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
This should theoretically allow us to turn down the tolerance on image comparison tests.
If all is going well, this should pass Travis-CI, which is now using a locally-built freetype.