Menu
▾
▴
valgrind-developers
|
From: <min...@wi...> - 2025-09-30 09:57:38
|
From: Mingli Yu <min...@wi...> Though the valgrind testing is extended to produce automake-style log into test-suite-overall.log [1], it's better also print the test result to the stdout. [1] https://sourceware.org/git/?p=valgrind.git;a=commitdiff;h=61e44a4aef8775b925a7a91f403ebd7f4f6670a4 Signed-off-by: Mingli Yu <min...@wi...> --- tests/vg_regtest.in | 2 ++ 1 file changed, 2 insertions(+) diff --git a/tests/vg_regtest.in b/tests/vg_regtest.in index 945b4c161..2f5f3f678 100644 --- a/tests/vg_regtest.in +++ b/tests/vg_regtest.in @@ -720,6 +720,7 @@ sub test_one_dir($$) close(TSDIRLOG); my $result = do_one_test($full_dir, $f); print TSLOG scalar localtime, " result: $result $full_dir/$f.log\n"; + print "$result: $full_dir/$f\n"; $num_results{$result} ++; if ($result ne "PASS") { # transcribe .log file into the overall log. @@ -823,6 +824,7 @@ while (1) { # we will exit after one loop, unless looptillfail my $result = do_one_test($dir, $file); print TSLOG scalar localtime, " result: $result $dir/$file.log\n"; + print "$result: $dir/$file\n"; $num_results{$result} ++; if ($result ne "PASS") { # transcribe .log file into the overall log. -- 2.34.1 |
|
From: Yu, M. <min...@wi...> - 2025-10-15 06:21:59
|
Ping. Thanks, On 9/30/25 17:19, mingli.yu--- via Valgrind-developers wrote: > CAUTION: This email comes from a non Wind River email account! > Do not click links or open attachments unless you recognize the sender and know the content is safe. > > From: Mingli Yu <min...@wi...> > > Though the valgrind testing is extended to produce automake-style log into > test-suite-overall.log [1], it's better also print the test result to the > stdout. > > [1] https://sourceware.org/git/?p=valgrind.git;a=commitdiff;h=61e44a4aef8775b925a7a91f403ebd7f4f6670a4 > > Signed-off-by: Mingli Yu <min...@wi...> > --- > tests/vg_regtest.in | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/tests/vg_regtest.in b/tests/vg_regtest.in > index 945b4c161..2f5f3f678 100644 > --- a/tests/vg_regtest.in > +++ b/tests/vg_regtest.in > @@ -720,6 +720,7 @@ sub test_one_dir($$) > close(TSDIRLOG); > my $result = do_one_test($full_dir, $f); > print TSLOG scalar localtime, " result: $result $full_dir/$f.log\n"; > + print "$result: $full_dir/$f\n"; > $num_results{$result} ++; > if ($result ne "PASS") { > # transcribe .log file into the overall log. > @@ -823,6 +824,7 @@ while (1) { # we will exit after one loop, unless looptillfail > > my $result = do_one_test($dir, $file); > print TSLOG scalar localtime, " result: $result $dir/$file.log\n"; > + print "$result: $dir/$file\n"; > $num_results{$result} ++; > if ($result ne "PASS") { > # transcribe .log file into the overall log. > -- > 2.34.1 > > > > _______________________________________________ > Valgrind-developers mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-developers |
|
From: Paul F. <pj...@wa...> - 2025-10-15 06:35:21
|
On 2025-10-15 08:21, Yu, Mingli via Valgrind-developers wrote: > Ping. > > Thanks, > The patch looks OK. What is the benefit to having both a PASS/FAIL line printed for every test and the summary listing all tailed tests with the kind of failure such as == 1 test, 1 stderr failure, 0 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures == memcheck/tests/freebsd/utrace (stderr) A+ Paul |
|
From: Yu, M. <min...@wi...> - 2025-11-12 01:46:35
|
On 10/15/25 14:35, Paul Floyd via Valgrind-developers wrote: > CAUTION: This email comes from a non Wind River email account! > Do not click links or open attachments unless you recognize the sender > and know the content is safe. > > On 2025-10-15 08:21, Yu, Mingli via Valgrind-developers wrote: >> Ping. >> >> Thanks, >> > > The patch looks OK. > > What is the benefit to having both a PASS/FAIL line printed for every > test and the summary listing all tailed tests with the kind of failure > such as > > == 1 test, 1 stderr failure, 0 stdout failures, 0 stderrB failures, 0 > stdoutB failures, 0 post > failures == > memcheck/tests/freebsd/utrace (stderr) > > A+ It's more helpful to collect the test result if we print the PASS/FAIL at stdout. And only need to check test-suite-overall.log for the detailed test log if some test fails. Thanks, > > Paul > > > > > _______________________________________________ > Valgrind-developers mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-developers |
|
From: Yu, M. <min...@wi...> - 2025-11-06 06:35:04
|
Ping. Thanks, On 9/30/25 17:19, mingli.yu--- via Valgrind-developers wrote: > CAUTION: This email comes from a non Wind River email account! > Do not click links or open attachments unless you recognize the sender and know the content is safe. > > From: Mingli Yu <min...@wi...> > > Though the valgrind testing is extended to produce automake-style log into > test-suite-overall.log [1], it's better also print the test result to the > stdout. > > [1] https://sourceware.org/git/?p=valgrind.git;a=commitdiff;h=61e44a4aef8775b925a7a91f403ebd7f4f6670a4 > > Signed-off-by: Mingli Yu <min...@wi...> > --- > tests/vg_regtest.in | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/tests/vg_regtest.in b/tests/vg_regtest.in > index 945b4c161..2f5f3f678 100644 > --- a/tests/vg_regtest.in > +++ b/tests/vg_regtest.in > @@ -720,6 +720,7 @@ sub test_one_dir($$) > close(TSDIRLOG); > my $result = do_one_test($full_dir, $f); > print TSLOG scalar localtime, " result: $result $full_dir/$f.log\n"; > + print "$result: $full_dir/$f\n"; > $num_results{$result} ++; > if ($result ne "PASS") { > # transcribe .log file into the overall log. > @@ -823,6 +824,7 @@ while (1) { # we will exit after one loop, unless looptillfail > > my $result = do_one_test($dir, $file); > print TSLOG scalar localtime, " result: $result $dir/$file.log\n"; > + print "$result: $dir/$file\n"; > $num_results{$result} ++; > if ($result ne "PASS") { > # transcribe .log file into the overall log. > -- > 2.34.1 > > > > _______________________________________________ > Valgrind-developers mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-developers |
Thanks for helping keep SourceForge clean.
X