public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/90787] filesystem tests fail if file permissions are not supported
Date: Tue, 12 Oct 2021 19:40:58 +0000	[thread overview]
Message-ID: <bug-90787-4-bPgeRCZSGT@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-90787-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90787

--- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-11 branch has been updated by Jonathan Wakely
<redi@gcc.gnu.org>:

https://gcc.gnu.org/g:cec047eaeb3ca40be65500d140a3a3f16db742e1

commit r11-9133-gcec047eaeb3ca40be65500d140a3a3f16db742e1
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Fri Aug 20 14:51:06 2021 +0100

    libstdc++: Skip filesystem tests that depend on permissions [PR90787]

    Tests that depend on filesystem permissions FAIL if run on Windows or as
    root. Add a helper function to detect those cases, so the tests can skip
    those checks gracefully.

    Signed-off-by: Jonathan Wakely <jwakely@redhat.com>

    libstdc++-v3/ChangeLog:

            PR libstdc++/90787
            * testsuite/27_io/filesystem/iterators/directory_iterator.cc:
            Use new __gnu_test::permissions_are_testable() function.
            *
testsuite/27_io/filesystem/iterators/recursive_directory_iterator.cc:
            Likewise.
            * testsuite/27_io/filesystem/operations/exists.cc: Likewise.
            * testsuite/27_io/filesystem/operations/is_empty.cc: Likewise.
            * testsuite/27_io/filesystem/operations/remove.cc: Likewise.
            * testsuite/27_io/filesystem/operations/remove_all.cc: Likewise.
            * testsuite/27_io/filesystem/operations/status.cc: Likewise.
            * testsuite/27_io/filesystem/operations/symlink_status.cc:
            Likewise.
            * testsuite/27_io/filesystem/operations/temp_directory_path.cc:
            Likewise.
            *
testsuite/experimental/filesystem/iterators/directory_iterator.cc:
            Likewise.
            *
testsuite/experimental/filesystem/iterators/recursive_directory_iterator.cc:
            Likewise.
            * testsuite/experimental/filesystem/operations/exists.cc:
            Likewise.
            * testsuite/experimental/filesystem/operations/is_empty.cc:
            Likewise.
            * testsuite/experimental/filesystem/operations/remove.cc:
            Likewise.
            * testsuite/experimental/filesystem/operations/remove_all.cc:
            Likewise.
            *
testsuite/experimental/filesystem/operations/temp_directory_path.cc:
            Likewise.
            * testsuite/util/testsuite_fs.h
(__gnu_test::permissions_are_testable):
            New function to guess whether testing permissions will work.

    (cherry picked from commit 29b2fd371f18169141e20b90effa7205db68fb11)

  parent reply	other threads:[~2021-10-12 19:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-90787-4@http.gcc.gnu.org/bugzilla/>
2021-07-18  7:08 ` pinskia at gcc dot gnu.org
2021-08-20 14:16 ` cvs-commit at gcc dot gnu.org
2021-08-20 14:16 ` redi at gcc dot gnu.org
2021-08-23  8:52 ` clyon at gcc dot gnu.org
2021-08-23 13:46 ` cvs-commit at gcc dot gnu.org
2021-10-12 19:40 ` cvs-commit at gcc dot gnu.org [this message]
2021-10-13 15:29 ` cvs-commit at gcc dot gnu.org
2021-10-13 17:07 ` redi at gcc dot gnu.org

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-90787-4-bPgeRCZSGT@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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: 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).