Flaky test: x11_overlay_frames_are_never_composited_half_presented

Open
#7,993 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
1-2 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
linux, rust
Domain
desktop, testing

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.

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

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from trycua/cua

All issues in trycua/cua

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.