Proton is failing for code already in production (current master) locally and for CI jobs.
Production is not affected.
Get latest Proton code and run npm test for it or submit any patch that doesn't change any code, like 516710.
Tests don't fail.
Tests fail with some 404 status and the following message:
HTTPError: request.uri.includes is not a function
| Project | Branch | Lines +/- | Subject | |
|---|---|---|---|---|
| mediawiki/services/chromium-render | master | +1 -1 | Fix html2pdf route |
There might be a breaking change upstream in one of the items npm pulls in? Because you're not on node10 you don't get the package-lock goodness…
OK, the last successful build of chromium-render-npm-browser-node-6-docker was on 29 April, #238, for change 504891 which was WIP. I just manually re-triggered this run as #243 and it failed with the same issue. It looks pretty likely that this is an upstream breakage.
Thanks for investigating, @Jdforrester-WMF. Looks like it's really time for T217114: Migrate Proton to k8s and nodejs 10 to happen.
Change 520307 had a related patch set uploaded (by MSantos; owner: MSantos):
[mediawiki/services/chromium-render@master] Fix html2pdf route
Change 520307 merged by jenkins-bot:
[mediawiki/services/chromium-render@master] Fix html2pdf route
Mentioned in SAL (#wikimedia-operations) [2019-07-31T19:59:53Z] <mbsantos@deploy1001> Started deploy [proton/deploy@ed6ebd8]: Update chromium-renderer to 529c493 (T227124)
Mentioned in SAL (#wikimedia-operations) [2019-07-31T20:01:37Z] <mbsantos@deploy1001> Finished deploy [proton/deploy@ed6ebd8]: Update chromium-renderer to 529c493 (T227124) (duration: 01m 43s)