2013/1/16 BILODEAU Andre andre.bilod...@safran-engineering.com:
Hello
I have finally the simplest setup which reproduces random BAD_COMMAND
errors:
- no compilations or produced binaries, justs tests
- tests are called without arguments or set properties
There are 20 tests, all of the form
Eric Noulard wrote:
and fill-in the form.
Then attach the zip file to your bug report.
You can even reply to this thread by simply giving the URL of
the bug in order to ease connecting the dots.
You can add yourself as monitoring the bug so that you'll get
follow-up from mantis.
You don't
2013/1/16 Rolf Eike Beer e...@sf-mail.de:
Eric Noulard wrote:
and fill-in the form.
Then attach the zip file to your bug report.
You can even reply to this thread by simply giving the URL of
the bug in order to ease connecting the dots.
You can add yourself as monitoring the bug so that
Am 16.01.2013 14:01, schrieb Eric Noulard:
2013/1/16 Rolf Eike Beer e...@sf-mail.de:
Eric Noulard wrote:
and fill-in the form.
Then attach the zip file to your bug report.
You can even reply to this thread by simply giving the URL of
the bug in order to ease connecting the dots.
You can add
: BILODEAU Andre
Cc : CMake ML
Objet : Re: [CMake] random BAD_COMMAND error on ctest
Andre please do not drop the ML address.
2013/1/9 BILODEAU Andre andre.bilod...@safran-engineering.com:
New test:
I just replaced my test driver by a simple stub, which is run for each of the
tests from test_01
...@gmail.com]
Envoyé : mercredi 9 janvier 2013 08:21
À : BILODEAU Andre
Cc : CMake ML
Objet : Re: [CMake] random BAD_COMMAND error on ctest
Andre please do not drop the ML address.
2013/1/9 BILODEAU Andre andre.bilod...@safran-engineering.com:
New test:
I just replaced my test driver by a simple stub
I just began to make ctest replace autotools for the program I develop, but I
still have some problems while running ctest.
Computer:
Intel(R) Core(TM)2 Duo CPU
E7500 @ 2.93GHz
RAM 3,37 GO
System:
Microsoft Windows XP
Version 2002
Service Pack 3
Environment:
Cygwin 1.7.17(0.262/5/3)
cmake
2013/1/8 BILODEAU Andre andre.bilod...@safran-engineering.com:
I just began to make ctest replace autotools for the program I develop, but
I still have some problems while running ctest.
Computer:
Intel(R) Core(TM)2 Duo CPU
E7500 @ 2.93GHz
RAM 3,37 GO
System:
Microsoft Windows XP
2013/1/8 BILODEAU Andre andre.bilod...@safran-engineering.com:
Thank you for your fast answer...
I have made more testing, in order to answer more questions:
1- With ctest -VV, the timeout is 9.99e+06, which seems comfortable.
2- With set_tests_properties, I set the timeout to 100. No
:37 +0100
From: BILODEAU Andre andre.bilod...@safran-engineering.com
Subject: [CMake] random BAD_COMMAND error on ctest
To: cmake@cmake.org
Message-ID:
d53c9aa26162984885f9060af83be1f527b...@sreublc136.eu.labinal.snecma
Content-Type: text/plain; charset=iso-8859-1
I just began to make
Andre please do not drop the ML address.
2013/1/9 BILODEAU Andre andre.bilod...@safran-engineering.com:
New test:
I just replaced my test driver by a simple stub, which is run for each of the
tests from test_01 to test_17:
#!/bin/ksh
exit 0
All the tests run without error.
That seems
11 matches
Mail list logo
