Pypy IRC meeting fri 17:00 UTC on #pypy (freenode.net)
Hi all, since EuroPython there's been some thinking and planning about doing a new release of PyPy 1.1 before the end of the year with a focus related to the recent work on compatibility with applications and CPython and stability. We think that an important step in the process is to improve and consolidate our testing infrastructure with the goal of making it easy to spot regressions. After some people availability checking on #pypy we agreed on scheduling a meeting: this Friday 29 Aug at 17:00 UTC (19:00 CEST) on #pypy IRC channel (freenode.net) The topics to discuss are: - which machines do we have available or we need (we would like at least to cover Linux x86-32 and windows 32bits) - requirements for our testing infrastructure - status of buildbot related work, what would it take to use buildbot for all out testing needs? - things to do first This is an open meeting, anybody interested in topics is invited to participate. It should not last more than 1 hour. We are also planning on having a sprint in October around the testing/release topics and others, we may also try at this meeting to finalize location and dates for that. regards.
Hi all, On Wed, Aug 27, 2008 at 11:23:35AM +0200, Samuele Pedroni wrote:
this Friday 29 Aug at 17:00 UTC (19:00 CEST)
Let me point out that time again, as it's not at 17:00 CEST as it usually was: it is at 19:00 CEST. Armin
Armin Rigo wrote:
I have to say that it would be extremely helpful NOT to repeat the wrong time in the unchanged subject line. Recognized that too late and made appointments. Really wanted to attend, but I'm reading IRC rarely in the hospital. ciao - chris -- Christian Tismer :^) <mailto:tismer@stackless.com> tismerysoft GmbH : Have a break! Take a ride on Python's Johannes-Niemeyer-Weg 9A : *Starship* http://starship.python.net/ 14109 Berlin : PGP key -> http://wwwkeys.pgp.net/ work +49 30 802 86 56 mobile +49 173 24 18 776 fax +49 30 80 90 57 05 PGP 0x57F3BF04 9064 F4E1 D754 C2FF 1619 305B C09C 5A3B 57F3 BF04 whom do you want to sponsor today? http://www.stackless.com/
Christian Tismer wrote:
Argh. Argh Argh, of course. Nothing was wrong with the title of this posting, but still it was extremely misleading for me. Will be more careful next time, but this one went wrong, sorry. ciao - chris -- Christian Tismer :^) <mailto:tismer@stackless.com> tismerysoft GmbH : Have a break! Take a ride on Python's Johannes-Niemeyer-Weg 9A : *Starship* http://starship.python.net/ 14109 Berlin : PGP key -> http://wwwkeys.pgp.net/ work +49 30 802 86 56 mobile +49 173 24 18 776 fax +49 30 80 90 57 05 PGP 0x57F3BF04 9064 F4E1 D754 C2FF 1619 305B C09C 5A3B 57F3 BF04 whom do you want to sponsor today? http://www.stackless.com/
Samuele Pedroni wrote:
I have checked in a brief summary of the meeting as: http://codespeak.net/svn/pypy/extradoc/planning/1.1/testing_infrastructure.t... regards.
Hi all, Samuele Pedroni wrote:
I have checked in a brief summary of the meeting as:
http://codespeak.net/svn/pypy/extradoc/planning/1.1/testing_infrastructure.t...
some work has been started to implement the strategy described in the summary to improve our testing infrastructure and consolidate it using buildbot for all our testing needs. The experimental buildbot master setup we are playing with lives in: http://codespeak.net/svn/pypy/build/bot2/ this setup is going to be used for a buildmaster running on wyvern. As described in the summary the main idea is to use the new event model on py.lib trunk to produce structured logfiles that can be used from the buildbot master to produce consolidated test result pages. Code doing that lives at: - http://codespeak.net/svn/py/trunk/contrib/filelog/ The integration between pypy and py.lib trunk py.test has been worked on in: - http://codespeak.net/svn/pypy/branch/pypy-pytrunk/ (this points through an external to the filelog code for it to be readily available) so far only the major issues have been tackled and we are still using the compatibility layer present in the py.test, medium term we want to switch away from using the deprecated methods. On the buildbot side: - there's the start of a status page that looks like the current one we use (the htmlconftest based one) but can merge results coming from multiple builders - and definitions of simple builds to run some of pypy own tests I have checked in a TODO file with what is likely needed for people interested in helping or following what is going on: http://codespeak.net/svn/pypy/build/bot2/TODO Samuele.
Hi all, On Wed, Aug 27, 2008 at 11:23:35AM +0200, Samuele Pedroni wrote:
this Friday 29 Aug at 17:00 UTC (19:00 CEST)
Let me point out that time again, as it's not at 17:00 CEST as it usually was: it is at 19:00 CEST. Armin
Armin Rigo wrote:
I have to say that it would be extremely helpful NOT to repeat the wrong time in the unchanged subject line. Recognized that too late and made appointments. Really wanted to attend, but I'm reading IRC rarely in the hospital. ciao - chris -- Christian Tismer :^) <mailto:tismer@stackless.com> tismerysoft GmbH : Have a break! Take a ride on Python's Johannes-Niemeyer-Weg 9A : *Starship* http://starship.python.net/ 14109 Berlin : PGP key -> http://wwwkeys.pgp.net/ work +49 30 802 86 56 mobile +49 173 24 18 776 fax +49 30 80 90 57 05 PGP 0x57F3BF04 9064 F4E1 D754 C2FF 1619 305B C09C 5A3B 57F3 BF04 whom do you want to sponsor today? http://www.stackless.com/
Christian Tismer wrote:
Argh. Argh Argh, of course. Nothing was wrong with the title of this posting, but still it was extremely misleading for me. Will be more careful next time, but this one went wrong, sorry. ciao - chris -- Christian Tismer :^) <mailto:tismer@stackless.com> tismerysoft GmbH : Have a break! Take a ride on Python's Johannes-Niemeyer-Weg 9A : *Starship* http://starship.python.net/ 14109 Berlin : PGP key -> http://wwwkeys.pgp.net/ work +49 30 802 86 56 mobile +49 173 24 18 776 fax +49 30 80 90 57 05 PGP 0x57F3BF04 9064 F4E1 D754 C2FF 1619 305B C09C 5A3B 57F3 BF04 whom do you want to sponsor today? http://www.stackless.com/
Samuele Pedroni wrote:
I have checked in a brief summary of the meeting as: http://codespeak.net/svn/pypy/extradoc/planning/1.1/testing_infrastructure.t... regards.
Hi all, Samuele Pedroni wrote:
I have checked in a brief summary of the meeting as:
http://codespeak.net/svn/pypy/extradoc/planning/1.1/testing_infrastructure.t...
some work has been started to implement the strategy described in the summary to improve our testing infrastructure and consolidate it using buildbot for all our testing needs. The experimental buildbot master setup we are playing with lives in: http://codespeak.net/svn/pypy/build/bot2/ this setup is going to be used for a buildmaster running on wyvern. As described in the summary the main idea is to use the new event model on py.lib trunk to produce structured logfiles that can be used from the buildbot master to produce consolidated test result pages. Code doing that lives at: - http://codespeak.net/svn/py/trunk/contrib/filelog/ The integration between pypy and py.lib trunk py.test has been worked on in: - http://codespeak.net/svn/pypy/branch/pypy-pytrunk/ (this points through an external to the filelog code for it to be readily available) so far only the major issues have been tackled and we are still using the compatibility layer present in the py.test, medium term we want to switch away from using the deprecated methods. On the buildbot side: - there's the start of a status page that looks like the current one we use (the htmlconftest based one) but can merge results coming from multiple builders - and definitions of simple builds to run some of pypy own tests I have checked in a TODO file with what is likely needed for people interested in helping or following what is going on: http://codespeak.net/svn/pypy/build/bot2/TODO Samuele.
participants (3)
-
Armin Rigo -
Christian Tismer -
Samuele Pedroni