Re: [boost] what happened to the "tools/regression" directory - and the stuff in it?

On 3/18/2015 5:18 PM, Rene Rivera wrote:

On Wed, Mar 18, 2015 at 3:44 PM, Robert Ramey wrote:

...

Rene Rivera-2 wrote

...

So my question is - how is one supposed to invoke this functionality in the

...

current setup?

I don't know.. Since you have told me what the functionality is specifically. What did you used to build/run? And how?

I've used the procedure described here

http://www.boost.org/doc/libs/1_57_0/tools/regression/doc/library_status.htm...

OK. I'll see about updating that to where the code for that went to. And making sure it's working as best as I can. Won't be soon though.

Thanks ! I agree with Robert on this even if I had not used local regression testing but just executed b2 manually many times with different compilers for my libraries. I test on quite a few compilers and different versions largely on Windows and less so on Linux. Having an automated procedure that can test all the compilers I want to use in their various configurations at once, and then show me the regression tests results locally, seems much better than what I do manually, even if though I have my own command files both on Windows and Linux to make things easier for myself.

Also, note that the code for that tool is now at < https://github.com/boostorg/regression/tree/develop/library_status>. And IIRC it's updated to build if you clone/get the regression repo. But I never tried using the resulting executable. And process_jam_log is at < https://github.com/boostorg/regression/tree/develop/testing>.

Obviously something equivalent to this is necessary for every library

...

author. What do other library authors use? What do you recommend for testing on one's own machine?

Like Steven I just use b2 directly and read the output. But then I have a very simple library to deal with. So I'm not a good example.