public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "clyon at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/98999] New: Random testsuite errors in 27_io/filesystem/operations/canonical.cc Date: Mon, 08 Feb 2021 09:48:01 +0000 [thread overview] Message-ID: <bug-98999-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98999 Bug ID: 98999 Summary: Random testsuite errors in 27_io/filesystem/operations/canonical.cc Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: clyon at gcc dot gnu.org Target Milestone: --- I've noticed random testsuite failures in 27_io/filesystem/operations/canonical.cc I'm targeting arm, executing under qemu. As an example I can see this in my libstdc++.log: terminate called after throwing an instance of 'std::filesystem::__cxx11::filesystem_error' what(): filesystem error: cannot make canonical path: No such file or directory [filesystem-test.Iwjpan-canonical] terminate called after throwing an instance of 'std::filesystem::__cxx11::filesystem_error' what(): filesystem error: comparing 'native' failed: Invalid argument [] [/aci-gcc-fsf/builds/gcc-fsf-gccsrc-thumb/obj-arm-none-linux-gnueabi/gcc3/arm-none-linux-gnueabi/libstdc++-v3/testsuite/normal3/filesystem-test.dJGwrB-canonical] I'm not sure how to match this to a source line in the testcase?
next reply other threads:[~2021-02-08 9:48 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-08 9:48 clyon at gcc dot gnu.org [this message] 2021-02-08 9:52 ` [Bug libstdc++/98999] " clyon at gcc dot gnu.org 2021-02-08 9:56 ` clyon 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-98999-4@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: 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).