Mustafa7 - @0hmx fanout tests in core main bran...

checking

Ah, something happened, but I’m not sure why. Core not showing this test failure, which occurred after the PR was merged. Merging the PR triggered another test run, but it ran against the PR branch instead of `main`. That’s very confusing and seems like a separate bug we should investigate later.

Am fixing it, ig its a new policy issue

Yea its related to decoupling caps

Its on us but we also need to fix core it hiding falling test if they are triggered after merge. like in this case.

isnt that a github ci issue?

Like running after merged

oh ok so its showing green checks very early right?

https://github.com/tscircuit/core/pull/3038 you can see here it just completed all workflows in just 3 mins?

How?

it took like one min to run tests?

this is diffrent issue tho i think idk

<@757706909351411845>

```Old behavior: Place components → route everything → tests pass New behavior: Recognize capacitor as decoupling ↓ Apply 1 mm limit ↓ Check placement before routing ↓ Endpoints are 2.68 mm / 7.27 mm apart ↓ Skip the entire subcircuit router ↓ Zero PCB traces → tests fail``` This was the main issue for failing the breakout tests

in core

https://github.com/tscircuit/core/pull/3038 i think we should merge it right?

<@809856037376491570>

The failure appear on `main` because GitHub Actions was experiencing downtime. As a result, the workflows were not triggered on time, causing a silent CI failure. Previously, all 15 test jobs were running now for the last 3 comments they did not even run. I think its fixed now again. haa shity downtime. the missed workflow runs did run after some time in which we caught the new test fails. <@1079361271687807026>

Ohh didn't even notice