[mozproxy] mitmproxy failing to start when using both 2.x and 4.x in same test job
Categories
(Testing :: Raptor, defect, P1)
Tracking
(firefox68 fixed)
| 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):
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
| Reporter | ||
Comment 1•7 years ago
|
||
:bebe, :tarek: would you please have a look? Thanks!
Comment 2•7 years ago
|
||
One solution would be to rename the binary so they include the version number in the executable name. What do you think Bebe?
| Assignee | ||
Comment 3•7 years ago
|
||
:tarek we could just create a version based folder where to download the bin file. That would avoid re-uploading
| Assignee | ||
Comment 4•7 years ago
|
||
| Assignee | ||
Comment 5•7 years ago
|
||
| Assignee | ||
Comment 6•7 years ago
|
||
Comment 8•7 years ago
|
||
| bugherder | ||
Updated•7 years ago
|
Description
•