public inbox for libstdc++-cvs@sourceware.org
help / color / mirror / Atom feed
* [gcc(refs/users/aoliva/heads/testme)] libstdc++: 60241.cc: tolerate slightly shorter aggregate sleep
@ 2022-06-22  5:22 Alexandre Oliva
  0 siblings, 0 replies; 3+ messages in thread
From: Alexandre Oliva @ 2022-06-22  5:22 UTC (permalink / raw)
  To: gcc-cvs, libstdc++-cvs

https://gcc.gnu.org/g:8b555d2b49171c4b0a327104e359e4ebc7e5cca2

commit 8b555d2b49171c4b0a327104e359e4ebc7e5cca2
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Mon Jun 20 20:44:10 2022 -0300

    libstdc++: 60241.cc: tolerate slightly shorter aggregate sleep
    
    On rtems under qemu, the frequently-interrupted nanosleep ends up
    sleeping shorter than expected, by a margin of less than 0,3%.
    
    I figured failing the library test over a system (emulator?) bug is
    undesirable, so I put in some tolerance for the drift.
    
    
    for  libstdc++-v3/ChangeLog
    
            * testsuite/30_threads/this_thread/60421.cc: Tolerate a
            slightly early wakeup.

Diff:
---
 libstdc++-v3/testsuite/30_threads/this_thread/60421.cc | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/libstdc++-v3/testsuite/30_threads/this_thread/60421.cc b/libstdc++-v3/testsuite/30_threads/this_thread/60421.cc
index 12dbeba1cc4..f3a5af453c4 100644
--- a/libstdc++-v3/testsuite/30_threads/this_thread/60421.cc
+++ b/libstdc++-v3/testsuite/30_threads/this_thread/60421.cc
@@ -51,9 +51,10 @@ test02()
   std::thread t([&result, &sleeping] {
     auto start = std::chrono::system_clock::now();
     auto time = std::chrono::seconds(3);
+    auto tolerance = std::chrono::milliseconds(10);
     sleeping = true;
     std::this_thread::sleep_for(time);
-    result = std::chrono::system_clock::now() >= (start + time);
+    result = std::chrono::system_clock::now() + tolerance >= (start + time);
     sleeping = false;
   });
   while (!sleeping)


^ permalink raw reply	[flat|nested] 3+ messages in thread

* [gcc(refs/users/aoliva/heads/testme)] libstdc++: 60241.cc: tolerate slightly shorter aggregate sleep
@ 2022-06-21  0:17 Alexandre Oliva
  0 siblings, 0 replies; 3+ messages in thread
From: Alexandre Oliva @ 2022-06-21  0:17 UTC (permalink / raw)
  To: gcc-cvs, libstdc++-cvs

https://gcc.gnu.org/g:4ff3b788e20d6ff5d1e9830ecc27cc82ee90879a

commit 4ff3b788e20d6ff5d1e9830ecc27cc82ee90879a
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Mon Jun 20 20:44:10 2022 -0300

    libstdc++: 60241.cc: tolerate slightly shorter aggregate sleep
    
    On rtems under qemu, the frequently-interrupted nanosleep ends up
    sleeping shorter than expected, by a margin of less than 0,3%.
    
    I figured failing the library test over a system (emulator?) bug is
    undesirable, so I put in some tolerance for the drift.
    
    
    for  libstdc++-v3/ChangeLog
    
            * testsuite/30_threads/this_thread/60421.cc: Tolerate a
            slightly early wakeup.

Diff:
---
 libstdc++-v3/testsuite/30_threads/this_thread/60421.cc | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/libstdc++-v3/testsuite/30_threads/this_thread/60421.cc b/libstdc++-v3/testsuite/30_threads/this_thread/60421.cc
index 12dbeba1cc4..f3a5af453c4 100644
--- a/libstdc++-v3/testsuite/30_threads/this_thread/60421.cc
+++ b/libstdc++-v3/testsuite/30_threads/this_thread/60421.cc
@@ -51,9 +51,10 @@ test02()
   std::thread t([&result, &sleeping] {
     auto start = std::chrono::system_clock::now();
     auto time = std::chrono::seconds(3);
+    auto tolerance = std::chrono::milliseconds(10);
     sleeping = true;
     std::this_thread::sleep_for(time);
-    result = std::chrono::system_clock::now() >= (start + time);
+    result = std::chrono::system_clock::now() + tolerance >= (start + time);
     sleeping = false;
   });
   while (!sleeping)


^ permalink raw reply	[flat|nested] 3+ messages in thread

* [gcc(refs/users/aoliva/heads/testme)] libstdc++: 60241.cc: tolerate slightly shorter aggregate sleep
@ 2022-06-21  0:09 Alexandre Oliva
  0 siblings, 0 replies; 3+ messages in thread
From: Alexandre Oliva @ 2022-06-21  0:09 UTC (permalink / raw)
  To: gcc-cvs, libstdc++-cvs

https://gcc.gnu.org/g:6db4e87608c136dea82c605deb795cc9c94de2d5

commit 6db4e87608c136dea82c605deb795cc9c94de2d5
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Mon Jun 20 20:44:10 2022 -0300

    libstdc++: 60241.cc: tolerate slightly shorter aggregate sleep
    
    On rtems under qemu, the frequently-interrupted nanosleep ends up
    sleeping shorter than expected, by a margin of less than 0,3%.
    
    I figured failing the library test over a system (emulator?) bug is
    undesirable, so I put in some tolerance for the drift.
    
    
    for  libstdc++-v3/ChangeLog
    
            * testsuite/30_threads/this_thread/60421.cc: Tolerate a
            slightly early wakeup.
    
    TN: V608-049

Diff:
---
 libstdc++-v3/testsuite/30_threads/this_thread/60421.cc | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/libstdc++-v3/testsuite/30_threads/this_thread/60421.cc b/libstdc++-v3/testsuite/30_threads/this_thread/60421.cc
index 12dbeba1cc4..f3a5af453c4 100644
--- a/libstdc++-v3/testsuite/30_threads/this_thread/60421.cc
+++ b/libstdc++-v3/testsuite/30_threads/this_thread/60421.cc
@@ -51,9 +51,10 @@ test02()
   std::thread t([&result, &sleeping] {
     auto start = std::chrono::system_clock::now();
     auto time = std::chrono::seconds(3);
+    auto tolerance = std::chrono::milliseconds(10);
     sleeping = true;
     std::this_thread::sleep_for(time);
-    result = std::chrono::system_clock::now() >= (start + time);
+    result = std::chrono::system_clock::now() + tolerance >= (start + time);
     sleeping = false;
   });
   while (!sleeping)


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2022-06-22  5:22 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-06-22  5:22 [gcc(refs/users/aoliva/heads/testme)] libstdc++: 60241.cc: tolerate slightly shorter aggregate sleep Alexandre Oliva
  -- strict thread matches above, loose matches on Subject: below --
2022-06-21  0:17 Alexandre Oliva
2022-06-21  0:09 Alexandre Oliva

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).