Public bug reported: In "Timer" the method used to control the timeout of the class context is not thread safe. If two different threads running in the same process set signal.signal, the last one will prevail in favor of the first one:
signal.signal(signal.SIGALRM, self._timeout_handler) signal.alarm(self._timeout) Another method, thread safe, to control the class timeout should be implemented. This error can be seen in [1]. [1] http://logs.openstack.org/89/664889/4/check/openstack-tox- py37/ecb7c8d/testr_results.html.gz ** Affects: neutron Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1832925 Title: Class neutron.common.utils.Timer is not thread safe Status in neutron: New Bug description: In "Timer" the method used to control the timeout of the class context is not thread safe. If two different threads running in the same process set signal.signal, the last one will prevail in favor of the first one: signal.signal(signal.SIGALRM, self._timeout_handler) signal.alarm(self._timeout) Another method, thread safe, to control the class timeout should be implemented. This error can be seen in [1]. [1] http://logs.openstack.org/89/664889/4/check/openstack-tox- py37/ecb7c8d/testr_results.html.gz To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1832925/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
