[19.0] checklog: ignore chrome zombie teardown warning#1577
Open
alan196 wants to merge 1 commit into
Open
Conversation
HttpCase tour tests emit a teardown WARNING when the headless Chrome leaves defunct (zombie) child processes that Odoo has to force-kill: WARNING ... Killing chrome descendants-or-self of N: M remaining - chrome (zombie) These processes are already dead and the warning is purely environmental (CI runner process reaping), but checklog-odoo flags it and turns every PR that runs a PoS/web tour red. Ignore it.
This was referenced Jun 27, 2026
|
@alan196 is this ready to merge? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Every PR in this repo that runs an HttpCase tour (PoS / web frontend tests) currently fails CI even though the tests themselves pass (
0 failed, 0 error(s)). The build is turned red bychecklog-odoo, which flags this teardown warning:The headless Chrome used by the tour leaves defunct (zombie) child processes that Odoo force-kills at the end of the test. They are already dead; the warning is purely environmental (CI runner process reaping) and not a defect in any addon.
Effect
Any migration/feature PR that adds or touches a tour is blocked (e.g. #1576, #1570, #1574 — all green tests, red build on this exact warning), while PRs without tours pass.
Fix
Add an ignore pattern for this teardown warning to
checklog-odoo.cfg, consistent with the existing0 failed, 0 error(s)ignore entry.