From: Jeff Law <jeffreyalaw@gmail.com>
To: Thiago Jung Bauermann <thiago.bauermann@linaro.org>,
gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] [contrib] validate_failures.py: Don't consider summary line in wrong place
Date: Sat, 17 Jun 2023 16:03:18 -0600 [thread overview]
Message-ID: <3566ed67-3689-bc4e-6ce4-45da7b8be467@gmail.com> (raw)
In-Reply-To: <20230616120214.114098-1-thiago.bauermann@linaro.org>
On 6/16/23 06:02, Thiago Jung Bauermann via Gcc-patches wrote:
> When parsing a summary or manifest file, if we're not either after a tool
> line (e.g. "=== gdb tests ===") or before a summary line (e.g.,
> "=== gdb Summary ===") then the current line can't be a valid result line
> so ignore it.
>
> This addresses a problem we're seeing when running the GDB testsuite in
> our CI environment where it produces a valid summary file, but then after
> the "=== gdb Summary ===" section it outputs a series of Tcl errors that
> match _VALID_TEST_RESULTS_REX and thus confuse the parsing logic:
>
> 05: 14:32 .sum file seems to be broken: tool="None", exp="None", summary_line="ERROR: -------------------------------------------"
> 05: 14:32 Traceback (most recent call last):
> 05: 14:32 File "/path/to/gcc/contrib/testsuite-management/validate_failures.py", line 706, in <module>
> 05: 14:32 retval = Main(sys.argv)
> 05: 14:32 File "/path/to/gcc/contrib/testsuite-management/validate_failures.py", line 697, in Main
> 05: 14:32 retval = CheckExpectedResults()
> 05: 14:32 File "/path/to/gcc/contrib/testsuite-management/validate_failures.py", line 572, in CheckExpectedResults
> 05: 14:32 actual = GetResults(sum_files)
> 05: 14:32 File "/path/to/gcc/contrib/testsuite-management/validate_failures.py", line 447, in GetResults
> 05: 14:32 build_results.update(ParseSummary(sum_fname))
> 05: 14:32 File "/path/to/gcc/contrib/testsuite-management/validate_failures.py", line 389, in ParseSummary
> 05: 14:32 result = result_set.MakeTestResult(line, ordinal)
> 05: 14:32 File "/path/to/gcc/contrib/testsuite-management/validate_failures.py", line 236, in MakeTestResult
> 05: 14:32 return TestResult(summary_line, ordinal,
> 05: 14:32 File "/path/to/gcc/contrib/testsuite-management/validate_failures.py", line 148, in __init__
> 05: 14:32 raise
>
> contrib/ChangeLog:
>
> * testsuite-management/validate_failures.py (IsInterestingResult):
> Add result_set argument and use it. Adjust callers.
Thanks. I pushed this to the trunk.
jeff
next prev parent reply other threads:[~2023-06-17 22:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-16 12:02 Thiago Jung Bauermann
2023-06-17 22:03 ` Jeff Law [this message]
2023-06-19 10:04 ` Thiago Jung Bauermann
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=3566ed67-3689-bc4e-6ce4-45da7b8be467@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=thiago.bauermann@linaro.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).