Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

BrainBarDashboardPanelControllerTests.testSearchOverlayDoesNotShrinkExpandedDetailsAndVerticalSizeIsPinned fails locally on clean main, but CI is green

Open
  • Is something wrong?
#906 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
3-5 days
Newbie friendliness
42/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
swift
Domain
ci-cd, testing-qa

Research direction

Start with BrainBarDashboardPanelControllerTests/testSearchOverlayDoesNotShrinkExpandedDetailsAndVerticalSizeIsPinned and reproduce it on clean origin/main with the provided swift test --filter command. Compare the local test path with the CI test selection and display environment to determine why visibleFrame differs or the test is omitted. Done means the discrepancy is explained and the local and CI health signals are made consistent.

Written by the indexing model from the issue text.

Description

Two tests, opposite blind spots

BrainBarDashboardPanelControllerTests/testSearchOverlayDoesNotShrinkExpandedDetailsAndVerticalSizeIsPinned
fails on clean origin/main (9f26d9f9) when run locally:

swift test --filter BrainBarDashboardPanelControllerTests/testSearchOverlayDoesNotShrinkExpandedDetailsAndVerticalSizeIsPinned
-> Test Suite 'BrainBarTests.xctest' failed
   0.0  vs  Double.greatestFiniteMagnitude

macOS 27.0, Xcode 27.0, CLT 27.0.0.0.1788430756.

Yet main's CI at 9f26d9f9 is green (CI: success, Ratchet attest: success).

Found by the double-render implementer running the full suite (929 tests, 5 skipped, 1 failure) and reported as
reproducing unchanged on clean main. I verified that claim independently before filing rather than relaying
it — it reproduces.

Why this is worth its own issue

Set it beside #891 and the pair is the actual problem:

#891 socket flake this test
locally passes, 0.102 s fails
in CI fails ~55% passes

Our local suite and our CI suite disagree about whether main is healthy, in both directions. Each one is
individually dismissible ("just a flake", "just a local quirk"); together they mean neither signal can be
trusted on its own, which is how a real regression gets through. That cost a day already this week — three
consecutive #891 failures got read as a regression in #902 that did not exist.

Not established

  • Why CI does not see it. Candidates: it is display-dependent and CI's environment differs; it is skipped or
    deselected in the CI path; or CI's runner produces a different visibleFrame. I have not checked which,
    and the answer decides whether this is a test bug or a coverage hole.
  • Whether it is a recent regression or long-standing. Not bisected.

Explicitly not done here

No fix, no skip, no deadline change — filing only. The double-render/line-restore lane did not attempt an
out-of-scope fix, which was the right call.

🤖 Generated with Claude Code

Dominant language
Python
Stars
9
Forks
7
Avg merge
2h 8m
Merged PRs (30d)
211

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 EtanHey/brainlayer

All issues in EtanHey/brainlayer

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.