Skip to content

Enabling safaridriver on macOS runners #2190

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

Closed
UebelAndre opened this issue Mar 11, 2025 · 8 comments
Closed

Enabling safaridriver on macOS runners #2190

UebelAndre opened this issue Mar 11, 2025 · 8 comments

Comments

@UebelAndre
Copy link
Contributor

UebelAndre commented Mar 11, 2025

I was trying to do this but the job just sits waiting for a password

Image

Would it be possible to enable this so I could support bazelbuild/rules_rust#3328 ?

I believe this would require an administrator to run:

safaridriver --enable
@UebelAndre
Copy link
Contributor Author

cc @meteorcloudy who I believe has been working on macos recently and might at least know how to do this.

@meteorcloudy
Copy link
Member

@fweikert is our Mac VM expert, I guess we could add safaridriver --enable to our image creation script.

@UebelAndre
Copy link
Contributor Author

Is that a change that's made in this repo?

@meteorcloudy
Copy link
Member

Nope, we have some internal scripts to build the image.

@meteorcloudy
Copy link
Member

We've updated the CI macOS VMs with this command, can you try to verify if it works now?

@UebelAndre
Copy link
Contributor Author

We've updated the CI macOS VMs with this command, can you try to verify if it works now?

I still see an error in the tests
bazelbuild/rules_rust#3354
https://buildkite.com/bazel/rules-rust-rustlang/builds/14560#0195a49b-2b69-463c-8296-3ca03587ff68

[2025-03-17T14:57:41Z DEBUG wasm_bindgen_test_runner::headless] executing "safaridriver" "--port=55523"
Failed to start driver, trying again ...
                                                  
driver status: exit status: 1
driver stderr:
    ERROR: safaridriver could not launch because it is not configured
    correctly or you need to authenticate. Re-run safaridriver(1) and
    pass the '--enable' flag to configure and/or authenticate.
    For more information, consult the safaridriver(1) man page.

@meteorcloudy
Copy link
Member

We did runsafaridriver --enable for image creation, but the ci user running on macOS doesn't have admin right, maybe that's the reason? If so, I don't think you can workaround this.

@meteorcloudy
Copy link
Member

Closing this one since I think there is no more action to take from our side.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants