-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Fix web-dashboard output conflict #4826
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
Conversation
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.
@inancgumus can you add a unit test for it, please?
As we stop supporting a use case, we should probably add a warning in the case a duplicate is intercepted.
I've marked as breaking change for now, but we will discuss internally if this is really the case or not as we never documented it before.
5e9470e
to
00d10b0
Compare
Running: K6_WEB_DASHBOARD=true k6 run --out web-dashboard script.js Results: listen tcp :port: bind: address already in use
00d10b0
to
42da59e
Compare
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, we decided to not mark as a breaking change as this was an undefined case.
Superseeded by #4193. |
What?
Fix web-dashboard output conflict.
Why?
Running:
Results:
Also see #4707.
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)
Closes #4707