1847773 - Be able to use raptor-browsertime locally with m-c virtualenv (e.g. not needing to use pyenv)

Status: NEW

(Release Engineering :: Applications: MozharnessCore, defect, P3)

Description

[Kash Shampur [:kshampur] ⌚EST]

Sometimes we have a frequent error where engineers are unable to run raptor-browsertime tests locally due to how the virtualenv is created + local python setup

A common work around was to use pyenv to manage the python versions locally
It happened enough times that we added a note about it into our documentation e.g. Bug 1822631

However we don't fully know the underlying reason why this is happening, why it only affects some users suddenly, etc. so it would be ideal if we didn't have to even do this.

That way it would be seamless for engineers to work with our raptor-browsertime tests without having to deal with configuring a separate tool

Comment 1

[Kash Shampur [:kshampur] ⌚EST]

Also noting that is not clear how to reproduce it sometimes, a big step towards fixing this would be to figure out the conditions to replicate it easily.

Comment 2

[Mike Hommey [:glandium]]

This is not a problem with raptor only, I've gotten the same error as bug 1847289 with talos just now.
Removing the codesigning code fixed it: https://searchfox.org/mozilla-central/rev/d9496bfef09039b2642da45585ca821c36917c6d/testing/mozharness/mozharness/base/python.py#593-616