Open Bug 1855075 Opened 2 years ago Updated 4 months ago

Make testing/raptor importable from other libraries

Categories

(Testing :: Raptor, defect, P3)

Product:
Testing
Component:
Raptor
Type:
defect

Tracking

(firefox-esr115 unaffected, firefox118 unaffected, firefox119 unaffected, firefox120 wontfix)

Tracking Flags:
Tracking Status
firefox-esr115 --- unaffected
firefox118 --- unaffected
firefox119 --- unaffected
firefox120 --- wontfix

People

(Reporter: alexandrui, Unassigned)

References

(Regression)

Details

(Keywords: regression, Whiteboard: [fxp][operational][vision])

Make testing/raptor importable from other libraries such testing/mozbase/mozproxy.

Type: enhancement → defect
Keywords: regression
Regressed by: 1732180
Whiteboard: [fxp]

Set release status flags based on info from the regressing bug 1732180

status-firefox118: --- → unaffected
status-firefox119: --- → unaffected
status-firefox120: --- → affected
status-firefox-esr115: --- → unaffected

:alexandrui, I'm not sure this is a regression/defect. Can you elaborate on that?

Flags: needinfo?(aionescu)

After the patch that avoids mozprofile for non-FF applications, we should've been able to import testing/raptor to testing/mozbase/mozproxy. While we are not, we had to hardcode a constant. I have no problem changing it to task.

Flags: needinfo?(aionescu)
Flags: needinfo?(gmierz2)

This is currently an expected issue/behaviour, so I think changing it to a task would make more sense. Another issue here is that you'd create a circular dependency if mozproxy depends on raptor, and raptor depends on mozproxy. We would need to create a separate module that would allow us to share these things.

Flags: needinfo?(gmierz2)
Whiteboard: [fxp] → [fxp][operational][vision]
You need to log in before you can comment on or make changes to this bug.