Several Wikibase builds, both test and gate-and-submit, have failed with strange npm errors. Example build: https://integration.wikimedia.org/ci/job/quibble-vendor-mysql-php72-selenium-docker/98120/console
npm WARN tarball tarball data for v8-compile-cache@https://registry.npmjs.org/v8-compile-cache/-/v8-compile-cache-2.2.0.tgz (sha512-gTpR5XQNKFwOd4clxfnhaqvfqMpqEwr4tOtCyz4MtYZX2JYhfr1JvBFKdS+7K/9rfpZR3VLX+YWBbKoxCgS43Q==) seems to be corrupted. Trying again. npm WARN tarball tarball data for resolve@https://registry.npmjs.org/resolve/-/resolve-1.19.0.tgz (sha512-rArEXAgsBG4UgRGcynxWIWKFvh/XZCcS8UJdHhwy91zwAvCZIbcs+vAbflgBnNjYMs/i/i+/Ux6IZhML1yPvxg==) seems to be corrupted. Trying again. npm WARN tarball tarball data for picomatch@https://registry.npmjs.org/picomatch/-/picomatch-2.2.2.tgz (sha512-q0M/9eZHzmr0AulXyPwNfZjtwZ/RBZlbN3K3CErVrk50T2ASYI7Bye0EvekFY3IP1Nt2DHu0re+V2ZHIpMkuWg==) seems to be corrupted. Trying again. npm WARN tarball tarball data for node-fetch@https://registry.npmjs.org/node-fetch/-/node-fetch-2.6.1.tgz (sha512-V4aYg89jEoVRxRb2fJdAg8FHvI7cEyYdVAh94HH0UIK8oJxUfkjlDQN9RbMx+bEjP7+ggMiFRprSti032Oipxw==) seems to be corrupted. Trying again. npm WARN tarball tarball data for normalize-url@https://registry.npmjs.org/normalize-url/-/normalize-url-4.5.1.tgz (sha512-9UZCFRHQdNrfTpGg8+1INIg93B6zE0aXMVFkw1WFwvO4SlZywU6aLg5Of0Ap/PgcbSw4LNxvMWXMeugwMCX0AA==) seems to be corrupted. Trying again. … npm ERR! code ENOENT npm ERR! syscall lstat npm ERR! path /cache/npm/_cacache/content-v2/sha512/e4/39/08c5e03b5c4441a8cc09ab468764e74c69d071e1ee9e0e8151bb24f9551f3627461c8360f033a19f03f11002127eb68453692d6521d4900aa82b9a13e797 npm ERR! errno -2 npm ERR! enoent ENOENT: no such file or directory, lstat '/cache/npm/_cacache/content-v2/sha512/e4/39/08c5e03b5c4441a8cc09ab468764e74c69d071e1ee9e0e8151bb24f9551f3627461c8360f033a19f03f11002127eb68453692d6521d4900aa82b9a13e797' npm ERR! enoent This is related to npm not being able to find a file. npm ERR! enoent
npm Status doesn’t show any errors at the moment.