Increase BatteryStatusTracker test tolerance for missing data

Because we were waiting 0.1 seconds to confirm there's no status
change, we were getting into a race, because the 0.1s timeout
finishes, the status changes because of missing data.

Increasing the tolerance for missing data fixes that.

This commit also increases the timeout for failures due to stale data,
to be clearly higher than `max_data_age`.

Signed-off-by: Sahas Subramanian <[email protected]>

Author: shsms

tests/actor/test_battery_status.py

@@ -753,7 +753,7 @@ async def setup_tracker(
             mock_microgrid,
             BatteryStatusTracker(
                 BATTERY_ID,
-                max_data_age=timedelta(seconds=0.1),
+                max_data_age=timedelta(seconds=0.2),
                 max_blocking_duration=timedelta(seconds=1),
                 status_sender=status_channel.new_sender(),
                 set_power_result_receiver=set_power_result_channel.new_receiver(),
@@ -1027,7 +1027,7 @@ async def test_stale_data(
 
         await self._send_healthy_inverter(mock_microgrid)
         await self._send_healthy_battery(mock_microgrid, timestamp)
-        assert await recv_timeout(status_receiver) == ComponentStatus(
+        assert await recv_timeout(status_receiver, 0.3) == ComponentStatus(
             BATTERY_ID, ComponentStatusEnum.NOT_WORKING
         )
 
@@ -1043,7 +1043,7 @@ async def test_stale_data(
 
         await self._send_healthy_battery(mock_microgrid)
         await self._send_healthy_inverter(mock_microgrid, timestamp)
-        assert await recv_timeout(status_receiver) == ComponentStatus(
+        assert await recv_timeout(status_receiver, 0.3) == ComponentStatus(
             BATTERY_ID, ComponentStatusEnum.NOT_WORKING
         )