From f9bfb829f86eb3c59c9321fb3c5b937d9aadc85a Mon Sep 17 00:00:00 2001 From: Gar Date: Thu, 8 May 2025 08:48:30 -0700 Subject: [PATCH] chore(smoke-tests): loosen check on install count These are not consistent and can change if the packages being installed change. It's not worth trying to keep up w/ this exact number. We have other tests that ensure the components of install work properly. This is just a smoke test. --- smoke-tests/test/large-install.js | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/smoke-tests/test/large-install.js b/smoke-tests/test/large-install.js index c7bf74affff2a..7b2cfae93de0a 100644 --- a/smoke-tests/test/large-install.js +++ b/smoke-tests/test/large-install.js @@ -29,9 +29,7 @@ const runTest = async (t, { lowMemory } = {}) => { // should be investigated. t.test('large install', async t => { const { stdout } = await runTest(t) - // As a bonus this test asserts that this package-lock always - // installs the same number of packages. - t.match(stdout, `added 130${process.platform === 'win32' ? 7 : 6} packages in`) + t.match(stdout, /added \d+ packages/) }) t.test('large install, no lock and low memory', async t => {