So ... I've been busy during the weeking poking the mesh viewer source
code with a stick g++ and can report some results. It seems quite some
of the issues were (re)introduced by mistakes in merge conflict
resolution. Some others are new. Here are the one's I've filed issues
for already:
Just so everyone knows I'm building on Windows 7 32-bit and both if the
tests that Boroondas mentions are actually memory leaking BADLY(test ballons
to nearly 1GB of mem usage) on my system just before crashing or I
terminated the process.
From: opensource-dev-boun...@lists.secondlife.com
I'm out of the office today and tomorrow, but will definitely be
looking into these patches and remaining issues on Wednesday. Thanks a
ton for helping us out!
Nyx
Sent from my iPhone
On Oct 25, 2010, at 10:27 AM, WolfPup Lowenhar wolfpu...@earthlink.net
wrote:
Just so everyone knows
On 10/25/2010 04:01 PM, Boroondas Gupte wrote:
Also, when tests are enabled, one of them errors out. That's right,
it's *not even failing*. :-P
Running: /usr/bin/python
${SRC_DIR}/indra/llmessage/tests/test_llsdmessage_peer.py
${BUILD_DIR}/llmessage/INTEGRATION_TEST_llsdmessage
On 10/25/2010 10:56 PM, Nicky Perian wrote:
I found the same thing about failed tests on 2d and subsequent builds.
The build has an error the first time but passes the second. This was
on VC++Express 2005 build. And, didn't matter about redoing develop.py.
So this isn't GNU make or even
It looks to be a problem with multiple tests running at the same time.
Looking at the error gives a hint that its a collision with a globally
shared named pipe of some type. Running the tests individually works
just fine for me, running more than one at a time doesn't.
On Mon, Oct 25, 2010 at
With my builds, if I rebuild the failed project individually the failure
repeats. If I build the full project a second time no failures are reported. It
appears that a run-once setting (if possible) is used for integration tests.
From: Zabb65 zab...@gmail.com
