You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 30, 2025. It is now read-only.
A CI pipeline failed with the following log, and it looks to be a deadlock around the WaitForFunction, and specifically waitForExecutionContext.
xk6-browser version
CI
OS
Ubuntu 20.04.5 LTS
Chrome version
Unknown
Docker version and image (if applicable)
NA
Steps to reproduce the problem
A CI pipeline failed with the following log (only the goroutine logs that are of interest have been added), and it looks to be a deadlock around the WaitForFunction, and specifically waitForExecutionContext. We had a similar issue with deadlock in the cloud, which was due to out of order CDP events which was fixed in #555. Could be something holding on executionContextMu in frame.
NOTE: The log is just the starting place to try and recreate the issue, but the root cause might be elsewhere in the system.
executionContextMu isn't needed to be locked and unlocked in this
(WaitForFunction) method as it doesn't r/w to executionContext or
documentHandle. This function later calls an unexported method with the
same name, which does require access to executionContext.
A deadlock was occurring later in waitForExecutionContext since
this method was holding on to the lock.
Closes: #635
executionContextMu isn't needed to be locked and unlocked in this
(WaitForFunction) method as it doesn't r/w to executionContext or
documentHandle. This function later calls an unexported method with the
same name, which does require access to executionContext.
A deadlock was occurring later in waitForExecutionContext since
this method was holding on to the lock.
Closes: #635
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
logs_4015.zip
Brief summary
A CI pipeline failed with the following log, and it looks to be a deadlock around the
WaitForFunction
, and specificallywaitForExecutionContext
.xk6-browser version
CI
OS
Ubuntu 20.04.5 LTS
Chrome version
Unknown
Docker version and image (if applicable)
NA
Steps to reproduce the problem
A CI pipeline failed with the following log (only the goroutine logs that are of interest have been added), and it looks to be a deadlock around the
WaitForFunction
, and specificallywaitForExecutionContext
. We had a similar issue with deadlock in the cloud, which was due to out of order CDP events which was fixed in #555. Could be something holding onexecutionContextMu
inframe
.NOTE: The log is just the starting place to try and recreate the issue, but the root cause might be elsewhere in the system.
CI action log: https://github.com/grafana/xk6-browser/actions/runs/3409862907/jobs/5672145446
Expected behaviour
The tests should pass.
Actual behaviour
Deadlock.
Related: #637
The text was updated successfully, but these errors were encountered: