Notes |
|
(0021791)
|
David Cole
|
2010-08-18 00:38
|
|
Does this still occur with ctest from git 'master' or 'next'...?
Are you talking about executing via a script or via "ctest -D Nightly" or ...?
An example, or steps to reproduce the problem would be helpful.
Thanks. |
|
|
(0022028)
|
David Cole
|
2010-08-31 15:30
|
|
We will not be addressing this for the upcoming CMake 2.8.3 release. |
|
|
(0025248)
|
Rolf Eike Beer
|
2011-02-03 15:15
|
|
If you use this as test program:
#include <stdio.h>
#include <unistd.h>
int main(void)
{
printf("foobar\n");
sleep(10000000);
return 0;
}
And set the timeout to something less than the value passed to sleep the CTest log will only show "timeout" but not the output produced by the program so far ("foobar"). |
|
|
(0027141)
|
David Cole
|
2011-08-01 11:18
|
|
I'm uncertain of how much effort this one will take to fix... I'll put it on the roadmap, but unless somebody has a patch, or the knowledge of what exactly to change to fix this, then there may not be enough time to come up with a fix in the next two weeks. |
|
|
(0027477)
|
David Cole
|
2011-09-22 16:56
|
|
Not enough time left to address this issue before the 2.8.6 release. Deferred until a future release. |
|
|
(0027613)
|
Rolf Eike Beer
|
2011-10-22 06:20
|
|
I don't have access to the original failing stuff anymore. But I just tested this again. When adding fflush(stdout); before the sleep to make the stuff actually written by the process I see the results in the output log. So until someone proves me wrong I would say this has been fixed. |
|
|
(0027669)
|
David Cole
|
2011-10-28 12:21
|
|
Reported as "apparently fixed" by reporter... |
|
|
(0028840)
|
David Cole
|
2012-03-06 08:37
|
|
Closing resolved issues that have not been updated in more than 4 months. |
|