You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Nothing seems out of place in my paths. The __w part is because I'm indeed running clang-tidy inside docker, but seems like that is what the repo_path_prefix is meant to handle.
I added a simple bit of printing to my fork before the assert:
So it would seem that the assertion failure is coming from this replacement:
- BuildDirectory: /__w/mainframe-tester/mainframe-tester/build
DiagnosticMessage:
FileOffset: 5
FilePath: /__w/mainframe-tester/mainframe-tester/main/ADC.hpp
Message: invalid case style for global function 'initAdc'
Replacements:
- FilePath: /__w/mainframe-tester/mainframe-tester/main/mainframe-tester.cpp
Length: 7
Offset: 4544
ReplacementText: InitAdc
- FilePath: /__w/mainframe-tester/mainframe-tester/main/ADC.hpp
Length: 7
Offset: 5
ReplacementText: InitAdc
DiagnosticName: readability-identifier-naming
Level: Warning
This replacement seems valid, since it's changing a method name in both the header where it's defined and in a .cpp file where it's used.
It appears the code in its current state assumes that each replacement is only in a single file, which seems to not necessarily be the case, at least in clang-tidy 15.
The text was updated successfully, but these errors were encountered:
My repo is failing this assertion
My Workflow yml
My build/fixes.yml (`head -n 50` -- full version attached)
fixes.yml.zip
Nothing seems out of place in my paths. The
__w
part is because I'm indeed running clang-tidy inside docker, but seems like that is what therepo_path_prefix
is meant to handle.I added a simple bit of printing to my fork before the assert:
And I see this in the logs:
So it would seem that the assertion failure is coming from this replacement:
This replacement seems valid, since it's changing a method name in both the header where it's defined and in a
.cpp
file where it's used.It appears the code in its current state assumes that each replacement is only in a single file, which seems to not necessarily be the case, at least in clang-tidy 15.
The text was updated successfully, but these errors were encountered: