|
Boost : |
From: Beman Dawes (bdawes_at_[hidden])
Date: 2004-01-12 12:15:24
At 03:19 AM 1/12/2004, Martin Wille wrote:
>Hello,
>
>have there been changes to process_jam_log?
No. It has been stable for awhile now.
>process_jam_log failed last night with this error:
>
>processing the regression test results for intel-7.1-linux:
>Usage: bjam [bjam-args] | process_jam_log [--echo] [locate-root]
> locate-root is the same as the bjam ALL_LOCATE_TARGET
> parameter, if any. Default is boost-root.
>boost_root: /home/BOOST/rc_1_31_0/boost
>locate_root: /home/BOOST/rc_1_31_0/boost
>
>**** exception(205): std::exception: process_jam_long.cpp:
>"/home/BOOST/rc_1_31_0/boost/ia1.test/bin/intel-7.1-linux/debug/test_log.xml
>":
>can't open output file
>******** errors detected; see standard output for details ********
>
>
>Why is it "ia1.test/bin" instead of "status/ia1.test" or
>"bin/boost/libs/iterator/test/ia1.test"?
That looks like a name has been chopped. The Win32 tests just ran, and
there isn't any test named "ial".
You might take a look at the initial lines of the bjam log file. See if you
can find the entry which is causing the problem. Is it well formed?
A well=formed entry looks like this (change \ -> / for Linux):
boost-test(RUN) "iterator_adaptor_test" :
"libs\iterator\test\iterator_adaptor_test.cpp"
(All on one line.)
You also might want to try another cvs update in case someone has fixed
something.
HTH,
--Beman
--Beman
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk