Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gevent
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
gevent
Commits
ca2de796
Commit
ca2de796
authored
Jan 12, 2021
by
Jason Madden
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Skip test_cross_thread_use during leakchecks.
The background thread is problematic.
parent
fb70b4a5
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
4 additions
and
1 deletion
+4
-1
src/gevent/tests/test__event.py
src/gevent/tests/test__event.py
+4
-1
No files found.
src/gevent/tests/test__event.py
View file @
ca2de796
...
...
@@ -140,6 +140,7 @@ class TestAsyncResult(greentest.TestCase):
self
.
assertRaises
(
gevent
.
Timeout
,
ar
.
get
,
block
=
False
)
self
.
assertRaises
(
gevent
.
Timeout
,
ar
.
get_nowait
)
@
greentest
.
ignores_leakcheck
def
test_cross_thread_use
(
self
,
timed_wait
=
False
,
wait_in_bg
=
False
):
# Issue 1739.
# AsyncResult has *never* been thread safe, and using it from one
...
...
@@ -192,13 +193,15 @@ class TestAsyncResult(greentest.TestCase):
# This results in a separate code path
worker
=
gevent
.
spawn
(
work
)
worker
.
join
()
del
worker
else
:
work
()
g_event
.
set
()
glet
.
join
()
del
glet
self
.
finished_event
.
set
()
gevent
.
get_hub
().
destroy
(
destroy_loop
=
True
)
thread
=
Thread
()
thread
.
start
()
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment