Comment 3 for bug 1417966

Revision history for this message
Martin Pitt (pitti) wrote :

When I run them on an r/w image so that the test dependencies actually get installed with apt, this now fails with

adt-run [08:20:02]: test sanity: [-----------------------
Traceback (most recent call last):
  File "/tmp/adt-run.qsFTLT/build.sGK/real-tree/debian/tests/sanity", line 23, in <module>
    from ubuntu_sanity_tests import sanity
ImportError: No module named 'ubuntu_sanity_tests'

because it doesn't set PYTHONPATH=. anywhere, and the binary is in debian/tests/. That's another reason why they currently can't work runnning from the tree instead of from the package. I fixed that with http://paste.ubuntu.com/10068247/ and now the tests actually do run. So I recommend applying this patch to lp:ubuntu-sanity-tests. The tests fail with

adt-run [08:28:52]: test sanity: [-----------------------
The ubuntuuitoolkit.emulators module is deprecated. Import the autopilot helpers from the top-level ubuntuuitoolkit module.
Loading tests from: /usr/lib/python3/dist-packages

Loading tests from: /tmp/adt-run.SVTNuP/build.0XB/real-tree

Sorry, try again.
Sorry, try again.
Sorry, try again.
sudo: 3 incorrect password attempts
adt-run [08:31:09]: test sanity: -----------------------]
adt-run [08:31:10]: test sanity: - - - - - - - - - - results - - - - - - - - - -
sanity FAIL non-zero exit status 1

But I did see quite some windows flying around; not sure what the sudo thingy is, presumably the config.py device_password key doesn't default to 0000?

But that still leaves me with not being able to reproduce your original crash. Can you please tell me the precise steps and commands that you did to get the /dev/uinput issue?