Re: [Boost-testing] [EXTERNAL] Run.py test failure 'minimal' is an invalid property

Subject: Re: [Boost-testing] [EXTERNAL] Run.py test failure 'minimal' is an invalid property
From: Tom Kent (lists_at_[hidden])
Date: 2017-06-08 12:39:41

On Wed, Jun 7, 2017 at 10:39 PM, Belcourt, Kenneth via Boost-Testing <
boost-testing_at_[hidden]> wrote:

> Hi,
>
> To followup with more info on this issue, testing is broken on master when
> building on the Mac, though not sure why.  Here’s what works okay:
>
> python run.py --tag=develop --runner="Sandia-clang-3.8"
> --toolset=clang-darwin --pjl-toolset=darwin --bjam-options="-j8”
>
> and what fails (same command with —tag=master):
>
> python run.py —tag=master --runner="Sandia-clang-3.8"
> --toolset=clang-darwin --pjl-toolset=darwin --bjam-options="-j8"
>
> The error from the failed master build is the error below.  It seems to be
> related to the context library use of alias (highlighted below).  Are there
> perhaps boost build or context changes that need to be merged to master
> into order to fix this issue?  From what I can tell, testing master on
> MacOS is hosed.
>
> Noel
>
>
> On Jun 7, 2017, at 6:03 PM, Belcourt, Kenneth via Boost-Testing <
> boost-testing_at_[hidden]> wrote:
>
>
>
> /Users/jenkins/slave/workspace/build-tpls/boost_bb/src/build/property.jam:529:
> in property.translate from module property
>
> error: 'minimal' is not a valid property specification
>
> /Users/jenkins/slave/workspace/build-tpls/boost_bb/
> src/build/property-set.jam:432: in property-set.create-from-user-input
> from module property-set
> /Users/jenkins/slave/workspace/build-tpls/boost_bb/
> src/build/property-set.jam:484: in property-set.refine-from-user-input
> from module property-set
> /Users/jenkins/slave/workspace/build-tpls/boost_bb/src/build/targets.jam:1619:
> in targets.main-target-requirements from module targets
> /Users/jenkins/slave/workspace/build-tpls/boost_bb/src/build/alias.jam:65:
> in test-suite from module alias
> *../libs/context/test/Jamfile.v2:97: in modules.load from module *
> Jamfile</Users/jenkins/slave/workspace/build-tpls/boost_
> root/libs/context/test>
> /Users/jenkins/slave/workspace/build-tpls/boost_bb/src/build/project.jam:325:
> in load-jamfile from module project
> /Users/jenkins/slave/workspace/build-tpls/boost_bb/src/build/project.jam:64:
> in load from module project
> /Users/jenkins/slave/workspace/build-tpls/boost_bb/src/build/project.jam:145:
> in project.find from module project
> Jamfile.v2:118: in run-tests from module Jamfile</Users/jenkins/slave/
> workspace/build-tpls/boost_root/status>
> Jamfile.v2:171: in modules.load from module Jamfile</Users/jenkins/slave/
> workspace/build-tpls/boost_root/status>
> /Users/jenkins/slave/workspace/build-tpls/boost_bb/src/build/project.jam:325:
> in load-jamfile from module project
> /Users/jenkins/slave/workspace/build-tpls/boost_bb/src/build/project.jam:64:
> in load from module project
> /Users/jenkins/slave/workspace/build-tpls/boost_bb/src/build/project.jam:145:
> in project.find from module project
> /Users/jenkins/slave/workspace/build-tpls/boost_bb/src/build-system.jam:535:
> in load from module build-system
> /Users/jenkins/slave/workspace/build-tpls/boost_bb/src/kernel/modules.jam:295:
> in import from module modules
> /Users/jenkins/slave/workspace/build-tpls/boost_bb/src/kernel/bootstrap.jam:139:
> in boost-build from module
> /Users/jenkins/slave/workspace/build-tpls/boost_root/boost-build.jam:17:
> in module scope from module
>
> I see the same error for master on linux and windows runners.
Tom