On my Win10-64 machine, test_winreg hangs, impervious to ^C.  I have to close Command Prompt.  (With IDLE I can run just test_winreg and then Restart Shell.)  This happened with repository builds last Friday and today, and with installed 3.6.2rc1.  But I believe I ran the entire test suite (to successful completion) not too many days before.The culprit is    def test_dynamic_key(self):        #Issue2810, when the value is dynamically generated, these        # raise "WindowsError: More data is available" in 2.6 and 3.1        try:            EnumValue(HKEY_PERFORMANCE_DATA, 0)        except OSError as e:            if e.errno in (errno.EPERM, errno.EACCES):                self.skipTest("access denied to registry key "                              "(are you running in a non-interactive session?)")            raise        QueryValueEx(HKEY_PERFORMANCE_DATA, "")Commenting out the whole function or both the EnumValue and QueryValueEx calls (replacing the former with pass) is required to allow the test to run (and pass).I have no idea why behavior on my machine is different from buildbots.  If the problem is with my registry, could the test be more robust?  Having to kill my console session, and lose history, after running the test suite, is unpleasant.

Ping.  I still cannot run the test suite to completion, so I cannot tell whether I add a warning failure regression.  Does anyone else have the same problem?  Should I patch the file to skip this test?

I just found -x test_winreg so I can run the test suite while waiting for this to be fixed.

What's the status of this issue?  It was previous marked as a "release blocker" and I subsequently downgraded it to a "deferred blocker" so as not to hold up releases.  Since a few maintenance releases have gone by without any action, I am removing the "deferred Blocker" status now.  Any one have any ideas?

test_winreg now works, taking about 5 seconds.  It has been working recently but I dont' know when or why the problem disappeared.