Google recently released Chrome 85 and our pipelines started to fail.
After some investigation we found out that there seem to be some issues (or changes that need to be addressed accordingly) with those recent Chrome versions. The "workaround" was to "lock" Chrome on version 84 to ensure our pipelines run correctly.
It was discovered on Aspera Connector context, but it would probably happen in WebUI and other projects that use our ftests framework and approach.
To reproduce it locally, using Aspera, the following steps are enough:
- Nuxeo 10.10 server, hot fixed with latest Aspera RC installed;
- Checkout https://github.com/nuxeo/nuxeo-aspera-connector (master);
- Open "nuxeo-aspera-web" and npm install;
- Execute npm run ftest
Please make sure latest Chrome is installed.