Fix flaky TestArchiveInquirer_RunProgressReport

[wsodsong]

Description

The test used a 1s ticker with a 1s sleep, creating a race between the ticker and the finished signal. This change reduces the ticker to 500ms so the ticker is guarantee to fire before shutdown.

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Refactoring (changes that do NOT affect functionality)
• Adds or updates testing
• This change requires a documentation update

[Copilot]

Pull request overview

Adjusts the TestArchiveInquirer_RunProgressReport timing to reduce flakiness caused by a race between the ticker firing and the shutdown signal in the archive inquirer progress reporter.

Changes:

• Reduced the progress-report ticker interval used by the test to 500ms.
• Increased the test’s wait time before signaling shutdown to 1s to allow a tick/log to occur.

Comments suppressed due to low confidence (1)

executor/extension/statedb/archive_inquirer_test.go:318

• duration is now only used for the ticker interval (the sleep is hard-coded to 1s). Renaming this variable to something like tickerDuration would make the intent clearer and avoid confusion about what the value controls.

	duration := 500 * time.Millisecond
	inquirer := &archiveInquirer{
		log:            mockLog,
		finished:       utils.MakeEvent(),
		tickerDuration: duration,
	}

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
see 2 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[rpl-ffl]

Ty!