librelist archives

« back to archive

osb failing tests

osb failing tests

From:
Giles Baxter
Date:
2010-06-12 @ 18:20
Hi,

I'm working through the osb deployment example (but with Python 2.6.5 and
Lamson 1.0), and when I run nosetests I don't just get the 2 expected
warnings.

Instead I get 10 failures.  One of these is AssertionError: Expected
'confirm' when sending... in test_new_user_comments

The captured stdout shows MESSAGE IN QUEUE, so msg must have been None.  Is
the failure of this assertion necessarily an error?  If I understand the
purpose of the test, it seems like the delayed confirmation might be a valid
state.

I'm just starting out with Lamson, so if anyone's encountered this or has
any insight I'd be most grateful!

Thanks
Giles

Re: [lamson] osb failing tests

From:
Zed A. Shaw
Date:
2010-06-12 @ 18:40
On Sun, Jun 13, 2010 at 04:20:22AM +1000, Giles Baxter wrote:
> Hi,
> 
> I'm working through the osb deployment example (but with Python 2.6.5 and
> Lamson 1.0), and when I run nosetests I don't just get the 2 expected
> warnings.
> 
> Instead I get 10 failures.  One of these is AssertionError: Expected
> 'confirm' when sending... in test_new_user_comments
> 
> The captured stdout shows MESSAGE IN QUEUE, so msg must have been None.  Is
> the failure of this assertion necessarily an error?  If I understand the
> purpose of the test, it seems like the delayed confirmation might be a valid
> state.
> 
> I'm just starting out with Lamson, so if anyone's encountered this or has
> any insight I'd be most grateful!

Hmm, I haven't actually ran that example in a while so it's possible it
had bit rotted some.  Can you submit a bug report:

http://support.lamsonproject.org/tktnew

Use the <verbatim></verbatim> tag to wrap outputs and code so I can
track it down.  If you're feeling adventurous you could also try to fix
it and then submit a patch.

-- 
Zed A. Shaw
http://zedshaw.com/

Re: [lamson] osb failing tests

From:
Giles Baxter
Date:
2010-06-13 @ 10:48
The tests passed when I used the full lamson server ('lamson start') instead
of the logging only server.

I'll submit a bug report with what I found (basically the logging server
isn't reachable on my setup).

On Sun, Jun 13, 2010 at 4:40 AM, Zed A. Shaw <zedshaw@zedshaw.com> wrote:

> On Sun, Jun 13, 2010 at 04:20:22AM +1000, Giles Baxter wrote:
> > Hi,
> >
> > I'm working through the osb deployment example (but with Python 2.6.5 and
> > Lamson 1.0), and when I run nosetests I don't just get the 2 expected
> > warnings.
> >
> > Instead I get 10 failures.  One of these is AssertionError: Expected
> > 'confirm' when sending... in test_new_user_comments
> >
> > The captured stdout shows MESSAGE IN QUEUE, so msg must have been None.
>  Is
> > the failure of this assertion necessarily an error?  If I understand the
> > purpose of the test, it seems like the delayed confirmation might be a
> valid
> > state.
> >
> > I'm just starting out with Lamson, so if anyone's encountered this or has
> > any insight I'd be most grateful!
>
> Hmm, I haven't actually ran that example in a while so it's possible it
> had bit rotted some.  Can you submit a bug report:
>
> http://support.lamsonproject.org/tktnew
>
> Use the <verbatim></verbatim> tag to wrap outputs and code so I can
> track it down.  If you're feeling adventurous you could also try to fix
> it and then submit a patch.
>
> --
> Zed A. Shaw
> http://zedshaw.com/
>