[Python-Dev] SystemErrors in generator (just happened in 2.5) (original) (raw)

Tim Peters tim.peters at gmail.com
Mon Apr 16 21:57:31 CEST 2007

[Neal Norwitz]

There were some SystemErrors on one of the Windows build slaves.

Not always, though -- looks to be rare.

Does anyone have any ideas what might be the cause? I looked through about 5 previous logs on the same slave and didn't see the same problem.

I'm home today and fired up my slave, and no problem there either.

I haven't seen this myself and I don't know if it's WIndows specific. I don't know if this has happened on the trunk or just 2.5.

Me neither.

For the full log see: http://python.org/dev/buildbot/2.5/x86%20XP%202.5/builds/197/step-test/0

n -- *** Previous context (I don't think this really matters): Re-running test 'testprofilehooks' in verbose mode testcaughtexception (test.testprofilehooks.ProfileHookTestCase) ... ok testcaughtnestedexception (test.testprofilehooks.ProfileHookTestCase) ... ok testdistantexception (test.testprofilehooks.ProfileHookTestCase) ... ok testexception (test.testprofilehooks.ProfileHookTestCase) ... ok testexceptioninexceptclause (test.testprofilehooks.ProfileHookTestCase) ... ok testexceptionpropogation (test.testprofilehooks.ProfileHookTestCase) ... ok testgenerator (test.testprofilehooks.ProfileHookTestCase) ... ok testnestedexception (test.testprofilehooks.ProfileHookTestCase) ... ok testraise (test.testprofilehooks.ProfileHookTestCase) ... ok testraisereraise (test.testprofilehooks.ProfileHookTestCase) ... ok testraisetwice (test.testprofilehooks.ProfileHookTestCase) ... ok testsimple (test.testprofilehooks.ProfileHookTestCase) ... ok teststopiteration (test.testprofilehooks.ProfileHookTestCase) ... ok testbasicexception (test.testprofilehooks.ProfileSimulatorTestCase) ... ok testcaughtexception (test.testprofilehooks.ProfileSimulatorTestCase) ... ok testdistantexception (test.testprofilehooks.ProfileSimulatorTestCase) ... ok testsimple (test.testprofilehooks.ProfileSimulatorTestCase) ... ok ---------------------------------------------------------------------- Ran 17 tests in 0.016s OK *** Here is the problem: Exception exceptions.SystemError: 'error return without exception set' in <generator object at 0x00CCCDF8> ignored Exception exceptions.SystemError: 'error return without exception set' in <generator object at 0x010891F8> ignored Exception exceptions.SystemError: 'error return without exception set' in <generator object at 0x01089578> ignored Exception exceptions.SystemError: 'error return without exception set' in <generator object at 0x01089838> ignored Exception exceptions.SystemError: 'error return without exception set' in <generator object at 0x00D3BFB8> ignored

*** The following messages occur in other successful tests too: a DOS box should flash briefly ...

Always happens in test_subprocess, during the Windows-specific test_creationflags. This is expected. When you /watch/ the tests running on Windows, it's intended to prevent panic when a mysterious DOS box appears ;-)

findlibrary('c') -> None findlibrary('m') -> None

Mysterious. Looks like debug/trace(!) output while running Lib/ctypes/test/test_loading.py's test_find().

C:\buildbotpy25\2.5.mcintyre-windows\build\lib\test\testunicodefile.py:103: UnicodeWarning: Unicode equal comparison failed to convert both arguments to Unicode - interpreting them as being unequal filename1==filename2 C:\buildbotpy25\2.5.mcintyre-windows\build\lib\shutil.py:36: UnicodeWarning: Unicode equal comparison failed to convert both arguments to Unicode - interpreting them as being unequal os.path.normcase(os.path.abspath(dst)))

Those started showing up months ago.

warning: DBTxn aborted in destructor. No prior commit() or abort().

Likewise, from the bsddb test, and we've been seeing this one on Unixish boxes too.

More information about the Python-Dev mailing list