Skip to content

fix(coverage): copy the shard instead of moving a root-owned file - #83

Merged
zeriyoshi merged 1 commit into
mainfrom
fix/coverage-shard-copy
Jul 27, 2026
Merged

fix(coverage): copy the shard instead of moving a root-owned file#83
zeriyoshi merged 1 commit into
mainfrom
fix/coverage-shard-copy

Conversation

@zeriyoshi

Copy link
Copy Markdown
Contributor

Summary

Fixes the Coverage / coverage failure on main (mv: cannot move 'ext/lcov.info' ...: Permission denied). The capture succeeded, but the file written by the container (root) could not be moved by the runner user. cp only needs read access and produces a runner-owned shard, so the collection step uses it instead. The checkout-restored ext/.gitkeep marker is also removed before the run so the container does not needlessly re-initialize the downloaded extension sources.

The other failure in the same run (Linux_Emulated s390x 8.4 zts alpine — Setup QEMU step) was another transient Docker Hub connection timeout, unrelated to any change; the post-merge run will retry it.

🤖 Generated with Claude Code

The capture inside the container leaves ext/lcov.info owned by root on
the runner, and mv from the runner user failed with EPERM. cp only
needs read access and produces a runner-owned shard, so use it instead.
Also drop the checkout-restored ext/.gitkeep marker before the run so
the container does not needlessly re-initialize the downloaded
extension sources.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@zeriyoshi
zeriyoshi merged commit ebf3c38 into main Jul 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant