Re: [SyncEvolution] server class + fork/exec dbus-server + command line testing
On Fr, 2012-04-13 at 18:27 +0200, Justus-bulk(a)Piater.name wrote:
I feel compelled to pitch in:
Krzesimir Nowak <qdlacz(a)gmail.com> wrote on Fri, 13 Apr 2012 17:27:50
+0200:
> I wonder if there is some crazy platform where stdout is buffered so
> long, that unbuffered stderr shows up first even if something earlier
> was printed into stdout.
stdout is generally buffered, whereas stderr is not. The "crazy"
situation you describe happens all the time.
True in general, but not in the SyncEvolution binaries. They disable
buffering.
> I guess that such tests are hardly reliable as an order of
messages is
> guaranteed for one stream, but not between two streams.
Precisely. You should not rely on synchronicity between different
output streams.
That is indeed the problem.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.