From: Robert Ramey (ramey_at_[hidden])
Date: 2007-11-09 20:48:54
On november 2, I reported that it does.
Here is the tail of a bjam.log in which a test fails with an assertion
but is reported as passed.
>> ====== BEGIN OUTPUT ======
>> assertion "result.second" failed: file
>> _type_info.cpp", line 75
>> EXIT STATUS: 34304
>> ====== END OUTPUT ======
>> ...updated 32 targets...
So I would expect that some tests are failing but are being reported
as passed. On the other hand, I grepped the boost source and
assert is used only occasionally so I wouldn't think that including
this fix will have a huge impact.
Rene Rivera wrote:
> K. Noel Belcourt wrote:
>> There's a problem in execunix.c where I don't set the correct process
>> termination status if the process crashes or otherwise fails to exit
>> through normal channels (by calling exit() or_exit(), or exiting
>> through main). This patch marks the process termination status as
>> having failed if it doesn't exit through normal channels.
>> If there's no objection, I'll get this committed to trunk.
> No objection, only a question. Is this something that affects testing
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk