"Jim Bell" <Jim@JC-Bell.com> wrote in message news:4CD18F27.8020803@JC-Bell.com...
On 1:59 PM, Dave Abrahams wrote:
That sounds much harder than simply running "bjam" in the library's test/ subdirectory.
Thanks! That does sound much easier. I didn't see that anywhere in the docs. That's a cryin' shame. Everyone seems to think they need to generate HTML, etc. etc. in order to run the tests, when all you need is bjam.
Could we add a section to <http://www.boost.org/development/running_regression_tests.html>, describing running tests locally? (Or at least a link to the page describing this?) That's the only documentation I've found (though I could easily have missed something).
I've burned a few hours on this. (And, more importantly, perceived it to be a difficult thing to do in isolation.)
+1 I also went with the procedure described on the web (for testing my new Boost.Function implementation) and as a result totally spammed the server(s)... A 'do not upload results to server' option for the run.py script would be quite useful (and the ability to see the HTML formatted/coloured results, w/o uploading, even more ;) ps. apologies if this was already discussed/solved...I just noticed this being discussed... -- "What Huxley teaches is that in the age of advanced technology, spiritual devastation is more likely to come from an enemy with a smiling face than from one whose countenance exudes suspicion and hate." Neil Postman