Issue 169168
Summary clang-tidy misreports progress when duplicating files due to multiple targets
Labels clang-tidy
Assignees
Reporter dkaszews
    Here is the log of `clang-tidy` progress when I run it on my repo, I edited paths to be relative and space-aligned first 9 items for readability.

```txt
[ 1/18] Processing file include/glug/detail/backport/type_traits.hpp.
[ 2/18] Processing file include/glug/filesystem.hpp.
[ 3/18] Processing file include/glug/filter.hpp.
[ 4/18] Processing file include/glug/glob.hpp.
[ 5/18] Processing file include/glug/regex.hpp.
[ 6/18] Processing file src/filesystem.cpp.
[ 7/18] Processing file src/filesystem.cpp.
[ 8/18] Processing file src/filter.cpp.
[ 9/18] Processing file src/filter.cpp.
[10/18] Processing file src/glob.cpp.
[11/18] Processing file src/glob.cpp.
[12/18] Processing file src/main.cpp.
[13/18] Processing file src/regex.cpp.
[14/18] Processing file src/regex.cpp.
[15/18] Processing file test/unit/main.cpp.
[16/18] Processing file test/unit/parametrized.hpp.
[17/18] Processing file test/unit/test_filesystem_explorer.cpp.
[18/18] Processing file test/unit/test_glob_decompose.cpp.
[19/18] Processing file test/unit/test_glob_filter.cpp.
[20/18] Processing file test/unit/test_glob_to_regex.cpp.
[21/18] Processing file test/unit/tree.cpp.
[22/18] Processing file test/unit/tree.hpp.
```

Note that all files in `src/` except for `main.cpp` are analyzed twice. This is completely expected, as they appear twice in the `compile_commands.json`: once for the main executable, once for UT. What I would like to see fixed though is the `[22/18]` part, as it is confusing and misleading, it should instead read as `[*/22]`, since that is the total number to analyse.

Environment:
* Invoked as: `clang-tidy $(git ls-files **.hpp **.cpp)`
* OS: `Linux 6.16.10-arch1-1 #1 SMP PREEMPT_DYNAMIC Thu, 02 Oct 2025 19:26:36
 +0000 x86_64 GNU/Linux`
* LLVM: `20.1.8`

_______________________________________________
llvm-bugs mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

Reply via email to