From: Alexandre Oliva <oliva@adacore.com>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: gcc Patches <gcc-patches@gcc.gnu.org>,
"libstdc++" <libstdc++@gcc.gnu.org>
Subject: Re: [PATCH] libstdc++: testsuite: test symlnks ifdef _GLIBCXX_HAVE_SYMLINK
Date: Thu, 23 Jun 2022 07:53:35 -0300 [thread overview]
Message-ID: <orilor647k.fsf@lxoliva.fsfla.org> (raw)
In-Reply-To: <CACb0b4=kLa=HcDLd26_1FhX2Uz5Nr5wut3r34kbM-XWcQEuKXw@mail.gmail.com> (Jonathan Wakely's message of "Wed, 22 Jun 2022 10:25:37 +0100")
On Jun 22, 2022, Jonathan Wakely <jwakely@redhat.com> wrote:
> Which tests are failing? I might be able to point you to the cause
> much faster than you can debug it yourself.
With commit 7e2db5d102dd05ffa9c46b89616f7a700a9889f8 (current
refs/users/aoliva/heads/testme) I get:
FAIL: 27_io/filesystem/iterators/caching.cc execution test
FAIL: 27_io/filesystem/iterators/error_reporting.cc execution test
FAIL: 27_io/filesystem/iterators/pop.cc execution test
FAIL: 27_io/filesystem/iterators/recursion_pending.cc execution test
FAIL: 27_io/filesystem/iterators/recursive_directory_iterator.cc execution test
terminate called after throwing an instance of 'std::filesystem::__cxx11::filesystem_error'
what(): filesystem error: cannot increment recursive directory iterator: No such file or directory
FAIL: 27_io/filesystem/operations/canonical.cc execution test
FAIL: 27_io/filesystem/operations/copy.cc execution test
terminate called after throwing an instance of 'std::filesystem::__cxx11::filesystem_error'
what(): filesystem error: cannot remove all: No such file or directory [...] [...]
FAIL: 27_io/filesystem/operations/create_directories.cc execution test
FAIL: experimental/filesystem/operations/create_directories.cc execution test
.../libstdc++-v3/testsuite/.../filesystem/operations/create_directories.cc:{84,78}: void test01(): Assertion 'count == 6' failed.
FAIL: 27_io/filesystem/operations/create_directory.cc execution test
FAIL: experimental/filesystem/operations/create_directory.cc execution test
[times out]
FAIL: 27_io/filesystem/operations/is_empty.cc execution test
FAIL: experimental/filesystem/operations/is_empty.cc execution test
Skipping tests that depend on filesystem permissions
[times out]
FAIL: 27_io/filesystem/operations/remove_all.cc execution test
FAIL: experimental/filesystem/operations/remove_all.cc execution test
.../libstdc++-v3/testsuite/.../filesystem/operations/remove_all.cc:6{7,8}: void test01(): Assertion '!ec' failed.
FAIL: 27_io/filesystem/operations/rename.cc execution test
FAIL: experimental/filesystem/operations/rename.cc execution test
.../libstdc++-v3/testsuite/.../filesystem/operations/rename.cc:5{1,2}: void test01(): Assertion '!ec' failed.
Also noteworthy, though unrelated with filesystem:
UNRESOLVED: 20_util/from_chars/4.cc compilation failed to produce executable
UNRESOLVED: 26_numerics/random/random_device/entropy.cc compilation failed to produce executable
error: 'log2' is not a member of 'std'; did you mean 'log'?
--
Alexandre Oliva, happy hacker https://FSFLA.org/blogs/lxo/
Free Software Activist GNU Toolchain Engineer
Disinformation flourishes because many people care deeply about injustice
but very few check the facts. Ask me about <https://stallmansupport.org>
next prev parent reply other threads:[~2022-06-23 10:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-22 6:13 Alexandre Oliva
2022-06-22 9:25 ` Jonathan Wakely
2022-06-22 10:42 ` Jonathan Wakely
2022-06-23 3:41 ` Alexandre Oliva
2022-06-23 10:53 ` Alexandre Oliva [this message]
2022-06-23 11:39 ` Jonathan Wakely
2022-06-23 11:02 ` Alexandre Oliva
2022-06-23 11:28 ` Jonathan Wakely
2022-06-23 11:29 ` Jonathan Wakely
2022-06-23 12:35 ` Alexandre Oliva
2022-06-23 12:37 ` Jonathan Wakely
2022-06-24 2:32 ` Alexandre Oliva
2022-06-27 13:29 ` Alexandre Oliva
2022-06-27 13:36 ` Jonathan Wakely
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=orilor647k.fsf@lxoliva.fsfla.org \
--to=oliva@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jwakely@redhat.com \
--cc=libstdc++@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).