launchpad-dev team mailing list archive

[Bjorn Tillenius <bjorn@xxxxxxxxxxxxx>]

On Tue, Jan 26, 2010 at 04:04:04PM -0500, Gary Poster wrote:
> (I am not regarding this as a release-critical problem, but I thought I should raise this.)
> 
> Looking through the full buildbot results, I saw odd Windmill errors-that-were-not-errors.  For instance, look at this output
> 
> https://lpbuildbot.canonical.com/builders/db_lp/builds/456/steps/shell_7/logs/stdio
> 
> and look for the string "test_results: ERROR".
> 
> This happens four times in the output, each time at the beginning of a windmill suite.  Here's an example from Registry, that I asked Curtis to verify was not a problem as a spot check:
> 
> test_adding_milestone_on_addrelease_page (lp.registry.windmill.tests.test_add_milestone.TestAddMilestone)test_results: ERROR    Test Failure in test {'version': '0.1', 'suite_name': 'AddMilestone', 'result': False, 'starttime': '2010-0-26T15:50:39.752Z', 'output': None, 'debug': 'Looking up name loginpage_submit_login, failed.', 'params': {'name': 'loginpage_submit_login', 'uuid': '732522b4-0a64-11df-9cbc-12313b015491'}, 'endtime': '2010-0-26T15:50:39.753Z', 'method': 'asserts.assertNode'}
> 
> The testrunner does not count this as an error.

The testrunner does not count this as an error, because it's not an
error. It's just Windmill logging stuff as ERROR, when it really
shouldn't. This ahappens when you use asserts to check something, for
example if a node is present. There is a parameter you can pass in to
make the assert not fail, which is fine, except that you get those log
messages that look like errors.

The fix is simply to tell Windmill not to log anything. If Paul is build
engineer next month, I believe this issue will be fixed :)


-- 
Björn Tillenius | https://launchpad.net/~bjornt