public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: YunQiang Su <wzssyqa@gmail.com>
To: vladimir.mezentsev@oracle.com
Cc: binutils@sourceware.org
Subject: Re: [PATCH] gprofng: 30700 tmpdir/gp-collect-app_F test fails
Date: Thu, 17 Aug 2023 12:22:24 +0800	[thread overview]
Message-ID: <CAKcpw6WVy2ZAXzQC=cx7DM9DNf4iJmX0rr5dOdtNO7gbkTOBKg@mail.gmail.com> (raw)
In-Reply-To: <20230803203339.822435-1-vladimir.mezentsev@oracle.com>

Vladimir Mezentsev via Binutils <binutils@sourceware.org> 于2023年8月4日周五 04:34写道:
>
> From: Vladimir Mezentsev <vladimir.mezentsev@oracle.com>
>
> gprofng/ChangeLog
> 2023-08-03  Vladimir Mezentsev  <vladimir.mezentsev@oracle.com>
>
>         PR gprofng/30700
>         * testsuite/gprofng.display/gp-collect-app_F.exp: Fix -name argument
>         for sub-experiment filtering.

With your patch, It seems that this test still fails.
And in fact there are 3 failures for Gprofng on x86_64-linux ( I test
it on Debian):

testcase /home/syq/git-push/binutils-gdb/gprofng/testsuite/gprofng.display/display.exp
completed in 7 seconds
Running /home/syq/git-push/binutils-gdb/gprofng/testsuite/gprofng.display/gp-archive.exp
...
mkdir -p tmpdir/gp-archive
% timeout 300 sh -c 'mkdir -p tmpdir/gp-archive' 2>&1
cd tmpdir/gp-archive &&  cat
/home/syq/git-push/binutils-gdb/gprofng/testsuite/lib/smalltest.c |
sed '1 i /* CORRECTSOURCE */' > t.c &&  gcc -g t.c  &&
/home/syq/git-push/binutils-gdb/x86_64-linux-gnu/gprofng/src/gprofng
collect app -p on -a off -O exp.er ./a.out
% timeout 300 sh -c 'cd tmpdir/gp-archive &&  cat
/home/syq/git-push/binutils-gdb/gprofng/testsuite/lib/smalltest.c |
sed '1 i /* CORRECTSOURCE */' > t.c &&  gcc -g t.c  &&
/home/syq/git-push/binutils-gdb/x86_64-linux-gnu/gprofng/src/gprofng
collect app -p on -a off -O exp.er ./a.out' 2>&1
Experiment is not created in tmpdir/gp-archive
FAIL: tmpdir/gp-archive
testcase /home/syq/git-push/binutils-gdb/gprofng/testsuite/gprofng.display/gp-archive.exp
completed in 0 seconds
Running /home/syq/git-push/binutils-gdb/gprofng/testsuite/gprofng.display/gp-collect-app_F.exp
...
mkdir -p tmpdir/gp-collect-app_F
% timeout 300 sh -c 'mkdir -p tmpdir/gp-collect-app_F' 2>&1
cd tmpdir/gp-collect-app_F &&
/home/syq/git-push/binutils-gdb/x86_64-linux-gnu/gprofng/src/gprofng
collect app -p on -a off -F 'off' -O exp.er  sh -c 'mkdir t && touch
t/x; rm -rf t'
% timeout 300 sh -c 'cd tmpdir/gp-collect-app_F &&
/home/syq/git-push/binutils-gdb/x86_64-linux-gnu/gprofng/src/gprofng
collect app -p on -a off -F 'off' -O exp.er  sh -c 'mkdir t && touch
t/x; rm -rf t' ' 2>&1
Experiment is not created in tmpdir/gp-collect-app_F
FAIL: tmpdir/gp-collect-app_F
testcase /home/syq/git-push/binutils-gdb/gprofng/testsuite/gprofng.display/gp-collect-app_F.exp
completed in 0 seconds
Running /home/syq/git-push/binutils-gdb/gprofng/testsuite/gprofng.display/setpath_map.exp
...
mkdir -p tmpdir/setpath_map/src
% timeout 300 sh -c 'mkdir -p tmpdir/setpath_map/src' 2>&1
cd tmpdir/setpath_map &&  cat
/home/syq/git-push/binutils-gdb/gprofng/testsuite/lib/smalltest.c |
sed '1 i /* CORRECTSOURCE */' > t.c &&  gcc -g t.c  &&
/home/syq/git-push/binutils-gdb/x86_64-linux-gnu/gprofng/src/gprofng
collect app -p on -a off -O exp.er ./a.out
% timeout 300 sh -c 'cd tmpdir/setpath_map &&  cat
/home/syq/git-push/binutils-gdb/gprofng/testsuite/lib/smalltest.c |
sed '1 i /* CORRECTSOURCE */' > t.c &&  gcc -g t.c  &&
/home/syq/git-push/binutils-gdb/x86_64-linux-gnu/gprofng/src/gprofng
collect app -p on -a off -O exp.er ./a.out' 2>&1
Experiment is not created in tmpdir/setpath_map
FAIL: tmpdir/setpath_map

> ---
>  gprofng/testsuite/gprofng.display/gp-collect-app_F.exp | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/gprofng/testsuite/gprofng.display/gp-collect-app_F.exp b/gprofng/testsuite/gprofng.display/gp-collect-app_F.exp
> index f791b0f7a95..02bcc8e5b49 100644
> --- a/gprofng/testsuite/gprofng.display/gp-collect-app_F.exp
> +++ b/gprofng/testsuite/gprofng.display/gp-collect-app_F.exp
> @@ -46,11 +46,11 @@ proc run_gp_collect_app { subExpCnt F_opt } {
>      return -code break
>    }
>
> -  set output [run_native_host_cmd "find $tdir -name '*x1.er' | wc -l"]
> +  set output [run_native_host_cmd "find $tdir -name '*_x?.er' | wc -l"]
>    set subExp [lindex $output 1]
>    if { $subExp != $subExpCnt } then {
>      set out [lindex $output 1]
> -    send_log "Test failed for -F $F_opt. subExp=$subExp. Shold be $subExpCnt\n"
> +    send_log "Test failed for -F $F_opt. subExp=$subExp. Should be $subExpCnt\n"
>      fail $tdir
>      return -code break
>    }
> --
> 2.31.1
>


-- 
YunQiang Su

  reply	other threads:[~2023-08-17  4:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-03 20:33 vladimir.mezentsev
2023-08-17  4:22 ` YunQiang Su [this message]
2023-08-17 18:44   ` Vladimir Mezentsev
2023-08-18  2:11     ` YunQiang Su
2023-08-18  5:01       ` Vladimir Mezentsev
2023-08-18  5:09         ` YunQiang Su
2023-08-18  5:10         ` Sam James
2023-08-18  6:38           ` Matthias Klose
2023-08-18  6:45             ` Sam James
     [not found]             ` <f4c4c9956ccb5bc55fe95f51ee858e3558aa6acbe8d0d0ca0e8716bafbc1fbab@mu.id>
2023-08-18  6:49               ` Sam James

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAKcpw6WVy2ZAXzQC=cx7DM9DNf4iJmX0rr5dOdtNO7gbkTOBKg@mail.gmail.com' \
    --to=wzssyqa@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=vladimir.mezentsev@oracle.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).