-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release 3.6 - September 2020 #12040
Comments
Bazel 3.6.0rc2 is now available for those that want to try it out. |
If possible I think we should cherry pick #12046 once it lands. Without it in sandboxed builds on darwin you get log spew for every static archive action:
|
My work to remove TransitionMode introduced some issues with Android builds: the symptoms are that android builds that set Also, #12069 was filed about a regression in 3.5, and could be fixed if we cherrypick 144d514 as well. |
I'll create a new candidate with the cherrypicks on Monday (sorry for the delay, I'm on vacation this week). |
I just opened a bug #12117. Don't know if it is big enough to be considered a release blocker for 3.6.0, but on the other hand, it looks like a glaring omission and hopefully is easy to fix. |
Cherrypick list so far: 1ae143b, 23b0b8a, 144d514, b3ac8f6, 26cbf77 #12117 doesn't seem critical and I haven't seen any fix for it. |
May I request to cherry-pick abc2211? This is a long-standing bug that the only workaround was to uninstall |
Cherrypicks are usually for recent regressions (something that worked with the previous version of Bazel). Since we're already late with Bazel 3.6 (and Bazel 3.7 process is starting this week), I'd rather not add any delay. |
Totally makes sense. We can wait for 3.7. |
Released Bazel 3.6 |
Bazel 3.6.0 arm64 binaries uploaded to GitHub and https://releases.bazel.build/3.6.0/release/. |
Fedora and Centos builds kicked off
https://copr.fedorainfracloud.org/coprs/build/1696184
|
@philwo can you share the full build flags used to invoke your arm64 builds? I'm wondering if it's memory issues or such, that cause all the aarch64 builds to fail on fedora and epel. |
@vbatts Sure! This is the full script used to build the binaries. There aren't any special flags, except the git fetch origin master
git fetch --force origin refs/notes/*:refs/notes/*
git checkout ${BUILDKITE_BRANCH}
release_name=$(buildkite-agent meta-data get "release_name")
echo "release_name = \"$release_name\""
bazel build --sandbox_tmpfs_path=/tmp //src:bazel
mkdir output
cp bazel-bin/src/bazel output/bazel
output/bazel build \
-c opt \
--stamp \
--sandbox_tmpfs_path=/tmp \
--embed_label "${release_name}" \
--workspace_status_command=scripts/ci/build_status_command.sh \
src/bazel
mkdir artifacts
cp "bazel-bin/src/bazel" "artifacts/bazel-\${release_name}-linux-arm64"
cd artifacts
buildkite-agent artifact upload "*" It runs inside this Docker container ( In order to get the initial mkdir bazel-3.6.0
cd bazel-3.6.0
curl -O https://releases.bazel.build/3.6.0/release/bazel-3.6.0-dist.zip
unzip bazel-3.6.0-dist.zip
./compile.sh which results in:
Our arm64 machine is hosted by packet.net and described as an "Ampere® eMAG processor, which features 32 Arm cores operating at 3.3 GHz, with 128GB of RAM, 480GB of SSD storage and dual 10Gbps network ports" (though of course building Bazel should work on a smaller machine, too 😅). |
@philwo good info. I don't have direct access to the arm machines used on the copr.fedorainfracloud.org/ build-infra, but fired up a pine64 (2G ram/1G swap; 4 cores), and the |
alrighty. I spun up a c1.large.arm on equinixmetal (on flatcar 🚋 ), ran a docker fedora:32 container, and in it: dnf install -y rpm-build make xz git
git clone https://github.com/vbatts/copr-build-bazel
cd copr-build-bazel/
make rebuild # also 'make rpm' will work And it successfully built the binary rpm in 570s or so. ( Given the cryptic failures I'm seeing on aarch64 on the copr.fedorainfracloud.org, it is my guess that their machines are too small, or that the bazel build is [too] demanding. (this c1.large.arm does have 96 cores/130G ram) |
We missed a cherry pick in 3.6.0, see #12086 (comment) |
Bazel 3.7 is out and should be used instead. |
Status of Bazel 3.6
To report a release-blocking bug, please file a bug using the
Release blocker
label, and cc me.Task list:
The text was updated successfully, but these errors were encountered: