🐛 [fix] ci: robust Chrome profile cleanup

[EricTechPro]

Note

Ready · Chrome cleanup regression reproduced and fixed

Problem

• macOS Chrome helpers can keep writing profile files after the parent exits, making successful visual checks fail during temporary-directory cleanup.

Solution

• Keep the existing Chrome exit wait and tolerate temporary-profile cleanup errors.
• Add an offline regression for late profile writes and preserve launch-error reporting.

Acceptance criteria

• A simulated ENOTEMPTY cleanup race preserves the DOM output.
• A missing Chrome binary still raises its launch error.
• Regression fails before the fix and passes after it.

Risk

• Low. A profile that cannot be deleted may remain in the OS temporary directory.

[qodo-code-review]

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →