> Tim Hatch wrote: >> In other testing news, it looks like the minimum Genshi version has >> increased again (beyond what I had on the OS X box), causing >> strange-looking failures running trac-admin. At some point we need to >> make a test for that to get an understandable failure. > > Yes, Christopher has merged the advanced-i18n branch back into trunk, > and we now require at least that revision. When you say "strange-looking > failures running trac-admin", I assume you mean that trac-admin refuses > to run because Genshi>=0.6dev-r1072 is not provided, right?
Yes, the unit test output shows 74 failures, none of which imply that it's a version issue. Functional test output is much better, containing a single failure with the traceback from the failed pkg_resources.require(). We should either skip the trac-admin tests when this requirement isn't met, or fail the whole test since running Trac without current Genshi isn't supported as far as I know. Unit: http://buildbot.timhatch.com/trac/builders/OS%20X%2010.5%20py26%20intel/builds/50/steps/unit%20tests/logs/stdio Functional: http://buildbot.timhatch.com/trac/builders/OS%20X%2010.5%20py26%20intel/builds/50/steps/functional%20tests/logs/stdio > I have also seen spurious failures due to random words being too long. > Some tests choose 5 random words e.g. for ticket summaries, and if all > words are relatively long, format_to_oneliner() shortens the summary > with an ellipsis, which makes some tests fail. Whoops. I've made patches locally for that, will test further and push up. Let me know of any other issues you notice. Tim -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en.
