Fix metrics processing after test run

[na--]

This is a quick and dirty fix for #1434, though as I mention in that issue, the proper solution would be rewriting that code from scratch...

[na--]

Maaybe I should have ran the tests before pushing a PR... 🤦‍♂️

[codecov-commenter]

Codecov Report

Merging #1460 into new-schedulers will increase coverage by 0.00%.
The diff coverage is 94.11%.

@@               Coverage Diff               @@
##           new-schedulers    #1460   +/-   ##
===============================================
  Coverage           76.69%   76.70%           
===============================================
  Files                 163      163           
  Lines               12986    12996   +10     
===============================================
+ Hits                 9960     9968    +8     
- Misses               2515     2517    +2     
  Partials              511      511           

Impacted Files	Coverage Δ
cmd/run.go	9.28% <0.00%> (ø)
core/engine.go	88.73% <100.00%> (+0.53%)	⬆️
lib/executor/variable_looping_vus.go	94.46% <0.00%> (-0.80%)	⬇️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e0ddf5d...c675aa9. Read the comment docs.

[imiric]

LGTM, though there's still the minor UI issue when run with -v that the Waiting for engine processes to finish and later log lines appear after the EOT summary is printed, which is a bit unsightly, but not a big deal.

[na--]

LGTM, though there's still the minor UI issue when run with -v that the Waiting for engine processes to finish and later log lines appear after the EOT summary is printed, which is a bit unsightly, but not a big deal.

Nothing we can do about that unfortunately... These events simply occur after the end-of-test summary has been printed.