public inbox for libstdc++-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jonathan Wakely <redi@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org
Subject: [gcc r14-8334] libstdc++: Fix check in testsuite/std/time/clock/file/io.cc
Date: Mon, 22 Jan 2024 13:06:29 +0000 (GMT)	[thread overview]
Message-ID: <20240122130629.2AA9E3858436@sourceware.org> (raw)

https://gcc.gnu.org/g:8229214faea572cd7157015711540e92e396523a

commit r14-8334-g8229214faea572cd7157015711540e92e396523a
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Mon Jan 22 10:48:55 2024 +0000

    libstdc++: Fix check in testsuite/std/time/clock/file/io.cc
    
    The test_format() function contained an incorrect assertion but wasn't
    actually being called from main.
    
    libstdc++-v3/ChangeLog:
    
            * testsuite/std/time/clock/file/io.cc: Fix expected result in
            assertion and call test_format() from main.

Diff:
---
 libstdc++-v3/testsuite/std/time/clock/file/io.cc | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/libstdc++-v3/testsuite/std/time/clock/file/io.cc b/libstdc++-v3/testsuite/std/time/clock/file/io.cc
index 3eee6bf5cc2..9ab9f10ec77 100644
--- a/libstdc++-v3/testsuite/std/time/clock/file/io.cc
+++ b/libstdc++-v3/testsuite/std/time/clock/file/io.cc
@@ -31,7 +31,7 @@ test_format()
   // PR libstdc++/113500
   auto ft = clock_cast<file_clock>(sys_days(2024y/January/21)) + 0ms + 2.5s;
   s = std::format("{}", ft);
-  VERIFY( s == "2024-01-17 00:00:02.500");
+  VERIFY( s == "2024-01-21 00:00:02.500");
 }
 
 void
@@ -54,5 +54,6 @@ test_parse()
 int main()
 {
   test_ostream();
+  test_format();
   test_parse();
 }

                 reply	other threads:[~2024-01-22 13:06 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=20240122130629.2AA9E3858436@sourceware.org \
    --to=redi@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.org \
    --cc=libstdc++-cvs@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).