• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

mozilla-releng / balrog / #5047 / 1
90%
main: 89%

Build:
Build:
LAST BUILD BRANCH: heads/refs/heads/main
DEFAULT BRANCH: main
Ran 05 Dec 2025 12:14PM UTC
Files 61
Run time 1s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

05 Dec 2025 12:06PM UTC coverage: 90.037%. First build
#5047.1

Pull #3589

circleci

Eijebong
Don't change render state while filtering releases

Every state changes triggers a state change, which gets react to create N
objects which get increasingly bigger (the spread operator with
...prevState). With 1000 releases, that's 500k copies. With 60k which is
what I'm testing with... `> sum(range(0, 60001)) = 1800030000` (yikes).
And that's not counting the state changes queuing re-renders, one per
release... Even if react batches those, it's again copies, and extra
work.

This commit changes it to create the state in one go, making filtering
60k releases actually something doable rather than something that will
freeze firefox for 30s for every typed character
Pull Request #3589: Don't change render state while filtering releases

2167 of 2544 branches covered (85.18%)

Branch coverage included in aggregate %.

5722 of 6218 relevant lines covered (92.02%)

0.92 hits per line

Source Files on job #5047.1
  • Tree
  • List 61
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Build 5047
  • 3eefadb9 on github
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc