On Tue, Aug 9, 2016 at 12:28 PM, Belcourt, Kenneth <kbelco@sandia.gov> wrote:
On Aug 9, 2016, at 5:21 AM, Murray Cumming <murrayc@murrayc.com> wrote:
On Di, 2016-06-28 at 17:32 +0000, Belcourt, Kenneth wrote:
The recent changes to the testing infrastructure has slowed this down as it’s now less-convenient to test that it was previously
Is this something different than this? https://github.com/boostorg/graph#running-tests
Related. I used to be able to edit status/Jamfile and remove all but a handful of libraries that I’d then test all together (so I could for example, test Graph, GraphParallel, MPI, etc.. all at once). The currently testing model doesn’t easily support testing multiple Boost libraries at one time and this slows me down.
Did you see my response at the time you brought this up on the command line options that let you control that? (i.e. the --limit-tests= option) Just wondering as I'm willing to add support for what you need if what's there is not enough. -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail