config.test randomly failing in CI (key store should be up-to-date) #611

MikeMcC399 · 2025-01-26T10:11:18Z

Issue

The CI Tests workflow is randomly failing in the build-and-test job in tests/config.test.ts inconsistently in Ubuntu, Windows & macOS with different Node.js versions.

  Object {
    "keys": Array [
      Object {
        "expires": null,
-       "key": "MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAE1Olb3zMAFFxXKHiIkQO5cJ3Yhl5i6UPp+IhuteBJbuHcA5UogKo0EWtlWwW6KSaKoTNEYL7JlCQiVnkhBktUgg==",
-       "keyid": "SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA",
+       "key": "MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEY6Ya7W++7aUPzvMTrezH6Ycx3c+HOKYCcNGybJZSCJq/fd7Qa8uuAKtdIkUQtQiEKERhAmE5lMMJhP8OkDOa2g==",
+       "keyid": "SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U",
        "keytype": "ecdsa-sha2-nistp256",
        "scheme": "ecdsa-sha2-nistp256",
      },
    ],
  }

Steps to reproduce

git clone https://github.com/nodejs/corepack
cd corepack
corepack yarn build
corepack yarn run vitest --run

or

corepack yarn run vitest -t "key store should be up-to-date" --run

Logs

$ corepack yarn run vitest -t "key store should be up-to-date" --run

 RUN  v2.0.3 /home/mike/github/corepack

 ↓ tests/Disable.test.ts (3) [skipped]
 ↓ tests/Enable.test.ts (3) [skipped]
 ↓ tests/Up.test.ts (1) [skipped]
 ↓ tests/Use.test.ts (2) [skipped]
 ❯ tests/config.test.ts (1) 786ms
   ❯ key store should be up-to-date (1) 785ms
     × should contain up-to-date npm keys (retry x2) 785ms
 ↓ tests/corepackUtils.test.ts (4) [skipped]
 ↓ tests/main.test.ts (81) [skipped]
 ↓ tests/npmRegistryUtils.test.ts (7) [skipped]

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Failed Tests 1 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯

 FAIL  tests/config.test.ts > key store should be up-to-date > should contain up-to-date npm keys
 FAIL  tests/config.test.ts > key store should be up-to-date > should contain up-to-date npm keys
 FAIL  tests/config.test.ts > key store should be up-to-date > should contain up-to-date npm keys
AssertionError: expected { keys: [ { expires: null, …(4) } ] } to match object { keys: [ { expires: null, …(4) } ] }

- Expected
+ Received

  Object {
    "keys": Array [
      Object {
        "expires": null,
-       "key": "MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAE1Olb3zMAFFxXKHiIkQO5cJ3Yhl5i6UPp+IhuteBJbuHcA5UogKo0EWtlWwW6KSaKoTNEYL7JlCQiVnkhBktUgg==",
-       "keyid": "SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA",
+       "key": "MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEY6Ya7W++7aUPzvMTrezH6Ycx3c+HOKYCcNGybJZSCJq/fd7Qa8uuAKtdIkUQtQiEKERhAmE5lMMJhP8OkDOa2g==",
+       "keyid": "SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U",
        "keytype": "ecdsa-sha2-nistp256",
        "scheme": "ecdsa-sha2-nistp256",
      },
    ],
  }

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[1/3]⎯

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Unhandled Errors ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯

Vitest caught 3 unhandled errors during the test run.
This might cause false positive tests. Resolve unhandled errors to make sure your tests are not affected.

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Unhandled Rejection ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
AssertionError: expected { keys: [ { expires: null, …(4) } ] } to match object { keys: [ { expires: null, …(4) } ] }

- Expected
+ Received

  Object {
    "keys": Array [
      Object {
        "expires": null,
-       "key": "MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAE1Olb3zMAFFxXKHiIkQO5cJ3Yhl5i6UPp+IhuteBJbuHcA5UogKo0EWtlWwW6KSaKoTNEYL7JlCQiVnkhBktUgg==",
-       "keyid": "SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA",
+       "key": "MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEY6Ya7W++7aUPzvMTrezH6Ycx3c+HOKYCcNGybJZSCJq/fd7Qa8uuAKtdIkUQtQiEKERhAmE5lMMJhP8OkDOa2g==",
+       "keyid": "SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U",
        "keytype": "ecdsa-sha2-nistp256",
        "scheme": "ecdsa-sha2-nistp256",
      },
    ],
  }

 ❯ Assertion.<anonymous> ../../.yarn/berry/cache/@vitest-expect-npm-2.0.3-7516a9278c-10c0.zip/node_modules/@vitest/expect/dist/index.js:1073:13
 ❯ Assertion.<anonymous> ../../.yarn/berry/cache/@vitest-expect-npm-2.0.3-7516a9278c-10c0.zip/node_modules/@vitest/expect/dist/index.js:912:17
 ❯ Assertion.methodWrapper ../../.yarn/berry/cache/chai-npm-5.1.1-2e09e40819-10c0.zip/node_modules/chai/chai.js:1591:25
 ❯ ../../.yarn/berry/cache/@vitest-expect-npm-2.0.3-7516a9278c-10c0.zip/node_modules/@vitest/expect/dist/index.js:1766:31
 ❯ processTicksAndRejections node:internal/process/task_queues:105:5

This error originated in "tests/config.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.
The latest test that might've caused the error is "should contain up-to-date npm keys". It might mean one of the following:
- The error was thrown, while Vitest was running this test.
- If the error occurred after the test had been completed, this was the last documented test before it was thrown.

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Unhandled Rejection ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
AssertionError: expected { keys: [ { expires: null, …(4) } ] } to match object { keys: [ { expires: null, …(4) } ] }

- Expected
+ Received

  Object {
    "keys": Array [
      Object {
        "expires": null,
-       "key": "MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAE1Olb3zMAFFxXKHiIkQO5cJ3Yhl5i6UPp+IhuteBJbuHcA5UogKo0EWtlWwW6KSaKoTNEYL7JlCQiVnkhBktUgg==",
-       "keyid": "SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA",
+       "key": "MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEY6Ya7W++7aUPzvMTrezH6Ycx3c+HOKYCcNGybJZSCJq/fd7Qa8uuAKtdIkUQtQiEKERhAmE5lMMJhP8OkDOa2g==",
+       "keyid": "SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U",
        "keytype": "ecdsa-sha2-nistp256",
        "scheme": "ecdsa-sha2-nistp256",
      },
    ],
  }

 ❯ Assertion.<anonymous> ../../.yarn/berry/cache/@vitest-expect-npm-2.0.3-7516a9278c-10c0.zip/node_modules/@vitest/expect/dist/index.js:1073:13
 ❯ Assertion.<anonymous> ../../.yarn/berry/cache/@vitest-expect-npm-2.0.3-7516a9278c-10c0.zip/node_modules/@vitest/expect/dist/index.js:912:17
 ❯ Assertion.methodWrapper ../../.yarn/berry/cache/chai-npm-5.1.1-2e09e40819-10c0.zip/node_modules/chai/chai.js:1591:25
 ❯ ../../.yarn/berry/cache/@vitest-expect-npm-2.0.3-7516a9278c-10c0.zip/node_modules/@vitest/expect/dist/index.js:1766:31
 ❯ processTicksAndRejections node:internal/process/task_queues:105:5

This error originated in "tests/config.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.
The latest test that might've caused the error is "should contain up-to-date npm keys". It might mean one of the following:
- The error was thrown, while Vitest was running this test.
- If the error occurred after the test had been completed, this was the last documented test before it was thrown.

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Unhandled Rejection ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
AssertionError: expected { keys: [ { expires: null, …(4) } ] } to match object { keys: [ { expires: null, …(4) } ] }

- Expected
+ Received

  Object {
    "keys": Array [
      Object {
        "expires": null,
-       "key": "MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAE1Olb3zMAFFxXKHiIkQO5cJ3Yhl5i6UPp+IhuteBJbuHcA5UogKo0EWtlWwW6KSaKoTNEYL7JlCQiVnkhBktUgg==",
-       "keyid": "SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA",
+       "key": "MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEY6Ya7W++7aUPzvMTrezH6Ycx3c+HOKYCcNGybJZSCJq/fd7Qa8uuAKtdIkUQtQiEKERhAmE5lMMJhP8OkDOa2g==",
+       "keyid": "SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U",
        "keytype": "ecdsa-sha2-nistp256",
        "scheme": "ecdsa-sha2-nistp256",
      },
    ],
  }

 ❯ Assertion.<anonymous> ../../.yarn/berry/cache/@vitest-expect-npm-2.0.3-7516a9278c-10c0.zip/node_modules/@vitest/expect/dist/index.js:1073:13
 ❯ Assertion.<anonymous> ../../.yarn/berry/cache/@vitest-expect-npm-2.0.3-7516a9278c-10c0.zip/node_modules/@vitest/expect/dist/index.js:912:17
 ❯ Assertion.methodWrapper ../../.yarn/berry/cache/chai-npm-5.1.1-2e09e40819-10c0.zip/node_modules/chai/chai.js:1591:25
 ❯ ../../.yarn/berry/cache/@vitest-expect-npm-2.0.3-7516a9278c-10c0.zip/node_modules/@vitest/expect/dist/index.js:1766:31
 ❯ processTicksAndRejections node:internal/process/task_queues:105:5

This error originated in "tests/config.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.
The latest test that might've caused the error is "tests/config.test.ts". It might mean one of the following:
- The error was thrown, while Vitest was running this test.
- If the error occurred after the test had been completed, this was the last documented test before it was thrown.
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯

 Test Files  1 failed | 7 skipped (8)
      Tests  1 failed | 101 skipped (102)
     Errors  3 errors
   Start at  10:26:53
   Duration  4.42s (transform 250ms, setup 97ms, collect 985ms, tests 786ms, environment 1ms, prepare 756ms)

Other

Manually viewing https://registry.npmjs.org/-/npm/v1/keys for instance with Postman shows:

{
    "keys": [
        {
            "expires": null,
            "keyid": "SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U",
            "keytype": "ecdsa-sha2-nistp256",
            "scheme": "ecdsa-sha2-nistp256",
            "key": "MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEY6Ya7W++7aUPzvMTrezH6Ycx3c+HOKYCcNGybJZSCJq/fd7Qa8uuAKtdIkUQtQiEKERhAmE5lMMJhP8OkDOa2g=="
        }
    ]
}

and this differs from

corepack/config.json

Lines 165 to 175 in 9dfbe18

    
           "keys": { 
        
             "npm": [ 
        
               { 
        
                 "expires": null, 
        
                 "keyid": "SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA", 
        
                 "keytype": "ecdsa-sha2-nistp256", 
        
                 "scheme": "ecdsa-sha2-nistp256", 
        
                 "key": "MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAE1Olb3zMAFFxXKHiIkQO5cJ3Yhl5i6UPp+IhuteBJbuHcA5UogKo0EWtlWwW6KSaKoTNEYL7JlCQiVnkhBktUgg==" 
        
               } 
        
             ] 
        
           }

The text was updated successfully, but these errors were encountered:

MikeMcC399 · 2025-01-26T12:51:22Z

This issue first occurred on Jan 22, 2025

See https://github.com/nodejs/corepack/actions/runs/12902587575/job/35976441289 from PR build(deps): bump vite from 5.4.6 to 5.4.14 #609

MikeMcC399 · 2025-01-27T19:37:55Z

This issue is no longer occurring randomly, and so it is being closed and replaced by issue config.test hard failure in CI (key store should be up-to-date) #613

MikeMcC399 mentioned this issue Jan 26, 2025

docs: add DEBUG=corepack logging instructions #605

Merged

MikeMcC399 mentioned this issue Jan 26, 2025

ci vitest fails "handle integrity checks" on Windows Node.js 23 #597

Open

sapphi-red mentioned this issue Jan 27, 2025

pnpm@10.1.0 / pnpm@9.15.4 cannot be installed due to key id mismatch #612

Open

MikeMcC399 changed the title ~~config.test randomly failing in CI~~ config.test randomly failing in CI (key store should be up-to-date) Jan 27, 2025

MikeMcC399 mentioned this issue Jan 27, 2025

config.test hard failure in CI (key store should be up-to-date) #613

Closed

MikeMcC399 closed this as not planned Won't fix, can't repro, duplicate, stale Jan 27, 2025

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

config.test randomly failing in CI (key store should be up-to-date) #611

config.test randomly failing in CI (key store should be up-to-date) #611

MikeMcC399 commented Jan 26, 2025 •

edited

Loading

MikeMcC399 commented Jan 26, 2025

MikeMcC399 commented Jan 27, 2025

config.test randomly failing in CI (key store should be up-to-date) #611

config.test randomly failing in CI (key store should be up-to-date) #611

Comments

MikeMcC399 commented Jan 26, 2025 • edited Loading

Issue

Steps to reproduce

Logs

Other

MikeMcC399 commented Jan 26, 2025

MikeMcC399 commented Jan 27, 2025

MikeMcC399 commented Jan 26, 2025 •

edited

Loading