Locally sanity tests seem to be failing on format issues. I'm trying to fix them.

Actually format issues looks like it is for an unrelated file: "./test/cpp/qps/json_run_localhost_scenarios.bzl"

Can you rerun the generation script? Sometimes I see the formatting complain of that file. If the complain persists, can you share the log?

Can you rerun the generation script? Sometimes I see the formatting complain of that file. If the complain persists, can you share the log?

I reran: ./tools/buildgen/generate_projects.sh but sanity check (python tools/run_tests/run_tests.py --use_docker -j 16 -l sanity -c dbg) still fails locally. It looks like it passed as part of CI though, so this might just be an environment issue on my side.

Going ahead to merge this PR since all tests in CI passes. I hope the BoringSSL optimization can be included in our next release. The time until next release should give us a chance to catch potential issue.

@emkornfield Awkwardly, the boringssl-with-bazel library is not available in google3. But the gen_build_yamp.py needs to be ran in both environments. Can you create a roll forward PR without directly depending on sources.json? Or we need to import the boringssl-with-bazel to third_party?

@lidizheng can you clarify if output is important or just a non zero exit code

The output is important. It generates the yaml file that both Bazel and Blaze reads.

Can you send directions on how to test in google3

@emkornfield There isn't a straightforward way to test this.

If a PR is merged. You can initiate an import by running /home/build/google3/third_party/grpc/copybara_import.sh. Its documentation is at go/grpc-import. This script imports newly merged code from GitHub to google3.

Or you can create a one PR import CL from go/grpc-cherrypick. It's a bit more complex, since it needs to get the ref commit hash for rebase. This approach only works for unmerged PRs.