slbotbm opened a new pull request, #3281:
URL: https://github.com/apache/iggy/pull/3281
## Which issue does this PR close?
Closes #
## Rationale
The linting step for cpp was surfacing the following error:
```bash
Save cache for disk-true
Warning: Error: Path Validation Error: Path(s) specified in the action for
caching do(es) not exist, hence no cache is being saved.
at
file:///home/runner/work/_actions/bazel-contrib/setup-bazel/c5acdfb288317d0b5c0bbd7a396a3dc868bb0f86/dist/node_modules/@actions/cache/lib/cache.js:400:1
at Generator.next (<anonymous>)
at fulfilled
(file:///home/runner/work/_actions/bazel-contrib/setup-bazel/c5acdfb288317d0b5c0bbd7a396a3dc868bb0f86/dist/node_modules/@actions/cache/lib/cache.js:4:1)
```
```bash
Save cache for repository
Warning: Error: Path Validation Error: Path(s) specified in the action for
caching do(es) not exist, hence no cache is being saved.
at
file:///home/runner/work/_actions/bazel-contrib/setup-bazel/c5acdfb288317d0b5c0bbd7a396a3dc868bb0f86/dist/node_modules/@actions/cache/lib/cache.js:400:1
at Generator.next (<anonymous>)
at fulfilled
(file:///home/runner/work/_actions/bazel-contrib/setup-bazel/c5acdfb288317d0b5c0bbd7a396a3dc868bb0f86/dist/node_modules/@actions/cache/lib/cache.js:4:1)
```
This PR disables bazel's caching for the cpp linting step.
## What changed?
setup-bazel step disabled for cpp linting.
## Local Execution
- N/A
- Pre-commit hooks ran
<!--
You must run your code locally before submitting.
"Relying on CI" is not acceptable - PRs from authors who haven't run the
code will be closed.
Did you have `prek` installed? It runs automatically on commit and covers
all project languages. See
[CONTRIBUTING.md](https://github.com/apache/iggy/blob/master/CONTRIBUTING.md).
-->
## AI Usage
If AI tools were used, please answer:
1. Which tools? codex
2. Scope of usage? issue finding
3. How did you verify the generated code works correctly? N/A
4. Can you explain every line of the code if asked? Yes
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
