Brief summary
Backend websocket connection getting closed with code: 1006 with 2.2.0-with-browser build. UI tests for same application works good with previous release 1.3.0-with-browser.
state=CLOSED msgs=0 event={'ev': 'error', 'at': 9} event={'ev': 'close', 'at': 10, 'code': 1006, 'reason': ''} CLOSED msgs=0 error@9-70ms → close@9-71ms code=1006 reason=“” console: matched=2 seen=54 → [“[error] Socket disconnected.”, …]
k6 version
2.2.0-with-browser
OS
Linux - k8s pod in AWS EKS
Docker version and image (if applicable)
2.2.0-with-browser
Steps to reproduce the problem
Use k6 build - 2.2.0-with-browser to test web application with backend websocket service.
Deploy in AWS EKS with linux node pool.
Expected behaviour
websocket connection should not get closed.
Actual behaviour
Getting code 1006, websocket connection getting closed.
Brief summary
Backend websocket connection getting closed with code: 1006 with
2.2.0-with-browserbuild. UI tests for same application works good with previous release 1.3.0-with-browser.state=CLOSED msgs=0 event={'ev': 'error', 'at': 9} event={'ev': 'close', 'at': 10, 'code': 1006, 'reason': ''} CLOSED msgs=0 error@9-70ms → close@9-71ms code=1006 reason=“” console: matched=2 seen=54 → [“[error] Socket disconnected.”, …]k6 version
2.2.0-with-browser
OS
Linux - k8s pod in AWS EKS
Docker version and image (if applicable)
2.2.0-with-browser
Steps to reproduce the problem
Use k6 build - 2.2.0-with-browser to test web application with backend websocket service.
Deploy in AWS EKS with linux node pool.
Expected behaviour
websocket connection should not get closed.
Actual behaviour
Getting code 1006, websocket connection getting closed.