Martin Sebor wrote:
Eric Lemings wrote:
Also,
http://stdcxx.apache.org/builds/4.2.x/linux_redhat_el-5.0-em64t-gcc-4.1.
1.html
Row 96. 1?
This comes from the exec output in the 11d and 15D logs:
22.locale.codecvt.out ./run (22.locale.codecvt.out):
execv ("./22.locale.codecvt.out", ...) error: Exec format error
1 0 0.000 0.000 0.010
Apparently execv() failed to execute the file. We should adjust
the exec utility to produce better output that can be interpreted
and formatted by the xcomp.awk script.
There are a couple of problems here: first, the child process
should indicate to the parent the nature of the exec() failure
by returning the appropriate exit status (as specified by
POSIX). Second, the exit status returned by the child needs
to be correctly interpreted (currently it isn't). I fixed
both of these problems (and more) in the following two commits.
Since the parent process now correctly handles the exit status
and reports the failure as it should (via the EXEC status)
I also removed the exec error that was screwing up the parser.
http://svn.apache.org/viewvc?rev=661050&view=rev
http://svn.apache.org/viewvc?rev=661053&view=rev
Martin
-----Original Message-----
From: Eric Lemings [mailto:[EMAIL PROTECTED] Sent:
Thursday, May 15, 2008 10:36 AM
To: [email protected]
Subject: RE: official location for stdcxx build results
Was just looking at this page:
http://stdcxx.apache.org/builds/4.2.x/aix-5.3-ppc-vacpp-9.0.html
I assume this page was not generated correctly. Something still amiss?
Brad.
-----Original Message-----
From: Martin Sebor [mailto:[EMAIL PROTECTED] On Behalf Of
Martin Sebor
Sent: Wednesday, May 14, 2008 6:31 PM
To: [email protected]
Subject: official location for stdcxx build results
As per STDCXX-682, I've set up the following directories for
the cross-build index pages and populated them with the latest
build results and logs:
trunk (5.0.x): http://stdcxx.apache.org/builds/trunk/
4.3.x: http://stdcxx.apache.org/builds/4.3.x/
4.2.x: http://stdcxx.apache.org/builds/4.2.x/
4.2.1: http://stdcxx.apache.org/builds/4.2.1/
4.2.0: http://stdcxx.apache.org/builds/4.2.0/
Please bookmark these as the official stdcxx build result pages.
The individual build logs (including the summary index.html page)
are stored in the logs/ subdirectory:
trunk: http://stdcxx.apache.org/builds/trunk/logs/
4.3.x: http://stdcxx.apache.org/builds/4.3.x/logs/
4.2.x: http://stdcxx.apache.org/builds/4.2.x/logs/
4.2.1: http://stdcxx.apache.org/builds/4.2.1/logs/
4.2.0: http://stdcxx.apache.org/builds/4.2.0/logs/
I also set up a cron job to update cross-build pages for all
trees in active development (i.e., trunk, 4.3.x and 4.2.x) at
8AM Mountain when any new build logs have been posted since
the last each page was generated. Logs from nightly builds
at Rogue Wave are generally posted around 7AM Mountain. The
current build schedule for these builds is as follows (builds
take place only if any changes occurred since the last build):
trunk: monthly, on the 1st
4.3.x: bimonthly, on the 2nd and 16th
4.2.x: nightly
