Closed Bug 1764901 Opened 4 years ago Closed 1 year ago

Install blackhole-2ch and blackhole-16ch on macOS test machines

Categories

(Infrastructure & Operations :: RelOps: General, defect, P5)

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: padenot, Assigned: rcurran, NeedInfo)

References

(Blocks 1 open bug)

Details

(Whiteboard: [relops-mac])

Attachments

(2 files)

106.06 KB, application/octet-stream
Details
106.24 KB, application/octet-stream
Details

It's on brew under those names if it helps, and it's free software (https://github.com/ExistentialAudio/BlackHole, GPL 3.0).

If we need more, we can compile it easily https://github.com/ExistentialAudio/BlackHole/wiki/Running-Multiple-BlackHole-Drivers. 2 more + the builtin should suffice though.

Assignee: nobody → relops
Component: WebRTC: Audio/Video → RelOps: General
Product: Core → Infrastructure & Operations

Dave, I'm told you might be the right person to look into this? If not, do you know who owns this? We need this for proper testing of bug 1238038 on macOS. We can test on Linux right now because PulseAudio has a facility to do this built-in, but on macOS it requires a 3rd party software.

Flags: needinfo?(dhouse)
Assignee: relops → dhouse

(In reply to Paul Adenot (:padenot) from comment #0)

It's on brew under those names if it helps, and it's free software (https://github.com/ExistentialAudio/BlackHole, GPL 3.0).

If we need more, we can compile it easily https://github.com/ExistentialAudio/BlackHole/wiki/Running-Multiple-BlackHole-Drivers. 2 more + the builtin should suffice though.

I downloaded the 2ch, 16ch, and 64ch pkg's. We don't use homebrew currently (removed for security concerns in '20). So the pkg files are perfect (we re-package dmgs or archives as pkg installs for the workers).

I'll set up a test instance with the 2ch and 16ch drivers installed for you to test. If they don't have unique uid's, I'll rebuild the 16ch one with "16ch" in the uid.

Whiteboard: [relops-mac]

(In reply to :dhouse from comment #2)

I'll set up a test instance with the 2ch and 16ch drivers installed for you to test. If they don't have unique uid's, I'll rebuild the 16ch one with "16ch" in the uid.

They can both be installed at the same time, not going to be a problem. Thanks!

Hi :padenot, here is a test pool "releng-hardware/gecko-t-osx-1015-r8-bug1764901". Can you try using the blackhole and see if this works for your tests? I set up the 2ch and 16ch blackhole in puppet and confirmed they are available, and so if this looks good I can roll it out to the production pool.

https://firefox-ci-tc.services.mozilla.com/provisioners/releng-hardware/worker-types/gecko-t-osx-1015-r8-bug1764901

Flags: needinfo?(dhouse) → needinfo?(padenot)

Thanks a lot!

Chun-Min, can you try your tests there? A command like:

mach try fuzzy --worker-suffix t-osx-1015-r8=-bug1764901

should allow scheduling something on the right worker, but I'm not sure we need to modify something in mochitest.ini or others, I don't remember if we had disabled on all OSes but Linux Desktop.

Flags: needinfo?(padenot) → needinfo?(cchang)

Do you mean the test D143102 added in bug 1238038? That test runs on every platform except Android, as long as the system has at least two audio input devices. I've pushed some mochitest jobs via ./mach try fuzzy --worker-suffix t-osx-1015-r8=-bug1238038. Is this what you expect?

Flags: needinfo?(cchang) → needinfo?(padenot)

Yeah, we'll see what's going to happen on those boxes, thanks.

Flags: needinfo?(padenot)

Dave, it seems like something went wrong with https://treeherder.mozilla.org/jobs?repo=try&revision=93f77969a2484ec6c11a53b0bae2b46a68110803, do you know how we would go about verifying this work, do we need anything from you, or should we try to simply re-push? Thanks!

Flags: needinfo?(dhouse)

:padenot i didn't get back to you on this! I've recreated the test pool as it had gone away after my long delay. It looks like the push from comment 8 was pointed at a different worker suffix/pool (the comment 8 mach appears to point at a pool named after the test's bug instead of this bug; my bad for naming it with a bug number!)
So the try push needs to be pushed like in comment 7: mach try fuzzy --worker-suffix t-osx-1015-r8=-bug1764901

Flags: needinfo?(dhouse) → needinfo?(padenot)
Assignee: dhouse → mgoossens
Status: NEW → ASSIGNED

Is this still needed?

Yes please, sorry for not answering earlier, this likely got buried in our bugmail without the NEEDINFO.

Flags: needinfo?(padenot)

Ryan and I are slowly deploying this on machines

Assignee: mgoossens → rcurran
Severity: -- → S4
Priority: -- → P5

Chun-Min, maybe you could try when you have a minute?

Flags: needinfo?(cchang)
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: