Travis Vitek wrote:
Martin Sebor wrote:
Travis Vitek wrote:
Martin Sebor wrote:
If this is true, we might want to change
the exec utility (which does the redirection) to send the output of
tests somewhere else.
Sure, that is one option. But that doesn't answer my question. Why is
this failing now, after it worked in the past. See
https://issues.apache.org/jira/browse/STDCXX-650
Dunno. Maybe it never did work correctly and I missed it when
closing the issue.
I'm absolutely certain it worked in the recent past, but I'll go back
and do a build to make sure I'm not totally insane.
You don't need to. Do a search among the older build logs
under http://stdcxx.apache.org/builds/4.2.x/logs/ instead.
Here's a recent list:
linux_suse-10.0-em64t-gcc-4.1.0-12D-654664-log.gz.txt
linux_suse-10.0-em64t-gcc-4.1.0-12D-655584-log.gz.txt
linux_suse-10.0-em64t-gcc-4.1.0-12D-656010-log.gz.txt
linux_suse-10.0-em64t-gcc-4.1.0-12D-656444-log.gz.txt
linux_suse-10.0-em64t-gcc-4.1.0-12D-656916-log.gz.txt
linux_suse-10.0-em64t-gcc-4.1.0-12D-657235-log.gz.txt
linux_suse-10.0-em64t-gcc-4.1.0-12D-658487-log.gz.txt
linux_suse-10.0-em64t-gcc-4.1.0-12D-658917-log.gz.txt
linux_suse-10.0-em64t-gcc-4.1.0-12D-659278-log.gz.txt
linux_suse-10.0-em64t-gcc-4.1.0-12D-659601-log.gz.txt
linux_suse-10.0-em64t-gcc-4.1.0-12D-660336-log.gz.txt
linux_suse-10.0-em64t-gcc-4.1.0-12D-660492-log.gz.txt
linux_suse-10.0-em64t-gcc-4.1.0-12D-661152-log.gz.txt
linux_suse-10.0-em64t-gcc-4.1.0-12D-661910-log.gz.txt
linux_suse-10.0-em64t-gcc-4.1.0-12D-662101-log.gz.txt
linux_suse-10.0-em64t-gcc-4.1.0-12D-662614-log.gz.txt
linux_suse-10.0-em64t-gcc-4.1.0-12D-663410-log.gz.txt
linux_suse-10.0-em64t-gcc-4.1.0-12D-664236-log.gz.txt
linux_suse-10.0-em64t-gcc-4.1.0-12D-665796-log.gz.txt
linux_suse-10.0-em64t-gcc-4.1.0-12D-666829-log.gz.txt
linux_suse-10.0-em64t-gcc-4.1.0-12D-668819-log.gz.txt
linux_suse-10.0-em64t-gcc-4.1.0-12D-669747-log.gz.txt
linux_suse-10.0-em64t-gcc-4.1.0-12D-670084-log.gz.txt
linux_suse-10.0-em64t-gcc-4.1.0-12D-670734-log.gz.txt
