Speed up CI: split tests across machines + fix hot spec files (cruft removal won't help)

Open
#2,933 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
30/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Active
Tech stack
github-actions, ruby
Domain
ci-cd, testing

Research direction

Start with the timing table: the hot spec files are spec/requests/dedupable_spec.rb, spec/services/tag_alias_seeder_spec.rb and spec/requests/events_spec.rb, and the test step runs under parallel_rspec. Splitting jobs across matrix runs means changing the CI workflow, which the payload does not name, so confirm the maintainers want that before starting. Done means a measured drop in wall-clock CI time, with the 17 pending examples handled separately.

Written by the indexing model from the issue text.

Description

blocked

🤖 From Claude:

CI takes 11–13 min. Deleting old/redundant specs won't fix that: removing every cruft candidate saves only about 25s. The time goes to the test step itself and a handful of slow spec files.

Measured from the per-example timing files of one green CI run (12,769 examples).

Where the time goes (one run, 11 min total)

Step Time
Setup (containers, Ruby, npm, Vite build, DBs) ~1:40
parallel_rspec, 4 processes 9:21
  • Total example time is 34.6 min, split 4 ways. Processes finished between 7:50 and 9:14.
  • By directory: requests 16.2 min (47%), services 8.0, system 3.8, models 3.4, everything else ~3.
  • Factories are cheap (2–40ms per create), so they aren't the cause.

Cruft: low value

Candidate Examples Total time Wall-clock saved
Auth-gate request specs (guest / regular user / denied) 463 1.0 min ~15s
View specs 563 0.5 min ~8s
Scaffold-style request specs 101 0.1 min ~2s
Pending/skipped examples 17 0 0
  • Delete or fix the 17 pending examples for hygiene. It won't speed anything up.
  • Keep the auth-gate specs. They're cheap and check the real routing and redirects.

Real levers

  1. Split tests across 2–3 GitHub Actions matrix jobs (biggest win)

    • 2 machines × 4 processes → tests ~4.5 min, CI ~6.5 min. 3 machines → CI ~5 min.
    • Repo is public, so standard runners are free.
    • parallel_rspec --only-group lets each job take a share.
  2. Speed up the hot files. The top 12 files are ~35% of all example time:

    File Time Examples Per example
    spec/requests/dedupable_spec.rb 124s 113 ~1.1s
    spec/requests/events_spec.rb 81s 413
    spec/services/event_registration_services/public_registration_spec.rb 77s 110 0.7s
    spec/requests/people_dedupe_professional_licenses_spec.rb 68s 31 2.2s
    spec/services/event_dashboard_spec.rb 57s 143
    spec/services/tag_alias_seeder_spec.rb 46s 23 2s (runs the whole seeder in every example)
    • Running heavy setup once per file instead of once per example could roughly halve these, saving ~1.5 min wall clock.
  3. Group by runtime instead of file size

    • Record a runtime log (ParallelTests::RSpec::RuntimeLogger) and use --group-by runtime.
    • Evens out the 7:50 vs 9:14 spread, saving ~30–40s.
  4. Two slow system specs (11–13s each), low priority

    • community_news_index_spec.rb:170 and notification_incoming_responded_spec.rb:8.
    • Probably slow only because they run first in their process and wait for Chrome to start.
Dominant language
Ruby
Stars
15
Forks
28
Avg merge
14h 29m
Merged PRs (30d)
292

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

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 rubyforgood/awbw

All issues in rubyforgood/awbw

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.