public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "carlos at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug build/13888] /tmp usage during testing
Date: Wed, 16 Oct 2013 04:57:00 -0000	[thread overview]
Message-ID: <bug-13888-131-YTU30i5gN1@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13888-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=13888

--- Comment #4 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to Ondrej Bilka from comment #3)
> After running git grep '"/tmp' | grep -v "XXX" and bit of filtering files
> with hardcoded tmpname are following:
> 
> conform/conformtest.pl:$tmpdir = "/tmp";
> nptl/sockperf.c:#define PATH "/tmp/s.sockperf"
> nptl/tst-umask1.c:#define TEST_FUNCTION do_test (argc < 2 ?
> "/tmp/tst-umask.tmp" : argv[1])
> stdio-common/bug3.c:  const char filename[] = "/tmp/bug3.test";
> stdio-common/bug4.c:  const char filename[] = "/tmp/bug4.test";
> stdio-common/bug5.c:  static char inname[] = "/tmp/bug5.in";
> stdio-common/bug5.c:  static char outname[] = "/tmp/bug5.out";
> stdio-common/scanf14.c:    tmpdir = "/tmp";
> stdio-common/scanf15.c:    tmpdir = "/tmp";
> stdio-common/scanf16.c:    tmpdir = "/tmp";
> stdio-common/scanf17.c:    tmpdir = "/tmp";
> stdio-common/test-fseek.c:#define TESTFILE "/tmp/test.dat"
> stdio-common/test-popen.c:      perror ("/tmp/tstpopen.tmp");
> stdio-common/test-popen.c:  remove ("/tmp/tstpopen.tmp");
> stdio-common/test_rdwr.c:  (void) sprintf (filename, "/tmp/%s.test", name);
> ~

We need to fix all of these :-)

-- 
You are receiving this mail because:
You are on the CC list for the bug.


      parent reply	other threads:[~2013-10-16  4:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-21 17:36 [Bug build/13888] New: " tschwinge at sourceware dot org
2012-03-21 21:55 ` [Bug build/13888] " joseph at codesourcery dot com
2012-10-19 23:35 ` jsm28 at gcc dot gnu.org
2013-10-11 17:56 ` neleai at seznam dot cz
2013-10-16  4:57 ` carlos at redhat dot com [this message]

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=bug-13888-131-YTU30i5gN1@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@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).