Version
npmPackages:
@rstest/adapter-rspack: catalog: => 0.10.2
@rstest/core: catalog: => 0.10.2
@rstest/coverage-istanbul: catalog: => 0.10.2Details
On the local machine test seems lot faster. After sampling few CI runs, it looks like rstests's workers pool maybe underutilized - while rstest is running, cpu usage stays around ~60%, same for the memory. Only at the end of test execution memory utilization reaches around ~90%, not sure if it's worker scheduling or coverage collection triggers it.
I'm not sure if this is intended behavior or not, wanted to double confirm.
Reproduce link
Reproduce Steps
no exact repro, running ~7000 test (~500 test suites) on the CI repeatedly and seeing these behavior, ends up test execution time gets bit longer.
Version
npmPackages: @rstest/adapter-rspack: catalog: => 0.10.2 @rstest/core: catalog: => 0.10.2 @rstest/coverage-istanbul: catalog: => 0.10.2Details
On the local machine test seems lot faster. After sampling few CI runs, it looks like rstests's workers pool maybe underutilized - while rstest is running, cpu usage stays around ~60%, same for the memory. Only at the end of test execution memory utilization reaches around ~90%, not sure if it's worker scheduling or coverage collection triggers it.
I'm not sure if this is intended behavior or not, wanted to double confirm.
Reproduce link
Reproduce Steps
no exact repro, running ~7000 test (~500 test suites) on the CI repeatedly and seeing these behavior, ends up test execution time gets bit longer.