tree f8cc4a83a0065d0a7d7470148c1206461ac1658e
parent 17f25a1772f7ba7535d57cd4dfa43ac1fc295843
author Boris Zbarsky <bzbarsky@apple.com> 1727115636 -0400
committer GitHub <noreply@github.com> 1727115636 +0000
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsFcBAABCAAQBQJm8bF0CRC1aQ7uu5UhlAAAXzUQADHknEzpDeSe81vQNYqsLp0G
 P21ipS+e3MVC5c+2DzJPwBsWY856+B9ncaeZt9hZbFlB285pioGIny4ViY70teqi
 9L8Lp/Y25Nwi3uyifmpCOcPUNpTKbYySo+h8qrn53HuMco7t0V6J8ALggaP/5vGB
 ppTKxwugpu/W7AOPcbOC7rGqXvWLgeBvhjABPj97sJe4qswwv3c6p7OdjpdIRQ2a
 vr63YdC1xkKb/AvHjk9HFKcZlU2NXxmL0AVWnHsZ+NAIQ5pRs9FEyGqtSofESSO7
 FpFcKKcxiTAuW2s9Ctw1cQHPUipSUXBQ4rZlqe7AvrdJm86hT19VscJyrXRDUO4d
 cw6Oc5l3EEGZIhKWw+nq0d93TMl0DsughtM7kCASNlBHyeAB1ZclPWMX+rmx1e91
 GeQ0N/5fGwyGlrcbVDUegznF3h6oI4+1peSStXSBee65ryAll+AnjbJLbeMyM+Pc
 GuRJODxVjjIkah5OxF934RSYcNtLzdAU0zjhZXvsR51P227UnnME/xhz84fN3vz/
 lt7JbtEEiMrj4SIWnLjt9SKHa6FLoN71hAK+Ddi93Ov36GdxTiyQuyZwFx2MPF3v
 +5pkDef6QBTl17jAL1rz7jtfHLP4N4uuCxOXSVAmD+Ga5TVnB+Nh4XqeFE5ntWiK
 2pFn7qDZH6hY0ydm4WRH
 =TOTJ
 -----END PGP SIGNATURE-----
 

Stop using MinInterval = 2 in tests that expect reports within 3 seconds. (#35707)

We had a bunch of subscription Darwin tests that set a 2-second MinInterval but
expected reports within 3 seconds.  This seems to have worked because for some
reason the 2-second timers fired pretty early (at closer to 1.5 seconds) on the
existing runners, but on the new ARM runners it actually fires at 2 seconds, and
then we have a very high test timeout rate.

The fix is to just use a MinInterval of 0 for the relevant subscriptions.

test012_SubscribeKeepingPreviousSubscription turned out to be relying on not
getting reports from when it sends the Off command until it sends the followup
On command, but now we do in fact send those reports.  So we need to wait for
them to clear through before we send the On command.