I've been trying to get reliable logging out of the PulseAudio server on Try. Confusingly, the PA server is launched in different locations for Ubuntu (test-linux.sh) and Debian (desktop_unittest.py) test images. Note that the Debian code explicitly terminates any existing server but the Ubuntu code will prefer any existing server over starting a new one. It turns out the PA launch in test-linux.sh has been broken since bug 1641395, since --dump-conf and --cleanup-shm are both single-shot arguments that terminate the server. That means the Ubuntu tests have been relying on a different PA server since 2020-06-02, probably the instance launched by the OS after the `pulseaudio` package is installed. Undoing that change from bug 1641395 reveals that the PA server launched from test-linux.sh fails to start sometimes due to an existing PA server being present. In other runs, the PA server launched from test-linux.sh is the one used by the tests - I suspect this reduces the incidence of this test failure.
Bug 1693151 Comment 10 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
I've been trying to get reliable logging out of the PulseAudio server on Try. Confusingly, the PA server is launched in different locations for Ubuntu (test-linux.sh) and Debian (desktop_unittest.py) test images. Note that the Debian code explicitly terminates any existing server but the Ubuntu code will prefer any existing server over starting a new one. It turns out the PA launch in test-linux.sh has been broken since bug 1641395, since --dump-conf and --cleanup-shm are both single-shot arguments that terminate the server. That means the Ubuntu tests have been relying on a different PA server since 2020-06-02, probably the instance launched by the OS after the `pulseaudio` package is installed. Undoing the change from bug 1641395 reveals that the PA server launched from test-linux.sh fails to start sometimes due to an existing PA server being present. In other runs, the PA server launched from test-linux.sh is the one used by the tests - I suspect this reduces the incidence of this test failure.
I've been trying to get reliable logging out of the PulseAudio server on Try. Confusingly, the PA server is launched in different locations for Ubuntu (test-linux.sh) and Debian (desktop_unittest.py) test images. Note that the Debian code explicitly terminates any existing server but the Ubuntu code will prefer any existing server over starting a new one. It turns out the PA launch in test-linux.sh has been broken since bug 1641395, since --dump-conf and --cleanup-shm are both single-shot arguments that terminate the server. That means the Ubuntu tests have been relying on a different PA server since 2020-06-02 - are we picking up a PA launched from elsewhere or left running after a prior test run? Undoing the change from bug 1641395 reveals that the PA server launched from test-linux.sh fails to start sometimes due to an existing PA server being present. In other runs, the PA server launched from test-linux.sh is the one used by the tests - I suspect this reduces the incidence of this test failure.
I've been trying to get reliable logging out of the PulseAudio server on Try. Confusingly, the PA server is launched in different locations for Ubuntu (test-linux.sh) and Debian (desktop_unittest.py) test images. Note that the Debian code explicitly terminates any existing server but the Ubuntu code will prefer any existing server over starting a new one. It turns out the PA launch in test-linux.sh has been broken since bug 1641395, since --dump-conf and --cleanup-shm are both single-shot arguments that terminate the server. That means the Ubuntu tests have been relying on a different PA server since 2020-06-02 - are we picking up a PA launched from elsewhere or left running after a prior test run? Perhaps this is a bad interaction with PA's auto-spawn functionality - it looks like that's explicitly disabled on Debian (and was on Ubuntu, but this was [removed](https://hg.mozilla.org/mozilla-central/rev/0db93079c806#l2.12) in bug 1641395 for some reason). Undoing the change from bug 1641395 reveals that the PA server launched from test-linux.sh fails to start sometimes due to an existing PA server being present. In other runs, the PA server launched from test-linux.sh is the one used by the tests - I suspect this reduces the incidence of this test failure.