Hey Henrik, thanks for chiming in. I appreciate your attention to this bug, it is a blocker for getting CI working with Fenix performance testing. I'm not in charge of triage but I'd set this as a P2 at least... even a partial solution for on-host USB and no TCP connections would be appreciated. In the meantime, I could work around this by using one linux VMs on the host per device, and only assigning that device's USB connection to the VM. This is a pain, and adds a bunch of complexity to the testing environment that is not required for other browsers (namely chrome).
Bug 1617810 Comment 2 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Hey Henrik, thanks for chiming in. I appreciate your attention to this bug, it is a blocker for getting CI working with Fenix performance testing. I'm not in charge of triage but I'd set this as a P2 at least... even a partial solution for on-host USB and no TCP connections would be appreciated. In the meantime, I could work around this by using one linux VM on the host per device, and only assigning that device's USB connection to the VM. This is a pain, and adds a bunch of complexity to the testing environment that is not required for other browsers (namely chrome).