test_normalization failures across community buildbots
Almost all community buildbots have failed the test step due to a failure in test_normalization. Here's a link to the community farm for the trunk:
http://www.python.org/dev/buildbot/community/trunk/
And here's an example of a failure:
http://www.python.org/dev/buildbot/community/trunk/x86%20OSX%20trunk/builds/...
test test_normalization failed -- Traceback (most recent call last): File "/Users/builder/pybots/pybot/trunk.osaf-x86/build/Lib/test/test_normalization.py", line 36, in test_main for line in open_urlresource(TESTDATAURL): File "/Users/builder/pybots/pybot/trunk.osaf-x86/build/Lib/test/test_support.py", line 271, in open_urlresource requires('urlfetch') File "/Users/builder/pybots/pybot/trunk.osaf-x86/build/Lib/test/test_support.py", line 94, in requires raise ResourceDenied(msg) ResourceDenied: Use of the `urlfetch' resource not enabled
Grig
On 4/16/07, Grig Gheorghiu grig.gheorghiu@gmail.com wrote:
Almost all community buildbots have failed the test step due to a failure in test_normalization. Here's a link to the community farm for the trunk:
http://www.python.org/dev/buildbot/community/trunk/
And here's an example of a failure:
http://www.python.org/dev/buildbot/community/trunk/x86%20OSX%20trunk/builds/...
test test_normalization failed -- Traceback (most recent call last): File "/Users/builder/pybots/pybot/trunk.osaf-x86/build/Lib/test/test_normalization.py", line 36, in test_main for line in open_urlresource(TESTDATAURL): File "/Users/builder/pybots/pybot/trunk.osaf-x86/build/Lib/test/test_support.py", line 271, in open_urlresource requires('urlfetch') File "/Users/builder/pybots/pybot/trunk.osaf-x86/build/Lib/test/test_support.py", line 94, in requires raise ResourceDenied(msg) ResourceDenied: Use of the `urlfetch' resource not enabled
Don't know what suddenly triggered this (nothing I did), but the code basically looks correct. What should be happening is regrtest should be catching that exception and just saying the test was skipped.
The last commit on regrtest was March 12, test_support was touched April 3, and test_normalization on April 5 according to ``svn log -r COMMITTED``.
-Brett
On 4/16/07, Brett Cannon brett@python.org wrote:
Don't know what suddenly triggered this (nothing I did), but the code basically looks correct. What should be happening is regrtest should be catching that exception and just saying the test was skipped.
The last commit on regrtest was March 12, test_support was touched April 3, and test_normalization on April 5 according to ``svn log -r COMMITTED``.
There's a check-in related to test_normalization.py on April 5th that seems to have triggered the failures:
http://www.python.org/dev/buildbot/community/trunk/changes/1292
Sorry I haven't reported this sooner, I've been swamped the last couple weeks.
Grig
On 4/16/07, Grig Gheorghiu grig.gheorghiu@gmail.com wrote:
On 4/16/07, Brett Cannon brett@python.org wrote:
Don't know what suddenly triggered this (nothing I did), but the code basically looks correct. What should be happening is regrtest should be catching that exception and just saying the test was skipped.
The last commit on regrtest was March 12, test_support was touched April
3,
and test_normalization on April 5 according to ``svn log -r COMMITTED``.
There's a check-in related to test_normalization.py on April 5th that seems to have triggered the failures:
http://www.python.org/dev/buildbot/community/trunk/changes/1292
Sorry I haven't reported this sooner, I've been swamped the last couple weeks.
That's Collin's checkin when he updated the test to use unittest. Any ideas, Collin?
-Brett
On 4/16/07, Brett Cannon brett@python.org wrote:
On 4/16/07, Grig Gheorghiu grig.gheorghiu@gmail.com wrote:
On 4/16/07, Brett Cannon brett@python.org wrote:
Don't know what suddenly triggered this (nothing I did), but the code basically looks correct. What should be happening is regrtest should be catching that exception and just saying the test was skipped.
The last commit on regrtest was March 12, test_support was touched April
3,
and test_normalization on April 5 according to ``svn log -r COMMITTED``.
There's a check-in related to test_normalization.py on April 5th that seems to have triggered the failures:
http://www.python.org/dev/buildbot/community/trunk/changes/1292
Sorry I haven't reported this sooner, I've been swamped the last couple
weeks.
That's Collin's checkin when he updated the test to use unittest. Any ideas, Collin?
This should be fixed in r54844. The problem was that the availability of the urlfetch resource wasn't being checked early enough and so test_support.run_suite() was converting the ResourceDenied exception into a TestError instance. This wasn't showing up on other machines since the urlfetch'd files weren't being cleaned out between test runs.
Collin Winter
[Collin Winter]
This should be fixed in r54844. The problem was that the availability of the urlfetch resource wasn't being checked early enough and so test_support.run_suite() was converting the ResourceDenied exception into a TestError instance. This wasn't showing up on other machines since the urlfetch'd files weren't being cleaned out between test runs.
Can you add code to clean them out between runs?
Raymond
On 4/16/07, Raymond Hettinger python@rcn.com wrote:
[Collin Winter]
This should be fixed in r54844. The problem was that the availability of the urlfetch resource wasn't being checked early enough and so test_support.run_suite() was converting the ResourceDenied exception into a TestError instance. This wasn't showing up on other machines since the urlfetch'd files weren't being cleaned out between test runs.
Can you add code to clean them out between runs?
I'll see what I can do.
Collin
participants (4)
-
Brett Cannon -
Collin Winter -
Grig Gheorghiu -
Raymond Hettinger