Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Split test action into two jobs #1342

Merged
merged 1 commit into from
Dec 3, 2024
Merged

Split test action into two jobs #1342

merged 1 commit into from
Dec 3, 2024

Conversation

jasonaowen
Copy link
Contributor

The GitHub Action for running our tests was doing two things: checking that the tests passed, and then generating and uploading a test coverage report.

Unfortunately, our tests are somewhat slow, so running them twice in the same job takes a few minutes. Split them up so they can be run in parallel.

See also #1333 (comment) .

As with that PR, we'll need to update the branch protection rules.

@jasonaowen
Copy link
Contributor Author

The split test checks took 1m 49s for the tests, and 2m 1s for the coverage, down from 3m 0s for the combined check on #3591.

Copy link

codecov bot commented Nov 26, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 87.34%. Comparing base (0287ff1) to head (0766c3e).
Report is 2 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1342   +/-   ##
=======================================
  Coverage   87.34%   87.34%           
=======================================
  Files         185      185           
  Lines        2387     2387           
  Branches      321      321           
=======================================
  Hits         2085     2085           
  Misses        276      276           
  Partials       26       26           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Member

@slifty slifty left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for this -- I wonder if the upstream bug that forced us to run twice ever got fixed...

The GitHub Action for running our tests was doing two things: checking
that the tests passed, and then generating and uploading a test coverage
report.

Unfortunately, our tests are somewhat slow, so running them twice in the
same job takes a few minutes. Split them up so they can be run in
parallel.
@jasonaowen jasonaowen merged commit 61bb4ed into main Dec 3, 2024
7 checks passed
@jasonaowen jasonaowen deleted the split-test-coverage branch December 3, 2024 18:53
@jasonaowen
Copy link
Contributor Author

I wonder if the upstream bug that forced us to run twice ever got fixed...

I don't think I remember that; tell me more?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants