Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
Debugging
⚠️ git log -1 --pretty=format:'%H%n%aN%n%aE%n%cN%n%cE%n%s' (return code 128)see https://github.com/agama-project/agama/actions/runs/15023225072/job/42217441468#step:14:166
fatal: detected dubious ownership in repository at '/__w/agama/agama'see https://github.com/agama-project/agama/actions/runs/15020310724/job/42207691974#step:9:9
gitCLI tool? Different glibc, nodejs or something else?)Solution
gitso a different owner is OK (this was not the root of the problem in the end but this could cause troubles elsewhere later so I'm keeping this change anyway.)(That's a bit tricky, if a job runs in a container then all steps run in the container, you cannot run a command outside the container. The workaround is to define a dependent job which runs outside the container and pass the coverage data as an artifact which is uploaded/downloaded.)
Testing