| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
| |
(GH-17773) (GH-17786)
(cherry picked from commit 46abfc1416ff8e450999611ef8f231ff871ab133)
|
| |
|
| |
(cherry picked from commit 1d094af716e8ce5e5710e1dfbce7832ba333be55)
|
| |
|
|
|
|
| |
(GH-14229) (GH-14231)
(cherry picked from commit 015000165373f8db263ef5bc682f02d74e5782ac)
|
| |
|
|
|
|
|
|
|
|
| |
Fixed QueueListener in order to avoid random deadlocks.
Unable to add regression tests atm due to time constraints, will add it in a bit.
Regarding implementation, although it's nested, it does not cause performance issues whatsoever, and does not call task_done() in case of an exception (which is the right thing to do IMHO).
https://bugs.python.org/issue36813
(cherry picked from commit 6b282e18877ec84e927b381b4ce187eaf4ba3dd7)
Co-authored-by: Bar Harel <bzvi7919@gmail.com>
|
| |
|
|
|
|
|
| |
(GH-11908) (GH-13183)
(cherry picked from commit ca87eebb22d202c33f3317cbf85059cadc64fa9f)
Co-authored-by: Riccardo Magliocchetti <riccardo.magliocchetti@gmail.com>
|
| |
|
|
|
| |
(cherry picked from commit 2c10538d11fa9be9a1a9f21605861e10ec4fa207)
Co-authored-by: Xtreak <tir.karthi@gmail.com>
|
| |
|
|
|
|
|
|
| |
Instead of attempting to acquire and release them all across fork
which was leading to deadlocks in some applications that had chained
their own handlers while holding multiple locks.
(cherry picked from commit 64aa6d2000665efb1a2eccae176df9520bf5f5e6)
Co-authored-by: Gregory P. Smith <greg@krypto.org> [Google LLC]
|
| |
|
|
|
|
|
| |
(GH-13061)
(cherry picked from commit 2dad96013ca24abdc5ba5a369ea42d70ff02487a)
Co-authored-by: Xtreak <tir.karthi@gmail.com>
|
| |
|
|
|
| |
(cherry picked from commit 65f64b1903ae85b97a30f514bbc1b7ce940c3af2)
Co-authored-by: Rémi Lapeyre <remi.lapeyre@henki.fr>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
bpo-6721: When os.fork() was called while another thread holds a logging lock, the child process may deadlock when it tries to log. This fixes that by acquiring all logging locks before fork and releasing them afterwards.
A regression test that fails before this change is included.
Within the new unittest itself: There is a small _potential_ due to mixing of fork and a thread in the child process if the parent's thread happened to hold a non-reentrant library call lock (malloc?) when the os.fork() happens. buildbots and time will tell if this actually manifests itself in this test or not. :/ A functionality test that avoids that would be a challenge.
An alternate test that isn't trying to produce the deadlock itself but just checking that the release and acquire calls are made would be the next best alternative if so.
(cherry picked from commit 19003841e965bbf56fd06824d6093620c1b66f9e)
Co-authored-by: Gregory P. Smith <greg@krypto.org> [Google]
|
| |
|
|
|
| |
(cherry picked from commit d345bb4d9b6e16c681cd8a4e1fff94ecd6b0bb09)
Co-authored-by: Cheryl Sabella <cheryl.sabella@gmail.com>
|
| |
|
|
|
|
|
|
| |
Change test_logging.SMTPHandlerTest timeout from 8 seconds to 1
minute. The test failed randomly on the slow x86 Gentoo Refleaks 3.7
buildbot.
(cherry picked from commit 31b50b8cbfbf49d5fc17c612cf0dfaa4d0c24983)
Co-authored-by: Victor Stinner <vstinner@redhat.com>
|
| |
|
|
|
|
|
| |
(GH-8008) (GH-8044)
(cherry picked from commit 087570af6d5d39b51bdd5e660a53903960e58678)
Co-authored-by: Xtreak <tirkarthi@users.noreply.github.com>
|
| |
|
|
|
|
| |
This solves a regression in logging config due to changes in BPO-23835.
(cherry picked from commit 214f18e49feb6a9d6c05aa09a4bb304905e81334)
Co-authored-by: Łukasz Langa <lukasz@langa.pl>
|
| |
|
| |
Drop support of FreeBSD 9 and older.
|
| |
|
|
|
|
|
|
| |
* Fix multiple typos in code comments
* Add spacing in comments (test_logging.py, test_math.py)
* Fix spaces at the beginning of comments in test_logging.py
|
| |
|
|
| |
Skip tests with test.support.import_module('multiprocessing.synchronize')
instead when the semaphore implementation is broken or missing.
|
| |
|
|
|
|
|
|
|
|
|
| |
This used to be the case on Python 2. Commit
212b590e118e3650b596917021ed9612a918180b changed the implementation for Python
3, making the `log()` method of LogAdapter call `logger._log()` directly. This
makes nested log adapters not execute their ``process()`` method. This patch
fixes the issue.
Also, now proxying `name`, too, to make `repr()` work with nested log adapters.
New tests added.
|
| |
|
|
| |
Due to a bug in the initial fix, the setter was in fact creating a different
property. This is now fixed.
|
| |
|
|
|
|
| |
Replaces PROTOCOL_TLSv* and PROTOCOL_SSLv23 with PROTOCOL_TLS_CLIENT and
PROTOCOL_TLS_SERVER.
Signed-off-by: Christian Heimes <christian@python.org>
|
| |
|
|
| |
join_thread() joins a thread but raises an AssertionError if the
thread is still alive after timeout seconds.
|
| |
|
|
|
|
| |
Some of the proxied methods use internal Logger state which isn't proxied,
causing failures if an adapter is applied to another adapter.
This commit fixes the issue, adds a new test for the use case.
|
| |
|
|
|
|
|
|
|
| |
socketserver.ThreadingMixIn now keeps a list of non-daemonic threads
to wait until all these threads complete in server_close().
Reenable test_logging skipped tests.
Fix SocketHandlerTest.tearDown(): close the socket handler before
stopping the server, so the server can join threads.
|
| |
|
|
|
|
| |
* Remove Setup.config
* Always define WITH_THREAD for compatibility.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* bpo-30830: test_logging uses threading_setup/cleanup
Replace @support.reap_threads on some methods with
support.threading_setup() in setUp() and support.threading_cleanup()
in tearDown() in BaseTest.
* bpo-30830: test_logging disables threaded socketserver tests
Disable tests because of socketserver.ThreadingMixIn leaks threads,
whereas leaking threads now makes a test to fail on buildbots.
Disable tests until socketserver is fixed: bpo-31233.
* Skip also setup_via_listener()
|
| |
|
|
| |
kwargs. (GH-2979)
|
| | |
|
| |
|
|
| |
stream. (GH-2921)
|
| | |
|
| |
|
| |
Implemented pickling for loggers.
|
| |
|
|
| |
(#1676)
|
| |
|
|
|
|
|
|
| |
QueueListenerTest of test_logging now closes the multiprocessing
Queue and joins its thread to prevent leaking dangling threads to
following tests.
Add also @support.reap_threads to detect earlier if a test leaks
threads (and try to "cleanup" these threads).
|
| |
|
|
| |
* Use @support.reap_threads on unit tests creating threads
* Call TestCase.fail() on thread.join(timeout) failure
|
| |\ |
|
| | |\ |
|
| | | | |
|
| | | | |
|
| |\ \ \
| |/ / |
|
| | | |
| | |
| | |
| | | |
Thanks to Xavier de Gaye for the report and patch improvements.
|
| |/ / |
|
| |\ \
| |/ |
|
| | |
| |
| |
| | |
would raise ImportError
|
| | | |
|
| |/ |
|
| | |
|
| | |
|
| | |
|
| |\ |
|
| | | |
|