Closed xmfcx closed 3 months ago
Thank you for contributing to the Autoware project!
🚧 If your pull request is in progress, switch it to draft mode.
Please ensure:
@veqcc it failed the test:
I think you need to either:
autoware/main/.clang-tidy-ci
Required
workflow.@xmfcx
@veqcc it failed the test:
I think you need to either:
- update the config file in
autoware/main/.clang-tidy-ci
- or fix the packages to conform to the new rules before we can make it a
Required
workflow.
Thank you for informing me!
I have confirmed the workflow result. It seems the clang-tidy just warns and invokes no errors, which is the expected behavior.
I have to check why the Run clang-tidy
step ends up with exit code 1. I'll do it tomorrow 👍
I have to check why the Run clang-tidy step ends up with exit code 1. I'll do it tomorrow
clang-tidy -p build/ -export-fixes /tmp/clang-tidy-result/fixes.yaml ${{ steps.get-target-files.outputs.target-files }} || true
- name: Mark the workflow as failed if the fixes.yaml file exists
if: ${{ steps.check-fixes-yaml-existence.outputs.exists == 'true' }}
run: |
exit 1
shell: bash
This is the reason it is making the job fail. I'll leave the rest to you.
This is the reason it is making the job fail. I'll leave the rest to you.
I have fixed in https://github.com/autowarefoundation/autoware-github-actions/pull/306
Description
This new config file we are pointing is located at
autoware/main/.clang-tidy-ci
.It is supposed to be less restrictive to make it a required check.
And we will make it more strict over time as we adjust existing code to adhere these new standards.
Related links
Follow up from:
Parent discussion:
How was this PR tested?
Notes for reviewers
Interface changes
None.
Effects on system behavior
None.