-
Notifications
You must be signed in to change notification settings - Fork 35
Improve and document act support #225
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
base: master
Are you sure you want to change the base?
Conversation
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers. ReviewsSee the guideline for information on the review process. |
I'm still testing whether It works. Thanks to the cache it runs a lot faster the second time. Output is a bit verbose and there's no summary. |
Nice changes. They seem very useful. It seems like they could be especially useful for testing non-nix jobs like openbsd locally, though not sure if that requires KVM support. Am a little curious why you needed this to run the sanitize job. Was it a macos issue? I regularly use the steps in the readme to run CI scripts locally on my machine without needing any containers (e.g. |
It's been a while, but last time I tried I couldn't get the nix based CI jobs to run on my Mac. Still doesn't work, e.g. for master @ a4f9296:
https://gist.github.com/Sjors/bda49b5576a668493575081b3abb11a9 M4 Apple Silicon macOS 26.0.1 |
It should be possible to do so, see https://github.com/maflcko/libmultiprocess/actions/runs/17243581016/job/48927248082 / e8dc12d. |
Facilitate using act with Docker / Podman as an alternative for using nix directly.
I found this very useful for testing the sanitizer job against individual commits in #222. That is, once I finally got it to work...
This disables
sandbox
andfilter-syscalls
(but not in the CI environment), which seems fine given that anyone building this code on their own machine has to trust it anyway.