We should not be able to merge code that is poorly formatted.
Running the tests might be blocked by having the build work in which case this task should also fix that.
We should not be able to merge code that is poorly formatted.
Running the tests might be blocked by having the build work in which case this task should also fix that.
I'm also working on the build for T233083, so we might want to make this a follow up of that (or vice versa).
Current sequential install time with npm install takes:
npm install 144.30s user 63.94s system 75% cpu 4:35.22 total
Current sequential install time with npm ci takes:
npm ci --verbose 88.89s user 51.78s system 125% cpu 1:52.24 total
Parallel: npm ci:
npm ci --verbose 78.94s user 42.81s system 212% cpu 57.290 total
Current sequential test run npm test takes (with one lint failure):
npm test 328.05s user 42.52s system 133% cpu 4:37.35 total
Parallel test run:
npm test 310.66s user 43.13s system 141% cpu 4:09.43 total
Looks like running in parallel would certainly be worth while.
Change 537986 had a related patch set uploaded (by Tarrow; owner: Tarrow):
[mediawiki/extensions/Wikibase@master] Tainted-ref: Make linting tests run on CI
Change 537987 had a related patch set uploaded (by Tarrow; owner: Tarrow):
[mediawiki/extensions/Wikibase@master] Use npm-run-all for install and test of node subcomponents
Change 537986 merged by jenkins-bot:
[mediawiki/extensions/Wikibase@master] Tainted-ref: Make linting tests run on CI
Change 537987 merged by jenkins-bot:
[mediawiki/extensions/Wikibase@master] Use npm-run-all for install and test of node subcomponents