From 22e174069e5b95703924b16923fa40f4be46ab2d Mon Sep 17 00:00:00 2001 From: Adam Williamson Date: Sat, 14 Oct 2023 10:34:01 -0700 Subject: [PATCH] gnome-panel: set update notification timestamp early If we do it after forcing the clock to 18:30, doing it takes so long we wind up at 18:32, and that kinda sets the rest of the test out of whack (we have several needles that assume we start at 18:30 or 18:31 after the snapshot). So let's set the update timestamp *before* we force the clock. This will mean it's waay in the future after we force the clock, but that should still do the job of avoiding notifications showing up, I hope. Signed-off-by: Adam Williamson --- tests/applications/gnome-panel/aaa_setup.pm | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/tests/applications/gnome-panel/aaa_setup.pm b/tests/applications/gnome-panel/aaa_setup.pm index f5e4dc90..ad6bbaee 100644 --- a/tests/applications/gnome-panel/aaa_setup.pm +++ b/tests/applications/gnome-panel/aaa_setup.pm @@ -7,6 +7,11 @@ use utils; sub run { my $self = shift; + # Set the update notification timestamp + # note: this will mean it's waaay in the future compared to the + # fake time we set below and use for the rest of the test, but + # that should do the job fine + set_update_notification_timestamp(); # Go to the root console to set up the test data and necessary stuff. $self->root_console(tty => 3); @@ -23,8 +28,6 @@ sub run { script_run("chmod 666 /dev/ttyS0"); # Return to Desktop desktop_vt(); - # Set the update notification timestamp - set_update_notification_timestamp(); # Check that the upper panel shows correct date and time. assert_screen("panel_datetime"); }