800111 - Update B2G mozharness scripts to use mozbase packages from puppetagain

Status: RESOLVED WONTFIX

(Release Engineering :: General, defect)

Description

[Jonathan Griffin (:jgriffin)]

Currently, we're using mozbase packages from tests.zip.  However, we need to push additional changes to mozbase to support B2G testing, and we have to run these tests on both m-c and aurora.  Porting all the necessary changes to aurora is risky, since we could potentially impact desktop automation running there.

Instead, we should change the B2G mozharness scripts to use mozbase packages that are uploaded to puppetagain.  We can then update these packages as needed, and don't have to worry about merging mozbase changes from m-c to aurora.

Comment 1

[Joel Maher ( :jmaher ) (UTC -8)]

we don't run unittests in a virtual env, we run them standalone python scripts.

Comment 2

[Aki Sasaki (not active)]

This is fine as long as we don't want different versions of mozbase between m-c through m-r.

If versions of mozbase are going to follow the trains, that's easiest to handle in tree.

Comment 3

[Aki Sasaki (not active)]

(In reply to Joel Maher (:jmaher) from comment #1)
> we don't run unittests in a virtual env, we run them standalone python
> scripts.

I think the "standalone" python scripts depend on mozbase, so require a virtualenv.

Comment 4

[Jonathan Griffin (:jgriffin)]

I've decided to hold off on this for now. 

If we switch to using puppetagain packages as a way of avoiding porting changes to mozdevice to mozilla-aurora, we'll potentially break the ability of people to run B2G unittests locally using aurora, since such tests run locally use in-tree versions of mozbase packages.

In order to implement this fix, we'd need to have tests everywhere use pypi/puppetagain packages, instead of in-tree versions of mozbase.  Since that doesn't seem likely in the near term, I'm closing this.