coverallsapp / coverage-reporter
95%

DEFAULT BRANCH: master
Repo Added
Files 44
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

LAST BUILD ON BRANCH master
branch: SELECT
CHANGE BRANCH
x

coverage: 95.438%. Remained the same
32906553634

push

github

web-flow 
docs: correct the cause behind the libevent pin and its regression gate (#215)

We attributed the v0.6.19-v0.6.21 startup crash to sandboxed container runtimes
(gVisor, Cloud Run, GKE Autopilot). That was a guess, and it was wrong.

The reporting customer's environment turned out to be ordinary Docker and
Kubernetes on RHEL/CentOS 7 hosts -- kernel 3.10, a genuine Red Hat build, no
sandbox and no emulation. CLOCK_BOOTTIME timerfds require Linux >= 3.15
(June 2014), so 3.10 returns EINVAL. Same missing capability, different reason.

That distinction matters for anyone reading these comments later. "gVisor"
invites the reader to conclude it does not apply to them; a kernel floor is
something they can actually check. It also means the exposed population was
larger than we assumed -- RHEL 7 ELS runs to 2028 and enterprise CI fleets are
full of it -- not the niche we described.

Comments only. No build flags, no seccomp rule, no behavior change, so no
release: the `build_cmd` line is byte-identical and the profile's `syscalls`
rule is untouched (only its inert `_comment` key changed). Re-verified the gate
still discriminates against the real published binaries: v0.6.21 exits 1,
v0.6.22 exits 0.

The regression gate itself was always correct -- it tests for the missing
capability, which is cause-agnostic, and would have caught this regardless of
which explanation we believed.

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>

1046 of 1096 relevant lines covered (95.44%)

2.22 hits per line

Relevant lines Covered
1096 RELEVANT LINES 1046 COVERED LINES
2.22 HITS PER LINE
Source Files on master

Recent builds

Builds Branch Commit Type Ran Committer Via Coverage
32906553634 master docs: correct the cause behind the libevent pin and its regression gate (#215) We attributed the v0.6.19-v0.6.21 startup crash to sandboxed container runtimes (gVisor, Cloud Run, GKE Autopilot). That was a guess, and it was wrong. The reporting ... push web-flow github
95.44
rc-x86_6... docs/correct-kernel-cause-comments Merge 3baa3e1db into d7e2b7b9d Pull #215 web-flow github
91.78
rc-aarch... docs/correct-kernel-cause-comments Merge 3baa3e1db into d7e2b7b9d Pull #215 web-flow github
91.78
32906079932 docs/correct-kernel-cause-comments Merge 3baa3e1db into d7e2b7b9d Pull #215 web-flow github
95.44
32903032163 master ci: bump dawidd6/action-download-artifact from 23 to 24 (#214) Bumps [dawidd6/action-download-artifact](https://github.com/dawidd6/action-download-artifact) from 23 to 24. - [Release notes](https://github.com/dawidd6/action-download-artifact/rele... push web-flow github
95.44
rc-aarch... dependabot/github_actions/dawidd6/action-download-artifact-24 Merge f11852b42 into 16146c29c Pull #214 web-flow github
91.78
rc-x86_6... dependabot/github_actions/dawidd6/action-download-artifact-24 Merge f11852b42 into 16146c29c Pull #214 web-flow github
91.78
32882655457 dependabot/github_actions/dawidd6/action-download-artifact-24 Merge f11852b42 into 16146c29c Pull #214 web-flow github
95.44
32310005832 master test: isolate jobs_spec from ambient CI env vars (#210) `request_body` is built from `Config#to_h`, which gains service_name, service_number and friends as soon as a CI provider is detected. Under GitHub Actions the real GITHUB_* vars are present... push web-flow github
95.44
rc-aarch... v0.6.22 0.6.22: Fix startup crash in sandboxed container runtimes (gVisor et al) Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> push afinetooth github
91.78
See All Builds (721)