@zooba

It looks like fixing test.bat fixed the test_socket failures. It passed on 3 buildbot builds in a row (2 debug, 1 retail, 2nd retail build is still running). I'm keeping an eye on this one to make sure it's not still timing out sometimes.

There are still failures in test_time and test_strptime

The failures in test_time have the same root cause inside the CRT as the other time bug I worked around (_tznames[] returns empty strings). timemodule.c (line 503) strftime(zone, sizeof(zone), "%Z", &buf); returns "" in zone

All of the tests in test_strptime have a ‘%Z’ in them. Which is the format string which when passed to strftime in timemodule.c that returns an empty string (should print the timezone).

Do you think I should try to workaround all of the %Z failures? Fixing all of the place strftime or strptime is used looks more complicated than fixing time.tznames was.