From 674d8f93c24f407d116c20c757499109d7792f94 Mon Sep 17 00:00:00 2001 From: "Masih H. Derkani" Date: Tue, 30 Jun 2026 18:35:41 +0100 Subject: [PATCH] Retry npm install for disable wasm integration test The Disable WASM integration shard was flaky because the test script ran a single bare `npm ci` before starting Hardhat. In the failed CI job, npm aborted with a transient `ECONNRESET` while fetching packages, so the shard failed before `DisableWasmTest.js` actually ran. Retry `npm ci` with a short backoff and remove any partial `node_modules` contents between attempts. Persistent install failures still fail the job, but temporary registry/network resets no longer make the test shard flaky. --- .../evm_module/scripts/disable_wasm.sh | 18 ++++++++++++++++-- 1 file changed, 16 insertions(+), 2 deletions(-) diff --git a/integration_test/evm_module/scripts/disable_wasm.sh b/integration_test/evm_module/scripts/disable_wasm.sh index 5533805ee0..f0bb5c5bf0 100755 --- a/integration_test/evm_module/scripts/disable_wasm.sh +++ b/integration_test/evm_module/scripts/disable_wasm.sh @@ -3,5 +3,19 @@ set -e cd contracts -npm ci -npx hardhat test --network seilocal test/DisableWasmTest.js \ No newline at end of file + +for attempt in 1 2 3; do + if npm ci; then + break + fi + + if [ "$attempt" -eq 3 ]; then + exit 1 + fi + + echo "npm ci failed; retrying in $((attempt * 5)) seconds..." + rm -rf node_modules + sleep $((attempt * 5)) +done + +npx hardhat test --network seilocal test/DisableWasmTest.js