Re: [Boost-build] [EXTERNAL] Re: [Boost-testing] Problems building bjam?

Subject: Re: [Boost-build] [EXTERNAL] Re: [Boost-testing] Problems building bjam?
From: Jurko Gospodnetić (jurko.gospodnetic_at_[hidden])
Date: 2012-07-07 14:26:43

   Hi.

> Well trunk bjam seems to work okay on darwin (Last Changed Rev: 79321).

   Great! :-)

> Look at both the trunk and release testing summaries.  Every Sandia
> tester on these pages runs every night (Cray runs every other or third
> night).  Any Sandia tester that doesn't post updated results every 24
> hours is having some problem.  Based on last nights results, every
> Sanida trunk Linux tester is broken except for Vacpp and Clang.

   Ok, now I know what to expect from those test results. Thanks.

> On the release branch most all Sandia testers were broken.

   Release branch testing is using bjam from the trunk? You sure about 
this? Because I do not think I pushed any changes to the release branch yet.

> Perhaps smaller commits where you wait for tests to cycle before
> pushing more changes would work better?

   I run all the Boost Build tests locally (msvc + gcc on Cygwin) before 
I commit (well, most of the time :-P but if I do not - I run them soon 
afterwards and it happened only for the simpler changes). This issue 
slipped by me because all I was (un)lucky that all the tests passed and 
it's some buffer overrun problem causing random failures that does not 
slip by all that often... :-)

   I'm really trying to make the commits small. :-) The only 'large' 
ones (as in - many lines of code change) are ones containing stylistic 
code cleanup collected while researching the code or working on specific 
issues.

   As for the 'pushing more changes' - I do not see that as a problem 
since the testers report which revision they tested so it is easy to 
find out which revision is the 'last working one'. After that - it's 
just 'find out how to detect the problem locally' and 'bisect'.

   Now that I know your expected schedule - I'll know to 'revert sooner' 
should something like this creep by again. Can't promise it won't 
though. :-) There are lots more things that I'd like to polish up in 
that code base...

   Off to the bug-hunting wild lands now... I'll let you know when the 
beast has been slain...

   Best regards,
     Jurko Gospodnetić