ning Boost Regression Tests
I have been using boost for quite a while (for years I used boost without running any tests other than those I wrote myself), and am now looking at running the regression tests. I found the statement: "To run every library's regression tests, run bjam from Boost's /status directory." What I haven't found is how to view the results of that testing on my own machine. I don't know if that is a catastrophic failure of the test script, or if I just didn't invoke bjam correctly. I ran bjam (in cygwin's bash, on Windows 7), without any arguments, in boost's status directory, and it executed a lot of tests. Obviously, that produced a lot more output than can be copied here, but the last few lines of output (after many many hundreds of lines of output) were: 1 [main] bjam 9280 fhandler_dev_zero::fixup_mmap_after_fork: requested 0x772B0000 != 0x0 mem alloc base 0x772B0000, state 0x1000, size 8192, Win32 error 487 263 [main] bjam 9280 C:\cygwin\home\Ted\boost_1_46_1\bjam.exe: *** fatal error - recreate_mmaps_after_fork_failed Stack trace: Frame Function Args 0028E5D0 6102796B (0028E5D0, 00000000, 00000000, 74C98458) 0028E8C0 6102796B (6117EC60, 00008000, 00000000, 61180977) 0028F8F0 61004F1B (61180DAC, 00000000, 61180DA6, 0041A000) 0028F930 610061B1 (00000060, 02000000, 6116A724, 6116A720) 0028F960 610064C0 (00000000, 00000002, 00000000, 75053480) 0028FA20 6106FC15 (61000000, 00000001, 0028FD24, 00000001) 0028FA40 77169960 (6106F960, 61000000, 00000001, 0028FD24) 0028FB34 7716D8C9 (0028FD24, 7EFDD000, 7EFDE000, 7723206C) 0028FCB0 771837EE (0028FD24, 77130000, 77AB63F9, 00000000) 0028FD00 77182187 (0028FD24, 77130000, 00000000, 00000000) 0028FD10 77169E89 (0028FD24, 77130000, 00000000, 0001002F) End of stack trace 0 [main] bjam 8628 fork: child -1 - died waiting for longjmp before initialization, retry 0, exit code 0x100, errno 11 vfork: Resource temporarily unavailable Obviously the last test executed failed, but I found no summary of the results, nothing to indicate whether or not most of the built library was built correctly. Did the regression test script abort without producing the summary, or do I need to pass some argument to tell it to display a summary (I had in mind the kind of output you get when building gcc, and you execute 'make check' before executing 'make install', as one doesn't want to install a library or anything else that didn't get built correctly)? Thanks Ted
On 4/29/2011 11:57 AM, Ted Byers wrote:
I have been using boost for quite a while (for years I used boost without running any tests other than those I wrote myself), and am now looking at running the regression tests.
I found the statement: "To run every library's regression tests, run bjamfrom Boost's /statusdirectory."
What I haven't found is how to view the results of that testing on my own machine. I don't know if that is a catastrophic failure of the test script, or if I just didn't invoke bjam correctly.
The output usually goes to 'boost/bin.v2'. If you look there, there is a 'lib' subdirectory and for each boost component its own directory under that subdirectory. Look for a subdirectory called 'test' for each component and if you drill down from there for each test you will eventually come to some output files for each test. Look at the file called 'sometest.output' and you will get the output for that test.
Thanks Edward,
On Fri, Apr 29, 2011 at 12:39 PM, Edward Diener
On 4/29/2011 11:57 AM, Ted Byers wrote:
I have been using boost for quite a while (for years I used boost without running any tests other than those I wrote myself), and am now looking at running the regression tests.
I found the statement: "To run every library's regression tests, run bjam from Boost's /statusdirectory."
What I haven't found is how to view the results of that testing on my own machine. I don't know if that is a catastrophic failure of the test script, or if I just didn't invoke bjam correctly.
The output usually goes to 'boost/bin.v2'. If you look there, there is a 'lib' subdirectory and for each boost component its own directory under that subdirectory. Look for a subdirectory called 'test' for each component and if you drill down from there for each test you will eventually come to some output files for each test. Look at the file called 'sometest.output' and you will get the output for that test.
OK, I find this. Thanks. But shall I assume, then, that the main test script failed because a proportion of the library directories do not have a test subdirectory? Also, I liked the testing done by gcc, in that for each part, it gave summary statistics about the number of passed and failed tests along with the expected number of passed and failed tests. When I write my own unit and integration tests, I accumulate that kind of summary and write it both to standard out and to a log file. Is such a summary, for individual libraries and for the whole collection of libraries, not available, or do I have to run the tests differently? Thanks again, Ted
participants (2)
-
Edward Diener -
Ted Byers