public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-1197] testsuite: outputs.exp: cleanup before running tests Date: Wed, 22 Jun 2022 02:11:39 +0000 (GMT) [thread overview] Message-ID: <20220622021139.1289D3835746@sourceware.org> (raw) https://gcc.gnu.org/g:7a1790ac6b475e9848e24200de9a1c44be422f5b commit r13-1197-g7a1790ac6b475e9848e24200de9a1c44be422f5b Author: Alexandre Oliva <oliva@adacore.com> Date: Tue Jun 21 23:10:59 2022 -0300 testsuite: outputs.exp: cleanup before running tests Use the just-added dry-run infrastructure to clean up files that may have been left over by interrupted runs of outputs.exp, which used to lead to spurious non-repeatable (self-fixing) failures. for gcc/testsuite/ChangeLog * gcc.misc-tests/outputs.exp: Clean up left-overs first. Diff: --- gcc/testsuite/gcc.misc-tests/outputs.exp | 3 +++ 1 file changed, 3 insertions(+) diff --git a/gcc/testsuite/gcc.misc-tests/outputs.exp b/gcc/testsuite/gcc.misc-tests/outputs.exp index a63ce66693b..ab919db1ccb 100644 --- a/gcc/testsuite/gcc.misc-tests/outputs.exp +++ b/gcc/testsuite/gcc.misc-tests/outputs.exp @@ -304,6 +304,9 @@ if { "$aout" != "" } then { set oaout "-o $aout" } +# Clean up any left-overs from an earlier interrupted run. +outest "$b-cleanup?" $sing "$oaout" {alt/ dir/ o/ od/ obj/} {{} {} {} {} {} {$aout}} + # Sometimes the -I or -L flags that cause the compiler driver to save # .args.[01], instead of leaving it for the linker to save .ld1_args, # is hiding in driver self specs.
reply other threads:[~2022-06-22 2:11 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220622021139.1289D3835746@sourceware.org \ --to=aoliva@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.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: linkBe 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).