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
test_strptime hangs sometimes on AMD64 Windows7 SP1 3.x buildbot #69476
Comments
The AMD64 Windows7 SP1 3.x buildbot randomly fails. Tests take a lot of time. I don't know if it's a slow hardware/VM, or if the system is very busy. By the way, regrtest is run with -j4 (run 4 tests in parallel). Example of errors: http://buildbot.python.org/all/builders/AMD64%20Windows7%20SP1%203.x/builds/6773/steps/test/logs/stdio command timed out: 3900 seconds without output, attempting to kill http://buildbot.python.org/all/builders/AMD64%20Windows7%20SP1%203.x/builds/6783/steps/test/logs/stdio command timed out: 3900 seconds without output, attempting to kill |
The system is a dedicated Quad CPU @2.66GHz with 8GB RAM and running the tests on an SSD. I doubt it is the hardware. Please note, it is the only 64-bit Windows buildbot AND the only multi-core Windows buildbot. So it catches lots of things that most others do not. Last chance I had to find the missing test, it was test__locale. Also note that 3.5 is passing just fine, so it is something particular to the 3.x branch. |
By the way, I'm surprised how slow is this buildbot. On Linux, running the whole test suite (399 tests) takes less than 5 minutes with -j4 on my PC (Intel i7-2600 @ 3.40GHz with 12 GB of RAM). Is Python much slower on Windows? Or the buildbot CPU is *much* slower than mine? |
Jeremy Kloth wrote:
That's not true anymore; in fact, all but David Bolen's XP and Windows 7 bots are 64-bit. Yours is the one one in the 'stable' set, but that classification is a bit out of date for the whole set. Current 64-bit Windows bots are yours, David Bolen's Windows8 and Windows10 bots, and my Windows8.1 Non-Debug bot.
This is still true, though. Victor Stinner wrote:
I think the test suite is significantly slower on Windows; I'm not certain about Python itself. It routinely takes well over 20 minutes on my Windows machines. The fact that the bot in question compiles in Debug configuration may also be playing into it; Debug config links with the debug CRT, which enables a bunch of extra checks at the CRT level. |
On Linux, I also run the Python test suite with Python compiled in Maybe the slowness comes from CRT checks, maybe. |
I was curious, so I checked: C:\Users\Zachary\code\hg.python.org\3.5>python.bat -m test.pystone C:\Users\Zachary\code\hg.python.org\3.5>python.bat -m test.pystone C:\Users\Zachary\code\hg.python.org\3.5>python.bat -m test.pystone These were run on a Windows 8.1 Virtualbox VM on a Mac. For reference, here's the results for the host machine using python3.5.0 from python.org: $ python3 -m test.pystone
Pystone(1.2) time for 50000 passes = 0.413982
This machine benchmarks at 120778 pystones/second |
It looks like the issue was a bug in setlocale() and that it was fixed in Windows! See the issue bpo-26624. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: