Skip to content

fix: TUI targets panel missing entries#24

Merged
haugoug merged 1 commit intogvsoc:mainfrom
germainh512:fix/tui-targets-panel
Mar 15, 2026
Merged

fix: TUI targets panel missing entries#24
haugoug merged 1 commit intogvsoc:mainfrom
germainh512:fix/tui-targets-panel

Conversation

@germainh512
Copy link

Problem

Some targets don't appear in the TUI targets panel. Two causes:

1. Pytest tests not registered with TUI

PytestTestset.enqueue() was not calling runner.count_test() or tui.count_target(), so pytest-based tests never appeared in the targets panel. Regular Shell tests call these via TestCommon.enqueue(), but pytest tests have their own enqueue path that bypassed this.

2. Targets panel height cap

The targets panel height was capped at top_h // 3 (~10 targets on a typical 40-row terminal). If you have more targets than that, the extra ones are simply not drawn.

Fix

  1. Added count_test() and tui.count_target() calls in PytestTestset.enqueue() for each discovered test.

  2. Increased targets panel cap to top_h // 2, with a minimum of 4 rows reserved for the running panel.

Testing

All 142 tests pass.

1. PytestTestset.enqueue() was not calling count_test() or
   tui.count_target(), so pytest-based tests never appeared
   in the TUI targets panel. Now registers each test.

2. Targets panel now shows all targets without cutting off.
   Only constraint: running panel keeps at least 1 content line.

3. Left and right panels now have equal width (50/50 split
   instead of 2/3 + 1/3).
@germainh512 germainh512 force-pushed the fix/tui-targets-panel branch from 3453c32 to 28af872 Compare March 15, 2026 20:39
@haugoug haugoug merged commit 2ad44db into gvsoc:main Mar 15, 2026
3 checks passed
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.

2 participants