Before Creating the Enhancement Request

• I have confirmed that this should be classified as an enhancement rather than a bug/feature.

Summary

Previously, we introduced the Bazel workflow in our community, which can quickly provide test results, but it also introduced some issues:

• The maintenance cost is relatively high. This includes timely updates to configuration files when new packages are introduced. The workflow often fails due to configuration issues, which can be confusing even when there are no actual problems.

• Although it can quickly provide test results, multiple workflows run simultaneously, and due to the bucket effect (wooden bucket principle), the final test results still require a long waiting time. Moreover, the test cases in other workflows can cover those in the Bazel workflow.

Therefore, I would like to propose removing this workflow. If you have any suggestions, please feel free to reply below.

Motivation

Removing the Bazel workflow

Describe the Solution You'd Like

Removing the Bazel workflow

Describe Alternatives You've Considered

No

Additional Context

No response