901095 - Desktop UnitTests should not rely on PyPi as a repo

Status: RESOLVED FIXED

(Release Engineering :: General, defect)

Description

[Mihai Tabara [:mtabara]⌚️GMT]

Attachment: desktop unit tests relying on pypi

While testing a new feature in Desktop_unittest mozharness script I came to an issue. I needed to add a python package script as a dependency, which currently lays in our puppet repos. I've changed the config to ignore the base index and  take into consideration our repos. Execution broke before it reached my package. That leads me to the question: sould we rely on pypi for our packages or should we start, gradually, copy them into our own repos so that we can manage them better?

Comment 1

[Rail Aliiev [:rail]]

Aki, I know that we want to get rid of using "repos" at some point and this patch may break local tests. Do you have any ideas how we should proceed here?

Comment 2

[John O'Duinn [:joduinn] (please use "needinfo?" flag)]

Found in triage. Not exactly sure if this is correct component, given the new scope of new bugzilla components, so feel free to move it on again if I guessed wrong!

Comment 3

[Aki Sasaki (not active)]

That's bug 885780.
I think unittests are already non-standalone friendly, sadly.  We shouldn't have anything relying on pypi in production, so this should only be a staging/standalone patch.

Possibly our path to victory is a standalone config that overrides production config items, or vice versa.

Comment 4

[Aki Sasaki (not active)]

I think this should be fixed with recent VirtualenvMixin changes... is this still an issue?

Comment 5

[Mihai Tabara [:mtabara]⌚️GMT]

AFAIK, it should no longer be an issue.
However, I'm not very well updated with the changes so I'll double check on Rail on this.

Comment 6

[Rail Aliiev [:rail]]

(In reply to Aki Sasaki [:aki] from comment #4)
> I think this should be fixed with recent VirtualenvMixin changes... is this
> still an issue?

Whatever aki says. :)