← Back to team overview

launchpad-dev team mailing list archive

Re: Odd Windmill messages in buildbot logs

 

On January 26, 2010, Curtis Hovey wrote:
> On Tue, 2010-01-26 at 16:04 -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_resu
> >lts: 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'}
> 
> This message has been appearing for as long as I recall with this test.
> 

That's unfortunate logging on the part of Windmill. It is caused by the login 
code that checks first if the user is already logged in as the requested user. 
The client side shouldn't log an error if assertion=False is used. (We want to 
check the existence of a node, but not fail if it's not present.)


-- 
Francis J. Lacoste
francis.lacoste@xxxxxxxxxxxxx

Attachment: signature.asc
Description: This is a digitally signed message part.


References