An open-source nuclear reactor analysis automation framework that helps design teams increase efficiency and quality
212
stars
82
forks
source link
How many parallel processes should tests have on GitHub Actions? #1740
Open
john-science opened 1 week ago
Right now, when we run ARMI unit tests on GitHub Actions, we do four parallel processes:
https://github.com/terrapower/armi/blob/de4eeeec280abf155f19cd709a5f32b9f899fef0/.github/workflows/unittests.yaml#L32
https://github.com/terrapower/armi/blob/de4eeeec280abf155f19cd709a5f32b9f899fef0/.github/workflows/wintests.yaml#L27
https://github.com/terrapower/armi/blob/de4eeeec280abf155f19cd709a5f32b9f899fef0/.github/workflows/coverage.yaml#L33
But is "4" the optimum number, to make the tests run as fast as possible?
We should try various other numbers, to see if we can run these tests faster.