Some warnings have a non-valid link to the code

[messers2]

The referenced sources still exist, but the reference seems to be invalid. Any ideas?
The PR-comment was produced during a job run that runs in parallel with more jobs during an PR-update

[JacobDomagala]

Is that file a part of git repository or is it being generated during build process? I'm asking because I can see //build/ in file path.
Do you build it inside a custom docker or as an action step?

Running in a matrix strategy shouldn't be a problem.

[messers2]

mmh, you're right, the file is from a fetch_content command and subsequently copied to the build directory. I'll have to check on this, but I think this happens also for other files (files located in the source). For this kind of files I'll have to filter out these warning lines. So I guess the /blob/-directory is not persistent as long as the PR is open but only as long as the build is running

[messers2]

For future reference: It really only affected sources that were part of external dependencies, so I could filter them out straight forward by treating the compiler output file like this (where the /_deps/ directory provides the means to discriminate the dependencies:

 sed -i '/.*\/_deps\/.*\swarning:/d' compiler_output/${{ matrix.configs }}.txt