September 2016 - Boost - lists.preview.boost.org

Boost-1.62: How to get list of all dirs under 'run-tests libs:' target from status/Jamfile?
by Sergey Sprogis 04 Sep '16

04 Sep '16

I use latest Boost versions to test new C++ compiler in development stage. It's important for me to know what would be "pass rate" for every library which Boost.org reports on its Regression Testing website. To calculate all those pass rates I created script which goes inside every library's 'test', 'example' or whatever subdirectory and launches bjam from there. It creates a separate logfile(s) for every library which I then analyze to calculate "pass rate". But before launching my script I need to know the whole list of dirs which Boost.org uses for its Regression testing. In the previous Boost-1.61.0 version I was able to easily produce such list by extracting it from 'status/Jamfile.v2'. It looked like this: run-tests libs : accumulators/test # test-suite accumulators algorithm/test # test-suite algorithm algorithm/minmax/test # test-suite algorith/minmax ... concept_check # test-suite concept_check config/test # test-suite config container/bench # test-suite container benchmarks container/example # test-suite container_example ..... As you may see this list contains not only 'test' subdirs, but also some others: 'example', 'bench', etc. But now the problem is that in Boost-1.62.0 'status/Jamfile.v2' does not have such full list anymore. Could anyone suggest me some hack how to produce the full list of tested libraries for Boost-1.62.0, similar to one which Boost-1.61.0 has? It would be nice if bjam will eventually have a special option which will allow to produce such list, but for now I'd appreciate just a hack which will help me to solve this issue. Thanks, Sergey

2 1

[test] Unrecognized option -u
by Andrey Semashev 03 Sep '16

03 Sep '16

Hi, I'm seeing test errors about unrecognized option -u presumably from Boost.Test, see here for example: http://www.boost.org/development/tests/develop/developer/output/teeks99-09b… The test in question is not mine, and I don't know what the -u option is supposed to be for, but I assume it was supported by Boost.Test at some point and now it isn't. Is this an intended change in Boost.Test, an oversight or just a mistake in the Jamfile? If it was supported by Boost.Test, what did the option do and is it ok to just remove it?

3 4

[release] Can I push a bug fix?
by Andrzej Krzemienski 01 Sep '16

01 Sep '16

Hi all, Do I need permission now to push a bug fix to master? I intend to put this fix: https://github.com/boostorg/optional/commit/5d5d1f46baac851c8ec0ca15059d3e7… Regards, &rzej;

2 1