public inbox for archer-commits@sourceware.org help / color / mirror / Atom feed
From: tromey@sourceware.org To: archer-commits@sourceware.org Subject: [SCM] tromey/fully-parallelize-test-suite: a couple more standard_temp_file calls Date: Wed, 14 Aug 2013 13:26:00 -0000 [thread overview] Message-ID: <20130814132635.2243.qmail@sourceware.org> (raw) The branch, tromey/fully-parallelize-test-suite has been updated via 2dc906cb9d153d7d5f21719003eb3364787a6fa1 (commit) via cd07b083cd4ae81835343eab33c50ffd4421edf8 (commit) from a4710630e77a6c1a1f495b7671274aa3b542a06d (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email. - Log ----------------------------------------------------------------- commit 2dc906cb9d153d7d5f21719003eb3364787a6fa1 Author: Tom Tromey <tromey@redhat.com> Date: Tue Aug 13 11:57:39 2013 -0600 a couple more standard_temp_file calls commit cd07b083cd4ae81835343eab33c50ffd4421edf8 Author: Tom Tromey <tromey@redhat.com> Date: Tue Aug 13 11:51:04 2013 -0600 fix up gdb_remote_download ----------------------------------------------------------------------- Summary of changes: gdb/testsuite/lib/cell.exp | 8 ++++---- gdb/testsuite/lib/gdb.exp | 14 +++++--------- 2 files changed, 9 insertions(+), 13 deletions(-) First 500 lines of diff: diff --git a/gdb/testsuite/lib/cell.exp b/gdb/testsuite/lib/cell.exp index 9a20f5c..448bd0a 100644 --- a/gdb/testsuite/lib/cell.exp +++ b/gdb/testsuite/lib/cell.exp @@ -78,10 +78,10 @@ gdb_caching_proc skip_cell_tests { # Set up, compile, and execute a combined Cell/B.E. test program. # Include the current process ID in the file names to prevent conflicts # with invocations for multiple testsuites. - set src cell[pid].c - set exe cell[pid].x - set src_spu cell[pid]-spu.c - set exe_spu cell[pid]-spu.x + set src [standard_temp_file cell[pid].c] + set exe [standard_temp_file cell[pid].x] + set src_spu [standard_temp_file cell[pid]-spu.c] + set exe_spu [standard_temp_file cell[pid]-spu.x] set f [open $src "w"] puts $f "#include <libspe2.h>" diff --git a/gdb/testsuite/lib/gdb.exp b/gdb/testsuite/lib/gdb.exp index fadbb4a..32602d3 100644 --- a/gdb/testsuite/lib/gdb.exp +++ b/gdb/testsuite/lib/gdb.exp @@ -3263,19 +3263,15 @@ proc gdb_touch_execfile { binfile } { } } -# Like remote_download but provides two gdb-specific behaviors. -# First, if TOFILE is not specified, then the [file tail] of FROMFILE -# is passed through standard_output_file to compute the destination. -# Second, if TOFILE has a directory component, it is first created on -# the appropriate machine. +# Like remote_download but provides a gdb-specific behavior. If DEST +# is "host", and the host is not remote, and TOFILE is not specified, +# then the [file tail] of FROMFILE is passed through +# standard_output_file to compute the destination. proc gdb_remote_download {dest fromfile {tofile {}}} { - if {$tofile == ""} { + if {$dest == "host" && ![is_remote host] && $tofile == ""} { set tofile [standard_output_file [file tail $fromfile]] } - if {[file dirname $tofile] != "."} { - remote_exec $dest mkdir [file dirname $tofile] - } return [remote_download $dest $fromfile $tofile] } hooks/post-receive -- Repository for Project Archer.
reply other threads:[~2013-08-14 13:26 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=20130814132635.2243.qmail@sourceware.org \ --to=tromey@sourceware.org \ --cc=archer-commits@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: 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).