Skip to content

Conversation

@alin-at-dfinity
Copy link
Contributor

IMHO, if a test has to wait for one hour for a response to be produced, then it's not a very useful test. And regardless of that, one hour should not be the default for every single system test.

This is intended as a fix for the significant flakiness experienced recently by //rs/tests/message_routing:state_sync_malicious_chunk_test. All the failures are timeouts. And the last relevant message before the test times out is Checking for subnet progress.... After which, the test proceeds to make a canister call that never completes and is never retried (because the test expires before the call, after 3600 seconds).

The other half of the fix (dfinity/agent-rs#693, which will have to wait for an ic-agent release) is to bail out if the status is still Unknown after 5 minutes, regardless of the configured max_polling_time.

IMHO, if a test has to wait for one hour for a response to be produced, then it's not a very useful test. And regardless of that, one hour should not be the default for every single system test.
@alin-at-dfinity alin-at-dfinity requested a review from a team as a code owner January 27, 2026 19:02
@github-actions github-actions bot added the fix label Jan 27, 2026
Copy link
Contributor

@mraszyk mraszyk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM since due to this PR, I no longer need a large timeout (but I didn't see a reason against so I kept it high so far)

@alin-at-dfinity alin-at-dfinity added this pull request to the merge queue Jan 28, 2026
@basvandijk basvandijk removed this pull request from the merge queue due to a manual request Jan 28, 2026
@basvandijk basvandijk added this pull request to the merge queue Jan 28, 2026
Merged via the queue into master with commit 2af77a5 Jan 28, 2026
140 of 149 checks passed
@basvandijk basvandijk deleted the alin/reduce-max_polling_time branch January 28, 2026 10:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants