# Mustafa7 - Why core tests taking so much time t...

Channel: #contributor
Source: https://discord.com/channels/1233487248129921135/1542240074417053776
Started: 2026-08-26T18:31:27.778000+00:00
Last activity: 2026-08-26T19:27:57.369000+00:00

## Mustafa7 — 2026-08-26T18:31:27.176000+00:00

Why core tests taking so much time to finish locally, literally takes hour to finish

## Seve — 2026-08-26T18:31:46.277000+00:00

yea not a good idea to run those locally

## Seve — 2026-08-26T18:31:56.893000+00:00

core has a lot of tests haha

## Seve — 2026-08-26T18:32:29.773000+00:00

this is common for any big codebase, maybe at some point we reduce them, or we could even start to optimize, but it's fairly common for a codebase with all tests to be too big to run locally

## Mustafa7 — 2026-08-26T18:33:05.090000+00:00

is there any command where i can update snapshots on core prs on github

## Seve — 2026-08-26T18:33:12.714000+00:00

yes

## Seve — 2026-08-26T18:33:19.354000+00:00

/us or something

## Seve — 2026-08-26T18:33:33.499000+00:00

usually ai can just read the PR and see which ones failed tho

## Seve — 2026-08-26T18:33:39.509000+00:00

that's a bit simpler sometimes

## Mustafa7 — 2026-08-26T18:34:54.254000+00:00

but thats repetetive coz there are like 10 shared bun tests in a matrix

## Seve — 2026-08-26T18:37:30.555000+00:00

we can disable the early cancellation

## Seve — 2026-08-26T18:37:36.084000+00:00

(that would fix that issue right)

## Seve — 2026-08-26T18:37:44.860000+00:00

i'm not having the same issue and i'm not sure why

## Seve — 2026-08-26T18:37:55.390000+00:00

i'm able to do PRs to core that update snapshots fairly easily

## Seve — 2026-08-26T18:38:07.696000+00:00

idk if it's because my cpu is running a lot of tests, but you have an M5 right

## Mustafa7 — 2026-08-26T18:42:31.395000+00:00

M4

## Seve — 2026-08-26T18:42:41.733000+00:00

hmm yea idk

## Seve — 2026-08-26T18:42:47.518000+00:00

maybe disable the early bail in the workflow

## mohan-bee — 2026-08-26T19:27:57.369000+00:00

i too face this one , also i do update trace solver like edit the packge.json manually and /us .