Regression tests broken

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Regression tests broken

Boost - Testing mailing list
All-
Sometime around 7pm yesterday (2-17) a commit went in (master and develop?, regression scripts?) that broke all my regression runners (linux and windows). I haven't had a ton of time to dig in, but the end of the results look like this:


notice: using boost library auto_config <layout>system
../libs/contract/test/Jamfile.v2:417: Unescaped special character in argument <define>BOOST_CONTRACT_ON_MISSING_CHECK_DECL="{ throw err(); }"
notice: [libjpeg] Using pre-installed library
notice: [libjpeg] Condition
notice: [zlib] zlib is already configured
notice: [libpng] Using pre-installed library
notice: [libpng] Condition
notice: [libtiff] Using pre-installed library
notice: [libtiff] Condition
/var/boost/run/boost_bb/src/build/feature.jam:447: in extend-feature from module feature
error: coverage is already associated with the "<variant>" feature
/var/boost/run/boost_bb/src/build/feature.jam:624: in feature.extend from module feature
/var/boost/run/boost_bb/src/tools/features/variant-feature.jam:79: in variant from module variant-feature
../libs/histogram/Jamfile:15: in modules.load from module Jamfile</var/boost/run/boost_root/libs/histogram>
/var/boost/run/boost_bb/src/build/project.jam:372: in load-jamfile from module project
/var/boost/run/boost_bb/src/build/project.jam:64: in load from module project
/var/boost/run/boost_bb/src/build/project.jam:109: in load-parent from module project
/var/boost/run/boost_bb/src/build/project.jam:513: in initialize from module project
/var/boost/run/boost_bb/src/build/project.jam:348: in load-jamfile from module project
/var/boost/run/boost_bb/src/build/project.jam:64: in load from module project
/var/boost/run/boost_bb/src/build/project.jam:142: in project.find from module project
Jamfile.v2:122: in run-tests from module Jamfile</var/boost/run/boost_root/status>
Jamfile.v2:196: in modules.load from module Jamfile</var/boost/run/boost_root/status>
/var/boost/run/boost_bb/src/build/project.jam:372: in load-jamfile from module project
/var/boost/run/boost_bb/src/build/project.jam:64: in load from module project
/var/boost/run/boost_bb/src/build/project.jam:142: in project.find from module project
/var/boost/run/boost_bb/src/build-system.jam:618: in load from module build-system
/var/boost/run/boost_bb/src/kernel/modules.jam:295: in import from module modules
/var/boost/run/boost_bb/src/kernel/bootstrap.jam:139: in boost-build from module
/var/boost/run/boost_root/boost-build.jam:17: in module scope from module


Any thoughts?

Tom

_______________________________________________
Boost-Testing mailing list
[hidden email]
https://lists.boost.org/mailman/listinfo.cgi/boost-testing
Reply | Threaded
Open this post in threaded view
|

Re: [boost] Regression tests broken

Boost - Testing mailing list
On Tue, 19 Feb 2019 at 12:23, Mateusz Loskot <[hidden email]> wrote:

> On Tue, 19 Feb 2019 at 11:49, Hans Dembinski via Boost <[hidden email]> wrote:
> > > On 19. Feb 2019, at 04:29, Peter Dimov via Boost <[hidden email]> wrote:
> > >
> > > Tom Kent wrote:
> > >> All-
> > >> Sometime around 7pm yesterday (2-17) a commit went in (master and develop?, regression scripts?) that broke all my regression runners (linux and windows).
> > >
> > > It's this one: https://github.com/boostorg/histogram/commit/9abbe46e3dd57e2b55f7ab52eaed15994f76ae52#diff-42dd6ec1330a7c47aaccf2ab2b8f1e02R12
> >
> > so it was me, sorry. This error didn't show up in my unit test. It seems to come from my `coverage` variant, which I copied and modified from beast, where it seems to work fine.
>
> You seem to be running `b2 -j2 -q toolset=gcc-7 coverage`, while it
> should read `variant=coverage`
>
> AFAIS, Beast's `.travis.yml` sets `VARIANT` and other env variables, then calls
> `libs/beast/tools/retry.sh libs/beast/tools/build-and-test.sh`
> which composes the `b2` command line

I take that back. Boost.Build fu shortage here.
Your use seems fine [1], ass we've got it clarified on Slack.

[1] https://boostorg.github.io/build/manual/develop/index.html
"The release and debug that we have seen in b2 invocations are just
a shorthand way to specify values of the variant feature."

Best regards,
--
Mateusz Loskot, http://mateusz.loskot.net
_______________________________________________
Boost-Testing mailing list
[hidden email]
https://lists.boost.org/mailman/listinfo.cgi/boost-testing