Open carbolymer opened 5 months ago
Initially, byDeadlineM
usage was considered an issue here, which was partially removed in https://github.com/IntersectMBO/cardano-node/pull/5707 - but instead of test failures we started getting cardano-tesnet freezes.
A suspicion here is that the test network is not advancing - the new blocks are not produced.
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 120 days.
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 120 days.
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 120 days.
Internal/External Internal if an IOHK staff member.
Area
Other Any other topic (Delegation, Ranking, ...).
Summary Sometimes a cardano-testnet test suite hangs indefinitely. It's like nodes are taking longer time to produce blocks. It may be related to what @james-iohk described here https://github.com/IntersectMBO/cardano-node/pull/5679#issuecomment-1959419678
The issue is more visible in slower machines, like macos runner in GHA or darwin cross-compilation in Hydra.
Steps to reproduce Steps to reproduce the behavior:
byDeadlineM
.The issue appears to appear more frequently when running testnet test suites in parallel.
Sample log of a failure: babbagetransaction.txt (taken from: https://github.com/IntersectMBO/cardano-node/pull/5695/checks?check_run_id=22357754517)
Expected behavior cardano-testnet does not hang, or retries, reports the failure with message explaining what happened.