Flaky test: x11_overlay_frames_are_never_composited_half_presented
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 48/100
Research direction
Start with crates/platform-linux/src/overlay.rs, especially the failing test at line 4456, and inspect how it samples composited frames under xvfb and picom. Re-run the Rust Linux unit test to see whether the failure reproduces, then determine whether delayed compositor output or partial overlay presentation explains the half-presented read. Done means identifying the cause and making the test reliably distinguish a timing flake from a real rendering issue.
Written by the indexing model from the issue text.
Description
overlay::tests::x11_overlay_frames_are_never_composited_half_presented (platform-linux, crates/platform-linux/src/overlay.rs) failed once in CI on a PR that does not touch the overlay code.
- PR: #5574, commit
8d2a3afba5770822e019c21f7fb4448932e43781 - Run: https://github.com/trycua/cua/actions/runs/41747393355/job/126331653247 (CI: Rust Linux unit, "Rust Linux unit and compile", attempt 2)
- The other X11 overlay tests in the same job passed,
x11_overlay_frames_are_never_seen_half_presentedamong them.
Failure:
thread 'overlay::tests::x11_overlay_frames_are_never_composited_half_presented' panicked at crates/platform-linux/src/overlay.rs:4456:9:
1 of 1063 reads saw a half-presented frame, first: ["red 24963, blue 0, other 0"]
PR #5574 changes no file under the overlay code, so this looks like a timing flake in the composited (xvfb + picom) path: one read in 1063 counted as half-presented.
If it fails again, please investigate it as a flake. Either the test samples the composited output before the compositor has settled, or the overlay can really present a partial frame under a compositor.
- Dominant language
- Rust
- Stars
- 32.3k
- Forks
- 2.4k
- Avg merge
- 4h 47m
- Merged PRs (30d)
- 711
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from trycua/cua
-
Difficulty 1/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
Similar issues
-
app-request
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
flatpark/flatpark#1423 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
helix-editor/termina#35 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 5 days
-
Add coverage reportsOpentype:ci
Difficulty 2/5 1-3 hours Newbie friendliness 68/100