From: vladimir.mezentsev@oracle.com
To: binutils@sourceware.org
Cc: Vladimir Mezentsev <vladimir.mezentsev@oracle.com>
Subject: [PATCH] gprofng: 30700 tmpdir/gp-collect-app_F test fails
Date: Thu, 3 Aug 2023 13:33:39 -0700 [thread overview]
Message-ID: <20230803203339.822435-1-vladimir.mezentsev@oracle.com> (raw)
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.
---
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
next reply other threads:[~2023-08-03 20:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-03 20:33 vladimir.mezentsev [this message]
2023-08-17 4:22 ` YunQiang Su
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=20230803203339.822435-1-vladimir.mezentsev@oracle.com \
--to=vladimir.mezentsev@oracle.com \
--cc=binutils@sourceware.org \
/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).