Public: anyone can read this; the crew can change it.

Full suite red: 3 files in check run 01m7j36bmjhzbhmjn6vws096d1 #14211

shipped production is serving it opened this has it

Landed in pull #14212 · run

opened this

_Filed by the scheduled full-suite report, not written by a person. It holds no pull, batch or release._

3 files failed in the full suite on main (check run 01m7j36bmjhzbhmjn6vws096d1, 3ee4bed), filed as one issue: one run red for one cause starts one builder.

  • test/start.test.ts
  • test/merge-queue-batch.test.ts
  • test/axe.test.ts

test/start.test.ts

  • the whole file took 21.3 s, over the 20 s file budget: make it faster, or name its file in SLOW in scripts/gate.ts with an issue
  • start, push, live, claim > the app is live, and a push to main deploys the new commit took 5.40 s, over the 2 s test budget: make it faster, or name its file in SLOW in scripts/gate.ts with an issue
  • the defenses > a few starts an hour from one source, then a wait; another source is not held took 3.07 s, over the 2 s test budget: make it faster, or name its file in SLOW in scripts/gate.ts with an issue

To reproduce:

bun test ./test/start.test.ts
bun test ./test/start.test.ts --rerun-each 10

The full suite ran it in shard 350/3691, 4 files at a time.

test/merge-queue-batch.test.ts

  • the merge queue's batch size > a red 16-batch with one bad pull lands its 15 good within 2 rounds, then the bad one is handed back alone took 5.04 s, over the 2 s test budget: make it faster, or name its file in SLOW in scripts/gate.ts with an issue
  • the merge queue's batch size > a red halves the batch, and two greens in a row double it back to the setting took 4.41 s, over the 2 s test budget: make it faster, or name its file in SLOW in scripts/gate.ts with an issue

To reproduce:

bun test ./test/merge-queue-batch.test.ts
bun test ./test/merge-queue-batch.test.ts --rerun-each 10

The full suite ran it in shard 594/3691, 4 files at a time.

test/axe.test.ts

  • in a real browser: an unlabelled input yields one axe:label finding in each scheme, and a script-filled <main> a no-js finding took 3.38 s, over the 2 s test budget: make it faster, or name its file in SLOW in scripts/gate.ts with an issue
  • the whole file took 21.3 s, over the 20 s file budget: make it faster, or name its file in SLOW in scripts/gate.ts with an issue
  • start, push, live, claim > the app is live, and a push to main deploys the new commit took 5.40 s, over the 2 s test budget: make it faster, or name its file in SLOW in scripts/gate.ts with an issue
  • the defenses > a few starts an hour from one source, then a wait; another source is not held took 3.07 s, over the 2 s test budget: make it faster, or name its file in SLOW in scripts/gate.ts with an issue
  • the merge queue's batch size > a red 16-batch with one bad pull lands its 15 good within 2 rounds, then the bad one is handed back alone took 5.04 s, over the 2 s test budget: make it faster, or name its file in SLOW in scripts/gate.ts with an issue
  • the merge queue's batch size > a red halves the batch, and two greens in a row double it back to the setting took 4.41 s, over the 2 s test budget: make it faster, or name its file in SLOW in scripts/gate.ts with an issue

the whole file took 21.3 s, over the 20 s file budget: make it faster, or name its file in SLOW in scripts/gate.ts with an issue failed


3 of 3691 shards failed:
(fail) the whole file took 21.3 s, over the 20 s file budget: make it faster, or name its file in SLOW in scripts/gate.ts with an issue [shard 350]

To reproduce:

bun test ./test/axe.test.ts
bun test ./test/axe.test.ts --rerun-each 10

The full suite ran it in shard 2551/3691, 4 files at a time.

Files: test/start.test.ts, test/merge-queue-batch.test.ts, test/axe.test.ts

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs