Closed Bug 1548574 Opened 2 years ago Closed 2 years ago

[mozproxy] mitmproxy failing to start when using both 2.x and 4.x in same test job

Categories

(Testing :: Raptor, defect, P1)

Version 3
defect

Tracking

(firefox68 fixed)

RESOLVED FIXED
mozilla68
Tracking Status
firefox68 --- fixed

People

(Reporter: rwood, Assigned: Bebe)

References

Details

Attachments

(1 file)

Looks like there is an issue where mozproxy fails to startup when using two different versions of mitmproxy (i.e. 2.x, 4.x) in the same tp6 suite.

:jmaher noticed that the Raptor tp6-8 Firefox jobs are actually failing (although they appear green):

https://treeherder.mozilla.org/#/jobs?repo=mozilla-central&searchStr=raptor%2Ctp6-8&selectedJob=244047942

Note that a bug is already on file for the fact the jobs themselves appear green but should be red, and will be fixed separately (Bug 1548477).

You'll see in the tp6-8 config that both versions of mitmproxy are used in the same suite:

https://searchfox.org/mozilla-central/source/testing/raptor/raptor/tests/raptor-tp6-8.ini

:bebe, :tarek: would you please have a look? Thanks!

Flags: needinfo?(tarek)
Flags: needinfo?(fstrugariu)

One solution would be to rename the binary so they include the version number in the executable name. What do you think Bebe?

Flags: needinfo?(tarek)

:tarek we could just create a version based folder where to download the bin file. That would avoid re-uploading

Flags: needinfo?(fstrugariu)
Pushed by fstrugariu@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/26561f2b9384
[mozproxy] mitmproxy failing to start when using both 2.x and 4.x in same test job r=tarek
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla68
Assignee: nobody → fstrugariu
You need to log in before you can comment on or make changes to this bug.