From jjinux at gmail.com  Wed Oct  4 23:56:42 2006
From: jjinux at gmail.com (Shannon -jj Behrens)
Date: Wed, 4 Oct 2006 14:56:42 -0700
Subject: [py-dev] greenlets: IO based scheduler
Message-ID: <c41f67b90610041456n6396b626t2fbb6582d5d125ed@mail.gmail.com>

I just learned about Greenlets today, and I can't seem to learn
enough.  The library as is is very nice, simple, and complete, but I'm
wondering if anyone is successfully using it for network servers yet?
Specifically, I'd like an IO-based scheduler based on Greenlets and
select.poll().  Can someone point me in the right direction?

Thanks,
-jj

-- 
The one who gets the last laugh isn't the one who did the laughing,
but rather the one who did the writing.


From mwh at python.net  Thu Oct  5 10:08:24 2006
From: mwh at python.net (Michael Hudson)
Date: Thu, 05 Oct 2006 09:08:24 +0100
Subject: [py-dev] greenlets: IO based scheduler
In-Reply-To: <c41f67b90610041456n6396b626t2fbb6582d5d125ed@mail.gmail.com>
	(Shannon's message of "Wed, 4 Oct 2006 14:56:42 -0700")
References: <c41f67b90610041456n6396b626t2fbb6582d5d125ed@mail.gmail.com>
Message-ID: <2mpsd7dw1z.fsf@starship.python.net>

"Shannon -jj Behrens" <jjinux at gmail.com> writes:

> I just learned about Greenlets today, and I can't seem to learn
> enough.  The library as is is very nice, simple, and complete, but I'm
> wondering if anyone is successfully using it for network servers yet?
> Specifically, I'd like an IO-based scheduler based on Greenlets and
> select.poll().  Can someone point me in the right direction?

There's some stuff in here:

http://codespeak.net/svn/user/arigo/hack/pypeers/

But maybe it would be best if Armin explained it (I'll be listening
too :-).

Cheers,
mwh

-- 
  <glyph> "Fetch me my internet pants."
                                                -- from Twisted.Quotes


From grig at agilistas.org  Fri Oct  6 17:05:08 2006
From: grig at agilistas.org (Grig Gheorghiu)
Date: Fri, 6 Oct 2006 08:05:08 -0700
Subject: [py-dev] Running py lib unit tests in Pybots
Message-ID: <dd49cdd20610060805l16d7cc00v23550983c936193f@mail.gmail.com>

Hi, guys

Not sure you've seen any of my announcements on the Pybots buildbot farm (<
http://pybots.org>). I was thinking it would be cool to run the py lib unit
tests on one of the buildslaves (I can run them on one of my 2), or even
better, maybe you can contribute a buildslave :-)

In any case, let me know if you're OK with having the tests running in
Pybots.]

Grig
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20061006/a609f1a4/attachment.html>

From fijal at genesilico.pl  Sun Oct  8 22:55:44 2006
From: fijal at genesilico.pl (Maciek Fijalkowski)
Date: Sun, 08 Oct 2006 22:55:44 +0200
Subject: [py-dev] [pypy-dev] py.test bug
In-Reply-To: <20061008125020.72f527e0.simon@arrowtheory.com>
References: <20061008125020.72f527e0.simon@arrowtheory.com>
Message-ID: <452965D0.8070800@genesilico.pl>

Simon Burton wrote:

>Traceback (most recent call last):
>  File "/home/simon/bin/py.test", line 4, in ?
>    py.test.cmdline.main()
>  File "/home/simon/local/pypy/py/test/cmdline.py", line 17, in main
>    failures = session.main(args)
>  File "/home/simon/local/pypy/py/test/terminal/terminal.py", line 34, in main
>    return super(TerminalSession, self).main(args)
>  File "/home/simon/local/pypy/py/test/session.py", line 52, in main
>    self.footer(colitems)
>  File "/home/simon/local/pypy/py/test/terminal/terminal.py", line 167, in footer
>    self.failures()
>  File "/home/simon/local/pypy/py/test/terminal/terminal.py", line 262, in failures
>    self.repr_failure(colitem, outcome)
>  File "/home/simon/local/pypy/py/test/terminal/terminal.py", line 280, in repr_failure
>    handler(item, excinfo, traceback)
>  File "/home/simon/local/pypy/py/test/terminal/terminal.py", line 297, in repr_failure_tblong
>    firstsourceline = entry.getfirstlinesource()
>AttributeError: 'TracebackEntry' object has no attribute 'getfirstlinesource'
>
>
>Simon.
>_______________________________________________
>pypy-dev at codespeak.net
>http://codespeak.net/mailman/listinfo/pypy-dev
>  
>
You seem to have old version of py.test. Please update to svn trunk.



From holger at merlinux.de  Thu Oct 12 20:18:32 2006
From: holger at merlinux.de (holger krekel)
Date: Thu, 12 Oct 2006 20:18:32 +0200
Subject: [py-dev] [py-svn] r33226 - py/dist/py/test/rsession
In-Reply-To: <20061012121239.19D65101EC@code0.codespeak.net>
References: <20061012121239.19D65101EC@code0.codespeak.net>
Message-ID: <20061012181832.GE10672@solar.trillke.net>

Hi Maciej! 

what about a test for this?  At least on linux 
issuing specific "kill" commands etc. should work. 

And thinking about good ways to test such things 
helps to be confident about py.test-distributed ... 

best, 

    holger

On Thu, Oct 12, 2006 at 14:12 +0200, fijal at codespeak.net wrote:

> Author: fijal
> Date: Thu Oct 12 14:12:37 2006
> New Revision: 33226
> 
> Modified:
>    py/dist/py/test/rsession/rsession.py
> Log:
> Better signal reporting.
> 
> 
> Modified: py/dist/py/test/rsession/rsession.py
> ==============================================================================
> --- py/dist/py/test/rsession/rsession.py	(original)
> +++ py/dist/py/test/rsession/rsession.py	Thu Oct 12 14:12:37 2006
> @@ -98,7 +98,10 @@
>              host = event.channel.gateway.sshaddress
>              self.out.sep('_', "%s on %s" % 
>                  (" ".join(event.item.listnames()), host))
> -            self.repr_failure(event.item, event.outcome)
> +            if event.outcome.signal:
> +                self.repr_signal(event.item, event.outcome)
> +            else:
> +                self.repr_failure(event.item, event.outcome)
>      
>      def repr_failure(self, item, outcome): 
>          excinfo = outcome.excinfo
> @@ -117,7 +120,16 @@
>          if outcome.stderr:
>              self.out.sep('-', " Captured process stderr: ")
>              self.out.write(outcome.stderr)
> -        
> +    
> +    def repr_signal(self, item, outcome):
> +        signal = outcome.signal
> +        self.out.line("Received signal: %d" % outcome.signal)
> +        if outcome.stdout:
> +            self.out.sep('-', " Captured process stdout: ")
> +            self.out.write(outcome.stdout)
> +        if outcome.stderr:
> +            self.out.sep('-', " Captured process stderr: ")
> +            self.out.write(outcome.stderr)
>  
>      def repr_failure_tblong(self, item, excinfo, traceback):
>          for index, entry in py.builtin.enumerate(traceback): 
> _______________________________________________
> py-svn mailing list
> py-svn at codespeak.net
> http://codespeak.net/mailman/listinfo/py-svn
> 

-- 
merlinux GmbH       Steinbergstr. 42    31139 Hildesheim   
http://merlinux.de  tel +49 5121 20800 75 (fax 77) 


From holger at merlinux.de  Thu Oct 12 20:22:27 2006
From: holger at merlinux.de (holger krekel)
Date: Thu, 12 Oct 2006 20:22:27 +0200
Subject: [py-dev] [py-svn] r33226 - py/dist/py/test/rsession
In-Reply-To: <20061012181832.GE10672@solar.trillke.net>
References: <20061012121239.19D65101EC@code0.codespeak.net>
	<20061012181832.GE10672@solar.trillke.net>
Message-ID: <20061012182227.GF10672@solar.trillke.net>

On Thu, Oct 12, 2006 at 20:18 +0200, holger krekel wrote:
> what about a test for this?  At least on linux 
> issuing specific "kill" commands etc. should work. 

hum, even testing it by calling the function
might work - which would be a better "unit" test
than firing up sub sessions etc. 

    holger
 
> And thinking about good ways to test such things 
> helps to be confident about py.test-distributed ... 
> 
> best, 
> 
>     holger
> 
> On Thu, Oct 12, 2006 at 14:12 +0200, fijal at codespeak.net wrote:
> 
> > Author: fijal
> > Date: Thu Oct 12 14:12:37 2006
> > New Revision: 33226
> > 
> > Modified:
> >    py/dist/py/test/rsession/rsession.py
> > Log:
> > Better signal reporting.
> > 
> > 
> > Modified: py/dist/py/test/rsession/rsession.py
> > ==============================================================================
> > --- py/dist/py/test/rsession/rsession.py	(original)
> > +++ py/dist/py/test/rsession/rsession.py	Thu Oct 12 14:12:37 2006
> > @@ -98,7 +98,10 @@
> >              host = event.channel.gateway.sshaddress
> >              self.out.sep('_', "%s on %s" % 
> >                  (" ".join(event.item.listnames()), host))
> > -            self.repr_failure(event.item, event.outcome)
> > +            if event.outcome.signal:
> > +                self.repr_signal(event.item, event.outcome)
> > +            else:
> > +                self.repr_failure(event.item, event.outcome)
> >      
> >      def repr_failure(self, item, outcome): 
> >          excinfo = outcome.excinfo
> > @@ -117,7 +120,16 @@
> >          if outcome.stderr:
> >              self.out.sep('-', " Captured process stderr: ")
> >              self.out.write(outcome.stderr)
> > -        
> > +    
> > +    def repr_signal(self, item, outcome):
> > +        signal = outcome.signal
> > +        self.out.line("Received signal: %d" % outcome.signal)
> > +        if outcome.stdout:
> > +            self.out.sep('-', " Captured process stdout: ")
> > +            self.out.write(outcome.stdout)
> > +        if outcome.stderr:
> > +            self.out.sep('-', " Captured process stderr: ")
> > +            self.out.write(outcome.stderr)
> >  
> >      def repr_failure_tblong(self, item, excinfo, traceback):
> >          for index, entry in py.builtin.enumerate(traceback): 
> > _______________________________________________
> > py-svn mailing list
> > py-svn at codespeak.net
> > http://codespeak.net/mailman/listinfo/py-svn
> > 
> 
> -- 
> merlinux GmbH       Steinbergstr. 42    31139 Hildesheim   
> http://merlinux.de  tel +49 5121 20800 75 (fax 77) 
> _______________________________________________
> py-dev mailing list
> py-dev at codespeak.net
> http://codespeak.net/mailman/listinfo/py-dev
> 

-- 
merlinux GmbH       Steinbergstr. 42    31139 Hildesheim   
http://merlinux.de  tel +49 5121 20800 75 (fax 77) 


From grig at agilistas.org  Thu Oct 12 20:24:12 2006
From: grig at agilistas.org (Grig Gheorghiu)
Date: Thu, 12 Oct 2006 11:24:12 -0700
Subject: [py-dev] Running py lib unit tests in Pybots
In-Reply-To: <dd49cdd20610060805l16d7cc00v23550983c936193f@mail.gmail.com>
References: <dd49cdd20610060805l16d7cc00v23550983c936193f@mail.gmail.com>
Message-ID: <dd49cdd20610121124g1164c293vde41e3c99f5472c4@mail.gmail.com>

On 10/6/06, Grig Gheorghiu <grig at agilistas.org> wrote:
>
> Hi, guys
>
> Not sure you've seen any of my announcements on the Pybots buildbot farm
> (<http://pybots.org>). I was thinking it would be cool to run the py lib
> unit tests on one of the buildslaves (I can run them on one of my 2), or
> even better, maybe you can contribute a buildslave :-)
>
> In any case, let me know if you're OK with having the tests running in
> Pybots.]
>
> Grig
>


Replying to my own post, since I haven't seen any other replies.....I assume
silence means it's OK for me to go ahead and do it :-)

Grig
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20061012/853fdad4/attachment.html>

From hpk at trillke.net  Thu Oct 12 22:53:08 2006
From: hpk at trillke.net (holger krekel)
Date: Thu, 12 Oct 2006 22:53:08 +0200
Subject: [py-dev] Running py lib unit tests in Pybots
In-Reply-To: <dd49cdd20610121124g1164c293vde41e3c99f5472c4@mail.gmail.com>
References: <dd49cdd20610060805l16d7cc00v23550983c936193f@mail.gmail.com>
	<dd49cdd20610121124g1164c293vde41e3c99f5472c4@mail.gmail.com>
Message-ID: <20061012205308.GI10672@solar.trillke.net>

Hey Grig! 

On Thu, Oct 12, 2006 at 11:24 -0700, Grig Gheorghiu wrote:
> On 10/6/06, Grig Gheorghiu <grig at agilistas.org> wrote:
> >
> >Hi, guys
> >
> >Not sure you've seen any of my announcements on the Pybots buildbot farm
> >(<http://pybots.org>). I was thinking it would be cool to run the py lib
> >unit tests on one of the buildslaves (I can run them on one of my 2), or
> >even better, maybe you can contribute a buildslave :-)
> >
> >In any case, let me know if you're OK with having the tests running in
> >Pybots.]
> >
> >Grig

somehow i don't remember your mail - but i just looked now! 
And interesting as we are also tackling approaches for
distributing tests, buildfarms and whatnot.  Seems
to be a hot topic (and rightfully so!). 

> Replying to my own post, since I haven't seen any other replies.....I assume
> silence means it's OK for me to go ahead and do it :-)

even explicitely: go ahead and post here any problems :) 

best, 

    holger


From grig at agilistas.org  Fri Oct 13 00:32:45 2006
From: grig at agilistas.org (Grig Gheorghiu)
Date: Thu, 12 Oct 2006 15:32:45 -0700
Subject: [py-dev] Running py lib unit tests in Pybots
In-Reply-To: <20061012205308.GI10672@solar.trillke.net>
References: <dd49cdd20610060805l16d7cc00v23550983c936193f@mail.gmail.com>
	<dd49cdd20610121124g1164c293vde41e3c99f5472c4@mail.gmail.com>
	<20061012205308.GI10672@solar.trillke.net>
Message-ID: <dd49cdd20610121532k7f64e852m40aaaf6a9070b835@mail.gmail.com>

On 10/12/06, holger krekel <hpk at trillke.net> wrote:
>
> Hey Grig!
>
> On Thu, Oct 12, 2006 at 11:24 -0700, Grig Gheorghiu wrote:
> > On 10/6/06, Grig Gheorghiu <grig at agilistas.org> wrote:
> > >
> > >Hi, guys
> > >
> > >Not sure you've seen any of my announcements on the Pybots buildbot
> farm
> > >(<http://pybots.org>). I was thinking it would be cool to run the py
> lib
> > >unit tests on one of the buildslaves (I can run them on one of my 2),
> or
> > >even better, maybe you can contribute a buildslave :-)
> > >
> > >In any case, let me know if you're OK with having the tests running in
> > >Pybots.]
> > >
> > >Grig
>
> somehow i don't remember your mail - but i just looked now!
> And interesting as we are also tackling approaches for
> distributing tests, buildfarms and whatnot.  Seems
> to be a hot topic (and rightfully so!).
>
> > Replying to my own post, since I haven't seen any other replies.....I
> assume
> > silence means it's OK for me to go ahead and do it :-)
>
> even explicitely: go ahead and post here any problems :)


Great, thanks! Will do. If you guys also want to contribute a buildslave,
please let me know.

Grig
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20061012/52061f1e/attachment.html>

From grig at agilistas.org  Fri Oct 13 00:53:28 2006
From: grig at agilistas.org (Grig Gheorghiu)
Date: Thu, 12 Oct 2006 15:53:28 -0700
Subject: [py-dev] Running py lib unit tests in Pybots
In-Reply-To: <dd49cdd20610121532k7f64e852m40aaaf6a9070b835@mail.gmail.com>
References: <dd49cdd20610060805l16d7cc00v23550983c936193f@mail.gmail.com>
	<dd49cdd20610121124g1164c293vde41e3c99f5472c4@mail.gmail.com>
	<20061012205308.GI10672@solar.trillke.net>
	<dd49cdd20610121532k7f64e852m40aaaf6a9070b835@mail.gmail.com>
Message-ID: <dd49cdd20610121553rced54aagf3ca7a78b5d2d527@mail.gmail.com>

On 10/12/06, Grig Gheorghiu <grig at agilistas.org> wrote:
>
> On 10/12/06, holger krekel <hpk at trillke.net> wrote:
>
> > go ahead and post here any problems :)
>
>

OK, I just did an svn co of the py lib on an Ubuntu Breezy box and I get 2
failures when running py.test in the topmost directory:

________________________ entrypoint: test_importall[81]
________________________

    def check_import(modpath):
        print "checking import", modpath
>       assert __import__(modpath)

[/tmp/pylib/py/misc/testing/test_initpkg.py:67]
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _

    """

    from py.__.test.rsession.web import exported_methods
E   from pypy.translator.js.modules import _dom as dom
>   ImportError: No module named pypy.translator.js.modules

[/tmp/pylib/py/test/rsession/webjs.py:6]
- - - - - - - - - - - - - -  [81]: recorded stdout - - - - - - - - - - - - -
- -
checking import py.__.test.rsession.webjs

________________________________________________________________________________
______________________ entrypoint: test_slave_main_simple
______________________

    def test_slave_main_simple():
        res = []
        q = [None,
             funcpass_spec,
             funcfail_spec
            ]
        slave_main(q.pop, res.append, str(rootdir))
        assert len(res) == 2
        res_repr = [ReprOutcome(r) for r in res]
        assert not res_repr[0].passed
E       assert res_repr[1].passed
>       assert <ReprOutcome signal=0 passed=False skipped=None
setupfailure=False excinfo=<Ex...close()\n            self.retval =
marshal.loads(retval_data)]> stdout= stderr=>.passed

[/tmp/pylib/py/test/rsession/testing/test_slave.py:110]
________________________________________________________________________________
===== tests finished: 1168 passed, 2 failed, 53 skipped in 137.70 seconds
======


Looks like the first test tries to import something from pypy, which I
haven't checked out. The second test -- not sure why it fails. Are these
failures expected?

Grig
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20061012/c20687fa/attachment.html>

From cfbolz at gmx.de  Fri Oct 13 00:58:03 2006
From: cfbolz at gmx.de (Carl Friedrich Bolz)
Date: Fri, 13 Oct 2006 00:58:03 +0200
Subject: [py-dev] Running py lib unit tests in Pybots
In-Reply-To: <dd49cdd20610121553rced54aagf3ca7a78b5d2d527@mail.gmail.com>
References: <dd49cdd20610060805l16d7cc00v23550983c936193f@mail.gmail.com>	<dd49cdd20610121124g1164c293vde41e3c99f5472c4@mail.gmail.com>	<20061012205308.GI10672@solar.trillke.net>	<dd49cdd20610121532k7f64e852m40aaaf6a9070b835@mail.gmail.com>
	<dd49cdd20610121553rced54aagf3ca7a78b5d2d527@mail.gmail.com>
Message-ID: <452EC87B.9090707@gmx.de>

Grig Gheorghiu wrote:
> On 10/12/06, *Grig Gheorghiu* <grig at agilistas.org
> <mailto:grig at agilistas.org>> wrote:
> 
>     On 10/12/06, *holger krekel* <hpk at trillke.net
>     <mailto:hpk at trillke.net>> wrote:
> 
>         go ahead and post here any problems :) 
> 
> 
> 
> OK, I just did an svn co of the py lib on an Ubuntu Breezy box and I get
> 2 failures when running py.test in the topmost directory:
> 
> ________________________ entrypoint: test_importall[81]
> ________________________
> 
>     def check_import(modpath):
>         print "checking import", modpath
>>       assert __import__(modpath)
> 
> [/tmp/pylib/py/misc/testing/test_initpkg.py:67]
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> _ _ _ _
> 
>     """
> 
>     from py.__.test.rsession.web import exported_methods
> E   from pypy.translator.js.modules import _dom as dom
>>   ImportError: No module named pypy.translator.js.modules
> 
> [/tmp/pylib/py/test/rsession/webjs.py:6]
> - - - - - - - - - - - - - -  [81]: recorded stdout - - - - - - - - - - -
> - - - -
> checking import py.__.test.rsession.webjs
> 
> ________________________________________________________________________________
> 
> ______________________ entrypoint: test_slave_main_simple
> ______________________
> 
>     def test_slave_main_simple():
>         res = []
>         q = [None,
>              funcpass_spec,
>              funcfail_spec
>             ]
>         slave_main(q.pop, res.append, str(rootdir))
>         assert len(res) == 2
>         res_repr = [ReprOutcome(r) for r in res]
>         assert not res_repr[0].passed
> E       assert res_repr[1].passed
>>       assert <ReprOutcome signal=0 passed=False skipped=None
> setupfailure=False excinfo=<Ex...close()\n            self.retval =
> marshal.loads(retval_data)]> stdout= stderr=>.passed
> 
> [/tmp/pylib/py/test/rsession/testing/test_slave.py:110]
> ________________________________________________________________________________
> ===== tests finished: 1168 passed, 2 failed, 53 skipped in 137.70
> seconds ======
> 
> 
> Looks like the first test tries to import something from pypy, which I
> haven't checked out. The second test -- not sure why it fails. Are these
> failures expected?

I don't think they are, but they might go undetected (since we all have
pypy checked out :-)). In theory the code should make sure that if pypy
is not importable it still works (maybe skipping the test or something).
Will look into it.

Thanks for the reporting!

Cheers,

Carl Friedrich


From fijal at genesilico.pl  Fri Oct 13 01:25:52 2006
From: fijal at genesilico.pl (Maciek Fijalkowski)
Date: Fri, 13 Oct 2006 01:25:52 +0200
Subject: [py-dev] Running py lib unit tests in Pybots
In-Reply-To: <dd49cdd20610121553rced54aagf3ca7a78b5d2d527@mail.gmail.com>
References: <dd49cdd20610060805l16d7cc00v23550983c936193f@mail.gmail.com>	<dd49cdd20610121124g1164c293vde41e3c99f5472c4@mail.gmail.com>	<20061012205308.GI10672@solar.trillke.net>	<dd49cdd20610121532k7f64e852m40aaaf6a9070b835@mail.gmail.com>
	<dd49cdd20610121553rced54aagf3ca7a78b5d2d527@mail.gmail.com>
Message-ID: <452ECF00.5010707@genesilico.pl>

Grig Gheorghiu wrote:

> On 10/12/06, *Grig Gheorghiu* <grig at agilistas.org 
> <mailto:grig at agilistas.org>> wrote:
>
>     On 10/12/06, *holger krekel* <hpk at trillke.net
>     <mailto:hpk at trillke.net>> wrote:
>
>         go ahead and post here any problems :) 
>
>
>
> OK, I just did an svn co of the py lib on an Ubuntu Breezy box and I 
> get 2 failures when running py.test in the topmost directory:
>
> ________________________ entrypoint: test_importall[81] 
> ________________________
>
>     def check_import(modpath):
>         print "checking import", modpath
> >       assert __import__(modpath)
>
> [/tmp/pylib/py/misc/testing/test_initpkg.py:67]
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> _ _ _ _ _
>
>     """
>
>     from py.__.test.rsession.web import exported_methods
> E   from pypy.translator.js.modules import _dom as dom
> >   ImportError: No module named pypy.translator.js.modules
>
> [/tmp/pylib/py/test/rsession/webjs.py:6]
> - - - - - - - - - - - - - -  [81]: recorded stdout - - - - - - - - - - 
> - - - - -
> checking import py.__.test.rsession.webjs
>
> ________________________________________________________________________________ 
>
> ______________________ entrypoint: test_slave_main_simple 
> ______________________
>
>     def test_slave_main_simple():
>         res = []
>         q = [None,
>              funcpass_spec,
>              funcfail_spec
>             ]
>         slave_main(q.pop, res.append, str(rootdir))
>         assert len(res) == 2
>         res_repr = [ReprOutcome(r) for r in res]
>         assert not res_repr[0].passed
> E       assert res_repr[1].passed
> >       assert <ReprOutcome signal=0 passed=False skipped=None 
> setupfailure=False excinfo=<Ex...close()\n            self.retval = 
> marshal.loads(retval_data)]> stdout= stderr=>.passed
>
> [/tmp/pylib/py/test/rsession/testing/test_slave.py:110]
> ________________________________________________________________________________
> ===== tests finished: 1168 passed, 2 failed, 53 skipped in 137.70 
> seconds ======
>
>
> Looks like the first test tries to import something from pypy, which I 
> haven't checked out. The second test -- not sure why it fails. Are 
> these failures expected?
>
> Grig
>
>------------------------------------------------------------------------
>
>_______________________________________________
>py-dev mailing list
>py-dev at codespeak.net
>http://codespeak.net/mailman/listinfo/py-dev
>  
>
Ok, first one is fixed (blame me), while the second one is a bit 
misterious for me. Can you reproduce it?

Btw: I'm quite curious about that, can we get test reports if they fail 
to py-dev mailing list?


From grig at agilistas.org  Fri Oct 13 01:57:03 2006
From: grig at agilistas.org (Grig Gheorghiu)
Date: Thu, 12 Oct 2006 16:57:03 -0700
Subject: [py-dev] Running py lib unit tests in Pybots
In-Reply-To: <452ECF00.5010707@genesilico.pl>
References: <dd49cdd20610060805l16d7cc00v23550983c936193f@mail.gmail.com>
	<dd49cdd20610121124g1164c293vde41e3c99f5472c4@mail.gmail.com>
	<20061012205308.GI10672@solar.trillke.net>
	<dd49cdd20610121532k7f64e852m40aaaf6a9070b835@mail.gmail.com>
	<dd49cdd20610121553rced54aagf3ca7a78b5d2d527@mail.gmail.com>
	<452ECF00.5010707@genesilico.pl>
Message-ID: <dd49cdd20610121657s117a256ay8d3c2c89dec5cb4d@mail.gmail.com>

On 10/12/06, Maciek Fijalkowski <fijal at genesilico.pl> wrote:
>
> Grig Gheorghiu wrote:
>
> > On 10/12/06, *Grig Gheorghiu* <grig at agilistas.org
> > <mailto:grig at agilistas.org>> wrote:
> >
> >     On 10/12/06, *holger krekel* <hpk at trillke.net
> >     <mailto:hpk at trillke.net>> wrote:
> >
> >         go ahead and post here any problems :)
> >
> >
> >
> > OK, I just did an svn co of the py lib on an Ubuntu Breezy box and I
> > get 2 failures when running py.test in the topmost directory:
> >
> > ________________________ entrypoint: test_importall[81]
> > ________________________
> >
> >     def check_import(modpath):
> >         print "checking import", modpath
> > >       assert __import__(modpath)
> >
> > [/tmp/pylib/py/misc/testing/test_initpkg.py:67]
> > _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> > _ _ _ _ _
> >
> >     """
> >
> >     from py.__.test.rsession.web import exported_methods
> > E   from pypy.translator.js.modules import _dom as dom
> > >   ImportError: No module named pypy.translator.js.modules
> >
> > [/tmp/pylib/py/test/rsession/webjs.py:6]
> > - - - - - - - - - - - - - -  [81]: recorded stdout - - - - - - - - - -
> > - - - - -
> > checking import py.__.test.rsession.webjs
> >
> >
> ________________________________________________________________________________
> >
> > ______________________ entrypoint: test_slave_main_simple
> > ______________________
> >
> >     def test_slave_main_simple():
> >         res = []
> >         q = [None,
> >              funcpass_spec,
> >              funcfail_spec
> >             ]
> >         slave_main(q.pop, res.append, str(rootdir))
> >         assert len(res) == 2
> >         res_repr = [ReprOutcome(r) for r in res]
> >         assert not res_repr[0].passed
> > E       assert res_repr[1].passed
> > >       assert <ReprOutcome signal=0 passed=False skipped=None
> > setupfailure=False excinfo=<Ex...close()\n            self.retval =
> > marshal.loads(retval_data)]> stdout= stderr=>.passed
> >
> > [/tmp/pylib/py/test/rsession/testing/test_slave.py:110]
> >
> ________________________________________________________________________________
> > ===== tests finished: 1168 passed, 2 failed, 53 skipped in 137.70
> > seconds ======
> >
> >
> > Looks like the first test tries to import something from pypy, which I
> > haven't checked out. The second test -- not sure why it fails. Are
> > these failures expected?
> >
> > Grig
> >
> >------------------------------------------------------------------------
> >
> >_______________________________________________
> >py-dev mailing list
> >py-dev at codespeak.net
> >http://codespeak.net/mailman/listinfo/py-dev
> >
> >
> Ok, first one is fixed (blame me), while the second one is a bit
> misterious for me. Can you reproduce it?



I just enabled the testing of py.test on one of my Pybots buildslaves. The
current Pybots build farm is here:

http://www.python.org/dev/buildbot/community/all/

There are 2 tests that fail (the pypy one was fixed). See the output here:

http://www.python.org/dev/buildbot/community/all/x86%20Ubuntu%20Breezy%20trunk/builds/34/step-py.test/0

Btw: I'm quite curious about that, can we get test reports if they fail
> to py-dev mailing list?
>


I'm working on getting email notifications to work from the buildmaster,
which is hosted on python.org -- and there are some issues with outgoing
email from there. As soon as I solve this issue, I'll configure the
buildmaster so it sends notifications on py.test failures to this mailing
list.

Grig
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20061012/f92a5ace/attachment.html>

From fijal at genesilico.pl  Fri Oct 13 02:27:02 2006
From: fijal at genesilico.pl (Maciek Fijalkowski)
Date: Fri, 13 Oct 2006 02:27:02 +0200
Subject: [py-dev] Running py lib unit tests in Pybots
In-Reply-To: <dd49cdd20610121657s117a256ay8d3c2c89dec5cb4d@mail.gmail.com>
References: <dd49cdd20610060805l16d7cc00v23550983c936193f@mail.gmail.com>	
	<dd49cdd20610121124g1164c293vde41e3c99f5472c4@mail.gmail.com>	
	<20061012205308.GI10672@solar.trillke.net>	
	<dd49cdd20610121532k7f64e852m40aaaf6a9070b835@mail.gmail.com>	
	<dd49cdd20610121553rced54aagf3ca7a78b5d2d527@mail.gmail.com>	
	<452ECF00.5010707@genesilico.pl>
	<dd49cdd20610121657s117a256ay8d3c2c89dec5cb4d@mail.gmail.com>
Message-ID: <452EDD56.6090500@genesilico.pl>

Grig Gheorghiu wrote:

> On 10/12/06, *Maciek Fijalkowski* <fijal at genesilico.pl 
> <mailto:fijal at genesilico.pl>> wrote:
>
>     Grig Gheorghiu wrote:
>
>     > On 10/12/06, *Grig Gheorghiu* <grig at agilistas.org
>     <mailto:grig at agilistas.org>
>     > <mailto:grig at agilistas.org <mailto:grig at agilistas.org>>> wrote:
>     >
>     >     On 10/12/06, *holger krekel* <hpk at trillke.net
>     <mailto:hpk at trillke.net>
>     >     <mailto:hpk at trillke.net <mailto:hpk at trillke.net>>> wrote:
>     >
>     >         go ahead and post here any problems :)
>     >
>     >
>     >
>     > OK, I just did an svn co of the py lib on an Ubuntu Breezy box and I
>     > get 2 failures when running py.test in the topmost directory:
>     >
>     > ________________________ entrypoint: test_importall[81]
>     > ________________________
>     >
>     >     def check_import(modpath):
>     >         print "checking import", modpath
>     > >       assert __import__(modpath)
>     >
>     > [/tmp/pylib/py/misc/testing/test_initpkg.py:67]
>     > _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>     _ _ _
>     > _ _ _ _ _
>     >
>     >     """
>     >
>     >     from py.__.test.rsession.web import exported_methods
>     > E   from pypy.translator.js.modules import _dom as dom
>     > >   ImportError: No module named pypy.translator.js.modules
>     >
>     > [/tmp/pylib/py/test/rsession/webjs.py:6]
>     > - - - - - - - - - - - - - -  [81]: recorded stdout - - - - - - -
>     - - -
>     > - - - - -
>     > checking import py.__.test.rsession.webjs
>     >
>     >
>     ________________________________________________________________________________
>     >
>     > ______________________ entrypoint: test_slave_main_simple
>     > ______________________
>     >
>     >     def test_slave_main_simple():
>     >         res = []
>     >         q = [None,
>     >              funcpass_spec,
>     >              funcfail_spec
>     >             ]
>     >         slave_main(q.pop, res.append, str(rootdir))
>     >         assert len(res) == 2
>     >         res_repr = [ReprOutcome(r) for r in res]
>     >         assert not res_repr[0].passed
>     > E       assert res_repr[1].passed
>     > >       assert <ReprOutcome signal=0 passed=False skipped=None
>     > setupfailure=False excinfo=<Ex...close()\n            self.retval =
>     > marshal.loads(retval_data)]> stdout= stderr=>.passed
>     >
>     > [/tmp/pylib/py/test/rsession/testing/test_slave.py:110]
>     >
>     ________________________________________________________________________________
>     > ===== tests finished: 1168 passed, 2 failed, 53 skipped in 137.70
>     > seconds ======
>     >
>     >
>     > Looks like the first test tries to import something from pypy,
>     which I
>     > haven't checked out. The second test -- not sure why it fails. Are
>     > these failures expected?
>     >
>     > Grig
>     >
>     >------------------------------------------------------------------------
>     >
>     >_______________________________________________
>     >py-dev mailing list
>     > py-dev at codespeak.net <mailto:py-dev at codespeak.net>
>     >http://codespeak.net/mailman/listinfo/py-dev
>     >
>     >
>     Ok, first one is fixed (blame me), while the second one is a bit
>     misterious for me. Can you reproduce it?
>
>
>
> I just enabled the testing of py.test on one of my Pybots buildslaves. 
> The current Pybots build farm is here:
>
> http://www.python.org/dev/buildbot/community/all/
>
> There are 2 tests that fail (the pypy one was fixed). See the output here:
>
> http://www.python.org/dev/buildbot/community/all/x86%20Ubuntu%20Breezy%20trunk/builds/34/step-py.test/0
>
>     Btw: I'm quite curious about that, can we get test reports if they
>     fail
>     to py-dev mailing list?
>
>
>
> I'm working on getting email notifications to work from the 
> buildmaster, which is hosted on python.org <http://python.org> -- and 
> there are some issues with outgoing email from there. As soon as I 
> solve this issue, I'll configure the buildmaster so it sends 
> notifications on py.test failures to this mailing list.
>
> Grig

The both tests look serious, altough I do not know how to reproduce them 
(they do not fail for me). Can I get access to the machine or maybe a 
(detailed) list of packages installed and such?

If I can reproduce the errors, I'll try to fix them.

But it's 2:30 AM  for me, so not today...



From grig at agilistas.org  Fri Oct 13 02:50:00 2006
From: grig at agilistas.org (Grig Gheorghiu)
Date: Thu, 12 Oct 2006 17:50:00 -0700
Subject: [py-dev] Running py lib unit tests in Pybots
In-Reply-To: <452EDD56.6090500@genesilico.pl>
References: <dd49cdd20610060805l16d7cc00v23550983c936193f@mail.gmail.com>
	<dd49cdd20610121124g1164c293vde41e3c99f5472c4@mail.gmail.com>
	<20061012205308.GI10672@solar.trillke.net>
	<dd49cdd20610121532k7f64e852m40aaaf6a9070b835@mail.gmail.com>
	<dd49cdd20610121553rced54aagf3ca7a78b5d2d527@mail.gmail.com>
	<452ECF00.5010707@genesilico.pl>
	<dd49cdd20610121657s117a256ay8d3c2c89dec5cb4d@mail.gmail.com>
	<452EDD56.6090500@genesilico.pl>
Message-ID: <dd49cdd20610121750x30037568ie63be57fcc4e3360@mail.gmail.com>

On 10/12/06, Maciek Fijalkowski <fijal at genesilico.pl> wrote:
>
> > I just enabled the testing of py.test on one of my Pybots buildslaves.
> > The current Pybots build farm is here:
> >
> > http://www.python.org/dev/buildbot/community/all/
> >
> > There are 2 tests that fail (the pypy one was fixed). See the output
> here:
> >
> >
> http://www.python.org/dev/buildbot/community/all/x86%20Ubuntu%20Breezy%20trunk/builds/34/step-py.test/0
> >
> The both tests look serious, altough I do not know how to reproduce them
> (they do not fail for me). Can I get access to the machine or maybe a
> (detailed) list of packages installed and such?
>
> If I can reproduce the errors, I'll try to fix them.
>
> But it's 2:30 AM  for me, so not today...
>
>
I seem to remember that some execnet tests used to fail for me on some
platforms, kind of randomly. As for the other test (test_slave.py), I'm not
sure what's going on. If you can't reproduce these failures on any other
boxes you have, I'll let you have access on my box.

Grig
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20061012/6f636fc5/attachment.html>

From grig at agilistas.org  Fri Oct 13 03:13:46 2006
From: grig at agilistas.org (Grig Gheorghiu)
Date: Thu, 12 Oct 2006 18:13:46 -0700
Subject: [py-dev] py lib tests are passing on pybots buildslave
Message-ID: <dd49cdd20610121813j5f9083dbn387e5d02b8ed575f@mail.gmail.com>

On 10/12/06, Grig Gheorghiu <grig at agilistas.org> wrote:
>
> On 10/12/06, Maciek Fijalkowski <fijal at genesilico.pl> wrote:
> >
> > How recent your checkout is? I think I've fixed those problems (at least
> > one) like yesterday or so.
> >
>
>
> I delete the original directory, then I do a fresh checkout every time I
> test. It may be a platform-specific issue.
>
> Grig
>


OK, now all tests are passing.

http://www.python.org/dev/buildbot/community/all/x86%20Ubuntu%20Breezy%20trunk/builds/35/step-py.lib/0

Grig
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20061012/f9fb61fb/attachment.html>

From fijal at genesilico.pl  Fri Oct 13 09:21:32 2006
From: fijal at genesilico.pl (Maciek Fijalkowski)
Date: Fri, 13 Oct 2006 09:21:32 +0200
Subject: [py-dev] py lib tests are passing on pybots buildslave
In-Reply-To: <dd49cdd20610121813j5f9083dbn387e5d02b8ed575f@mail.gmail.com>
References: <dd49cdd20610121813j5f9083dbn387e5d02b8ed575f@mail.gmail.com>
Message-ID: <452F3E7C.70400@genesilico.pl>

Grig Gheorghiu wrote:

> On 10/12/06, *Grig Gheorghiu* <grig at agilistas.org 
> <mailto:grig at agilistas.org>> wrote:
>
>     On 10/12/06, *Maciek Fijalkowski* <fijal at genesilico.pl
>     <mailto:fijal at genesilico.pl>> wrote:
>
>         How recent your checkout is? I think I've fixed those problems
>         (at least
>         one) like yesterday or so.
>
>
>
>     I delete the original directory, then I do a fresh checkout every
>     time I test. It may be a platform-specific issue.
>
>     Grig
>
>
>
> OK, now all tests are passing.
>
> http://www.python.org/dev/buildbot/community/all/x86%20Ubuntu%20Breezy%20trunk/builds/35/step-py.lib/0 
> <http://www.python.org/dev/buildbot/community/all/x86%20Ubuntu%20Breezy%20trunk/builds/35/step-py.lib/0>
>
> Grig

Cool.

I suspect .pyc files or so...



From holger at merlinux.de  Mon Oct 16 23:30:07 2006
From: holger at merlinux.de (holger krekel)
Date: Mon, 16 Oct 2006 23:30:07 +0200
Subject: [py-dev] [py-svn] r33350 - in py/dist/py: . code test/rsession
In-Reply-To: <20061016204908.64B5A10068@code0.codespeak.net>
References: <20061016204908.64B5A10068@code0.codespeak.net>
Message-ID: <20061016213007.GX10672@solar.trillke.net>

Hi Maciej, 


On Mon, Oct 16, 2006 at 22:49 +0200, fijal at codespeak.net wrote:

> Author: fijal
> Date: Mon Oct 16 22:48:34 2006
> New Revision: 33350
> 
> Modified:
>    py/dist/py/__init__.py
>    py/dist/py/code/excinfo.py
>    py/dist/py/code/traceback2.py

could you add tests for this within py/code (not indirectly
through some py/test/rsession code)?  

best, 

    holger


From arigo at tunes.org  Sun Oct 22 21:03:53 2006
From: arigo at tunes.org (Armin Rigo)
Date: Sun, 22 Oct 2006 21:03:53 +0200
Subject: [py-dev] greenlets pickle support
In-Reply-To: <2af4014d0610200212h745ec9a7uc4290aeb4bc5af1c@mail.gmail.com>
References: <2af4014d0610200212h745ec9a7uc4290aeb4bc5af1c@mail.gmail.com>
Message-ID: <20061022190353.GB24285@code0.codespeak.net>

Hello,

On Fri, Oct 20, 2006 at 11:12:17AM +0200, Paolo Losi wrote:
> I'm looking at greenlets for a workflow engine project.
> It would be nice if greenlets execution state could be persisted
> via cPickle. Is pickle support planned / easy to implement?

Not at all.  To get this you need the full Stackless Python - or PyPy
:-)  But there is no way I can think of to make greenlet pickling even
remotely realizable.


A bientot,

Armin


From fijal at genesilico.pl  Sun Oct 22 22:39:30 2006
From: fijal at genesilico.pl (Maciek Fijalkowski)
Date: Sun, 22 Oct 2006 22:39:30 +0200
Subject: [py-dev] Note
Message-ID: <453BD702.2010002@genesilico.pl>

not to forget...

When writing tests for LSession/RSession and friends, there are two 
States of setups, one in tests and one in testing utility itself. They 
badly interfere (like setup_module called few times). I don't know if 
it's a bug or whatever. I can propose several things:
1. Not use setup_* in those tests (this is done by now)
2. Make sure that setup_module is never introduced twice for the same 
module (as a warning or whatever) - I think it's easy to implement and 
quite usefull, but still you cannot use two states
3. Make somehow two possible states - one for testing, one for running 
test suite, altough it's hard to do.


From elmo13 at jippii.fi  Mon Oct 23 01:56:33 2006
From: elmo13 at jippii.fi (=?UTF-8?B?RWxtbyBNw6RudHluZW4=?=)
Date: Mon, 23 Oct 2006 02:56:33 +0300
Subject: [py-dev] Global state
Message-ID: <453C0531.2000401@jippii.fi>

The tested code interfaces with hardware, so I have to share a handle
between tests which I wouldn't want to confine to a single module. I
used to share state by importing a common module from the test_modules,
but after updating pylib, even skipping every test but one doesn't seem
to work. It might be my fault, but I'd like to know what I should've
been doing so I can test who is really at fault.


Elmo


From hpk at trillke.net  Mon Oct 23 08:26:37 2006
From: hpk at trillke.net (holger krekel)
Date: Mon, 23 Oct 2006 08:26:37 +0200
Subject: [py-dev] Note
In-Reply-To: <453BD702.2010002@genesilico.pl>
References: <453BD702.2010002@genesilico.pl>
Message-ID: <20061023062637.GJ10672@solar.trillke.net>

On Sun, Oct 22, 2006 at 22:39 +0200, Maciek Fijalkowski wrote:
> not to forget...
> 
> When writing tests for LSession/RSession and friends, there are two 
> States of setups, one in tests and one in testing utility itself. They 
> badly interfere (like setup_module called few times). I don't know if 
> it's a bug or whatever. I can propose several things:
> 1. Not use setup_* in those tests (this is done by now)
> 2. Make sure that setup_module is never introduced twice for the same 
> module (as a warning or whatever) - I think it's easy to implement and 
> quite usefull, but still you cannot use two states
> 3. Make somehow two possible states - one for testing, one for running 
> test suite, altough it's hard to do.

can you give a more concrete example of what goes bad? 

    holger


From grig at agilistas.org  Thu Oct 26 23:20:33 2006
From: grig at agilistas.org (Grig Gheorghiu)
Date: Thu, 26 Oct 2006 14:20:33 -0700
Subject: [py-dev] py lib tests fail in Pybots buildbot
Message-ID: <dd49cdd20610261420r4b8c0363ieee0c7e3f8619d87@mail.gmail.com>

Noticed some new failures.

Full log for build step with Python trunk binary:

http://www.python.org/dev/buildbot/community/all/x86%20Ubuntu%20Breezy%20trunk/builds/63/step-py.lib/0

Full log for build step with Python 2.5 binary:

http://www.python.org/dev/buildbot/community/all/x86%20Ubuntu%20Breezy%202.5/builds/33/step-py.lib/0

Here are the errors from the 2.5 build step:

_________________ entrypoint: TestRest().test_class_typedefs __________________

    def test_class_typedefs(self):
        class A(object):
            def __init__(self, x):
                pass

        class B(object):
            def __init__(self, y):
                pass

        def xxx(x):
            return x

        descs = {'A':A, 'B':B, 'xxx':xxx}
        ds = DocStorage().from_dict(descs)
        t = Tracer(ds)
        t.start_tracing()
        xxx(A(3))
        xxx(B("f"))
        t.end_tracing()
        lg = DirectPaste()
        tempdir = temppath.ensure("classargs", dir=True)
        r = RestGen(ds, lg, DirWriter(tempdir))
>       r.write()

[/tmp/pylib/py/apigen/rest/testing/test_rest.py:285]
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

    def write(self):
        """write the data to the writer"""
        # note that this builds up a list of Rest elements for the index as
        # 'side effect', the list is passed along and filled, while the actual
        # sections (also ReST elements) are returned by the write_* methods
        # XXX this is quite icky! would be nice to have refactored
        indexlst = [Title("Module: %s" % self.dsa.get_module_name(),
                          belowchar="="),
                    Paragraph(self.dsa.get_module_info()),
                    Title("Exported functions:", belowchar="-")]
        funclst = self.write_function_list(indexlst)
        indexlst.append(Title("Exported classes:", belowchar="-"))
>       classlst = self.write_class_list(indexlst)

[/tmp/pylib/py/apigen/rest/genrest.py:128]
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

    def write_class_list(self, indexlst):
        retlst = []
        for name in self.dsa.get_class_names():
            sectionname = 'class_%s' % (name,)
            linktarget = self.writer.getlink('class', name, sectionname)
            indexlst.append(ListItem(Text("Class: "), Link(name, linktarget)))
>           retlst.append((sectionname, self.write_class(sectionname, name)))

[/tmp/pylib/py/apigen/rest/genrest.py:157]
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

    def write_class(self, section_name, class_name):
        classlst = [Title("Class: %s" % class_name, belowchar='-'),
                    LiteralBlock(self.dsa.get_function_doc(class_name))]

        # write down exported methods
        classlst.append(Title("Exported methods:", belowchar="^"))
        funclist = []
        for method in self.dsa.get_class_methods(class_name):
            sectionname = 'method_%s_%s' % (class_name, method)
            linktext = '%s.%s' % (class_name, method)
            linktarget = self.writer.getlink('function', linktext,
                                                  sectionname)
            classlst.append(ListItem(Link(linktext, linktarget)))
            # XXX assuming a function is always part of a class section
            funclist.append((sectionname,
                             self.write_function(sectionname,
                                                 class_name + "." + method,
>                                                '^')))

[/tmp/pylib/py/apigen/rest/genrest.py:177]
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

    def write_function(self, section_name, fun_name, belowchar='-'):
        # XXX I think the docstring should either be split on \n\n and cleaned
        # from indentation, or treated as ReST too (although this is obviously
        # dangerous for non-ReST docstrings)...
        lst = [Title("Function: %s" % fun_name, belowchar=belowchar),
               LiteralBlock(self.dsa.get_function_doc(fun_name)),
               LiteralBlock(self.dsa.get_function_definition(fun_name))]


        args, retval = self.dsa.get_function_signature(fun_name)
        arg_str = "\n".join(["%s :: %s" % (str(name), str(type)) for
name, type in args])
        arg_str += "\n" + "Return value :: %s" % str(retval)
        lst.append(Paragraph("where:"))
        lst.append(LiteralBlock(arg_str))

        # XXX missing implementation of dsa.get_function_location()
        #filename, lineno = self.dsa.get_function_location(fun_name)
        #linkname, linktarget = self.linkgen.getlink(filename, lineno)
        #if linktarget:
        #    lst.append(Paragraph("Function source: ",
        #               Link(linkname, linktarget)))
        #else:
        lst.append(Paragraph('Function source:'))
>       lst.append(LiteralBlock(self.dsa.get_function_source(fun_name)))

[/tmp/pylib/py/apigen/rest/genrest.py:203]
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

    def get_function_source(self, name):
        desc = self.ds.descs[name]
        try:
>           return str(py.code.Source(desc.pyobj))

[/tmp/pylib/py/apigen/tracer/docstorage.py:196]
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

    def __init__(self, *parts, **kwargs):
        self.lines = lines = []
        de = kwargs.get('deindent', True)
        rstrip = kwargs.get('rstrip', True)
        for part in parts:
            if not part:
                partlines = []
            if isinstance(part, Source):
                partlines = part.lines
            elif isinstance(part, (unicode, str)):
                partlines = part.split('\n')
                if rstrip:
                    while partlines:
                        if partlines[-1].strip():
                            break
                        partlines.pop()
            else:
>               partlines = getsource(part, deindent=de).lines

[/tmp/pylib/py/code/source.py:30]
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

    def getsource(obj, **kwargs):
        if hasattr(obj, 'func_code'):
            obj = obj.func_code
        elif hasattr(obj, 'f_code'):
            obj = obj.f_code
        try:
            fullsource = obj.co_filename.__source__
        except AttributeError:
>           strsrc = inspect.getsource(obj)

[/tmp/pylib/py/code/source.py:231]
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

    def getsource(object):
        """Return the text of the source code for an object.

        The argument may be a module, class, method, function, traceback, frame,
        or code object.  The source code is returned as a single string.  An
        IOError is raised if the source code cannot be retrieved."""
>       lines, lnum = getsourcelines(object)

[/usr/lib/python2.4/inspect.py:563]
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

    def getsourcelines(object):
        """Return a list of source lines and starting line number for an object.

        The argument may be a module, class, method, function, traceback, frame,
        or code object.  The source code is returned as a list of the lines
        corresponding to the object and the line number indicates where in the
        original source file the first line of code was found.  An IOError is
        raised if the source code cannot be retrieved."""
        lines, lnum = findsource(object)

        if ismodule(object): return lines, 0
>       else: return getblock(lines[lnum:]), lnum + 1

[/usr/lib/python2.4/inspect.py:555]
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

    def getblock(lines):
        """Extract the block of code at the top of the given list of lines."""
        try:
>           tokenize.tokenize(ListReader(lines).readline, BlockFinder().tokeneater)

[/usr/lib/python2.4/inspect.py:538]
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

    def tokenize(readline, tokeneater=printtoken):
        """
        The tokenize() function accepts two parameters: one representing the
        input stream, and one providing an output mechanism for tokenize().

        The first parameter, readline, must be a callable object which provides
        the same interface as the readline() method of built-in file objects.
        Each call to the function should return one line of input as a string.

        The second parameter, tokeneater, must also be a callable object. It is
        called once for each token, with five arguments, corresponding to the
        tuples generated by generate_tokens().
        """
        try:
>           tokenize_loop(readline, tokeneater)

[/usr/lib/python2.4/tokenize.py:153]
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

    def tokenize_loop(readline, tokeneater):
>       for token_info in generate_tokens(readline):

[/usr/lib/python2.4/tokenize.py:159]
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

    def generate_tokens(readline):
        """
        The generate_tokens() generator requires one argment, readline, which
        must be a callable object which provides the same interface as the
        readline() method of built-in file objects. Each call to the function
        should return one line of input as a string.

        The generator produces 5-tuples with these members: the token type; the
        token string; a 2-tuple (srow, scol) of ints specifying the row and
        column where the token begins in the source; a 2-tuple (erow, ecol) of
        ints specifying the row and column where the token ends in the source;
        and the line on which the token was found. The line passed is the
        logical line; continuation lines are included.
        """
        lnum = parenlev = continued = 0
        namechars, numchars = string.ascii_letters + '_', '0123456789'
        contstr, needcont = '', 0
        contline = None
        indents = [0]

        while 1:                                   # loop over lines in stream
            line = readline()
            lnum = lnum + 1
            pos, max = 0, len(line)

            if contstr:                            # continued string
                if not line:
                    raise TokenError, ("EOF in multi-line string", strstart)
                endmatch = endprog.match(line)
                if endmatch:
                    pos = end = endmatch.end(0)
                    yield (STRING, contstr + line[:end],
                               strstart, (lnum, end), contline + line)
                    contstr, needcont = '', 0
                    contline = None
                elif needcont and line[-2:] != '\\\n' and line[-3:] != '\\\r\n':
                    yield (ERRORTOKEN, contstr + line,
                               strstart, (lnum, len(line)), contline)
                    contstr = ''
                    contline = None
                    continue
                else:
                    contstr = contstr + line
                    contline = contline + line
                    continue

            elif parenlev == 0 and not continued:  # new statement
                if not line: break
                column = 0
                while pos < max:                   # measure leading whitespace
                    if line[pos] == ' ': column = column + 1
                    elif line[pos] == '\t': column = (column/tabsize +
1)*tabsize
                    elif line[pos] == '\f': column = 0
                    else: break
                    pos = pos + 1
                if pos == max: break

                if line[pos] in '#\r\n':           # skip comments or
blank lines
                    yield ((NL, COMMENT)[line[pos] == '#'], line[pos:],
                               (lnum, pos), (lnum, len(line)), line)
                    continue

                if column > indents[-1]:           # count indents or dedents
                    indents.append(column)
                    yield (INDENT, line[:pos], (lnum, 0), (lnum, pos), line)
                while column < indents[-1]:
                    if column not in indents:
E                       raise IndentationError(
                            "unindent does not match any outer
indentation level")
>                       IndentationError: unindent does not match any outer indentation level

[/usr/lib/python2.4/tokenize.py:229]
_______________________________________________________________________________
______ entrypoint: TestPopenGateway().test_channel_passing_over_channel _______

    def test_channel_passing_over_channel(self):
        channel = self.gw.remote_exec('''
                        c = channel.gateway.newchannel()
                        channel.send(c)
                        c.send(42)
                      ''')
        c = channel.receive()
        x = c.receive()
        assert x == 42

        # check that the both sides previous channels are really gone
        channel.waitclose(0.3)
E       assert channel.id not in self.gw.channelfactory._channels
>       AssertionError: (inconsistently failed then succeeded)

[/tmp/pylib/py/execnet/testing/test_gateway.py:160]
_______________________________________________________________________________
_______________________ entrypoint: test_importall[226] _______________________

    def check_import(modpath):
        print "checking import", modpath
E       assert __import__(modpath)
>       ImportError: No module named package.submodule.__init__

[/tmp/pylib/py/misc/testing/test_initpkg.py:67]
- - - - - - - - - - - - -  [226]: recorded stdout - - - - - - - - - - - - - -
checking import py.__.apigen.tracer.testing.package.submodule.__init__

_______________________________________________________________________________
_______________________ entrypoint: test_importall[227] _______________________

    def check_import(modpath):
        print "checking import", modpath
E       assert __import__(modpath)
>       ImportError: No module named package.submodule.pak.__init__

[/tmp/pylib/py/misc/testing/test_initpkg.py:67]
- - - - - - - - - - - - -  [227]: recorded stdout - - - - - - - - - - - - - -
checking import py.__.apigen.tracer.testing.package.submodule.pak.__init__

_______________________________________________________________________________
_______________________ entrypoint: test_importall[228] _______________________

    def check_import(modpath):
        print "checking import", modpath
E       assert __import__(modpath)
>       ImportError: No module named package.submodule.pak.mod

[/tmp/pylib/py/misc/testing/test_initpkg.py:67]
- - - - - - - - - - - - -  [228]: recorded stdout - - - - - - - - - - - - - -
checking import py.__.apigen.tracer.testing.package.submodule.pak.mod

_______________________________________________________________________________
===== tests finished: 1256 passed, 5 failed, 55 skipped in 154.12 seconds =====
inserting into sys.path: /tmp/pylib
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20061026/79a1c53d/attachment.html>

From fijal at genesilico.pl  Fri Oct 27 15:51:01 2006
From: fijal at genesilico.pl (Maciek Fijalkowski)
Date: Fri, 27 Oct 2006 15:51:01 +0200
Subject: [py-dev] py lib tests fail in Pybots buildbot
In-Reply-To: <dd49cdd20610261420r4b8c0363ieee0c7e3f8619d87@mail.gmail.com>
References: <dd49cdd20610261420r4b8c0363ieee0c7e3f8619d87@mail.gmail.com>
Message-ID: <45420EC5.8000407@genesilico.pl>

Thanks. I've fixed one of the errors, 3 to fix and one which I cannot
reproduce. Just for the interest: are there more than one projects which
involve py.test on pybots?



From grig at agilistas.org  Fri Oct 27 17:52:32 2006
From: grig at agilistas.org (Grig Gheorghiu)
Date: Fri, 27 Oct 2006 08:52:32 -0700
Subject: [py-dev] py lib tests fail in Pybots buildbot
In-Reply-To: <45420EC5.8000407@genesilico.pl>
References: <dd49cdd20610261420r4b8c0363ieee0c7e3f8619d87@mail.gmail.com>
	<45420EC5.8000407@genesilico.pl>
Message-ID: <dd49cdd20610270852v49a5d944qf960e98d5ee04363@mail.gmail.com>

On 10/27/06, Maciek Fijalkowski <fijal at genesilico.pl> wrote:
>
> Thanks. I've fixed one of the errors, 3 to fix and one which I cannot
> reproduce. Just for the interest: are there more than one projects which
> involve py.test on pybots?
>
>

I only have one machine running the py lib tests. It's running Ubuntu
Breezy. If you guys can contribute some more machines, I'd be happy to work
with you in configuring buildbot on them so they can be part of the Pybots
farm.

Grig
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20061027/e01992ec/attachment.html>