At this moment we cannot run the clipboard job on VMs. There was a long investigation in bug 1270962 to see if we could make this job run on VMs. Given that, our only option is to run the job on real hardware in-house like talos jobs. I'm filing this bug as a placeholder and make it part of the migration (bug 1141248). From jmaher: > the cl (clipboard) job historically doesn't run on VM because the VM has a > clipboard service which we were not able to disable and that interferes > with the OS level one causing problems. If we can show that cl runs > 40 times in opt/debug e10s/non-e10s without problem (or very rare non > repeating intermittent) I would be happy to switch it to vm.

Found in triage. jmaher: do you know if this is still an issue?

no, we have fixed issues and this runs on VM just fine now.