-
Notifications
You must be signed in to change notification settings - Fork 368
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
sandbox too strict on macos #4389
Comments
hannesm
added a commit
to hannesm/ca-certs
that referenced
this issue
Oct 12, 2020
hannesm
added a commit
to hannesm/ca-certs
that referenced
this issue
Oct 12, 2020
To reproduce more easily: |
I don't a have a macos to test. What is failing, network or denial access to part of the system where are stored certificates ? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The sandbox script on macos denies to properly run various commands in the test phase, as an example
security find-certificate -a -p /System/Library/Keychains/SystemRootCertificates.keychain
does not output the trust anchors as expected -- observed in https://travis-ci.org/github/ocaml/opam-repository/jobs/734785206How to reproduce: on a macos system,
opam pin -n ca-certs https://github.com/mirage/ca-certs.git#v0.1.2 && opam install -t ca-certs
. The expected result is that all tests are passing (which is the case if you executedune runtest
from the above repository). The observed result are failures since the above mentioned command executed successfully (exit status = 0), but did not produce any output.The text was updated successfully, but these errors were encountered: