Entrypoint scripts spawning processes may break testing (e.g. geoipupdate)

[ap-wtioit]

It seems since [FIX] tests: catch remain processes ](odoo/odoo#231942) tests in doodba fail (for >= 17.0) in tearDownClass:

2025-11-25 08:38:04,893 1 INFO devel odoo.modules.loading: Module my_module: loading demo 
2025-11-25 08:38:04,894 1 INFO devel odoo.modules.loading: loading my_module/demo/my_module_data.xml 
2025-11-25 08:38:04,911 1 INFO devel odoo.addons.my_module.tests.test_update_planning: Starting TestUpdatePlanning.test_update_my_module ... 
2025-11-25 08:38:04,960 1 INFO devel odoo.addons.base.models.ir_attachment: filestore gc 0 checked, 0 removed 
2025-11-25 08:38:04,961 1 WARNING devel odoo.tests.common: A child process was found, terminating it: psutil.Process(pid=16, name='geoipupdate', status='sleeping', started='08:38:01') 
2025-11-25 08:38:04,961 1 WARNING devel odoo.tests.common: A child process was found, terminating it: psutil.Process(pid=28, name='sudo', status='zombie', started='08:38:01') 
2025-11-25 08:38:04,961 1 WARNING devel odoo.tests.common: A child process was found, terminating it: psutil.Process(pid=49, name='bash', status='sleeping', started='08:38:01') 
2025-11-25 08:38:04,962 1 INFO devel odoo.tests.suite: ====================================================================== 
2025-11-25 08:38:04,962 1 ERROR devel odoo.tests.suite: ERROR: tearDownClass (odoo.addons.my_module.tests.test_update_my_module.TestUpdateMyModule)
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/psutil/__init__.py", line 1183, in _send_signal
    os.kill(self.pid, sig)
PermissionError: [Errno 1] Operation not permitted

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/opt/odoo/custom/src/odoo/odoo/tests/common.py", line 362, in check_remaining_processes
    child.terminate()
  File "/usr/local/lib/python3.10/site-packages/psutil/__init__.py", line 278, in wrapper
    return fun(self, *args, **kwargs)
  File "/usr/local/lib/python3.10/site-packages/psutil/__init__.py", line 1236, in terminate
    self._send_signal(signal.SIGTERM)
  File "/usr/local/lib/python3.10/site-packages/psutil/__init__.py", line 1193, in _send_signal
    raise AccessDenied(self.pid, self._name)
psutil.AccessDenied: (pid=49, name='bash')
 
2025-11-25 08:38:04,973 1 INFO devel odoo.modules.loading: Module my_module loaded in 0.31s (incl. 0.06s test), 294 queries (+4 test, +294 other) 
2025-11-25 08:38:04,973 1 ERROR devel odoo.modules.loading: Module my_module: 0 failures, 1 errors of 1 tests 

Has anybody already dealt with this and fixed it?

[pedrobaeza]

Not faced yet any test with that, as tests rarely use tearDown.

[ap-wtioit]

Since odoo/odoo#231942 a tearDownClass (cls.addClassCleanup(...)) was added for odoo.tests.common.BaseCase, or do you have code running on your side to skip those?

For me it happens with GeoIP enabled when running docker compose run --rm odoo -u my_module --stop-after-init --no-http --test-enable --workers 0 in an odoo TransactionTestCase that only has the test method with self.assertTrue(True)

Edit: also happens without geoip (for us): because doodba entrypoint correctly execs odoo. odoo get's pid 1 and everything else is a child for odoo. We have a DNS watcher entrypoint script that is detected by Odoo's test tear down. So i think this should only happen to other doodba users if geoipupdate is running (or they have similar entrypoint scripts that spawn additional processes).

[pedrobaeza]

Uhm, no, all our tests in 17 and 18 are OK during all these weeks...