Split Scheduler.Run()
into Init()
and Run()
again
#2893
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This reverts a big part of #2885 because, with all of the logic in
Run()
, k6 didn't know if it needed to wait when--linger
was specified.In general, if a script error or
test.abort()
occurs during init,--linger
should not apply and k6 should exit immediately. But iftest.abort()
is called during the test run itself, or the test was stopped in some other way besidesCtrl+C
(e.g. REST API, thresholds withabortOnFail
),--linger
means that k6 should not exit immediately after stopping the test.This PR is on top of #2815, which we should later merge in
master
. #2804 is a somewhat related issue, where I'll also document this somewhat hidden and implicit requirements.