On 09/11/2015 12:37 PM, Roman Wüger wrote:
> I added the required command line options, but it doesn't produce
> the expected output. It works in a normal environment, but not
> in the "CTest test case". Could you have a look at it?
We need to distinguish running CTest in dashboard script mode,
g [mailto:brad.k...@kitware.com]
> Gesendet: Donnerstag, 10. September 2015 17:14
> An: Roman Wüger <roman.wue...@gmx.at>
> Cc: cmake-developers@cmake.org
> Betreff: Re: [cmake-developers] CTest threshold exceeds 1024 bytes
>
> On 09/10/2015 11:11 AM, Roman Wüger wrote:
> > I've
On 09/11/2015 12:37 PM, Roman Wüger wrote:
> It works in a normal environment, but not in the "CTest test case".
> Could you have a look at it?
No, sorry. You're implementing this feature so it is up to you to
debug and get it working.
-Brad
--
Powered by www.kitware.com
Please keep messages
Hi Brad,
I fail on implementing the test cases, I'm not familiar with testing this way
in general. How can we finish this change?
Best regards
Roman
> Am 31.08.2015 um 21:19 schrieb Brad King :
>
>> On 08/31/2015 07:36 AM, "Roman Wüger" wrote:
>> Attached you will find
On 09/10/2015 05:40 AM, Roman Wüger wrote:
> I fail on implementing the test cases, I'm not familiar with
> testing this way in general. How can we finish this change?
We need to have proper testing or the feature will break in the
future. You may not even need the new options. Have you tried
I know what you mean, sure I have tested it on a developer machine but not as
part of a "ctest unit test". I've tested it on a real world example.
My problem is to add a "ctest unit test case".
> Am 10.09.2015 um 17:06 schrieb Roman Wüger :
>
> I've tested it in the
On 09/10/2015 10:57 AM, Roman Wüger wrote:
> I don't know where to set the variables nor where to set the command line
> parameters.
> How can I then test that the maximum passed size is 40 bytes and the failed
> size is 60 for example?
> Where can I produce such test data (test.xml) with the
On 09/10/2015 11:11 AM, Roman Wüger wrote:
> I've tested it on a real world example.
>
> My problem is to add a "ctest unit test case".
The patch I last sent earlier in this thread adds a unit test
that produces and reads the Test.xml file. I left a comment:
# TODO: actually check the content
On 08/31/2015 07:36 AM, "Roman Wüger" wrote:
> Attached you will find the corrected patch.
Thanks. I've attached a revised version. I renamed the options
and added release notes. I also started the test case. Please
try completing the test and getting it to pass from there.
BTW, I noticed
Hi Brad,
sorry for the long response time, but I was on vacation.
Attached you will find the corrected patch.
Best regards
Roman
Am 20.08.15 um 17:30 schrieb Brad King
> On 08/20/2015 06:30 AM, Roman Wüger wrote:
>
> > I made the "atoi" change but my problem is the test itself.
>
> > I
Hello Brad,
I made the atoi change but my problem is the test itself. I don't know how to
specify the command line parameter and check the generated xml file.
Best Regards
RomN
Am 27.07.2015 um 17:52 schrieb Brad King brad.k...@kitware.com:
On 07/23/2015 03:23 AM, Roman Wüger wrote:
I
On 08/20/2015 06:30 AM, Roman Wüger wrote:
I made the atoi change but my problem is the test itself.
I don't know how to specify the command line parameter and
check the generated xml file.
Okay, please post the latest version of the patch so far and
I'll see if I can find a chance to work on
On 07/23/2015 03:23 AM, Roman Wüger wrote:
I don't know how to use the -check.cmake scripts to check the
length of the output.
My advice to use Tests/RunCMake/CTestCommandLine turns out to be
incorrect. Use Tests/RunCMake/ctest_test instead because that
one actually produces the .xml file.
Hello,
when I run CTest from the command line with the same parameters as on the build
server, then everything is working fine.
If I run the command on the build server then I get a message which says that
the threshold of 1024 bytes are exceeded. The output are debug messages and
not
14 matches
Mail list logo