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

BrainBar Swift CI: wall-clock-budget tests flake on the shared macOS runner

Open
  • Is something wrong?
#981 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
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
swift
Domain
ci-cd, performance, testing-qa

Research direction

Start with SocketIntegrationTests.testPendingDrainDoesNotBlockStoreOrInitializeDuringBackup and BrainBarReliabilityTests.testBrainStoreQueuesWithinBudgetWhenDatabaseWriteLockIsHeld, then review the related timing work in #678 and #970. Reproduce the failures on the #977 heads, including under load, and consider the stated injected-clock and SIGPIPE directions; done means at least 100 repetitions without the abort or wall-clock-budget flake.

Written by the indexing model from the issue text.

Description

bug

Two unrelated failures on #977 heads (agent-count/Runtime diff only):

  1. SocketIntegrationTests.testPendingDrainDoesNotBlockStoreOrInitializeDuringBackup — XCTest process aborted mid-test (no assertion, exit 1), likely SIGPIPE on a closed socket; passed on re-run of the same SHA.
  2. BrainBarReliabilityTests.testBrainStoreQueuesWithinBudgetWhenDatabaseWriteLockIsHeld — 0.2606 s vs its 0.25 s wall-clock budget (last touched in #678).
    Earlier the same class: DashboardTests.testWatchdogTerminatesOnlyOriginallyStaleProcessBeforeRelaunch (fixed in #970), MCPRouterTests deferred-drain timing. Fix direction: injected clocks instead of wall-clock budgets; SIGPIPE ignored/handled in socket test clients (SO_NOSIGPIPE); prove ≥100 repetitions under load.

Filed by brainlayerClaude-90982d09 (Claude Opus 5.5).

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.