On Mon, Oct 20, 2008 at 10:53 AM, David Cole [EMAIL PROTECTED] wrote:
Another common source of apparently random results is uninitialized
variables. I don't think it is in ctest itself, as this is the first we've
heard of something like this on this mailing list (although anything's
Another common source of apparently random results is uninitialized
variables. I don't think it is in ctest itself, as this is the first we've
heard of something like this on this mailing list (although anything's
possible...)
Have you run your test code through valgrind to see if it catches any
I'm getting a strange, random error when running CTest...I've searched
all over and haven't been able to find anybody else with the same
problem. When I run a bunch of tests, some or all of them frequently
fail with a BAD_COMMAND error message. For instance, running ctest
just now gave me
On 2008-10-17 20:27-0400 Ian Mackenzie wrote:
I'm getting a strange, random error when running CTest...I've searched
all over and haven't been able to find anybody else with the same
problem.
[...]Each individual test executable runs fine, and none of them include
any randomness (e.g.
On Fri, Oct 17, 2008 at 10:09 PM, Alan W. Irwin
[EMAIL PROTECTED] wrote:
One potential source of randomness is failing or iffy hardware.
Have you kept track of such things as systematic changes in system
temperature under the same load conditions? I must clean out the dust from
one of my
