|
Boost Testing : |
From: David Abrahams (dave_at_[hidden])
Date: 2007-03-27 14:00:49
on Tue Mar 27 2007, David Abrahams <dave-AT-boost-consulting.com> wrote:
> Martin, regardless of your discomfort, could we please follow my
> amended version of Nicola's suggested procedure, detailed below? We
> still obviously have some problems on your machines, as
> http://engineering.meta-comm.com/boost-regression/CVS-RC_1_34_0/developer/output/Martin%20Wille%20V2-boost-bin-v2-libs-python-test-extract-test-gcc-3-4-5_linux-debug_release.html
> shows. I don't see how we have the slightest hope of clearing these
> problems on your machines unless I can see the actual commands used to
> invoke, and the errors reported by, the run. Ideally, you could grant
> me temporary access to the actual systems running the tests so I could
> try to reproduce the problems there. Failing that, I have an account
> with nearly every major IM system and we could set up a chat session
> to handle this.
In fact, these failures look highly suspicious to me. Exit status 139
indicates a segmentation fault. I haven't seen these tests actually
/crash/ on any system or compiler before, including all viable
permutations 32/64-bit linux/windows gcc/msvc. There's definitely
something very odd going on here; I hope we can clear it up quickly.
-- Dave Abrahams Boost Consulting www.boost-consulting.com