public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Ulrich Müller" <ulm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/g-sorcery:master commit in: tests/
Date: Tue,  4 May 2021 15:50:36 +0000 (UTC)	[thread overview]
Message-ID: <1620143287.5a2f2b831f4190e74ccd2b6be263370d02fca56a.ulm@gentoo> (raw)

commit:     5a2f2b831f4190e74ccd2b6be263370d02fca56a
Author:     Brian Dolbec <dolsen <AT> gentoo <DOT> org>
AuthorDate: Thu Apr 23 17:28:31 2020 +0000
Commit:     Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Tue May  4 15:48:07 2021 +0000
URL:        https://gitweb.gentoo.org/proj/g-sorcery.git/commit/?id=5a2f2b83

tests/server.py: Add time.sleep() delay after shutdown

This is to help prevent a possible threading lock error if
traceback errors are raised.
I was experiencing this fault while debugging python 3.7 and 3.8 test
errors.  It prevented the sys.exit() at the end of the tests.

Signed-off-by: Brian Dolbec <dolsen <AT> gentoo.org>
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>

 tests/server.py | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/tests/server.py b/tests/server.py
index 51d49b7..6a32a2d 100644
--- a/tests/server.py
+++ b/tests/server.py
@@ -13,6 +13,7 @@
 
 import os
 import threading
+import time
 
 from g_sorcery.compatibility import py2k
 
@@ -49,3 +50,4 @@ class Server(threading.Thread):
 
     def shutdown(self):
         self.httpd.shutdown()
+        time.sleep(0.5)


             reply	other threads:[~2021-05-04 15:50 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-04 15:50 Ulrich Müller [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-05-04 15:50 [gentoo-commits] proj/g-sorcery:master commit in: tests/ Ulrich Müller
2021-05-04 15:50 Ulrich Müller
2013-09-18 22:52 Jauhien Piatlicki
2013-09-18 22:52 Jauhien Piatlicki
2013-09-18 22:09 Jauhien Piatlicki
2013-09-18 22:09 Jauhien Piatlicki
2013-09-18  0:57 Jauhien Piatlicki
2013-09-16 14:33 Jauhien Piatlicki
2013-09-16  0:19 Jauhien Piatlicki
2013-09-15 22:38 Jauhien Piatlicki
2013-09-15 22:38 Jauhien Piatlicki
2013-09-15 22:38 Jauhien Piatlicki
2013-07-17 15:41 Jauhien Piatlicki
2013-07-14 23:39 Jauhien Piatlicki
2013-07-08 23:53 Jauhien Piatlicki
2013-07-02 14:48 Jauhien Piatlicki
2013-07-02 10:21 Jauhien Piatlicki
2013-06-23  0:44 Jauhien Piatlicki
2013-06-23  0:44 Jauhien Piatlicki

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=1620143287.5a2f2b831f4190e74ccd2b6be263370d02fca56a.ulm@gentoo \
    --to=ulm@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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