-
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
Pass and respect a Context
when initializing VUs
#2800
Merged
Merged
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
24cbf79
Thread a real context when initializing new VUs
na-- d459657
Simplify the js/Bundle.instantiate() API
na-- 7b70cf1
Interrupt the JS runtime during VU init if the context was cancelled
na-- e7a1cc3
Ensure all VUs are gracefully aborted when an init error occurs
na-- 384bf5c
Simplify and improve mid-test abort mechanisms for integration tests
na-- 0a2defd
Add a test to check Ctrl+C interruption during the VU init phase
na-- a7ad53f
Improve code and comments from PR suggestions
na-- File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
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.
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.
This function is only called from
TestAbortedByUserWithRestAPI
, and just wraps another helper function. So I would inline theasyncWaitForStdoutAndRun()
call, and remove this.asyncWaitForStdoutAndRun()
is also called with the same arguments, except for the callback func. So I would drop the unneded arguments, and add them once they're needed.In general, abstractions add a layer of indirection that complicates code comprehension, so I wouldn't use them so liberally, and would prefer even some duplication between tests. Or, if tests really are similar, turn them into table tests and avoid the helper functions.
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.
I agree and I was about to fix this, but I think the "fix" here is to just add more tests that abort the test run via the k6 REST API 😅 See #2804, we need more tests about this behavior... 😞
In #2815 or soon after it, we should be able to nicely abort the test with the REST even during VU init or
setup()
, so I'd prefer to keep this helper method here and add more tests that use it in that PR.