Re: [boost] [Boost-testing] [EXTERNAL] Run.py test failure 'minimal' is an invalid property
On Wed, Jun 7, 2017 at 10:39 PM, Belcourt, Kenneth via Boost-Testing < boost-testing@lists.boost.org> 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@lists.boost.org> 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_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 Jamfile.v2:171: in modules.load from module Jamfile /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
On Jun 8, 2017, at 6:39 AM, Tom Kent via Boost
wrote: On Wed, Jun 7, 2017 at 10:39 PM, Belcourt, Kenneth via Boost-Testing < boost-testing@lists.boost.org> wrote:
To followup with more info on this issue, testing is broken on master when building on the Mac, though not sure why.
/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_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 Jamfile.v2:171: in modules.load from module Jamfile /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.
Yes, I can confirm —tag=master is toast on Linux as well. So how is it possible that we completely missing catastrophic regression testing breakage on master? And how are any master testers even working, are they doing incremental runs? — Noel
On Thu, Jun 8, 2017 at 11:50 AM, Belcourt, Kenneth via Boost < boost@lists.boost.org> wrote:
Yes, I can confirm —tag=master is toast on Linux as well.
So how is it possible that we completely missing catastrophic regression testing breakage on master? And how are any master testers even working, are they doing incremental runs?
According to travis it's been broken for one day. Since this.. < https://travis-ci.org/boostorg/boost/builds/240420569>. As to why it went unnoticed.. Some times I'm really busy :-\ I'm looking to see what changed at that point. -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail
On Thu, Jun 8, 2017 at 12:29 PM, Rene Rivera
On Thu, Jun 8, 2017 at 11:50 AM, Belcourt, Kenneth via Boost < boost@lists.boost.org> wrote:
Yes, I can confirm —tag=master is toast on Linux as well.
So how is it possible that we completely missing catastrophic regression testing breakage on master? And how are any master testers even working, are they doing incremental runs?
According to travis it's been broken for one day. Since this.. < https://travis-ci.org/boostorg/boost/builds/240420569>. As to why it went unnoticed.. Some times I'm really busy :-\ I'm looking to see what changed at that point.
It could be either one of these two changes: < https://github.com/boostorg/context/commit/2b0bbd56a7fac1ad4cacc1b654a7997b8...
< https://github.com/boostorg/coroutine2/commit/7772218724ac21156390ccbf4ad123...
Don't know why though. -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail
Rene Rivera wrote:
https://github.com/boostorg/context/commit/2b0bbd56a7fac1ad4cacc1b654a7997b8...
There's a doubled test-suite full : minimal ; in this one.
On Thu, Jun 8, 2017 at 1:31 PM, Peter Dimov via Boost wrote: Rene Rivera wrote: https://github.com/boostorg/context/commit/2b0bbd56a7fac1ad4 cacc1b654a7997b8d6fbb7b#diff-e97299ad55a4013dc19889043aa464a5 There's a doubled test-suite full : minimal ; in this one. Thanks for finding that.. Not sure how I missed it. And looking at it while
fixing it.. Seems all the test targets are duplicated.
--
-- Rene Rivera
-- Grafik - Don't Assume Anything
-- Robot Dreams - http://robot-dreams.net
-- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail
On Jun 8, 2017, at 12:38 PM, Rene Rivera via Boost
wrote: On Thu, Jun 8, 2017 at 1:31 PM, Peter Dimov via Boost
wrote:
Rene Rivera wrote:
https://github.com/boostorg/context/commit/2b0bbd56a7fac1ad4
cacc1b654a7997b8d6fbb7b#diff-e97299ad55a4013dc19889043aa464a5
There's a doubled
test-suite full : minimal ;
in this one.
Thanks for finding that.. Not sure how I missed it. And looking at it while fixing it.. Seems all the test targets are duplicated.
Seems master tests are cycling normally again. Thanks for the quick fix!
On Fri, Jun 9, 2017 at 10:56 AM, Belcourt, Kenneth
On Jun 8, 2017, at 12:38 PM, Rene Rivera via Boost < boost@lists.boost.org> wrote:
On Thu, Jun 8, 2017 at 1:31 PM, Peter Dimov via Boost < boost@lists.boost.org
wrote:
Rene Rivera wrote:
https://github.com/boostorg/context/commit/2b0bbd56a7fac1ad4
cacc1b654a7997b8d6fbb7b#diff-e97299ad55a4013dc19889043aa464a5
There's a doubled
test-suite full : minimal ;
in this one.
Thanks for finding that.. Not sure how I missed it. And looking at it while fixing it.. Seems all the test targets are duplicated.
Seems master tests are cycling normally again. Thanks for the quick fix!
Welcome, and thanks for noticing. I also have to figure out why I didn't get error emails from Appveyor that it was broken. As otherwise I would have noticed immediately. -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail
On Fri, Jun 9, 2017 at 10:56 AM, Belcourt, Kenneth via Boost < boost@lists.boost.org> wrote:
On Jun 8, 2017, at 12:38 PM, Rene Rivera via Boost < boost@lists.boost.org> wrote:
On Thu, Jun 8, 2017 at 1:31 PM, Peter Dimov via Boost < boost@lists.boost.org
wrote:
Rene Rivera wrote:
https://github.com/boostorg/context/commit/2b0bbd56a7fac1ad4
cacc1b654a7997b8d6fbb7b#diff-e97299ad55a4013dc19889043aa464a5
There's a doubled
test-suite full : minimal ;
in this one.
Thanks for finding that.. Not sure how I missed it. And looking at it while fixing it.. Seems all the test targets are duplicated.
Seems master tests are cycling normally again. Thanks for the quick fix!
It looks like it was fixed for a couple runs, then broke again. I'm still seeing it across my windows and linux runners. Tom
On 10 June 2017 at 14:00, Tom Kent via Boost
It looks like it was fixed for a couple runs, then broke again. I'm still seeing it across my windows and linux runners.
Hopefully fixed now? https://github.com/boostorg/context/pull/59
On Sat, Jun 10, 2017 at 8:34 AM, Daniel James via Boost < boost@lists.boost.org> wrote:
On 10 June 2017 at 14:00, Tom Kent via Boost
wrote: It looks like it was fixed for a couple runs, then broke again. I'm still seeing it across my windows and linux runners.
Hopefully fixed now?
Hopefully.. And this is the second time Oliver messes up the build. Would it be possible to set the author on the super-project commits to the responsible author(s)? So that they get notifications about their failures? -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail
participants (5)
-
Belcourt, Kenneth
-
Daniel James
-
Peter Dimov
-
Rene Rivera
-
Tom Kent