Closed jpuri closed 1 month ago
Oof, I see that CI is failing. This could be either a problem where the cache is not being properly restored, or the incorrect set of files is being saved in the cache. In other repos we've discussed replacing yarn --immutable --immutable-cache
with yarn --immutable
in .github/workflows/build-lint-test.yml
. I'll try to investigate soon, but you could experimenting with that if you're stuck.
Oof, I see that CI is failing. This could be either a problem where the cache is not being properly restored, or the incorrect set of files is being saved in the cache. In other repos we've discussed replacing
yarn --immutable --immutable-cache
withyarn --immutable
in.github/workflows/build-lint-test.yml
. I'll try to investigate soon, but you could experimenting with that if you're stuck.
Saw this in other repos when rerunning previously passing jobs. Also specifically Node 22.
Node.js 22.5.0 was just released so maybe something lurking here?
Unless it's simply an intermittent infra issue at GH.
Oof, I see that CI is failing. This could be either a problem where the cache is not being properly restored, or the incorrect set of files is being saved in the cache. In other repos we've discussed replacing
yarn --immutable --immutable-cache
withyarn --immutable
in.github/workflows/build-lint-test.yml
. I'll try to investigate soon, but you could experimenting with that if you're stuck.Saw this in other repos when rerunning previously passing jobs. Also specifically Node 22.
Node.js 22.5.0 was just released so maybe something lurking here?
Unless it's simply an intermittent infra issue at GH.
Oof, I see that CI is failing. This could be either a problem where the cache is not being properly restored, or the incorrect set of files is being saved in the cache. In other repos we've discussed replacing
yarn --immutable --immutable-cache
withyarn --immutable
in.github/workflows/build-lint-test.yml
. I'll try to investigate soon, but you could experimenting with that if you're stuck.Saw this in other repos when rerunning previously passing jobs. Also specifically Node 22.
Node.js 22.5.0 was just released so maybe something lurking here?
Unless it's simply an intermittent infra issue at GH.
@legobeat a fix for this has just been included in a new node patch v22.5.1
I've fixed the Node issue here: https://github.com/MetaMask/eth-json-rpc-middleware/pull/321
The PR addresses these 2 issues:
https://github.com/MetaMask/metamask-extension/issues/25733 https://github.com/MetaMask/MetaMask-planning/issues/2810