[py3.10-ocb16.0] Chrome version 126 incompatible with recent Odoo tests commit: chrome_debug.log location

[Honeyxilia]

Describe the bug

A log saving was added to Odoo v16.0, for the ChromeBrowser executable, where they try to access the file self.user_data_dir (eg. /tmp/tmpXXX_chrome_odoo) + "/chrome_debug.log"

However, while on Chrome versions 128 and later, the initial profile is created within the provided self.user_data_dir, on previous versions, such as 126 (used in the aforementioned image), there's an additionnal Default subdirectory created, meaning the

On a local instance, with a more recent version of Chrome (or chromium), a test will pass, but on a previous version (ie. 126), the test will fail due to that log file.

To Reproduce

Affected versions: 16.0, with the py3.10-ocb16.0 docker image ( ghcr.io/oca/oca-ci/py3.10-ocb16.0:latest )

Steps to reproduce the behavior:

1. Create a test using HttpCase and browser_js
2. Insert a 16.0 .github/workflow/tests.yml with oca_run_tests and push onto a Git repository
3. Run the tests job

Expected behavior
The tests should pass within the docker image

Additional context
I have checked the Chrome release notes ( https://developer.chrome.com/release-notes/128 ) as well as Chromium's code, however I can't pinpoint the exact change which changed the user data directory behavior

However, having a more recent version of Chrome (such as 139) would circumvent this

[Honeyxilia]

Here's an exemple of this behavior : https://github.com/OCA/web/actions/runs/23501688842/job/68398207324?pr=3397

[Honeyxilia]

This issue seems to be tackled with this PR (and its author having submitted a comment on Odoo's repo) : #123

[Honeyxilia]

Unfortunally, the proposed PR does not fixes the bug for older Chrome versions, in which the chrome_debug.log file is created in a different folder (/tmp/tmpXXX_chrome_odoo/Default/chrome_debug.log as opposed to /tmp/tmpXXX_chrome_odoo/chrome_debug.log )

However, Odoo seems to be working on a more permanent fix, which is to check the file's presence before trying to open it, so once it's merged in Odoo 16.0, it should work better : odoo/odoo#255736