Boost logo

Boost Testing :

Subject: Re: [Boost-testing] [EXTERNAL] URGENT: Regression testing repo migration..
From: Belcourt, Kenneth (kbelco_at_[hidden])
Date: 2015-01-27 13:06:28

On Jan 21, 2015, at 2:42 PM, Belcourt, K. Noel <kbelco_at_[hidden]> wrote:

> On Jan 21, 2015, at 2:30 PM, Rene Rivera <grafikrobot_at_[hidden]> wrote:
>> FYI.. I've started restructuring the regression repo to better know what the various tools are and the subparts thereof. And to try and work towards faster, cleaner, and easier to maintain code. And part of that restructure is done enough for report generation use. So..
>> On Fri, Jan 16, 2015 at 11:00 AM, Rene Rivera <grafikrobot_at_[hidden]> wrote:
>> I'm going to remove the outdated regression testing code in the boostorg/boost super-repo the weekend of January 24th. Everyone MUST stop using the old scripts immediately as they will disappear in approximately 7 days.
> While I fully appreciate and support your desire to do this, it appears there’s something wrong with the new version, at least our uses of it. I’ve tried several things and our testers do not seem to run correctly under the new, no idea why as yet. Could I ask that you please not remove the old stuff until we get this issue resolved?

Alright, I’ve found the source of our problem with the new script. For whatever reason, PJL was being built only once, rather than once per tester. I guess this is because I used to run testers with a completely clean test directory so PJL was built each time a tester ran. With the new script, it was finding a previously built PJL but was unable to locate the dependent shared libraries due to an overwritten LD_LIB path.

So Rene, I think you can safely remove the outdated regression testing code, thanks for giving me a chance to track this down.

— Noel

Boost-testing list run by mbergal at