-
Notifications
You must be signed in to change notification settings - Fork 42
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
Add K6_BROWSER_EXECUTABLE_PATH in ci #962
Conversation
2e13017
to
8ff018c
Compare
e65317e
to
fa7e2a0
Compare
The github runners have both chromium and google chrome installed. Google chrome is kept up to date whereas chromium isn't. We want to work with the latest version of google chrome (for now, in the future we may want to install the exact version we want to work with). We've had issues working with chromium in the runners where the application crashes on startup.
0a455ba
to
f704402
Compare
It's not known why this example doesn't work in the github action runner. It works fine on a Windows 11 computer.
ef03811
to
e0bf96e
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.
Thanks for looking into this! LGTM.
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.
Thanks for making things better 👍
2be84e3
to
e0bf96e
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.
02bd099
to
e0bf96e
Compare
The e2e workflow for windows using the tip version of go doesn't seem to work on Windows (or at least in the ci github action). The tip is installed correctly, but when it comes to building the k6 binary using xk6, xk6 seems to always execute the stable version of the go binary and not the tip version. When running commands outside of xk6 to verify the env vars (e.g. GOROOT) it always returns the tip paths. It's unclear why this is happening. For now, we're skipping the windows e2e tip workflow.
e0bf96e
to
7d983cd
Compare
Description of changes
The main change (initially) was to work with the
K6_BROWSER_EXECUTABLE_PATH
env var on linux github actions to ensure it picks chrome and not chromium. The github runners have both chromium and google chrome installed. Google chrome is kept up to date whereas chromium isn't. We want to work with the latest version of google chrome (for now, in the future we may want to install the exact version we want to work with).I also found that the e2e workflow wasn't correctly using the defined matrix, and was only working with
ubuntu-latest
. There are several commits which attempt to resolve this.Two issues which were discovered but not resolved in the e2e workflow were:
examples/hosts.js
test script doesn't pass in the Windows stable e2e test. When tested in a Windows 11 computer, the test passed. I've opened a new issue (Fix e2e & test CI workflows #963) to track this.GOROOT
is pointing to the tip version and not the stable version that is already on the system), but even still xk6 works with the stable version of go which ends up with an error. This hasn't been tested on a standalone windows computer. I've opened a new issue (Investigate why tip e2e tests on Windows github action runner fails #1002) to track this.Closes: #963
Checklist