-
-
Notifications
You must be signed in to change notification settings - Fork 810
WIP: fix fuse tests hanging #6196
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
WIP: fix fuse tests hanging #6196
Conversation
| sudo tccutil --service kTCCServiceSystemPolicyAllFiles --insert /bin/sh | ||
| sudo tccutil --enable /bin/sh |
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.
doesn't work, likely SIP is enabled.
|
@m3nu any idea how to get test_fuse not hanging forever? |
|
Installing and running FUSE in an automated way is ambitious. Doesn't it need confirmation of the module in the Security Preferences? If so, there is probably a notification popup blocking somewhere. I can check for that by taking screenshots while Github Actions is running, but may not have a solution for the actual error. Similar to doing things with the Keychain. One needs to be very very careful to avoid triggering a confirmation message. |
|
Will try this today. We shouldn't disable SIP or any other feature. |
|
Here where it gets stuck. The workarounds in the script are being blocked. Looking at other options to install this headless. (added debug code here m3nu@3a290ea) |
|
Looked into this a bit more (macfuse/macfuse#828 (comment)) and don't think we should spend time to override a security feature here. Better to mock the MacFUSE parts and focus on the code Borg runs. |
|
Only alternative I see is Vagrant or something local, which allows disabling SIP. |
|
@m3nu thanks for investigating! ok, so according to your results / advice, we'll have:
So I am closing this PR, won't work like this. |
|
well, github is deprecating macOS 10 based testing. today a test failed with a note telling so. so guess we have the same problem again on github as we are now forced to move to macOS 11 or 12. |

No description provided.