<br><br><div><span class="gmail_quote">On 4/16/07, <b class="gmail_sendername">Grig Gheorghiu</b> <<a href="mailto:grig.gheorghiu@gmail.com">grig.gheorghiu@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On 4/16/07, Brett Cannon <<a href="mailto:brett@python.org">brett@python.org</a>> wrote:<br>> Don't know what suddenly triggered this (nothing I did), but the code<br>> basically looks correct. What should be happening is regrtest should be
<br>> catching that exception and just saying the test was skipped.<br>><br>> The last commit on regrtest was March 12, test_support was touched April 3,<br>> and test_normalization on April 5 according to ``svn log -r COMMITTED``.
<br>><br><br>There's a check-in related to test_normalization.py on April 5th that<br>seems to have triggered the failures:<br><br><a href="http://www.python.org/dev/buildbot/community/trunk/changes/1292">http://www.python.org/dev/buildbot/community/trunk/changes/1292
</a><br><br>Sorry I haven't reported this sooner, I've been swamped the last couple weeks.</blockquote><div><br><br>That's Collin's checkin when he updated the test to use unittest. Any ideas, Collin?<br>
<br>-Brett <br></div><br></div><br>