| commit | 526b9cd12005aaf3b82212905be864c239afc3d3 | [log] [tgz] |
|---|---|---|
| author | Nicholas Hollingum <hollingum@google.com> | Mon Nov 25 02:56:33 2019 |
| committer | Commit Bot <commit-bot@chromium.org> | Wed Nov 27 03:16:22 2019 |
| tree | 9eaa06b98aa26d34450a9284ba8aaee5bf7d70a8 | |
| parent | 8166682798fd811978c27cd85d48d71c72eb23de [diff] |
Make libdrm and mesa build sequentially in the same shard The partially-completed crrev.com/c/1925907 sharded the mesa builds incorrectly, meaning mesa would be built against a potentially out-of-date libdrm. The correct behaviour is to build libdrm in the same shard as mesa. This CL makes that fix, as well as several smaller fixes suggested in the other CL. The job configuration is changed in cl/282267687. BUG=chromium:1018519 TEST=(if anyone knows how to test this i'm all ears) Change-Id: Ic051e8920d11a3903cbdd40226af974a03f26945 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/containers/cros-container-guest-tools/+/1933610 Reviewed-by: kokoro <noreply+kokoro@google.com> Reviewed-by: Stephen Barber <smbarber@chromium.org> Reviewed-by: David Munro <davidmunro@google.com> Tested-by: Nic Hollingum <hollingum@google.com> Commit-Queue: Nic Hollingum <hollingum@google.com>
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.