Nabble - Boost - Testing

Re: tests wedged?

2009-12-19T21:07:50Z

Hi Eric,

> On Dec 19, 2009, at 7:30 PM, Eric Niebler wrote:
> Looks like trunk test results were last updated Dec 16, and release
> was last updated Dec 17. 'Sup?
Regrettably we're having persistent (intermittent) network switch
problems. I reported this issue on Dec 8th and, last I heard, the
switch won't be replaced for at least several more weeks. I won't be
able to get test reporting going until at Monday at the earliest.

Here's my message from the 8th.

> FYI,
> It appears we're experiencing problems with a network switch that is
> (or will) prevent both test reporting from cycling normally and the
> Sandia tester results from running at all. Unfortunately I don't
> know how long it will take to resolve this issue. If the problems
> persist, as seems likely, it may be worth considering whether
> someone else could run the test reporting while we're experiencing
> problems.
-- Noel

_______________________________________________
Boost-Testing mailing list
Boost-Testing@...
http://lists.boost.org/mailman/listinfo.cgi/boost-testing

tests wedged?

2009-12-19T18:30:52Z

Looks like trunk test results were last updated Dec 16, and release was
last updated Dec 17. 'Sup?

--
Eric Niebler
BoostPro Computing
http://www.boostpro.com
_______________________________________________
Boost-Testing mailing list
Boost-Testing@...
http://lists.boost.org/mailman/listinfo.cgi/boost-testing

Re: Sandia-gcc-3.4.6 error on Boost.Graph

2009-12-15T15:38:52Z

On Tue, 15 Dec 2009, Belcourt, Kenneth wrote:

> Hi Jeremiah,
>
> On Dec 15, 2009, at 12:22 PM, Jeremiah Willcock wrote:
>
>> When building the boost_graph library, the Sandia-gcc-3.4.6 tester gets an
>> error that has no message (shown at http://tinyurl.com/yefx5mp). Could
>> someone please look at that machine and see what the problem is? Thank
>> you.
>
> Here's the error message:
> "/home/sntools/extras/compilers/gcc-3.4.6/bin/g++" -ftemplate-depth-128 -O0
> -fno-inline -Wall -g -fPIC -m32 -DBOOST_ALL_NO_LIB=1 -DBOOST_GRAPH_DYN_LINK=1
> -I".." -I"../libs/graph/src" -c -o
> "/tmp/kbelco/boost/results/boost/bin.v2/libs/graph/build/gcc-3.4.6/debug/address-model-32/graphml.o"
> "../libs/graph/src/graphml.cpp"
> ../boost/property_tree/detail/xml_parser_read_rapidxml.hpp: In function `void
> boost::property_tree::xml_parser::read_xml_internal(std::basic_istream<typename
> Ptree::key_type::value_type, std::char_traits<typename
> Ptree::key_type::value_type> >&, Ptree&, int, const std::string&) [with Ptree
> = boost::property_tree::basic_ptree<std::string, std::string,
> std::less<std::string> >]':
> ../boost/property_tree/xml_parser.hpp:52: instantiated from `void
> boost::property_tree::xml_parser::read_xml(std::basic_istream<typename
> Ptree::key_type::value_type, std::char_traits<typename
> Ptree::key_type::value_type> >&, Ptree&, int) [with Ptree =
> boost::property_tree::ptree]'
> ../libs/graph/src/graphml.cpp:48: instantiated from here
> ../boost/property_tree/detail/xml_parser_read_rapidxml.hpp:108: error:
> non-constant `(((int)f_c) | 3072)' cannot be used as template argument
> ../boost/property_tree/detail/xml_parser_read_rapidxml.hpp:108: error: no
> matching function for call to `rapidxml::xml_document<char>::parse(char*)'
> Is this what you're looking for?

Yes, thank you. I guess the issue isn't a BGL bug, though.

-- Jeremiah Willcock
_______________________________________________
Boost-Testing mailing list
Boost-Testing@...
http://lists.boost.org/mailman/listinfo.cgi/boost-testing

Re: Sandia-gcc-3.4.6 error on Boost.Graph

2009-12-15T15:12:12Z

Hi Jeremiah,

On Dec 15, 2009, at 12:22 PM, Jeremiah Willcock wrote:

> When building the boost_graph library, the Sandia-gcc-3.4.6 tester
> gets an
> error that has no message (shown at http://tinyurl.com/yefx5mp).
> Could
> someone please look at that machine and see what the problem is?
> Thank
> you.

Here's the error message:
"/home/sntools/extras/compilers/gcc-3.4.6/bin/g++" -ftemplate-
depth-128 -O0 -fno-inline -Wall -g -fPIC -m32 -DBOOST_ALL_NO_LIB=1 -
DBOOST_GRAPH_DYN_LINK=1 -I".." -I"../libs/graph/src" -c -o "/tmp/
kbelco/boost/results/boost/bin.v2/libs/graph/build/gcc-3.4.6/debug/
address-model-32/graphml.o"
"../libs/graph/src/graphml.cpp" ../boost/property_tree/detail/
xml_parser_read_rapidxml.hpp: In function `void
boost
::property_tree
::xml_parser::read_xml_internal(std::basic_istream<typename
Ptree::key_type::value_type, std::char_traits<typename
Ptree::key_type::value_type> >&, Ptree&, int, const std::string&)
[with Ptree = boost::property_tree::basic_ptree<std::string,
std::string, std::less<std::string> >]':
../boost/property_tree/xml_parser.hpp:52: instantiated from `void
boost::property_tree::xml_parser::read_xml(std::basic_istream<typename
Ptree::key_type::value_type, std::char_traits<typename
Ptree::key_type::value_type> >&, Ptree&, int) [with Ptree =
boost::property_tree::ptree]'
../libs/graph/src/graphml.cpp:48: instantiated from here
../boost/property_tree/detail/xml_parser_read_rapidxml.hpp:108: error:
non-constant `(((int)f_c) | 3072)' cannot be used as template argument
../boost/property_tree/detail/xml_parser_read_rapidxml.hpp:108: error:
no matching function for call to
`rapidxml::xml_document<char>::parse(char*)'
Is this what you're looking for?

-- Noel

_______________________________________________
Boost-Testing mailing list
Boost-Testing@...
http://lists.boost.org/mailman/listinfo.cgi/boost-testing

Sandia-gcc-3.4.6 error on Boost.Graph

2009-12-15T11:22:44Z

When building the boost_graph library, the Sandia-gcc-3.4.6 tester gets an
error that has no message (shown at http://tinyurl.com/yefx5mp). Could
someone please look at that machine and see what the problem is? Thank
you.

-- Jeremiah Willcock
_______________________________________________
Boost-Testing mailing list
Boost-Testing@...
http://lists.boost.org/mailman/listinfo.cgi/boost-testing

Test reporting

2009-12-08T07:37:30Z

FYI,

It appears we're experiencing problems with a network switch that is
(or will) prevent both test reporting from cycling normally and the
Sandia tester results from running at all. Unfortunately I don't know
how long it will take to resolve this issue. If the problems persist,
as seems likely, it may be worth considering whether someone else
could run the test reporting while we're experiencing problems.

-- Noel

_______________________________________________
Boost-Testing mailing list
Boost-Testing@...
http://lists.boost.org/mailman/listinfo.cgi/boost-testing

Re: boost::function Small Buffer Optimization (SBO) and allocators

2009-12-03T11:11:25Z

On Thu, Dec 3, 2009 at 9:56 AM, Chris Hite <C.Hite@...> wrote:
> I would really like to specify the SBO size on boost::function! How about
> changing the signature to?:
> template<typename Signature,std::size_t SBOSize=3*sizeof(void*)>
> class function;

The small buffer optimization is an implementation detail, you
shouldn't know about it. What would you do if you wanted to customize
the size for the small buffer optimization in std::string? :)

> The copy constructor and equals operators require serious hackery, since
> these constructors on boost function don't allow you to pass a new allow you
> to pass a new allocator. There's no
> template<typename Allocator>
> functionN(const functionN&, Allocator);

It's tricky, but yours seems like a typical use case for allocators.

> This is also not such a wonderful solution, because the SBO is wasted.

It has been some time since I last looked at that code but I can't
think of any reason why the SBO would be wasted. In principle, the
allocator object and the buffer can overlap, since they're never used
together.

Emil Dotchevski
Reverge Studios, Inc.
http://www.revergestudios.com/reblog/index.php?n=ReCode
_______________________________________________
Boost-Testing mailing list
Boost-Testing@...
http://lists.boost.org/mailman/listinfo.cgi/boost-testing

boost::function Small Buffer Optimization (SBO) and allocators

2009-12-03T09:56:43Z

I would really like to specify the SBO size on boost::function! How
about changing the signature to?:
template<typename Signature,std::size_t SBOSize=3*sizeof(void*)>
class function;

I've been trying to do a work around using the constructor with the
allocator. I was going to define my own function class derived from the
boost one, with a private one time allocator using a private buffer.
This approach works find as long as constructors where the Functor type
is present.

The copy constructor and equals operators require serious hackery, since
these constructors on boost function don't allow you to pass a new allow
you to pass a new allocator. There's no
template<typename Allocator>
functionN(const functionN&, Allocator);

This means that the Function constructor has to affect data underlying
the const Function instance it's copying such that when the allocator is
copied over it mutates into one that points at the private buffer of the
new constructing instance.

This is doable, but kind of scary since I'm making assumptions about
when and how the Allocator is copied.

This is also not such a wonderful solution, because the SBO is wasted.

Any chance of just parameterizing the SBO size?

Chris

_______________________________________________
Boost-Testing mailing list
Boost-Testing@...
http://lists.boost.org/mailman/listinfo.cgi/boost-testing

Test reporting is back

2009-11-23T09:37:23Z

Hi,

I apologize for the lengthy down time, our outage lasted the entire
weekend. Both release and trunk reporting are running again though
it may take several hours before the results are uploaded to the server.

Again, sorry about the delay.

-- Noel

_______________________________________________
Boost-Testing mailing list
Boost-Testing@...
http://lists.boost.org/mailman/listinfo.cgi/boost-testing

Reporting interruption

2009-11-20T20:48:35Z

Hi,

Sorry about the late notice but it seems we have a power outage this
weekend. I am hopeful that reporting can restart tomorrow.

-- Noel

_______________________________________________
Boost-Testing mailing list
Boost-Testing@...
http://lists.boost.org/mailman/listinfo.cgi/boost-testing

Test Reporting Interruption

2009-11-16T14:22:39Z

Hi,

I expect there will be an interruption in the nightly test reporting
(also impacting many Sandia test runners) that could last as long as
24 hours. Our file systems will be mounted read-only during this time
while they're migrated to new servers. I'll let you know if the delay
will run longer than 24 hours.

Sorry about the interruption.

-- Noel

_______________________________________________
Boost-Testing mailing list
Boost-Testing@...
http://lists.boost.org/mailman/listinfo.cgi/boost-testing

Boost.Test: access name of test case within that case?

2009-11-16T01:17:53Z

Hi,

I'm wondering if the name of a test case is available within that case.
Couldn't find it in the documentation or via a web search, nor by a quick
browse of the sources.

Thanks for any reply

Martin

--
Martin Moene, http://www.eld.physics.LeidenUniv.nl/~moene/

_______________________________________________
Boost-Testing mailing list
Boost-Testing@...
http://lists.boost.org/mailman/listinfo.cgi/boost-testing

Re: Process jam log build problems

2009-11-12T13:29:03Z

On Thu, Nov 12, 2009 at 2:40 PM, Belcourt, Kenneth <kbelco@...> wrote:

> Hi,
>
> Some of the nightly tests failed with this error.
>
> "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall
> -DBOOST_ALL_NO_LIB=1 -DBOOST_SYSTEM_STATIC_LINK=1 -DNDEBUG
> -I"/var/scratch/boost/boost" -c -o
> "/var/scratch/boost/boost/bin.v2/libs/system/build/gcc-3.4.6/release/link-static/error_code.o"
> "/var/scratch/boost/boost/libs/system/src/error_code.cpp"
>
> /var/scratch/boost/boost/libs/system/src/error_code.cpp: In member function
> `virtual boost::system::error_condition
> <unnamed>::system_error_category::default_error_condition(int) const':
> /var/scratch/boost/boost/libs/system/src/error_code.cpp:196: error:
> `too_many_synbolic_link_levels' was not declared in this scope
> /var/scratch/boost/boost/libs/system/src/error_code.cpp:196: warning: unused
> variable 'too_many_synbolic_link_levels'
> ...failed gcc.compile.c++
> /var/scratch/boost/boost/bin.v2/libs/system/build/gcc-3.4.6/release/link-static/error_code.o...

Should be alright now.

Thanks,

--Beman
_______________________________________________
Boost-Testing mailing list
Boost-Testing@...
http://lists.boost.org/mailman/listinfo.cgi/boost-testing

Process jam log build problems

2009-11-12T11:40:48Z

Hi,

Some of the nightly tests failed with this error.

"g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -
Wall -DBOOST_ALL_NO_LIB=1 -DBOOST_SYSTEM_STATIC_LINK=1 -DNDEBUG -I"/
var/scratch/boost/boost" -c -o "/var/scratch/boost/boost/bin.v2/libs/
system/build/gcc-3.4.6/release/link-static/error_code.o" "/var/scratch/
boost/boost/libs/system/src/error_code.cpp"

/var/scratch/boost/boost/libs/system/src/error_code.cpp: In member
function `virtual boost::system::error_condition
<unnamed>::system_error_category::default_error_condition(int) const':
/var/scratch/boost/boost/libs/system/src/error_code.cpp:196: error:
`too_many_synbolic_link_levels' was not declared in this scope
/var/scratch/boost/boost/libs/system/src/error_code.cpp:196: warning:
unused variable 'too_many_synbolic_link_levels'
...failed gcc.compile.c++ /var/scratch/boost/boost/bin.v2/libs/system/
build/gcc-3.4.6/release/link-static/error_code.o...

-- Noel

_______________________________________________
Boost-Testing mailing list
Boost-Testing@...
http://lists.boost.org/mailman/listinfo.cgi/boost-testing

Re: Problems with trunk regression tests ?

2009-11-11T06:01:49Z

2009/11/10 Richard Webb <richard.webb@...>:
>
> Is the Hash jamfile broken ?

Sorry about that, it worked for me. But I'll revert the change.

Daniel
_______________________________________________
Boost-Testing mailing list
Boost-Testing@...
http://lists.boost.org/mailman/listinfo.cgi/boost-testing

Problems with trunk regression tests ?

2009-11-10T14:15:37Z

I just tried to run the Trunk regression tests with VC9 and got the error:

..\libs\functional\hash\test\Jamfile.v2:50: in modules.load
*** argument error
* rule compile-fail ( sources + : requirements * : target-name ? )
* called with: ( namespace_fail_test.cpp : : : <warnings-as-errors>off )
* extra argument <warnings-as-errors>off
W:/boosttrunk/tools_bb/tools\testing.jam:133:see definition of rule 'compile-fail' being called
W:/boosttrunk/tools_bb/build\project.jam:313: in load-jamfile
W:/boosttrunk/tools_bb/build\project.jam:62: in load
W:/boosttrunk/tools_bb/build\project.jam:168: in project.find
W:/boosttrunk/tools_bb/build\targets.jam:406: in find-really
W:/boosttrunk/tools_bb/build\targets.jam:428: in find
W:/boosttrunk/tools_bb/build\targets.jam:291: in targets-to-build
W:/boosttrunk/tools_bb/build\targets.jam:256: in object(project-target)@495.generate
W:/boosttrunk/tools_bb\build-system.jam:704: in load
W:\boosttrunk\tools_bb/kernel\modules.jam:283: in import
W:\boosttrunk\tools_bb\kernel\bootstrap.jam:142: in boost-build
W:\boosttrunk\boost\boost-build.jam:17: in module scope

Is the Hash jamfile broken ?

Re: Problem with PPC Darwin Nightly Tests

2009-11-10T09:22:44Z

K. Noel Belcourt wrote:
> I've attached the relevant part of the nightly test error we're having
> on PPC Tiger. It looks like an issue with feature.jam.

Sorry, this was my mistake. I made a change which started using the
patch version on the Xcode SDK detection. Which worked for iPhone
builds, but not regular OSX builds. I just checked in a quick fix. A
better, more flexible, fix will come along in the near future.

--
-- Grafik - Don't Assume Anything
-- Redshift Software, Inc. - http://redshift-software.com
-- rrivera/acm.org (msn) - grafik/redshift-software.com
-- 102708583/icq - grafikrobot/aim,yahoo,skype,efnet,gmail
_______________________________________________
Boost-Testing mailing list
Boost-Testing@...
http://lists.boost.org/mailman/listinfo.cgi/boost-testing

Problem with PPC Darwin Nightly Tests

2009-11-10T08:59:43Z

Hi,

I've attached the relevant part of the nightly test error we're
having on PPC Tiger. It looks like an issue with feature.jam.

Thanks.

-- Noel

A boost/boost.css
A boost/CMakeLists.txt
U boost
Checked out revision 57528.
# Found patch file "/Users/kbelco/boost_tiger_ppc/patch_boost". Executing it.
# Preinstalled "/Users/kbelco/boost_tiger_ppc/bjam" is not found; building one...
# Found "bjam" source directory "/Users/kbelco/boost_tiger_ppc/tools_bjam"
# Building "bjam" (./build.sh darwin)...
###
### Using 'darwin' toolset.
###
rm -rf bootstrap
mkdir bootstrap
cc -o bootstrap/jam0 command.c compile.c debug.c expand.c glob.c hash.c hdrmacro.c headers.c jam.c jambase.c jamgram.c lists.c make.c make1.c newstr.c option.c output.c parse.c pathunix.c pathvms.c regexp.c rules.c scan.c search.c subst.c timestamp.c variable.c modules.c strings.c filesys.c builtins.c pwd.c class.c native.c w32_getreg.c modules/set.c modules/path.c modules/regex.c modules/property-set.c modules/sequence.c modules/order.c execunix.c fileunix.c
./bootstrap/jam0 -f build.jam --toolset=darwin --toolset-root= clean
...found 1 target...
...updating 1 target...
...updated 1 target...
./bootstrap/jam0 -f build.jam --toolset=darwin --toolset-root=
...found 47 targets...
...updating 2 targets...
[MKDIR] bin.macosxppc
[COMPILE] bin.macosxppc/bjam
...updated 2 targets...
# Searching for "bjam" in "/Users/kbelco/boost_tiger_ppc/tools_bjam"...
# bjam succesfully built in "/Users/kbelco/boost_tiger_ppc/tools_bjam/bin.macosxppc/bjam" location
# Preinstalled "/Users/kbelco/boost_tiger_ppc/process_jam_log" is not found; building one...
# Found "process_jam_log" source directory "/Users/kbelco/boost_tiger_ppc/tools_regression/build"
# Building "process_jam_log" ("/Users/kbelco/boost_tiger_ppc/tools_bjam/bin.macosxppc/bjam" "-sBOOST_BUILD_PATH=/Users/kbelco/boost_tiger_ppc:/Users/kbelco/boost_tiger_ppc/tools_bb" "-sBOOST_ROOT=/Users/kbelco/boost_tiger_ppc/boost" "--boost=/Users/kbelco/boost_tiger_ppc/boost" "--boost-build=/Users/kbelco/boost_tiger_ppc/tools_bb" "--debug-configuration" process_jam_log -d2 -l300 darwin)...
notice: found boost-build.jam at /Users/kbelco/boost_tiger_ppc/boost-build.jam
notice: loading Boost.Build from /Users/kbelco/boost_tiger_ppc/tools_bb
notice: Searching /etc /Users/kbelco /Users/kbelco/boost_tiger_ppc/tools_bb /Users/kbelco/boost_tiger_ppc /Users/kbelco/boost_tiger_ppc/tools_bb /Users/kbelco/boost_tiger_ppc/tools_bb/kernel /Users/kbelco/boost_tiger_ppc/tools_bb/util /Users/kbelco/boost_tiger_ppc/tools_bb/build /Users/kbelco/boost_tiger_ppc/tools_bb/tools /Users/kbelco/boost_tiger_ppc/tools_bb/contrib /Users/kbelco/boost_tiger_ppc/tools_bb/. for site-config configuration file site-config.jam .
notice: Loading site-config configuration file site-config.jam from /Users/kbelco/boost_tiger_ppc/tools_bb/site-config.jam .
notice: Searching /Users/kbelco /Users/kbelco/boost_tiger_ppc/tools_bb /Users/kbelco/boost_tiger_ppc /Users/kbelco/boost_tiger_ppc/tools_bb /Users/kbelco/boost_tiger_ppc/tools_bb/kernel /Users/kbelco/boost_tiger_ppc/tools_bb/util /Users/kbelco/boost_tiger_ppc/tools_bb/build /Users/kbelco/boost_tiger_ppc/tools_bb/tools /Users/kbelco/boost_tiger_ppc/tools_bb/contrib /Users/kbelco/boost_tiger_ppc/tools_bb/. for user-config configuration file user-config.jam .
notice: Loading user-config configuration file user-config.jam from /Users/kbelco/boost_tiger_ppc/tools_bb/user-config.jam .
notice: [python-cfg] Configuring python...
notice: [python-cfg] user-specified version: "2.3"
notice: [python-cfg] user-specified cmd-or-prefix: "/usr/bin/python"
notice: [python-cfg] Checking interpreter command "/usr/bin/python"...
notice: [python-cfg] running command '"/usr/bin/python" -c "from sys import *; print('version=%d.%d\nplatform=%s\nprefix=%s\nexec_prefix=%s\nexecutable=%s' % (version_info[0],version_info[1],platform,prefix,exec_prefix,executable))" 2>&1'
notice: [python-cfg] ...requested configuration matched!
notice: [python-cfg] Details of this Python configuration:
notice: [python-cfg] interpreter command: "/usr/bin/python"
notice: [python-cfg] include path: "/System/Library/Frameworks/Python.framework/Versions/2.3/include/python2.3"
notice: [python-cfg] library path: "/System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/config" "/System/Library/Frameworks/Python.framework/Versions/2.3/lib"
notice: [python-cfg] framework directory is "/System/Library/Frameworks/Python.framework"
===============MPI Auto-configuration===============
Found recent LAM-MPI or Open MPI wrapper compiler: mpic++
MPI compilation flags: -D_REENTRANT -I/usr/local/include
MPI link flags: -Wl,-u,_munmap -Wl,-multiply_defined,suppress -L/usr/local/lib -lmpi_cxx -lmpi -lopen-rte -lopen-pal
MPI build features:
<define>_REENTRANT <include>/usr/local/include <library-path>/usr/local/lib <find-shared-library>mpi_cxx <find-shared-library>mpi <find-shared-library>open-rte <find-shared-library>open-pal <linkflags>-Wl,-u,_munmap <linkflags>-Wl,-multiply_defined,suppress
MPI launcher: mpirun -np
====================================================
notice: OSX version on this machine is 10.4.11
notice: will use '/usr/bin/g++' for darwin, condition <toolset>darwin-4.0.1
notice: using strip :: <toolset>darwin-4.0.1 :: /usr/bin/strip
notice: using archiver :: <toolset>darwin-4.0.1 :: /usr/bin/libtool
/Users/kbelco/boost_tiger_ppc/tools_bb/build/feature.jam:483: in feature.validate-value-string from module feature
error: "10.3.9" is not a known value of feature <macosx-version>
error: legal values: "10.6" "10.5" "10.4" "10.3" "10.2" "10.1" "iphone-3.2" "iphonesim-3.2" "iphone-3.1.2" "iphonesim-3.1.2" "iphone-3.1" "iphonesim-3.1" "iphone-3.0" "iphonesim-3.0" "iphone-2.2.1" "iphonesim-2.2.1" "iphone-2.2" "iphonesim-2.2" "iphone-2.1" "iphonesim-2.1" "iphone-2.0" "iphonesim-2.0" "iphone-1.x"
/Users/kbelco/boost_tiger_ppc/tools_bb/build/property.jam:276: in validate1 from module property
/Users/kbelco/boost_tiger_ppc/tools_bb/build/property.jam:301: in validate from module property
/Users/kbelco/boost_tiger_ppc/tools_bb/build/property.jam:310: in property.validate-property-sets from module property
/Users/kbelco/boost_tiger_ppc/tools_bb/build/toolset.jam:151: in flags from module toolset
/Users/kbelco/boost_tiger_ppc/tools_bb/tools/darwin.jam:262: in init-available-sdk-versions from module darwin
/Users/kbelco/boost_tiger_ppc/tools_bb/tools/darwin.jam:209: in darwin.init from module darwin
/Users/kbelco/boost_tiger_ppc/tools_bb/build/toolset.jam:38: in using from module toolset
/Users/kbelco/boost_tiger_ppc/tools_bb/user-config.jam:28: in modules.load from module user-config
/Users/kbelco/boost_tiger_ppc/tools_bb/build-system.jam:241: in load-config from module build-system
/Users/kbelco/boost_tiger_ppc/tools_bb/build-system.jam:383: in load-configuration-files from module build-system
/Users/kbelco/boost_tiger_ppc/tools_bb/build-system.jam:538: in load from module build-system
/Users/kbelco/boost_tiger_ppc/tools_bb/kernel/modules.jam:283: in import from module modules
/Users/kbelco/boost_tiger_ppc/tools_bb/kernel/bootstrap.jam:142: in boost-build from module
/Users/kbelco/boost_tiger_ppc/boost-build.jam:17: in module scope from module

# Searching for "process_jam_log" in "/Users/kbelco/boost_tiger_ppc/tools_regression/build"...
Traceback (most recent call last):
File "run.py", line 60, in ?
runner(root)
File "/Users/kbelco/boost_tiger_ppc/tools_regression_src/regression.py", line 193, in __init__
self.main()
File "/Users/kbelco/boost_tiger_ppc/tools_regression_src/regression.py", line 551, in main
getattr(self,action_m)()
File "/Users/kbelco/boost_tiger_ppc/tools_regression_src/regression.py", line 508, in command_regression
self.command_setup()
File "/Users/kbelco/boost_tiger_ppc/tools_regression_src/regression.py", line 300, in command_setup
self.build_if_needed(self.process_jam_log,self.pjl_toolset)
File "/Users/kbelco/boost_tiger_ppc/tools_regression_src/regression.py", line 650, in build_if_needed
tool[ 'build_path' ] = self.tool_path( tool )
File "/Users/kbelco/boost_tiger_ppc/tools_regression_src/regression.py", line 673, in tool_path
raise Exception( 'Cannot find "%s" in any of the following locations:\n%s' % (
Exception: Cannot find "process_jam_log" in any of the following locations:
/Users/kbelco/boost_tiger_ppc/process_jam_log
/Users/kbelco/boost_tiger_ppc/tools_regression/build
s863076:~/boost_tiger_ppc kbelco$

_______________________________________________
Boost-Testing mailing list
Boost-Testing@...
http://lists.boost.org/mailman/listinfo.cgi/boost-testing

Boost.build.txt (682 bytes) Download Attachment

Re: Difference between BDG-Ubuntu & Debian-Sid?

2009-11-02T18:51:15Z

On Mon, Nov 02, 2009 at 03:30:48AM -0800, Richard Webb wrote:
>
> It looks like the Debian-Sid tests are being run in c++0x mode,

That is true.

> but the BDG-Ubuntu tests are in default (c++98?) mode.

Yes, that could be the case.

> There are generally more test failures in c++0x mode - if you look at the
> Trunk results you can see several versions of GCC being tested in both modes
> with the _0x versions having more failures.

That would explain a lot.

Thanks,
-Steve

_______________________________________________
Boost-Testing mailing list
Boost-Testing@...
http://lists.boost.org/mailman/listinfo.cgi/boost-testing

signature.asc (197 bytes) Download Attachment

Re: Difference between BDG-Ubuntu & Debian-Sid?

2009-11-02T03:30:47Z

It looks like the Debian-Sid tests are being run in c++0x mode, but the BDG-Ubuntu tests are in default (c++98?) mode.

There are generally more test failures in c++0x mode - if you look at the Trunk results you can see several versions of GCC being tested in both modes with the _0x versions having more failures.

Thanks,
Richard Webb

Difference between BDG-Ubuntu & Debian-Sid?

2009-11-01T12:47:46Z

Hi,

This message is addressed to the maintainer of "BGD-Ubuntu". There's
no contact info listed, but hopefully that person reads this list.
It's probably useful to involve all linux developers on this list,
anyway.

I've been running the "Debian-Sid" test machine for a fair while now
and notice that my system generally has more failures than yours.
Given that Ubuntu is a variant of Debian, I find this strange and
would like to understand why this is the case.

To start with: is it a 32 bit or 64 bit system? Are you using a
"stable" ubuntu or something more bleeding-edge, akin to "Debian/sid"?

Any ideas why things fail to compile on my system with GCC 4.4, but
do on yours; e.g. assign [1], dynamic_bitset [2], etc?

Thanks,
-Steve

[1] http://www.boost.org/development/tests/release/developer/assign.html
[2] http://www.boost.org/development/tests/release/developer/dynamic_bitset.html

_______________________________________________
Boost-Testing mailing list
Boost-Testing@...
http://lists.boost.org/mailman/listinfo.cgi/boost-testing

signature.asc (197 bytes) Download Attachment

Testing with Comeau C/C++ Compiler

2009-10-23T13:02:23Z

Hi,

What is current status of the Boost 'compilability'
using the Comeau C/C++ compiler? Boost trunk, in particular.

I'm have observed compilation errors [1] but I'm not sure if it's
problem on my end or Boost's.

[1] https://svn.boost.org/trac/boost/ticket/3548
http://thread.gmane.org/gmane.comp.lib.boost.devel/195085/focus=195126

I'm a little bit confused, so I'd kindly ask for clarification.
What is the difference between the regression tests summary [2]
and the upload-based tests hosted here at http://boost.cowic.de/rc/
If I would like to run Boost regression tests using Comeau C/C++,
frequently, how can I contribute them to the summary?
Is the run.py script the right way I should learn about?

[2] http://www.boost.org/development/tests/trunk/developer/summary.html

Best regards,
--
Mateusz Loskot, http://mateusz.loskot.net
Charter Member of OSGeo, http://osgeo.org
_______________________________________________
Boost-Testing mailing list
Boost-Testing@...
http://lists.boost.org/mailman/listinfo.cgi/boost-testing

--
Mateusz Loskot
http://mateusz.loskot.net

Re: Boost compatibility with Old Compilers

2009-10-14T20:39:21Z

AMDG

chin wrote:
> So does it mean, that for Solaris where we are using Sun WorkShop 6 update 2
> C++ 5.3, we will have to update our Compiler version?
>

Almost certainly. It's also highly likely that you will need to update
gcc as well.
It depends on what libraries you are using. Older libraries like bind
and MPL
are more likely to work with gcc 3.3 than newer libraries.

In Christ,
Steven Watanabe

_______________________________________________
Boost-Testing mailing list
Boost-Testing@...
http://lists.boost.org/mailman/listinfo.cgi/boost-testing

Re: Boost compatibility with Old Compilers

2009-10-14T20:24:39Z

Thanks for posting,

So does it mean, that for Solaris where we are using Sun WorkShop 6 update 2 C++ 5.3, we will have to update our Compiler version?

Steven Watanabe-4 wrote:

AMDG

chin wrote:
> We are planning to use Boost version 1.39 on Windows. In docs i found the
> following:
>
> ----------------------------------------------------------------------------------------------------
> <snip>
> ----------------------------------------------------------------------------------------------------
>
> My concern is:
> We are supposed to use Boost both for Linux and Solaris, but the compilers
> being used are slightly old.
> On Debian Linux we have GCC 3.3

Some libraries may work with this version. I believe that we were
testing under compilers based on gcc 3.3 until pretty recently.

> and on Solaris we have Sun WorkShop 6 update
> 2 C++ 5.3.
>

I don't think that this version has ever been supported by Boost.

> Is Boost compatible with these versions? Does this list mean that Boost is
> not compatible with older versions of Compiler?
>

In Christ,
Steven Watanabe

_______________________________________________
Boost-Testing mailing list
Boost-Testing@lists.boost.org
http://lists.boost.org/mailman/listinfo.cgi/boost-testing

Re: Boost compatibility with Old Compilers

2009-10-14T14:45:01Z

AMDG

chin wrote:

> We are planning to use Boost version 1.39 on Windows. In docs i found the
> following:
>
> ----------------------------------------------------------------------------------------------------
> <snip>
> ----------------------------------------------------------------------------------------------------
>
> My concern is:
> We are supposed to use Boost both for Linux and Solaris, but the compilers
> being used are slightly old.
> On Debian Linux we have GCC 3.3

Some libraries may work with this version. I believe that we were
testing under compilers based on gcc 3.3 until pretty recently.

> and on Solaris we have Sun WorkShop 6 update
> 2 C++ 5.3.
>

I don't think that this version has ever been supported by Boost.

> Is Boost compatible with these versions? Does this list mean that Boost is
> not compatible with older versions of Compiler?
>

In Christ,
Steven Watanabe

_______________________________________________
Boost-Testing mailing list
Boost-Testing@...
http://lists.boost.org/mailman/listinfo.cgi/boost-testing

Re: Serialization library est errors for vaccp, borland and sun

2009-10-14T11:44:55Z

> Trunk tests for the serialization library on the following platforms suggest > that the code being tested is different than that in the trunk: They fail > for lack of files which should no longer appear in "#include" directives: > > vacpp - IBM_Canada_Ltd > borland-cb2010 - codegear > Thanks for pointing this out. We will have a look to see if we can figure out what is going on.
Chris Cambly
XL C++ Compiler Development
_______________________________________________
Boost-Testing mailing list
Boost-Testing@...
http://lists.boost.org/mailman/listinfo.cgi/boost-testing

Boost compatibility with Old Compilers

2009-10-13T21:59:52Z

HI,

We are planning to use Boost version 1.39 on Windows. In docs i found the
following:

----------------------------------------------------------------------------------------------------
Compilers Tested

Boost's primary test compilers are:

o Linux:
o GCC 4.3.3 on Ubuntu Linux.

o Windows:
o Visual C++ 7.1 SP1, 8.0 SP1 and 9.0 SP1 on Windows
XP.

Boost's additional test compilers include:

o Linux:
o Intel 9.0 on Red Hat Enterprise Linux.
o Intel 10.0 on Red Hat Enterprise Linux.
o Intel 10.1 on 64-bit Linux Redhat 5.1 Server.
o Intel 10.1 on Suse Linux on 64 bit Itanium.
o Intel 11.0 on Red Hat Enterprise Linux.
o Intel 11.1 on Red Hat Enterprise Linux.
o GCC 3.4.3, GCC 4.0.1, GCC 4.2.4, GCC 4.3.3 and GCC
4.4.0 on Red Hat Enterprise Linux.
o GCC 4.3.3 and GCC 4.4.0 with C++0x extensions on
Red Hat Enterprise Linux.
o GCC 4.1.1, 4.2.1 on 64-bit Red Hat Enterprise
Linux.
o GCC 4.1.2 on Suse Linux on 64 bit Itanium.
o GCC 4.1.2 on 64-bit Redhat Server 5.1.
o GCC Open64 4.2.2 on Red Hat Enterprise Linux.
o GCC 4.3.4 on Debian unstable.
o QLogic PathScale(TM) Compiler Suite: Version 3.1 on
Red Hat Enterprise Linux.
o GCC version 4.2.0 (PathScale 3.2 driver) on 64-bit
Red Hat Enterprise Linux.
o Sun 5.9 on Red Hat Enterprise Linux.

o Windows:
o Visual C++ 7.1 on XP.
o Visual C++ 9.0 on XP.
o Visual C++ 9.0 on Vista.
o Visual C++ 9.0 on Vista 64-bit.
o Visual C++ 9.0, using STLport 5.2, on XP and
Windows Mobile 5.0.
o Visual C++ 10.0 beta.
o Borland 5.9.3, 6.1.0, 6.1.3.
o Borland C++ Builder 2007 and 2009.
o Intel C++ 11.1, with a Visual C++ 9.0 backend, on
Vista 32-bit.
o Intel C++ 11.1, with a Visual C++ 9.0 backend, on
Vista 64-bit.
o GCC 4.3.3 and 4.4.0, on Mingw with C++0x features.

o Solaris:
o Sun C++ 5.7, 5.8, 5.9 on Solaris 5.10.
o GCC 3.4.6 on Solaris 5.10.

----------------------------------------------------------------------------------------------------

My concern is:
We are supposed to use Boost both for Linux and Solaris, but the compilers being used are slightly old.
On Debian Linux we have GCC 3.3 and on Solaris we have Sun WorkShop 6 update
2 C++ 5.3.

Is Boost compatible with these versions? Does this list mean that Boost is not compatible with older versions of Compiler?

Re: Serialization library est errors for vaccp, borland and sun

2009-10-13T11:10:08Z

Hi Robert,

On Oct 13, 2009, at 10:54 AM, K. Noel Belcourt wrote:

> On Oct 13, 2009, at 11:11 AM, Robert Ramey wrote:
>
>> These tests seem to fail to build the library but no error messages
>> are
>> emitted.
>>
>> sun- 5.9 - Sandia-Linux-sun
>> sun- 5.10 - Sandia-Linux-sun
>
> sun-5.10 is on Solaris, not Linux.

This is the key error. It seems that the serialization library won't
be built if shared_ptr_helper.o failed, as you can see here:

...skipped <p/var/scratch/boost/results/boost/bin.v2/libs/
serialization/build/sun-5.9/debug/stdlib-sun-
stlport>libboost_serialization.so.1.41.0 for lack of <p/var/scratch/
boost/results/boost/bin.v2/libs/serialization/build/sun-5.9/debug/
stdlib-sun-stlport>shared_ptr_helper.o...

So I'd suggest that, in general, start with seeing if
shared_ptr_helper was built correctly.

[ This is on Linux ]

sun.compile.c++ /var/scratch/boost/results/boost/bin.v2/libs/
serialization/build/sun-5.9/debug/stdlib-sun-stlport/shared_ptr_helper.o

"/home/sntools/extras/compilers/studio12.old/sunstudio12/bin/CC"
+d -library=stlport4 -g -erroff=%none -KPIC -DBOOST_ALL_NO_LIB=1 -
DBOOST_SERIALIZATION_DYN_LINK=1 -I".." -c -o "/var/scratch/boost/
results/boost/bin.v2/libs/serialization/build/sun-5.9/debug/stdlib-
sun-stlport/shared_ptr_helper.o" "../libs/serialization/src/
shared_ptr_helper.cpp"

"../boost/serialization/void_cast_fwd.hpp", line 33: Error: Default
arguments cannot be added in later declarations of the template
function in the same scope.
"../boost/serialization/void_cast_fwd.hpp", line 33: Error: Default
arguments cannot be added in later declarations of the template
function in the same scope.
2 Error(s) detected.
...failed sun.compile.c++ /var/scratch/boost/results/boost/bin.v2/
libs/serialization/build/sun-5.9/debug/stdlib-sun-stlport/
shared_ptr_helper.o...

-- Noel

_______________________________________________
Boost-Testing mailing list
Boost-Testing@...
http://lists.boost.org/mailman/listinfo.cgi/boost-testing

Re: Serialization library est errors for vaccp, borland and sun

2009-10-13T09:54:51Z

On Oct 13, 2009, at 11:11 AM, Robert Ramey wrote:

> Trunk tests for the serialization library on the following
> platforms suggest
> that the code being tested is different than that in the trunk:
> They fail
> for lack of files which should no longer appear in "#include"
> directives:
>
> vacpp - IBM_Canada_Ltd
> borland-cb2010 - codegear
>
> These tests seem to fail to build the library but no error messages
> are
> emitted.
>
> sun- 5.9 - Sandia-Linux-sun
> sun- 5.10 - Sandia-Linux-sun

sun-5.10 is on Solaris, not Linux.

I'll see if I can figure out why no output is being generated.

-- Noel

_______________________________________________
Boost-Testing mailing list
Boost-Testing@...
http://lists.boost.org/mailman/listinfo.cgi/boost-testing

Serialization library est errors for vaccp, borland and sun

2009-10-13T09:08:37Z

Trunk tests for the serialization library on the following platforms suggest
that the code being tested is different than that in the trunk: They fail
for lack of files which should no longer appear in "#include" directives:

vacpp - IBM_Canada_Ltd
borland-cb2010 - codegear

These tests seem to fail to build the library but no error messages are
emitted.

sun- 5.9 - Sandia-Linux-sun
sun- 5.10 - Sandia-Linux-sun

Robert Ramey

_______________________________________________
Boost-Testing mailing list
Boost-Testing@...
http://lists.boost.org/mailman/listinfo.cgi/boost-testing

Re: Test Running Crash

2009-10-02T06:28:19Z

Everything seems to be running well now, thanks!

I may be back when I try to get it going on a 64bit machine :-)

Vladimir Prus wrote:

> Tom Kent wrote:
>
>> So, now I seem to be having the same problem, except with msvc-8.0.
>>
>> I run my command:
>> python run.py --runner=BoeingVM-01 --toolset=msvc-8.0 --tag=trunk
>> --proxy=http://www-stl-proxy.boeing.com:31060 > log.txt 2>&1
>>
>> and get the output:
>> http://boost.teeks99.com/log_vs8.txt
>>
>> and the reuslts/bjam.log:
>> http://boost.teeks99.com/bjam.log
>>
>> Any thoughts on this one?
>
> Tom,
>
> this is a completely different problem; it even have a different error message ;-)
> The relevant output is:
>
> warning: No toolsets are configured.
> warning: Configuring default toolset "msvc".
> warning: If the default is wrong, your build may not work correctly.
> warning: Use the "toolset=xxxxx" option to override our guess.
> warning: For more configuration options, please consult
> ...
> error: "8.0" is not a known subfeature value of <toolset>msvc
>
> You had 9.0 configured by default, not 8.0. You can fix this by putting:
>
> using msvc : all ;
>
> in your user-config.jam. See
>
> http://www.boost.org/boost-build2/doc/html/bbv2/advanced/configuration.html
>
> for documentation about where user-config.jam should be placed.
>
> - Volodya
>
>
> _______________________________________________
> Boost-Testing mailing list
> Boost-Testing@...
> http://lists.boost.org/mailman/listinfo.cgi/boost-testing
>

_______________________________________________
Boost-Testing mailing list
Boost-Testing@...
http://lists.boost.org/mailman/listinfo.cgi/boost-testing

Re: Test Running Crash

2009-09-29T22:12:07Z

Tom Kent wrote:

> So, now I seem to be having the same problem, except with msvc-8.0.
>
> I run my command:
> python run.py --runner=BoeingVM-01 --toolset=msvc-8.0 --tag=trunk
> --proxy=http://www-stl-proxy.boeing.com:31060 > log.txt 2>&1
>
> and get the output:
> http://boost.teeks99.com/log_vs8.txt
>
> and the reuslts/bjam.log:
> http://boost.teeks99.com/bjam.log
>
> Any thoughts on this one?

Tom,

this is a completely different problem; it even have a different error message ;-)
The relevant output is:

warning: No toolsets are configured.
warning: Configuring default toolset "msvc".
warning: If the default is wrong, your build may not work correctly.
warning: Use the "toolset=xxxxx" option to override our guess.
warning: For more configuration options, please consult
...
error: "8.0" is not a known subfeature value of <toolset>msvc

You had 9.0 configured by default, not 8.0. You can fix this by putting:

using msvc : all ;

in your user-config.jam. See

http://www.boost.org/boost-build2/doc/html/bbv2/advanced/configuration.html

for documentation about where user-config.jam should be placed.

- Volodya

_______________________________________________
Boost-Testing mailing list
Boost-Testing@...
http://lists.boost.org/mailman/listinfo.cgi/boost-testing

Re: Test Running Crash

2009-09-29T13:28:26Z

So, now I seem to be having the same problem, except with msvc-8.0.

I run my command:
python run.py --runner=BoeingVM-01 --toolset=msvc-8.0 --tag=trunk
--proxy=http://www-stl-proxy.boeing.com:31060 > log.txt 2>&1

and get the output:
http://boost.teeks99.com/log_vs8.txt

and the reuslts/bjam.log:
http://boost.teeks99.com/bjam.log

Any thoughts on this one?

Tom

Tom Kent wrote:

> Aparently it was just something out of wack. I didn't change anything
> and tried again this morning and it all worked.
>
> I'm going to try one with msvc-9.0, msvc-8.0, and msvc-7.1 overnight and
> see how that goes.
>
> Tom
>
> Vladimir Prus wrote:
>> Tom Kent wrote:
>>
>>> About six months ago, I had several machines setup to run tests on the
>>> trunk a couple times a day, but the configuration got messed up and I'm
>>> just getting around to putting them back together.
>>>
>>> Now, when I run with the same command I used to use, it crashes on what
>>> I'm guessing is the first test:
>>>
>>> Traceback (most recent call last):
>>> File "run.py", line 60, in <module>
>>> runner(root)
>>> File "C:\Testing\tools_regression_src\regression.py", line 193, in
>>> __init__
>>> self.main()
>>> File "C:\Testing\tools_regression_src\regression.py", line 551, in main
>>> getattr(self,action_m)()
>>> File "C:\Testing\tools_regression_src\regression.py", line 516, in
>>> command_regression
>>> self.command_test()
>>> File "C:\Testing\tools_regression_src\regression.py", line 317, in
>>> command_test
>>> self.command_test_boost_build()
>>> File "C:\Testing\tools_regression_src\regression.py", line 354, in
>>> command_test_boost_build
>>> "boost/bin.v2/libs/any/test/any_test.test"));
>>> WindowsError: [Error 3] The system cannot find the path specified:
>>> 'C:\\Testing\\results\\boost/bin.v2/libs/any/test/any_test.test/*.*'
>>>
>>> I start running with just run.py and comment.html in the C:\Testing
>>> directory on Windows XP. I run the following command on it:
>>>
>>> python run.py --runner=BoeingVM-01 --toolset=msvc-9.0 --tag=trunk
>>> --proxy=http://www-stl-proxy.boeing.com:31060 > log.txt 2>&1
>>>
>>> If you want to view the entire log, you can see it at:
>>> http://boost.teeks99.com/log_crash.txt
>> The interesting log is:
>>
>> "C:\Testing\results\bjam.log"
>>
>> which is probably saying this:
>>
>> error: Unable to find file or target named
>> error: 'algorithm/nview.cpp'
>> error: referred from project at
>> error: '../libs/fusion/test'
>>
>> Due to a file somebody has forgot to commit. You should have more luck when that file is added.
>>
>> - Volodya
>>
>>
>>
>> _______________________________________________
>> Boost-Testing mailing list
>> Boost-Testing@...
>> http://lists.boost.org/mailman/listinfo.cgi/boost-testing
>>
> _______________________________________________
> Boost-Testing mailing list
> Boost-Testing@...
> http://lists.boost.org/mailman/listinfo.cgi/boost-testing
>

_______________________________________________
Boost-Testing mailing list
Boost-Testing@...
http://lists.boost.org/mailman/listinfo.cgi/boost-testing

Re: [spirit] [test] Double deletion problem?

2009-09-28T21:20:52Z

Gennadiy Rozental wrote:
> Beman Dawes <bdawes <at> acm.org> writes:
>
>> Did this get resolved?--Beman
>
> I am looking into this. I hope to get a hold of this platform next weekend.

Got one now. This should be resolved.

Gennadiy
_______________________________________________
Boost-Testing mailing list
Boost-Testing@...
http://lists.boost.org/mailman/listinfo.cgi/boost-testing

Re: [spirit] [test] Double deletion problem?

2009-09-28T14:55:57Z

Beman Dawes <bdawes <at> acm.org> writes:

> Did this get resolved?--Beman

I am looking into this. I hope to get a hold of this platform next weekend.

Genandiy

_______________________________________________
Boost-Testing mailing list
Boost-Testing@...
http://lists.boost.org/mailman/listinfo.cgi/boost-testing