-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Ignore minIterationDuration in setup/teardown stage #1175
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1175 +/- ##
==========================================
- Coverage 73.65% 73.63% -0.03%
==========================================
Files 145 145
Lines 10603 10593 -10
==========================================
- Hits 7810 7800 -10
Misses 2334 2334
Partials 459 459
Continue to review full report at Codecov.
|
bed4bfe
to
19b4180
Compare
Close #1003 js: drop *lib.State return from runFn The state returned by runFn is never used anywhere, so drop it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, just left a small nitpick.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Beside the minor nit I commented on inline, this change LGTM. Looking at the current overall architecture in runner.go
, it definitely could be improved and probably needs to be refactored... But we can leave that task for the future, maybe when we work on #785...
minIterrationDuration
is affecting setup/teardown stages. That should not be the case, and must only affect normal iteration only.So ignore
minterationDuration
when in setup/teardown stage.Close #1003