924997 - No module named moztest.results when running mach commands related to marionette

Status: RESOLVED DUPLICATE of bug 925005

(Testing :: General, defect)

Description

[Andrew Halberstadt [:ahal]]

Looks like fallout from bug 879900

STR:

./mach marionette-test (or ./mach mochitest-b2g-desktop) after a fresh build.

Result:
ImportError: No module named moztest.results

  File "/home/ahal/hg/mozilla-central/testing/marionette/mach_commands.py", line 33, in run_marionette
    from marionette.runtests import (
  File "/home/ahal/hg/mozilla-central/testing/marionette/client/marionette/__init__.py", line 10, in <module>
    from runtests import MarionetteTestResult
  File "/home/ahal/hg/mozilla-central/testing/marionette/client/marionette/runtests.py", line 22, in <module>
    from moztest.results import TestResultCollection

Comment 1

[Andrew Halberstadt [:ahal]]

Oddly running ./mach python and then 'from moztest.results import TestResultCollection' works fine for me.

Comment 2

[Jonathan Griffin (:jgriffin)]

This implies that an out-of-date moztest is being used; trying to reproduce.

Comment 3

[Andrew Halberstadt [:ahal]]

Yeah, pip freeze is showing moztest==0.1 with the in-tree virtualenv activated. Though my testing/mozbase/moztest appears to be up to date and at 0.3.

I'm guessing clobbering would solve my problem, though I don't understand why comment 1 would work but not comment 0.

Comment 4

[Jonathan Griffin (:jgriffin)]

It works ok for me with a clobber build; I wonder if we should be populating the in-tree virtualenv with pip -e, so that the packages get updated automatically?

Comment 5

[Andrew Halberstadt [:ahal]]

Clobber build didn't fix anything, though the patch from bug 925005 works for me.

Comment 6

[Jonathan Griffin (:jgriffin)]

Cool, let's dupe this then.