Force GNOME to notify updates, re-enable test on Workstation
ClosedPublic

Authored by adamwill on Oct 26 2016, 10:02 PM.

Details

Summary

GNOME's update notification criteria are pretty braindead: it
fires the update check timer once on login then once every hour
thereafter, but only actually checks for and notifies of updates
once a day if it's after 6am(?!?!?!). So we have to do a bunch
of fiddling around to ensure we reliably get a notification.
Move the clock to 6am if it's earlier than that, and reset the
'last update check' timer to 48 hours ago, then log in to GNOME
after that.

Note: I thought this still wasn't fully reliable, but I've looked
into all the recent failures of either test on staging and
there's only one which was really 'no update notification came
up', and the logs clearly indicate PK did run an update check,
so I don't think that was a test bug (I think something went
wrong with the update check). The other failures are all 'GNOME
did something wacky', plus one case where the needle didn't quite
match because I think the match area is slightly too tall; I'll
fix that in a second.

Test Plan

Run the tests on both KDE and GNOME and check they
work properly now (assuming nothing unrelated breaks, like KDE
crashing...)

Diff Detail

Repository
rOPENQATESTS os-autoinst-distri-fedora
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.
adamwill retitled this revision from to Force GNOME to notify updates, re-enable test on Workstation.Oct 26 2016, 10:02 PM
adamwill updated this object.
adamwill edited the test plan for this revision. (Show Details)
adamwill added reviewers: jskladan, garretraziel.
adamwill updated this revision to Diff 2650.Oct 26 2016, 10:04 PM

Make the GNOME 'update notification only' needle a bit shorter

See https://openqa.stg.fedoraproject.org/tests/51882#step/desktop_notifications/35

garretraziel accepted this revision.Oct 27 2016, 2:31 PM

What? 6 AM? Why? What is the purpose of that? Why have they done that? Maybe we'll never know...

This revision is now accepted and ready to land.Oct 27 2016, 2:31 PM

That's *exactly* what I thought.

This revision was automatically updated to reflect the committed changes.