| commit | 9a017c4a428b9d88ed914d9b6fc382fa0d3a3f2f | [log] [tgz] |
|---|---|---|
| author | David Riley <davidriley@chromium.org> | Wed Oct 23 18:33:20 2019 -0700 |
| committer | chrome-bot <chrome-bot@chromium.org> | Fri Oct 25 15:37:16 2019 -0700 |
| tree | 5d3a625c506ce4afd59d6de48d643782cbde8b35 | |
| parent | 3177b41cb7647074f77999764958ff20883d724d [diff] |
mesa/buster: Add glbench package. glbench requires a newer version of waffle that is configured to come from the testing repo. BUG=None TEST=Docker builds packages with https://chromium-review.googlesource.com/c/chromiumos/platform/glbench/+/1877689 Change-Id: I58ae93c535d6029435996429263f593a40920ba0 Reviewed-on: https://chromium-review.googlesource.com/1877847 Tested-by: kokoro <noreply+kokoro@google.com> Commit-Ready: David Riley <davidriley@chromium.org> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Stephen Barber <smbarber@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. The CrOS milestone to target and release name (stretch, buster, etc.) are required.
bazel build //... --action_env="MILESTONE=74" --action_env="RELEASE=buster" --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.