Re: [boost] [test] Re: Conflicts when building libraries at root

Subject: Re: [boost] [test] Re: Conflicts when building libraries at root
From: Vladimir Prus (vladimir_at_[hidden])
Date: 2015-03-11 18:03:54

On 03/11/2015 01:40 PM, Vladimir Prus wrote:

>> The real issue is that the regression tests did not capture this because they
>> don't run the "bootstrap.{sh|bat} ; b2" "end-user build" sequence at all. And
>> my reports, others reports and my replies were obviously ignored, so
>> Boost.Context even got merged to master causing the same failure.
>> Sorry, I can't do much more than regularly (read: daily) building boost
>> develop and reporting bugs for the foreseeable future.
>> I'd really appreciate it if someone would enhance "run.py" to run the end-user
>> build sequence first and bail out with bells and whistles if that don't work.
>> This would have prevented us from getting into this mess in the first place.
>
> That's a valid point, and I understand why you would be upset. I've asked release
> managers what technical solutions we could use; it would be great if we could get
> notification of failed builds faster than the current builds turnaround - e.g.
> if we could just use Jenkins or similar.

Ok, we now have some solution. This job:

        https://travis-ci.org/boostorg/boost

is supposed to be triggered on any superproject commit and does "./bootstrap.sh; ./b2 -n" on
Linux, so it should detect total build failures. It's still unclear who to setup email
notification so that they go to the original author, not the bot that updates superproject.

-- 
Vladimir Prus
CodeSourcery / Mentor Embedded
http://vladimirprus.com