public inbox for gdb-testers@sourceware.org help / color / mirror / Atom feed
From: sergiodj+buildbot@redhat.com To: gdb-testers@sourceware.org Subject: [binutils-gdb] testsuite: Make standard_temp_file use invocation-specific directories Date: Tue, 16 Feb 2016 15:36:00 -0000 [thread overview] Message-ID: <c4ef31bf6fb68f0024800565a532015fc3390aaa@gdb-build> (raw) *** TEST RESULTS FOR COMMIT c4ef31bf6fb68f0024800565a532015fc3390aaa *** Author: Simon Marchi <simon.marchi@ericsson.com> Branch: master Commit: c4ef31bf6fb68f0024800565a532015fc3390aaa testsuite: Make standard_temp_file use invocation-specific directories Just like standard_output_file, standard_temp_file should use multiple directories to make the tests parallel-safe. However, standard_temp_file is sometimes called in some procedures that are not test-specific. For example, gdb_init uses it, but is called once before all test files are ran. Therefore, we can't organize it in a temp/gdb.subdir/testname layout, like standard_output_file. Because it's just meant for temporary files that don't really need to be inspected after the test, we can just put them in a directory based on the runtest pid. There is always a single exp file being executed by a particular runtest invocation at any given time, so it should be safe. gdb/testsuite/ChangeLog: * lib/gdb.exp (standard_temp_file): Return a path specific to the runtest invocation.
next reply other threads:[~2016-02-16 15:36 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-02-16 15:36 sergiodj+buildbot [this message] 2016-02-16 15:36 ` Failures on Fedora-x86_64-m32, branch master sergiodj+buildbot 2016-02-16 15:43 ` Failures on RHEL-s390x-m64, " sergiodj+buildbot 2016-02-16 15:45 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot 2016-02-16 15:48 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot 2016-02-16 15:57 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot 2016-02-16 16:45 ` Failures on AIX-POWER7-plain, " sergiodj+buildbot 2016-02-16 17:45 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot 2016-02-16 20:01 ` Failures on Debian-i686, " sergiodj+buildbot 2016-02-16 20:23 ` Failures on Fedora-ppc64be-m64, " sergiodj+buildbot 2016-02-16 20:41 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj+buildbot 2016-02-16 21:00 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot 2016-02-16 21:21 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot 2016-02-16 21:57 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " sergiodj+buildbot
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=c4ef31bf6fb68f0024800565a532015fc3390aaa@gdb-build \ --to=sergiodj+buildbot@redhat.com \ --cc=gdb-testers@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).