public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/109288] New: std/time/time_zone/get_info_local.cc failure with tzdata2023a Date: Sun, 26 Mar 2023 20:15:17 +0000 [thread overview] Message-ID: <bug-109288-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109288 Bug ID: 109288 Summary: std/time/time_zone/get_info_local.cc failure with tzdata2023a Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: jakub at gcc dot gnu.org Target Milestone: --- As mentioned in http://mm.icann.org/pipermail/tz-announce/2023-March/000077.html tzdata2023a includes Egypt now uses DST again, from April through October. and that change caused FAIL: std/time/time_zone/get_info_local.cc execution test because the test expects it doesn't use DST since 2014 or so.
next reply other threads:[~2023-03-26 20:15 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-26 20:15 jakub at gcc dot gnu.org [this message] 2023-03-27 9:55 ` [Bug libstdc++/109288] " redi at gcc dot gnu.org 2023-03-28 20:14 ` cvs-commit at gcc dot gnu.org 2023-03-28 20:21 ` 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-109288-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).