Open Geethree opened 1 month ago
As documented on https://github.com/aspect-build/rules_lint/blob/main/docs/format.md#format_test - the format_test
rule is not recommended because it's impossible for it to be hermetic when you've set no_sandbox = True
. Maybe on your CI you're getting a remote cache hit so it's not actually running the formatter on the files?
I'd recommend having a separate CI step to assert the changed files are formatted. Our https://aspect.build/workflows product includes this.
What happened?
As the title states, starting to pull my hair our locally. Currently I have my format targets configured like..
Locally on ubuntu 22.04 and on MacOS a current commit fails as such:
Summary here as it is just formatting yaml files and a BUILD file. *
In CI this isn't the case.. as all targets pass
CI here is running in gitlab inside of the
gcr.io/bazel-public/bazel:7.1.0
container image.I'm not really sure of how to go about debugging this..
Version
bazel version
Bazelisk version: development Build label: 7.1.1 Build target: @@//src/main/java/com/google/devtools/build/lib/bazel:BazelServer Build time: Thu Mar 21 18:08:59 2024 (1711044539) Build timestamp: 1711044539 Build timestamp as int: 1711044539
bazel run @buildifier_prebuilt//:buildifier -- -version buildifier version: 6.4.0 buildifier scm revision: 433ea8554e82832e4fa4bdd530ca471564071511
bazel run @multitool//tools/yamlfmt -- -version
yamlfmt 0.13.0 (dd8547d)
How to reproduce
No response
Any other information?
No response