[Q4 2023] macOS fleet expansion #1708
Comments
fweikert
added a commit
to fweikert/continuous-integration
that referenced
this issue
Jul 11, 2023
- Also include platform name in caching key on macOS to avoid problems with Intel chip machines vs M1 machines. - Disable caching for the new QA machines since they need a GCS-based cache (which hasn't been set up yet) Progress towards bazelbuild#1708
fweikert
added a commit
that referenced
this issue
Jul 12, 2023
- Also include platform name in caching key on macOS to avoid problems with Intel chip machines vs M1 machines. - Disable caching for the new QA machines since they need a GCS-based cache (which hasn't been set up yet) Progress towards #1708
fweikert
added a commit
to fweikert/continuous-integration
that referenced
this issue
Jul 12, 2023
This is an experiment. Progress towards bazelbuild#1708
fweikert
added a commit
that referenced
this issue
Jul 12, 2023
This is an experiment. Progress towards #1708
fweikert
added a commit
to fweikert/continuous-integration
that referenced
this issue
Nov 17, 2023
The script now simply uses the oldest installed Xcode version if no specific version was requested or if the requested version isn't installed. Progress towards bazelbuild#1708
fweikert
added a commit
that referenced
this issue
Nov 20, 2023
The script now simply uses the oldest installed Xcode version if no specific version was requested or if the requested version isn't installed. Progress towards #1708
fweikert
added a commit
to fweikert/bazel
that referenced
this issue
Nov 20, 2023
Soon we'll set JAVA_TOOL_OPTIONS in MacOS CI workers, which results in a additional warning in the log, thus failing bazel_command_log_test. Progress towards bazelbuild/continuous-integration#1708
fweikert
changed the title
fweikert
added a commit
to fweikert/continuous-integration
that referenced
this issue
Nov 21, 2023
Bazel requires additional flags when running in an IPv6-only network. Progress towards bazelbuild#1708
fweikert
added a commit
that referenced
this issue
Nov 21, 2023
Bazel requires additional flags when running in an IPv6-only network. Progress towards #1708
copybara-service bot
pushed a commit
to bazelbuild/bazel
that referenced
this issue
Nov 21, 2023
Soon we'll set JAVA_TOOL_OPTIONS in MacOS CI workers, which results in a additional warning in the log, thus failing bazel_command_log_test. Progress towards bazelbuild/continuous-integration#1708 Closes #20274. PiperOrigin-RevId: 584405074 Change-Id: Ideb9aff097b9ee9900b1da423f2504da9ba82999
fweikert
added a commit
to fweikert/continuous-integration
that referenced
this issue
Dec 8, 2023
This should fix "Network is unreachable" errors in Python tests. Progress towards bazelbuild#1708
meteorcloudy
pushed a commit
that referenced
this issue
Dec 8, 2023
This should fix "Network is unreachable" errors in Python tests. Progress towards #1708
fmeum
pushed a commit
to fmeum/continuous-integration
that referenced
this issue
Dec 10, 2023
- Also include platform name in caching key on macOS to avoid problems with Intel chip machines vs M1 machines. - Disable caching for the new QA machines since they need a GCS-based cache (which hasn't been set up yet) Progress towards bazelbuild#1708
fmeum
pushed a commit
to fmeum/continuous-integration
that referenced
this issue
Dec 10, 2023
This is an experiment. Progress towards bazelbuild#1708
fweikert
added a commit
to fweikert/continuous-integration
that referenced
this issue
Dec 19, 2023
Progress towards bazelbuild#1708
fweikert
added a commit
to fweikert/continuous-integration
that referenced
this issue
Feb 5, 2024
With a high number of shards it becomes very hard to see which tests are actually failing. This change adds annotations that contain a test summary for all failing tests for each platform. Related to bazelbuild#1708
fweikert
added a commit
to fweikert/continuous-integration
that referenced
this issue
Feb 5, 2024
With a high number of shards it becomes very hard to see which tests are actually failing. This change introduces the --print_shard_summary flag. If set, there will be one Buildkite annotation per failing sharded platform that contains a test summary of all failing tests. Related to bazelbuild#1708 m
fweikert
added a commit
to fweikert/continuous-integration
that referenced
this issue
Feb 5, 2024
With a high number of shards it becomes very hard to see which tests are actually failing. This change introduces the --print_shard_summary flag. If set, there will be one Buildkite annotation per failing sharded platform that contains a test summary of all failing tests. Example: https://buildkite.com/bazel/bazel-bazel-macos-ninja/builds/420 Related to bazelbuild#1708
fweikert
added a commit
to fweikert/continuous-integration
that referenced
this issue
Feb 5, 2024
With a high number of shards it becomes very hard to see which tests are actually failing. This change introduces the --print_shard_summary flag. If set, there will be one Buildkite annotation per failing sharded platform that contains a test summary of all failing tests. Example: https://buildkite.com/bazel/bazel-bazel-macos-ninja/builds/420 Related to bazelbuild#1708
fweikert
added a commit
that referenced
this issue
Feb 6, 2024
With a high number of shards it becomes very hard to see which tests are actually failing. This change introduces the `--print_shard_summary` flag. If set, there will be one Buildkite annotation per failing sharded platform that contains a test summary of all failing tests. Example: https://buildkite.com/bazel/bazel-bazel-macos-ninja/builds/420 Related to #1708
fweikert
added a commit
to fweikert/continuous-integration
that referenced
this issue
Feb 8, 2024
fweikert
added a commit
that referenced
this issue
Feb 8, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Our goal is to grow the macOS CI worker fleet for both Intel and M1 chips in Q3. Currently macOS workers are the most significant bottleneck when it comes to CI performance.
The text was updated successfully, but these errors were encountered: