RE: svn commit: r954328 - /subversion/trunk/build/run_tests.py

Hi Hyrum,

I think you should revert to sending plain text mails to this list ;-)

I can confirm that your latest patch resolves the test output issues.

                Bert

From: hyrum_at_hyrumwright.org [mailto:hyrum_at_hyrumwright.org] On Behalf Of
Hyrum K. Wright
Sent: maandag 14 juni 2010 2:48
To: dev
Cc: commits
Subject: Re: svn commit: r954328 - /subversion/trunk/build/run_tests.py

On Mon, Jun 14, 2010 at 2:36 AM, Bert Huijben <bert_at_vmoo.com> wrote:

> -----Original Message-----
> From: hwright_at_apache.org [mailto:hwright_at_apache.org]
> Sent: maandag 14 juni 2010 1:20
> To: commits_at_subversion.apache.org
> Subject: svn commit: r954328 - /subversion/trunk/build/run_tests.py
>
> Author: hwright
> Date: Sun Jun 13 23:19:53 2010
> New Revision: 954328
>
> URL: http://svn.apache.org/viewvc?rev=954328
<http://svn.apache.org/viewvc?rev=954328&view=rev> &view=rev
> Log:
> * build/run_tests.py
> (_run_prog): Remove all the custom stdout/stderr redirect handling, in
> favor
> of the subprocess module's built-in facilities.

For some reason I don't see any test output when running the tests now.
(stdout doesn't show anything when starting the tests). The buildbots show
the same effect: No streaming per test results on Windows.

I'm confused: what are you seeing, and what do you expect. For myself, I
couldn't see *any* difference between the windows buildbot from before this
change and the buildbot after, for both the testlog and stdio files.
 

And it is very hard to debug without output. (Looking at the process monitor
and the log file shows that the tests just run fine).

Agreed that we should have useful output.

Cheers,
-Hyrum
Received on 2010-06-15 10:47:53 CEST