emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Regression tests and stderr
Date: Thu, 01 Mar 2012 23:04:53 +0100	[thread overview]
Message-ID: <80obsguge2.fsf@somewhere.org> (raw)
In-Reply-To: 87ehtcouw5.fsf@Rainer.invalid

Hi Achim,

Achim Gratz wrote:
> "Sebastien Vauban"
> <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> writes:
>> Pretty good. One failure, though, which I'll try to investigate (later on).
> That's a new test from Nicolas which seems to need some testing
> itself... :-)

Just saw your reporting as well... Thanks for pointing out anyway.

>> What's weird is the output that comes _after_ the above summary:
> Let me guess, you are on a Windows console or running cmd in a shell
> buffer?  Then the order of output between STDOUT / STDERR is not
> predictable since by default both streams will be buffered.

On Windows, yes. But in a MinTTY terminal with Cygwin.

I never have seen mixed (delayed) streams with other applications, but they
may be less verbose: exit on error, for example, while here a lot of output is
written anyway.

The delay is a problem. The fact that normal messages (vs only calls to
`error') are sent to `stderr' is another big, I think. We can't grep through
errors only, or check for some file to be empty (when redirecting stderr to a
file), or...

Best regards,

Sebastien Vauban

      reply	other threads:[~2012-03-01 22:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-01 21:35 Regression tests and stderr Sebastien Vauban
2012-03-01 21:48 ` Achim Gratz
2012-03-01 22:04   ` Sebastien Vauban [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=80obsguge2.fsf@somewhere.org \
    --to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).