The key highlight from the release notes:
Build without the Bytes for builds using remote caching and/or remote
execution is now enabled by default (i.e. --remote_download_outputs
defaults to toplevel). This means that Bazel will no longer try to
download any intermediate outputs from the remote server, but only the
outputs of requested top-level targets instead. This significantly
improves build performance. Bazel now also handles the case of an
artifact falling out of the remote cache gracefully, by rewinding the
build.
Signed-off-by: Andrei Vagin <avagin@gmail.com>
Instead of lying to clang about the targeted system, we can install the
necessary package only on x86_64 machines. Our tooling supports multiarch
packages (see tools/images.mk).
PiperOrigin-RevId: 591385576
This patch adds the EROFS rootfs support. No gofer process will be
created for the container, when there is no need to pass through host
files into a container via the gofer process. Annotations for rootfs
are also introduced to provide extra information, including the mount
source, mount type and overlay config. Additionally, busybox-static
is added to the default image and will be used to build the EROFS
rootfs images during the test.
Updates #8956
Signed-off-by: Tiwei Bie <tiwei.btw@antgroup.com>
This patch adds an EROFS test which checks that the checksums we get
from the target directory in container are identical with the ones
got from the source directory that we used to create the EROFS images.
erofs-utils is also added to the default image and will be used to
build the EROFS images during the test.
Signed-off-by: Tiwei Bie <tiwei.btw@antgroup.com>
A recent change stopped using the correct file (the export data, not the
archive) and checklocks started failing. Unfortunately, this was suppressed,
since the filter command was not failing with findings.
This change fixes that problem and adds a test to ensure that this cannot
happen again. If nogo starts failing to identify problems, the sanity_test in
nogo/sanity will also start to fail.
This change also requires updating the WORKSPACE to the latest rules_go and
Go version, in order to pick up the fixed go_tools. The latest rules_go in
turn required an updated bazel, which in turn required a minor change in the
coverdata implementation.
Fixing the fact propagation brought forward a number of problems with caching
for bazel workers. Its unclear whether this was a core worker issue or whether
some caching was broken, but the situation was basically undebugable. Instead,
the way facts are stored and loaded is optimized to be able to remove the use
of workers altogether and ideally make nogo debuggable.
PiperOrigin-RevId: 426327186
...and a bunch of other things as I worked through the rot. Notably:
- Upgrade to bazel 4.0.0
- Upgrade to Go 1.15.7
Remove go_branch stderr suppression; this made it quite difficult to see
what was failing while developing this patch.
PiperOrigin-RevId: 355257833
A few images were broken with respect to aarch64. We should now
be able to run push-all-images with ARCH=aarch64 as part of the
regular continuous integration builds, and add aarch64 smoke tests
(via user emulation for now) to the regular test suite (future).
PiperOrigin-RevId: 346685462
Recursive make is difficult to follow and debug. Drop this by using
internal functions, which, while difficult, are easier than trying to
following recursive invokations.
Further simplify the Makefile by collapsing the image bits and removing
the tools/vm directory, which is effectively unused.
Fixes#4952
PiperOrigin-RevId: 346569133
Andrei VaginandgVisor bot
Andrei VaginandAndrei Vagin
Kevin KrakauerandgVisor bot
Tiwei Bie
Adin ScannellandAndrei Vagin
Etienne PerotandgVisor bot
Zeling FengandgVisor bot
Fengjin Chenandchenfengjin
Tamir DubersteinandgVisor bot
