March 2017 - Boost - lists.boost.org

[release] 1.64.0 closed for major changes
by Rene Rivera 02 Mar '17

02 Mar '17

The master branch is now closed for new libraries and breaking changes, and will be closing for major changes in a week and closed for the beta in two weeks. Also, if you're ready, you can also add your libraries' changes to the release notes at: < https://github.com/boostorg/website/blob/master/feed/history/boost_1_64_0.q… > Thanks, -- The Boost Release Team

1 0

Re: [boost] [Boost-testing] Much longer linux regression run times
by Tom Kent 01 Mar '17

01 Mar '17

On Tue, Feb 28, 2017 at 9:08 PM, Rene Rivera <grafikrobot(a)gmail.com> wrote: > On Tue, Feb 28, 2017 at 8:55 PM, Tom Kent via Boost-Testing < > boost-testing(a)lists.boost.org> wrote: > >> >> I'm not really sure how to trace this down. Is there any way to log the >> time it takes the various libraries to complete their test suites? >> > > Not currently. The individual tests can run in parallel. To give you that > number we would have to save the information as part of the regression data > and sum it up as part of the regression reports. > > >> I'm guessing that will show one library that is using 3+ hours. Although, >> it is possible that a change went in to a higher level library that just >> adds a few seconds to each call and is used across many of the libraries. >> >> Thoughts? >> > > Binary search manually? You can limit what tests you run on the command > line by using the "--include-tests" b2 option < > https://github.com/boostorg/boost/blob/develop/status/Jamfile.v2#L18>. So > start off by only running tests for [a-m] or [n-z], then [a-g], and so on. > Until you find the time hog. > That sounds tough. As a shortcut, I've looked at the libraries that had commits to develop on the 18th: https://github.com/boostorg/boost/commits/develop?after=Y3Vyc29yOudbdLMAs4G… It looks like hana, chrono, ratio, and thread (with wave and core/winapi the previous day). If I get a chance tonight I'll start checking through those. Meanwhile, if those authors could look at those and see if there is anything that might be causing this, it would be appreciated. > > Other than that, maybe it's one of the libraries tested on Travis < > https://travis-ci.org/boostorg/boost>. And maybe check the length of > those first if they are long on Travis perhaps they are also long on > regular tests. > I could find the travis scripts for the superset repo (no change in build time), but I'm not clear on what that is doing. Is it testing individual libraries? Tom

3 2

[smart_ptr][thread] Build failures
by Raffi Enficiaud 01 Mar '17

01 Mar '17

Hi all, I have the following compilation issues on master and develop, failing the VS2008, VS2012, VS2013 builds for boost.test (VS2015 ok): 01-Mar-2017 09:57:43 common.mkdir ..\..\..\bin.v2\libs\thread 01-Mar-2017 09:57:43 common.mkdir ..\..\..\bin.v2\libs\thread\build 01-Mar-2017 09:57:43 common.mkdir ..\..\..\bin.v2\libs\thread\build\msvc-11 01-Mar-2017 09:57:43 common.mkdir ..\..\..\bin.v2\libs\thread\build\msvc-11\debug 01-Mar-2017 09:57:43 common.mkdir ..\..\..\bin.v2\libs\thread\build\msvc-11\debug\link-static 01-Mar-2017 09:57:43 common.mkdir ..\..\..\bin.v2\libs\thread\build\msvc-11\debug\link-static\threading-multi 01-Mar-2017 09:57:43 common.mkdir ..\..\..\bin.v2\libs\thread\build\msvc-11\debug\link-static\threading-multi\win32 01-Mar-2017 09:57:45 compile-c-c++ ..\..\..\bin.v2\libs\thread\build\msvc-11\debug\link-static\threading-multi\win32\thread.obj 01-Mar-2017 09:57:45 thread.cpp 01-Mar-2017 09:57:45 D:\bamboo_build_dir\SW-BCB108-VC2012W64\library\boost/thread/detail/thread.hpp(486) : warning C4067: unexpected tokens following preprocessor directive - expected a newline 01-Mar-2017 09:57:45 D:\bamboo_build_dir\SW-BCB108-VC2012W64\library\boost/smart_ptr/allocate_shared_array.hpp(355) : error C2059: syntax error : ')' 01-Mar-2017 09:57:45 D:\bamboo_build_dir\SW-BCB108-VC2012W64\library\boost/smart_ptr/allocate_shared_array.hpp(358) : see reference to class template instantiation 'boost::detail::sp_less_align<T,U>' being compiled 01-Mar-2017 09:57:45 D:\bamboo_build_dir\SW-BCB108-VC2012W64\library\boost/smart_ptr/allocate_shared_array.hpp(357) : error C2143: syntax error : missing ')' before ';' 01-Mar-2017 09:57:45 D:\bamboo_build_dir\SW-BCB108-VC2012W64\library\boost/smart_ptr/allocate_shared_array.hpp(357) : error C2143: syntax error : missing '}' before ')' 01-Mar-2017 09:57:45 D:\bamboo_build_dir\SW-BCB108-VC2012W64\library\boost/smart_ptr/allocate_shared_array.hpp(357) : error C2059: syntax error : ')' 01-Mar-2017 09:57:45 D:\bamboo_build_dir\SW-BCB108-VC2012W64\library\boost/smart_ptr/allocate_shared_array.hpp(357) : error C2238: unexpected token(s) preceding ';' Can those be quickly fixed? Thanks, Raffi

3 4

[thread]Forever sleeping
by Niklas Angare 01 Mar '17

01 Mar '17

Recent runs of my regression test runner NA-QNX660-x86 leave a lot of Boost.Thread test executables stuck in nanosleep, waiting for a condition variable, or both. Commit 544eda [1] which switched from CLOCK_REALTIME to CLOCK_MONOTONIC seems suspicious to me. If the returned timespec is ever compared to values based on the CLOCK_REALTIME epoch, such as system_clock, the results will be quite undesirable. Are you sure the return values of timespec_now() are only ever compared to each other and values based on the CLOCK_MONOTONIC epoch? [1] https://github.com/boostorg/thread/commit/544eda51bdf0c62b2f29dea6fe1cf935a… Regards, Niklas Angare

3 9