Since today, an unusual number of selenium builds seem to fail with errors like this:
15:34:30 npm error code ECONNRESET 15:34:30 npm error errno ECONNRESET 15:34:30 npm error network Invalid response body while trying to fetch https://registry.npmjs.org/@typescript-eslint%2fvisitor-keys: aborted 15:34:30 npm error network This is a problem related to network connectivity. 15:34:30 npm error network In most cases you are behind a proxy or have bad network settings. 15:34:30 npm error network 15:34:30 npm error network If you are behind a proxy, please make sure that the 15:34:30 npm error network 'proxy' config is set properly. See: 'npm help config' 15:34:30 npm error A complete log of this run can be found in: /cache/npm/_logs/2025-01-08T14_33_52_660Z-debug-0.log 15:34:30 ERROR: "install:bridge" exited with 1. 15:34:30 npm error code 1 15:34:30 npm error path /workspace/src/extensions/Wikibase 15:34:30 npm error command failed 15:34:30 npm error command sh -c npm-run-all -p install:*
@Michael noticed that these errors seemingly always come from the install:bridge step in Wikibase, even though (AFAIK) that’s far from the only place where we install dependencies from npm. But the errors don’t always happen – some builds go through successfully. My gut feeling is that roughly half the builds fail at the moment.
Affected builds (incomplete list):
- https://integration.wikimedia.org/ci/job/quibble-vendor-mysql-php74-selenium/63028/console
- https://integration.wikimedia.org/ci/job/wmf-quibble-selenium-php74/47840/console
- https://integration.wikimedia.org/ci/job/wmf-quibble-selenium-php74/47841/console
- https://integration.wikimedia.org/ci/job/wmf-quibble-selenium-php74/47848/console