From: Raymond F. <ray...@de...> - 2018-10-25 18:14:36
|
There is this little bit of code in __builtin__.unichr that creates a hole in unicode values for utf-16 encoding. if (i >= 0xD800 && i <= 0xDFFF) { throw Py.ValueError("unichr() arg is a lone surrogate in range (0xD800, 0xDFFF) (Jython UTF-16 encoding)"); } Anyway... I don't see any way that test_normalization can pass given that sys.max_unicode > 0xd800 and one of the tests does a for range(sys.maxunicode) unichr(...). Strangely though, this does pass from travis-ci.org. Apparently there is some sort of reactive blocking in place that will drop connections to www.unicode.org from your IP if you trigger something, probably rate of get requests for test files. The test in question grabs a file from www.unicode.org and skips the test on timeout, so it doesn't hit the part of the test that will always fail. Anyway, after troubleshooting for a while, I managed to trigger this and suddenly can't reach unicode.org from my LAN, but if I switch my phone over to mobile data for a new source address, clearly the site is still up. I can even ping it but tcp syn is dropped. I've also noticed that urllib2 tests work fine from my network, but fail on travis-ci. My guess is that the at least one of the test targets are taking steps to reduce impact of being hard coded into so many CI tests. *Ray Ferguson* *Enterprise Solutions Developer* *Devendor Tech LLC* *ray...@de...* <ray...@de...> *W: 608-960-8090 C: 608-516-9391* ᐧ |