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

Ignore minIterationDuration in setup/teardown stage #1175

Merged
merged 2 commits into from
Oct 18, 2019
Merged

Conversation

cuonglm
Copy link
Contributor

@cuonglm cuonglm commented Sep 25, 2019

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

@cuonglm cuonglm changed the title js: skip minIterationDuration in setup/teardown Skip minIterationDuration in setup/teardown stage Sep 25, 2019
@cuonglm cuonglm changed the title Skip minIterationDuration in setup/teardown stage Ignore minIterationDuration in setup/teardown stage Sep 25, 2019
@codecov-io
Copy link

codecov-io commented Sep 25, 2019

Codecov Report

Merging #1175 into master will decrease coverage by 0.02%.
The diff coverage is 88.88%.

Impacted file tree graph

@@            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
Impacted Files Coverage Δ
js/runner.go 82.1% <88.88%> (ø) ⬆️
core/engine.go 92.99% <0%> (-0.94%) ⬇️
lib/options.go 92.82% <0%> (-0.22%) ⬇️
lib/types/types.go 85.88% <0%> (+1.61%) ⬆️

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 f09a8e8...0ef45e4. Read the comment docs.

@cuonglm cuonglm added this to the v0.26.0 milestone Sep 25, 2019
js/runner.go Outdated Show resolved Hide resolved
core/engine_test.go Outdated Show resolved Hide resolved
js/runner.go Outdated Show resolved Hide resolved
js/runner.go Outdated Show resolved Hide resolved
js/runner.go Show resolved Hide resolved
core/engine_test.go Outdated Show resolved Hide resolved
Close #1003

js: drop *lib.State return from runFn

The state returned by runFn is never used anywhere, so drop it.
imiric
imiric previously approved these changes Oct 1, 2019
Copy link
Contributor

@imiric imiric left a 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.

core/engine_test.go Show resolved Hide resolved
Copy link
Member

@na-- na-- left a 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...

js/runner.go Outdated Show resolved Hide resolved
@cuonglm cuonglm merged commit 56cf629 into master Oct 18, 2019
@cuonglm cuonglm deleted the fix/1003 branch October 18, 2019 06:16
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.

minIterationDuration must not apply in setup() and teardown()
6 participants