Volume preferences are not persisted on login through autotest |
||||
Issue descriptionChrome Version: 10323.58.0 OS: Chrome What steps will reproduce the problem? (1) Get a device you can SSH into and mute it (2) On your workstation, enter chroot with cros_sdk (3) run test_that login: test_that --autotest_dir ../third_party/autotest/files/ -b <board> <IP> login What is the expected result? Audio is still muted What happens instead? Audio becomes unmuted
,
Jul 24
I don't know how volume preferences work. Is this a bug because test_that is actively resetting the volume preferences, or is there an idiosyncrasy in how volume preferences are persisted? Is this breaking some test?
,
Jul 24
I mostly filed this bug because I was running a suite of tests against 3p ARC apps locally, and many of those apps play audio on startup. Despite me manually muting the device and confirming that a manual login to my own test account keeps the device muted, I noticed that on each subsequent autotest-driven login, the audio would become unmuted. It's annoying for the device to play audio in the office, especially if I may not be at my desk when I am running a test.
,
Jul 24
Removing myself as owner of this bug
,
Jul 25
That sounds like WAI, since tests run in a clean environment and letting persistent settings affect tests is bad. A workaround for the audio issue is plugging something into the headphone jack |
||||
►
Sign in to add a comment |
||||
Comment 1 by maajid@chromium.org
, May 25 2018