Skip to content
test

fix: stop calling removeCuFromCC #7785

Sign in to view logs

fix: stop calling removeCuFromCC

fix: stop calling removeCuFromCC #7785

Triggered via pull request February 9, 2026 10:07
@fluencebotfluencebot
synchronize #1133
fix/stop-calling-remove-cu-from-cc
Status Failure
Total duration 7m 11s
Artifacts –

run-tests.yml

on: pull_request
fluence-cli  /  Run tests
6m 2s
fluence-cli / Run tests
Fit to window
Zoom out
Zoom in

Annotations

2 errors
fluence-cli / Run tests
Process completed with exit code 1.
test/tests/provider.test.ts > provider tests > should be able to register and update provider with a new name: packages/cli/package/test/helpers/commonWithSetupTests.ts#L99
Error: Command: /opt/actions-runner/_work/cli/cli/packages/cli/package/dist/fluence/bin/node --no-warnings --no-deprecation /opt/actions-runner/_work/cli/cli/packages/cli/package/dist/fluence/bin/run.js provider cc-finish --no-input --priv-key 0x59c6995e998f97a5a0044966f0945389dc9e86dae88c7a8412f4603b6b78690d --offers newOffer exited with code 1. Reason: 2026-02-09T10:14:13.294Z fcli:debug command execution started Using local blockchain environment 2026-02-09T10:14:13.389Z fcli:debug rpcUrl: http://localhost:8545 2026-02-09T10:14:13.390Z fcli:debug chainId: 31337 2026-02-09T10:14:13.390Z fcli:debug networkName: Fluence Local 2026-02-09T10:14:13.408Z fcli:debug Trying to check if blockchain client is connected 2026-02-09T10:14:13.408Z fcli:debug Going to run contracts.diamond.bytesPerRam() to check if blockchain client is connected 2026-02-09T10:14:13.442Z fcli:debug Blockchain client is connected 2026-02-09T10:14:13.443Z fcli:debug Succeeded to check if blockchain client is connected 2026-02-09T10:14:13.558Z fcli:debug ipfsGateway: https://ipfs-gateway.fluence.dev 2026-02-09T10:14:13.558Z fcli:debug wsUrl: wss://chain-rpc:8545 2026-02-09T10:14:13.783Z fcli:debug Got USDC number of decimals: 6 2026-02-09T10:14:13.791Z fcli:debug subgraphUrl: http://localhost:8000/subgraphs/name/fluence-deal-contracts › Warning: You can withdraw collateral only from commitments with "Inactive" › or "Failed" status. The following commitments have invalid status: › › Status: Completed (peer-0,peer-1,peer-2) › › Peer: peer-0 › PeerId: 12D3KooW9qjP2DNPLTrZAW7pDexR4PyNRfaDLQ6pqGXxNP42sJjr › CommitmentId: › 0xbb51fd2a08dbd76762389e399f8e6331d7cc76b8397b5c2c7339970030d8775a › › Peer: peer-1 › PeerId: 12D3KooWCJ7TGMS2LLrTubqW452bjcVM1V62rhSur2vurXyirr8o › CommitmentId: › 0xad4ca816604e954bfa1f1f5110773642c98b14e94d355e686cf7cd28b13f7876 › › Peer: peer-2 › PeerId: 12D3KooWKBGzoVkmXYJGZzBGF567XLD3atNAr121gXaNijdWxP6y › CommitmentId: › 0x423ef3fb9a21d7e15558f2fabf60a58fb353a821e1488a5b665248ed736b443d Error: No commitments with 'Inactive' or 'Failed' status found ❯ Module.fluence test/helpers/commonWithSetupTests.ts:99:13 ❯ test/tests/provider.test.ts:157:7 ❯ test/helpers/utils.ts:35:5