Skip to content
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

Actions fail when running on self hosted github runner #102

Open
ToyVo opened this issue Nov 1, 2024 · 1 comment
Open

Actions fail when running on self hosted github runner #102

ToyVo opened this issue Nov 1, 2024 · 1 comment

Comments

@ToyVo
Copy link

ToyVo commented Nov 1, 2024

I have been maintaining a package called nh_darwin, a fork of nh with support for nix-darwin.
I have recently had an issue where a user was requesting a binary cache and helped write the build.yml file for github actions. Importantly I was using self hosed github runners as I own some mac minis for server purposes and it was a good fit to not have to pay 10x a linux runner.

Preamble out of the way, that single build.yml works for my self hosted runners and the github hosted runners equally well. But now I would like to export nh_darwin within my nur-packages I'm trying to setup.

aarch64-darwin: https://github.com/ToyVo/nur-packages/actions/runs/11632820895/job/32396712104
aarch64-linux: https://github.com/ToyVo/nur-packages/actions/runs/11632820894/job/32396712101
x86_64-darwin: https://github.com/ToyVo/nur-packages/actions/runs/11632820896/job/32396712063

basically, it seems like building for a specific nixpkgs ref in the matrix doesn't work on self hosted runners due to the restrict-eval setting.

Now obviously I could just build with nixpkgs-unstable from the flake, but I would like to get it building with all three refs with a single build script.

Removing restrict-eval doesn't fix it: https://github.com/ToyVo/nur-packages/actions/runs/11633280382/job/32398109279

It almost seems like I cannot set the nixpkgs ref on self hosted runners.

@Mic92
Copy link
Member

Mic92 commented Nov 2, 2024

Interestingly the nix-instantiate command can resolve nixpkgs fine though.

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