wine/test.h: Identify the process responsible for test summary lines.
Sebastian Lackner
sebastian at fds-team.de
Thu Mar 9 09:20:08 CST 2017
On 22.02.2017 15:33, Francois Gouget wrote:
> Currently the child process summary lines are indistinguishable from the
> main process one. This makes it impossible to automatically detect
> when a process exits abruptly, i.e. without printing a summary line,
> if it has run a subprocess.
> This patch will let analysis tools identify which summary lines
> correspond to processes they started and thus when some are missing.
> Note also that in case of a crash the 'unhandled exception' play the
> same role as the test summary lines. Thus it is important to also tag
> them with the pid of the source process.
>
> Signed-off-by: Francois Gouget <fgouget at codeweavers.com>
> ---
> include/wine/test.h | 8 +++++---
> programs/winetest/main.c | 14 +++++++++-----
> 2 files changed, 14 insertions(+), 8 deletions(-)
Ugh... actually it looks like we have a summary line hardcoded in schedsvc tests:
--- snip ---
if (winetest_debug)
{
fprintf(stdout, "rpcapi: 0 tests executed (0 marked as todo, 0 failures), 1 skipped.\n");
fflush(stdout);
}
ExitProcess(0);
--- snip ---
Is it still recognized by the testbot?
More information about the wine-devel
mailing list