Re: improving python3 regression test setup

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: improving python3 regression test setup
Date: 2012-09-07 00:56:03
Message-ID: 1346979282-sup-716@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Excerpts from Peter Eisentraut's message of jue sep 06 21:33:33 -0300 2012:
> I have developed a patch to make the python3 regression test setup a bit
> simpler. Currently, we are making mangled copies of
> plpython/{expected,sql} to plpython/python3/{expected,sql}, and run the
> tests in plpython/python3. This has the disadvantage that the
> regression.diffs file, if any, ends up in plpython/python3, which is not
> the normal location. If we instead make the mangled copies in
> plpython/{expected,sql}/python3/, we can run the tests from the normal
> directory, regression.diffs ends up the normal place, and the pg_regress
> invocation also becomes a lot simpler. It's also more obvious at run
> time what's going on, because the tests end up being named
> "python3/something" in the test output.

Uhm .. wouldn't it be simpler if the sql files were in input/ and the
expected in output/, and have pg_regress do the mangling? Maybe there
would need to be some tweak to pg_regress itself (such as the ability to
pass mangling to be done), but that seems cleaner to me.

--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2012-09-07 02:54:25 Re: 9.2rc1 produces incorrect results
Previous Message Peter Eisentraut 2012-09-07 00:33:33 improving python3 regression test setup