You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[IMP] odoo/tests: reporting & handling of chrome start issues
If we can't find the devtools port file after 10 seconds we skip the
test, however
- this is an invisible error because the runbot does not surface
skipped tests, so this specific variant should also have a warning
(also the skip from not finding a chrome executable)
- if chrome started but got stuck before it managed to create the port
file we don't `stop` the chromebrowser as it never finished
starting, however this means we leave a chrome running in the void
a `user_data_dir` littering the machine / vm's tempdir
So improve the handling of that bit. Also have chrome write its stderr
to a file (in the `user_data_dir`) so we can log that out in case it
contains useful information as to why chrome didn't finish booting.
While at it backport the spawn changes from odoo#206574 for consistency
and simplicity: we don't need to test the platform for every single
tour and the indirection makes updating the `Popen` parameters
unnecessary complicated.
closesodoo#232612
Signed-off-by: Xavier Morel (xmo) <xmo@odoo.com>
0 commit comments