Image: touch_ro build 56 (and others)
We sometimes see the camera-app tests fail on test_capture.TestCapture.test_shoot_button_disable
Here's a traceback from a recent failure:
21:25:04.845 INFO globals:49 - ************************************************************
21:25:04.846 INFO globals:50 - Starting test camera_app.tests.test_capture.TestCapture.test_shoot_button_disable (with touch)
21:25:04.847 WARNING testcase:118 - No tracing available - install the python-autopilot-trace package!
21:25:04.916 WARNING testcase:155 - Process manager backend unavailable, application snapshot support disabled.
21:25:04.934 INFO __init__:157 - Launching process: ['/usr/bin/camera-app', '-testability', '--fullscreen', '--desktop_file_hint=/usr/share/applications/camera-app.desktop']
21:25:05.311 INFO __init__:404 - dbus.DBusException while attempting to get PID for org.freedesktop.DBus: DBusException("Could not get PID of name 'org.freedesktop.DBus': no such name",)
21:25:06.590 DEBUG dbus:430 - Selecting objects of type QQuickView with attributes: {}
21:25:06.643 DEBUG dbus:430 - Selecting objects of type ShootButton with attributes: {}
21:25:06.679 INFO testcase:553 - waiting for process to exit.
21:25:06.679 INFO testcase:555 - Killing process 2164
}}}
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/camera_app/tests/test_capture.py", line 145, in test_shoot_button_disable
self.assertEquals(exposure_button.enabled, True)
File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 322, in assertEqual
self.assertThat(observed, matcher, message)
File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 417, in assertThat
raise MismatchError(matchee, matcher, mismatch, verbose)
MismatchError: Boolean(False) != True
Ran 1 test in 2.433s
FAILED (failures=1)
More detailed logs can be found at: https://jenkins.qa.ubuntu.com/job/saucy-touch_ro-maguro-smoke-camera-app-autopilot/79/console
It's a test that has a high race condition (http://
Look at the final 3 lines there:
The point of the test seems to:
1- take a photo
2- see that the shutter is disabled (since camera is not ready)
3- reenable shutter (since camera is ready for new snaps)
Observations:
- The time between 2 and 3 can be anything.
- Nothing triggers the final assert, hence it's testing a transition.
- The 'False' assert could already have been done by the time it's 'looked' at.