eventlet not waking after signal on py3 (and test_child_signal_sighup takes >60s/times out)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
oslo.service |
Fix Released
|
Medium
|
Zane Bitter |
Bug Description
It takes oslo_service.
Here are some more details on test runs: https:/
Notice the runtime for py35:
Test id Runtime (s)
-------
oslo_service.
And py27:
Test id Runtime (s)
-------
oslo_service.
summary: |
- py3: it takes 60 seconds to run - oslo_service.tests.test_service.ServiceLauncherTest.test_child_signal_sighup + py3: test_child_signal_sighup takes 500 times longer to run on py3 |
summary: |
- py3: test_child_signal_sighup takes 500 times longer to run on py3 + py3: test_child_signal_sighup takes ~500 times longer to run on py3 |
Changed in oslo.service: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in oslo.service: | |
assignee: | nobody → Zane Bitter (zaneb) |
summary: |
- py3: test_child_signal_sighup takes ~500 times longer to run on py3 + eventlet not waking after signal on py3 (and test_child_signal_sighup + takes >60s/times out) |
Fun fact: it also uses 100% of a CPU core during those 60s.
Python 3.4 is not affected, which suggests an issue with the fix for bug 1705047, but the problem appears to predate that patch (although strangely I can no longer reproduce the bug that patch fixed, even on py35 with eventlet 0.20.0).
The issue also occurs on stable/rocky, with eventlet 0.20.0.
Prior to https:/ /review. openstack. org/599032 there were similar issues with the oslo_service. tests.test_ service. EventletServerS erviceLauncherT est.test_ graceful_ stop_with_ exceeded_ graceful_ shutdown_ timeout and oslo_service. tests.test_ service. EventletServerS erviceLauncherT est.test_ shuts_down_ on_sigint_ when_client_ connected tests, which suggests that maybe that fix was incomplete?