• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

qtile / qtile / 29548058254 / 2
83%
master: 83%

Build:
DEFAULT BRANCH: master
Ran 17 Jul 2026 02:08AM UTC
Files 156
Run time 5s
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

17 Jul 2026 01:40AM UTC coverage: 73.715%. Remained the same
29548058254.2

push

github

tych0
tests: surface qtile's logs on stderr when it fails to start

When a test's qtile process fails to come up, the harness previously
raised a bare "Error launching qtile" (plus a traceback if the child
sent one), but qtile's own log output -- which is written to a pipe and
only read on demand via get_log_buffer() -- was silently dropped. That
made startup failures in CI very hard to diagnose.

Add _drain_logs()/_dump_logs() to read whatever qtile buffered in the
log pipe (non-blocking) and print it to stderr, which pytest captures
and shows on failure. This is wired into both the start() failure paths
and terminate() when qtile exits with a non-zero exit code.

Also move the log pipe handler setup ahead of backend.create() in the
child so that the most common startup failure -- not being able to
connect to the display -- actually gets logged to the pipe and can be
surfaced.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

15349 of 20822 relevant lines covered (73.72%)

0.74 hits per line

Source Files on job 3.13-wayland - 29548058254.2
  • Tree
  • List 156
  • Changed 3
  • Source Changed 0
  • Coverage Changed 3
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 29548058254
  • cd96632e on github
  • Prev Job for on master (#28241224929.2)
  • Next Job for on master (#29548009764.2)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc