| 2013-05-14 21:35:09 |
Francis Ginther |
description |
We're seeing these failures in the daily-release testing when running python-autopilot-tests [1]:
Traceback (most recent call last):
File "/usr/bin/autopilot", line 41, in <module>
from platform import node
ImportError: cannot import name node
I instrumented /usr/bin/autopilot and when this happens, sys.path is:
sys.path: ['/usr/bin', '/usr/lib/python2.7/dist-packages/autopilot', '/usr/lib/python2.7', '/usr/lib/python2.7/plat-x86_64-linux-gnu', '/usr/lib/python2.7/lib-tk', '/usr/lib/python2.7/lib-old', '/usr/lib/python2.7/lib-dynload', '/usr/local/lib/python2.7/dist-packages', '/usr/lib/python2.7/dist-packages', '/usr/lib/python2.7/dist-packages/PILcompat', '/usr/lib/python2.7/dist-packages/gtk-2.0', '/usr/lib/pymodules/python2.7', '/usr/lib/python2.7/dist-packages/ubuntu-sso-client', '/usr/lib/python2.7/dist-packages/ubuntuone-client', '/usr/lib/python2.7/dist-packages/ubuntuone-control-panel', '/usr/lib/python2.7/dist-packages/ubuntuone-storage-protocol']
And an import of platform gives:
dir platform: ['_PlatformDetector', '__builtins__', '__doc__', '__file__', '__name__', '__package__', '_get_property_file', '_parse_build_properties_file', 'exists', 'image_codename', 'model']
This is because '/usr/lib/python2.7/dist-packages/autopilot' is second in the search path, before the python libs. I think this happens as a result of the autopilot tests creating a test script and running autopilot during the autopilot run.
[1] - https://jenkins.qa.ubuntu.com/job/ps-generic-autopilot-release-testing/365/label=autopilot-intel/artifact/results/artifacts/ap_test_debug_log.txt |
We're seeing these failures in the daily-release testing when running python-autopilot-tests [1]:
Traceback (most recent call last):
File "/usr/bin/autopilot", line 41, in <module>
from platform import node
ImportError: cannot import name node
I instrumented /usr/bin/autopilot and when this happens, sys.path is:
sys.path: ['/usr/bin', '/usr/lib/python2.7/dist-packages/autopilot', '/usr/lib/python2.7', '/usr/lib/python2.7/plat-x86_64-linux-gnu', '/usr/lib/python2.7/lib-tk', '/usr/lib/python2.7/lib-old', '/usr/lib/python2.7/lib-dynload', '/usr/local/lib/python2.7/dist-packages', '/usr/lib/python2.7/dist-packages', '/usr/lib/python2.7/dist-packages/PILcompat', '/usr/lib/python2.7/dist-packages/gtk-2.0', '/usr/lib/pymodules/python2.7', '/usr/lib/python2.7/dist-packages/ubuntu-sso-client', '/usr/lib/python2.7/dist-packages/ubuntuone-client', '/usr/lib/python2.7/dist-packages/ubuntuone-control-panel', '/usr/lib/python2.7/dist-packages/ubuntuone-storage-protocol']
And an import of platform gives:
dir platform: ['_PlatformDetector', '__builtins__', '__doc__', '__file__', '__name__', '__package__', '_get_property_file', '_parse_build_properties_file', 'exists', 'image_codename', 'model']
This is because '/usr/lib/python2.7/dist-packages/autopilot' is second in the search path, before the python libs. I think this happens as a result of the autopilot tests creating a test script and running autopilot during the autopilot run.
[1] - https://jenkins.qa.ubuntu.com/job/ps-generic-autopilot-release-testing/365/label=autopilot-intel/artifact/results/artifacts/ap_test_debug_log.txt
[Reproduce]
Run python-autopilot-tests from the raring package. |
|
