public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Loren James Rittle <rittle@latour.labs.mot.com>
To: gcc@gcc.gnu.org
Subject: an analysis of gfortran.dg/stat_[12].f90 FAILs
Date: Fri, 21 Aug 2009 21:37:00 -0000	[thread overview]
Message-ID: <200908211644.n7LGis47084921@latour.labs.mot.com> (raw)

To whom it may concern:

Regarding the 16 gfortran failures involving gfortran.dg/stat_[12].f90
as seen in http://gcc.gnu.org/ml/gcc-testresults/2009-08/msg02179.html
(and all other recent testsuite reports from me):

It turns out that my gcc objdir was in a tmp directory owned by the
wheel group (0) and my primary group is users (15).  All new
(sub-)directories and files created under that tmp gained wheel group.
Thus, the test cases failed. Perhaps the tests should ensure that the
file is actually created with the same group ownership as the primary
group to be checked later in the test rather than assuming it.  I do
not know how to do that from within an f90 fortran program...

Regards,
Loren

                 reply	other threads:[~2009-08-21 16:46 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=200908211644.n7LGis47084921@latour.labs.mot.com \
    --to=rittle@latour.labs.mot.com \
    --cc=gcc@gcc.gnu.org \
    --cc=rittle@labs.mot.com \
    /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).