Skip to content

ci: build e2e image on ubuntu-22.04 to match runtime glibc#935

Merged
scarmuega merged 1 commit into
mainfrom
ci/e2e-fix-glibc
Jun 14, 2026
Merged

ci: build e2e image on ubuntu-22.04 to match runtime glibc#935
scarmuega merged 1 commit into
mainfrom
ci/e2e-fix-glibc

Conversation

@scarmuega

Copy link
Copy Markdown
Member

Problem

The e2e run failed in every test leg with:

oura: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.39' not found (required by oura)

Not a missing library — a glibc version mismatch. #934 switched e2e to a native build, but its build job ran on ubuntu-latest (now Ubuntu 24.04, glibc 2.39). The .github/image/Dockerfile runtime is debian:12-slim (glibc 2.36), which can't satisfy a GLIBC_2.39 symbol. The build step passed; the failure only surfaced at runtime in the test legs.

Fix

Pin the e2e build job to ubuntu-22.04 (glibc 2.35) — the same runner docker.yml already uses — so the binary's glibc floor is compatible with the debian:12 runtime. One line.

The production docker.yml image was never affected (it already builds on ubuntu-22.04). The test job stays on ubuntu-latest since it runs the image inside a container, where the host glibc is irrelevant.

Verification

Re-dispatch the e2e workflow on this branch and confirm the test legs get past image startup.

🤖 Generated with Claude Code

The e2e build job ran on ubuntu-latest (24.04, glibc 2.39), so the binary
linked GLIBC_2.39, which the debian:12-slim runtime image (glibc 2.36)
can't satisfy:

  oura: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.39' not found

Pin the build to ubuntu-22.04 (glibc 2.35), matching docker.yml's build
runner, so the binary is compatible with the runtime image.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@scarmuega scarmuega requested a review from paulobressan as a code owner June 14, 2026 00:36
@coderabbitai

coderabbitai Bot commented Jun 14, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@scarmuega, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 1 minute and 22 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 9f351b4b-815f-4803-9b9c-96b518ff2e33

📥 Commits

Reviewing files that changed from the base of the PR and between e474c08 and 5a4aee1.

📒 Files selected for processing (1)
  • .github/workflows/e2e.yaml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch ci/e2e-fix-glibc

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@scarmuega scarmuega merged commit e91db32 into main Jun 14, 2026
12 checks passed
@scarmuega scarmuega deleted the ci/e2e-fix-glibc branch June 14, 2026 00:40
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