Subject: Re: [boost] [test] Re: Conflicts when building libraries at root
From: Jürgen Hunold (jhunold_at_[hidden])
Date: 2015-03-13 03:14:08
Am Mittwoch, 11. März 2015, 15:03:54 schrieb Vladimir Prus:
> On 03/11/2015 01:40 PM, Vladimir Prus wrote:
> > 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.
Well, the tool itself does not change anything.
> Ok, we now have some solution. This job:
> is supposed to be triggered on any superproject commit and does
> "./bootstrap.sh; ./b2 -n" on Linux, so it should detect total build
Okay, that is better than nothing. Does it does not work on my fork for
creating PRs unfortunately. Investigating this. But that still won't catch the
"asynch-exceptions=on" Boost.Test case on windows. So we still have a long way
to go. Thanks for implementing this.
> It's still unclear who to setup email notification so that they
> go to the original author, not the bot that updates superproject.
Yes, that is unfortunate.
-- * Dipl.-Math. Jürgen Hunold ! * voice: ++49 4257 300 ! Fährstraße 1 * fax : ++49 4257 300 ! 31609 Balge/Sebbenhausen * jhunold_at_gmx.eu ! Germany
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk