Prevent race between Ended & Interrupted exec states #4665
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.
What?
It only marks the test as "ended" (
lib.ExecutionStatusEnded
, by callinge.state.MarkEnded()
) when it hasn't been aborted.Why?
With the current flow, in particular scenarios like the one above, the test goes through
lib.ExecutionStatusRunning
, thenlib.ExecutionStatusEnded
, and finallyExecutionStatusInterrupted
, which isn't technically correct because from an external standpoint, another process using the K6 API to check the status (e.g., k6 TC) can temporally see it as successfully finished (e.g.,lib.ExecutionStatusEnded
).This is likely the reason why integration tests have been intermittently failing for long, especially:
TestAbortTestVUDefault
TestTheErrorOnPushMetricTest
,which are aborted, and expect:
but sometimes get
cloudapi.RunStatusFinished
.Checklist
make check
) and all pass.Checklist: Documentation (only for k6 maintainers and if relevant)
Please do not merge this PR until the following items are filled out.
Related PR(s)/Issue(s)
N/A