A flaky clock-app autopilot test test_add_recurring_type_alarm_must_add_to_alarm_list(weekday)

Bug #1307458 reported by Timo Jyrinki
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Ubuntu Clock App
Invalid
Undecided
Unassigned

Bug Description

The test_add_recurring_type_alarm_must_add_to_alarm_list(weekday) test is flaky as on the image #294 tests a re-run was needed before the test passed. On the flaky run it ended with "ubuntuuitoolkit.emulators.ToolkitEmulatorException: The tab with index 1 was not selected."

I'm attaching a log snippet from the failing run. It may be however hard to reproduce since I've not been able to reproduce it locally.

Revision history for this message
Timo Jyrinki (timo-jyrinki) wrote :
Revision history for this message
Nicholas Skaggs (nskaggs) wrote :

Have you seen this before or was it a one-off? Adding Leo to see if this is simply a tab switching thing with the emulator.

Revision history for this message
Timo Jyrinki (timo-jyrinki) wrote :

So far this seems one off.

Revision history for this message
Leo Arias (elopio) wrote :

This exception was one we added to avoid an infinite loop while switching tabs. It means that the switch is not working, but without a video of what's going on it's really hard to tell the reason.

From the logs:
06:34:30.655 DEBUG emulators:155 - Switch to tab with index 1.
06:34:31.004 DEBUG emulators:164 - Current tab index: 0.
06:34:31.007 DEBUG emulators:140 - Switch to next tab.
06:34:32.331 DEBUG emulators:164 - Current tab index: 0.
06:34:32.333 DEBUG emulators:140 - Switch to next tab.
06:34:33.896 DEBUG emulators:164 - Current tab index: 0.
06:34:33.898 DEBUG emulators:140 - Switch to next tab.
06:34:35.249 DEBUG emulators:164 - Current tab index: 0.

It could be that the header is unresponsive, or that autopilot is not clicking on the right place.

Changed in ubuntu-clock-app:
milestone: none → alarm-blockers
Revision history for this message
Nicholas Skaggs (nskaggs) wrote :

This is still an odd error to see, but the simplest explanation is a UI freeze, not something within the test or sdk helper.

As to why the UI would sometimes lock, since this is adding alarms, I would have to ask Nekhelesh if having a worker thread for adding an alarm would affect the UI or not. I will say I have seen this as a one-off before in other apps.

Changed in ubuntu-clock-app:
status: New → Incomplete
Revision history for this message
Nekhelesh Ramananthan (nik90) wrote :

Well the saving of the alarms is already done asynchronously by the SDK. So I don't think there is much that I can do here. Let me talk to zsombor and see if the situation can be improved.

Changed in ubuntu-clock-app:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.