[pypy-dev] Running pypy unit tests

[Matej Stuchlik]

Hi Armin,

----- Original Message -----
> From: "Armin Rigo" <arigo at tunes.org>
> To: "Vaibhav Sood" <vaibhav_sood at persistent.com>
> Cc: pypy-dev at python.org
> Sent: Thursday, August 6, 2015 10:46:27 AM
> Subject: Re: [pypy-dev] Running pypy unit tests
> 
> Hi Vaibhav,
> 
> On 5 August 2015 at 10:22, Vaibhav Sood <vaibhav_sood at persistent.com> wrote:
> > The way I run the tests is “./pytest.py <folder>” for each folder in the
> > source code, I get the test results all folders but the command hangs for
> > one particular folder “pypy/module”
> 
> By "each folder" we mean "each individual 'test' subfolder".  The
> pypy/module directory contains a large number of subdirectories, each
> with their own tests, so you should not run all the pypy/module tests
> at once.
> 
> Yes, there is an automatic way.  However in general we don't use it
> ourselves.  It is used automatically by the nightly test runs which
> show up at http://buildbot.pypy.org (when the web site is not down
> like now...).

Could you please describe the automatic way in a little more detail?
buildbot.pypy.org seems to be down right now, so I can't look it up there.
We run all the tests when building pypy for Fedora and I'm pretty sure the
way we run them is not exactly current by now. :)

Matt


> Instead, when we do changes somewhere, we run directly the tests in
> the "test" subdirectory of where we did the changes, and if they pass,
> we commit.  In the rare case where this breaks things at some
> unrelated place, we will notice the next morning after the nightly
> run, and fix it then.
> 
> 
> A bientôt,
> 
> Armin.
> _______________________________________________
> pypy-dev mailing list
> pypy-dev at python.org
> https://mail.python.org/mailman/listinfo/pypy-dev
>