Increased mining timeout in mock_mining and partial_tenure_fork integration tests

[rdeioris]

Description

This patch increases mining timeout for 2 integration tests for allowing the CI to not fail on them.

The tests are:

tests::nakamoto_integrations::mock_mining
tests::signer::v0::partial_tenure_fork

Applicable issues

• fixes Resolve integration test flakiness #5556

Additional info (benefits, drawbacks, caveats)

Checklist

• Test coverage for new or modified code paths
• Changelog is updated
• Required documentation changes (e.g., docs/rpc/openapi.yaml and rpc-endpoints.md for v2 endpoints, event-dispatcher.md for new events)
• New clarity functions have corresponding PR in clarity-benchmarking repo
• New integration test(s) added to bitcoin-tests.yml

[jbencin]

Can you provide some info in the description on how this was tested or why the longer timeout is necessary? Like how many times was this tested and the failure rates using the different timeout, or what specifically was taking longer than 1-2 minutes that made the previous timeouts inadequate?

[obycode]

LGTM. Glad it was that simple!

[rdeioris]

@jbencin in all of the runner errrors i was able to get related to the two tests (unofrtunately the runner logs in the base issue are no more available as they got recycled) the error was always "Timed out waiting for follower to catch up to the miner".

This is effectively the time the test thread waits for the synchronization of a follower (spawned in a new thread) til the chain tip.

On my local machine this time is extremely variable while running tests (between 40 and 60 seconds). If you think it is worthy i can log the time required by a github worflow node to have a better idea on the true timings

[blockstack-devops]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.