Since the Appveyor run is timing out, I went hunting for some low hanging fruit to speed up the tests. From the slower tests, this seemed like an obvious target as each run of the test is taking ~10 seconds. This seems to work fine.

Since gtk3cairo is disabled in this test, the comment doesn't seem relevant any more.

PR checklist

"closes #0000" is in the body of the PR description tolink the related issue
new and changed code istested
Plotting related features are demonstrated in anexample
New Features andAPI Changes are noted with adirective and release note
Documentation complies withgeneral anddocstring guidelines

dstansby changed the title~~Reduce pause time interactive timer test~~Reduce pause time in interactive timer test

Jul 7, 2025

Reduce pause time in interactive tests

3208831

dstansby force-pushed thespeedup-interactive-timer-tests branch fromc72b054 to3208831Compare

July 8, 2025 10:59

dstansby marked this pull request as ready for review

July 8, 2025 11:00

QuLogic requested a review fromgreglucas

July 8, 2025 19:59

greglucas approved these changes

Jul 9, 2025

View reviewed changes

Copy link

Contributor

greglucas left a comment

Choose a reason for hiding this comment

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

This is fine as an incremental update since you note GTK isn't being tested here.

The interactive timers are currently not correct IMO and we need to update them to make sure the timers don't overrun their pause duration. This test is completely reworked in#29062 but that is also failing on the appveyor runs with the GTK backends, I assume because the underlying OS there is causing that timer to be even slower and not get as many triggers. Feel free to review/comment on that PR if you have suggestions there too.