| 2013-10-04 02:58:36 |
Leo Arias |
description |
After some more weird error by jenkins, we noticed that the failed tests tend to have in their log that they failed to open the toolbar.
I ran the toolbar test around 300 times on saucy with no error. Then I ran them on my mako phone and it failed like 1 out of 30 times. The failure is really weird. I set a breakpoint when the toolbar failed to open and I got something like this:
02:54:15.621 DEBUG _uinput:365 - Dragging from 384,1279 to 384,1218
(didn't open)
> /home/phablet/ubuntu-ui-toolkit/tests/autopilot/ubuntuuitoolkit/emulators.py(87)open_toolbar()
-> return toolbar
(Pdb) self.pointing_device.drag(384, 1279, 384, 1218)
02:54:45.867 DEBUG _uinput:365 - Dragging from 384,1279 to 384,1218
(didn't open)
(Pdb) self.pointing_device.drag(384, 1279, 384, 1218)
02:54:48.701 DEBUG _uinput:365 - Dragging from 384,1279 to 384,1218
(didn't open)
(Pdb) self.pointing_device.drag(384, 1279, 384, 1218)
02:54:50.672 DEBUG _uinput:365 - Dragging from 384,1279 to 384,1218
(didn't open)
(Pdb) self.pointing_device.drag(384, 1279, 384, 1218)
02:54:52.139 DEBUG _uinput:365 - Dragging from 384,1279 to 384,1218
(opened)
So, there's something non-deterministic happening. I repeated the same action a number of times, until it finally worked. And the required number of times was never the same.
The problem might be on the toolkit, on unity or on autopilot.
The test is deterministic, what is flaky is the environment. |
After some more weirds error by jenkins, we noticed that the failed tests tend to have in their log that they failed to open the toolbar.
I ran the toolbar test around 300 times on saucy with no error. Then I ran them on my mako phone and it failed like 1 out of 30 times. The failure is really weird. I set a breakpoint when the toolbar failed to open and I got something like this:
02:54:15.621 DEBUG _uinput:365 - Dragging from 384,1279 to 384,1218
(didn't open)
> /home/phablet/ubuntu-ui-toolkit/tests/autopilot/ubuntuuitoolkit/emulators.py(87)open_toolbar()
-> return toolbar
(Pdb) self.pointing_device.drag(384, 1279, 384, 1218)
02:54:45.867 DEBUG _uinput:365 - Dragging from 384,1279 to 384,1218
(didn't open)
(Pdb) self.pointing_device.drag(384, 1279, 384, 1218)
02:54:48.701 DEBUG _uinput:365 - Dragging from 384,1279 to 384,1218
(didn't open)
(Pdb) self.pointing_device.drag(384, 1279, 384, 1218)
02:54:50.672 DEBUG _uinput:365 - Dragging from 384,1279 to 384,1218
(didn't open)
(Pdb) self.pointing_device.drag(384, 1279, 384, 1218)
02:54:52.139 DEBUG _uinput:365 - Dragging from 384,1279 to 384,1218
(opened)
So, there's something non-deterministic happening. I repeated the same action a number of times, until it finally worked. And the required number of times was never the same.
The problem might be on the toolkit, on unity or on autopilot.
The test is deterministic, what is flaky is the environment. |
|
