-
Notifications
You must be signed in to change notification settings - Fork 284
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 for small plot changes with freetype 2.10. #3297
Conversation
Could not review pull request. It may be too large, or contain no reviewable changes. |
(help!!) I don't get this. On my desktop, running lib/iris/tests/tests-image_json.py gives :
Which is what I expect, until the test-iris-imagehash PR is merged However, when I first made this PR, the travis 8970.3 test (python2, not TEST_MINIMAL) was failing with above message, as expected, but the 8970.4 (python3, not TEST_MINIMAL) was "silently" succeeding. [
So, even if the latter is a spurious / occasional failure, it seems that the expected *failure of this test is not reliable : Sometimes this test randomly + unexpectedly fails to fail ??? |
Now re-spinning those tests again ... ... and now they both simply pass |
Re-checking with the warning messages for debug, running locally, I had hit the rate-limit for unauthenticated github api requests. |
Just observed : Python2 test reports 13 requests remaining (??per hour??), and Python3 reports 0 left, and aborts. |
Further investigation confirms that the "unittest.skip" causes a successful test completion without any message. I will re-draft the test to report the rate-limit "skip" as an error. |
Latest : whereas Monday afternoon (25th Mar) I could not get this to behave, yesterday (Tuesday 24th) it did work. This is quite distinct from a "real" lack of requests, which looks like this :
However, the difference can be seen in the "captured logging" section where the 403 return is visible. While this happened consistently on Monday afternoon, it seems to have resolved yesterday. NEXT STEPS: I'll re-propose this PR when I'm confident that it probably won't cause ongoing repeated problems like we saw Monday afternoon ! |
Similar problems emerging, including 403 error. Most recently, getting ...
This seems to imply that the results of the rate-limit enquiry were ok, but then the access failed. Python 3.6
Seems to say that the rate-limit says no remaining requests. |
Some hours later, re-spin again... |
Results:
Respin again for this morning : Thu 28 ... |
... Respin again for this morning : Thu 28 ...
|
Could not review pull request. It may be too large, or contain no reviewable changes. |
Removed text formatting changes in imagerepo.json. TL;DR for the below... I'm still not sure why we keep getting these format changes, but we have added + removed all the trailing spaces several times in the history of the I suspect that the extra spaces are added by the use of idiff, especially combined with manual editing by contributors who can't remember / work out how to use idiff. Many editors would remove trailing spaces in python mode. So I thought the spaces might come where idiff uses a json.dump to recreate the file. |
* Fix for small plot changes with freetype 2.10. * Remove spurious end-of-line spaces in imagerepo.json.
* Fix for small plot changes with freetype 2.10. * Remove spurious end-of-line spaces in imagerepo.json.
* Fix for small plot changes with freetype 2.10. * Remove spurious end-of-line spaces in imagerepo.json.
HISTORY NOTE
Used to contain a lot of trial code attempting to make 'test_image_json' work.
I've taken all that out again, as that solution now lies in #3308
So this can now be merged ok.
SciTools/test-iris-imagehash#22 relates, but that is now merged.