FileNotFoundError: 'compile_commands.json' in CI

[lalten]

I'm trying to set up the compile_commands.json generation in GitHub Actions CI to feed it to clang-tidy in the next step. But it looks like this line:

bazel-compile-commands-extractor/refresh.template.py

Line 1053 in 19808d6

with open('compile_commands.json', 'w') as output_file:

fails if the file does not exist yet:

INFO: Running command line: bazel-bin/external/hedron_compile_commands/refresh_all
>>> Automatically added //external workspace link:
    This link makes it easy for you--and for build tooling--to see the external dependencies you bring in. It also makes your source tree have the same directory structure as the build sandbox.
    It's a win/win: It's easier for you to browse the code you use, and it eliminates whole categories of edge cases for build tooling.
>>> Analyzing commands used in @//...
>>> Finished extracting commands for @//...
Traceback (most recent call last):
  File "/github/home/.cache/bazel/_bazel_root/284f8c6ca1cf5fd7f4e20c15176f40/execroot/repo/bazel-out/k8-fastbuild/bin/external/hedron_compile_commands/refresh_all.runfiles/hedron_compile_commands/refresh_all.py", line 1060, in <module>
    with open('compile_commands.json', 'w') as output_file:
FileNotFoundError: [Errno 2] No such file or directory: 'compile_commands.json'
Error: Process completed with exit code 1.

[lalten]

Never mind, this was an error on my side: compile_commands.json was a symlink to build/compile_commands, which did not exist in CI.

[cpsauer]

Glad you got through it, and thanks for your interest in using the tool @lalten.

Just for my learning and understanding: What's motivating the symlink?

[lalten]

It's from a CMake build that we're transitioning away from currently