commit | 0767a9fc6cb36b0349326714bc0c60a69e64ce07 | [log] [tgz] |
---|---|---|
author | Chih-Yang Hsia <paulhsia@chromium.org> | Thu Jun 04 11:35:14 2020 |
committer | Commit Bot <commit-bot@chromium.org> | Sat Jun 06 11:33:36 2020 |
tree | a69f1be3bc4768c1a7f16151ed8562abe3da7cdb | |
parent | c91e2b470403205b8d0534706182c2f404bd4c72 [diff] |
cros-pulse-config: Deploy configs and remove oneshot service The CL uprev cros-pulse-config package to v0.2.0 with the following changes: - Remove cros-pulse-config.service oneshot service The oneshot approach is flaky and can be replaced by commands in pulseaudio configuration files. - Deploy a customized default.pa configuration With minimal pulseaudio setup and it loads alsa output / input device. - [b/158172260] Deploy a customized daemon.conf with lower latency settings Reduce latency from default buffer size = 3 * 33 ms (~100 ms) to 4 * 20ms (80 ms). - Divert conflict configurations /etc/pulse/* to *.distrib We test multiple device loading scenarios in PulseAudioSanity in CL:2230743. Some test cases will fail v0.1.3 but v0.2.0 can pass them. BUG=b:155857693 BUG=b:158062611 BUG=chromium:1068945 BUG=b:158172260 TEST=dpkg --install cros-pulse-config_0.2.0_all.deb && \ dpkg --remove cros-pulse-config TEST=crostini.AudioSanity.* TEST=crostini.PulseAudioSanity.* TEST=Measure glitches by - Run playback in youtube in browser in Crostini - Multi-tasking on host Chrome Change-Id: I77e8670fbf0ec9bffcb2712ac415b6fbe3506b43 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/containers/cros-container-guest-tools/+/2230391 Reviewed-by: Stephen Barber <smbarber@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com> Tested-by: Chih-Yang Hsia <paulhsia@chromium.org> Commit-Queue: Chih-Yang Hsia <paulhsia@chromium.org>
These are the guest packages for setting up a container to integrate with Chrome OS. This includes build scripts that are run in Google's internal continuous integration service.
The guest packages can be built with Bazel.
bazel build //cros-debs:debs --host_force_python=py2
promote\_apt.sh MILESTONE
and promote\_container.sh MILESTONE
in scripts are used to promote containers from staging to live. NOTE: Whatever is the latest in staging is what gets promoted to live so make sure it's what was tested.