test: grant immediate_migration_chunks_a_fragmented_wallet the heavy timeout - #2752
Merged
Conversation
…timeout The test proves more Orchard spends than fit one split transaction and has always run near nextest's default 600-second ceiling. The suite speedups merged in #2741 reshuffled the schedule so it now overlaps the other long-chain heavies: the last green dev run passed it at 571.8 seconds, and every CI run since 2026-08-26 kills it at 600. Listing it in the existing long-chain heavies override raises its limit to 1200 seconds in both profiles, beside its sibling drain_chunks_a_fragmented_wallet. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
This PR adds
immediate_migration_chunks_a_fragmented_walletto the long-chain heavies override in.config/nextest.toml. The override raises the kill limit from 600 to 1200 seconds. Both the default and the ci profile get the entry.Why
The test proves more Orchard spends than fit one split transaction. It has always run near the 600-second default ceiling. The suite speedups in #2741 reshuffled the schedule, so the test now overlaps the other long-chain heavies. The last green dev run passed it at 571.8 seconds. Every dev CI run since 2026-08-26 kills it at 600 seconds. The sibling test
drain_chunks_a_fragmented_walletalready sits in this override.This timeout also fails CI on unrelated PRs, such as #2750.
🤖 Generated with Claude Code