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

ci: Build action has been consistently failing macos-arm64-build #137

Closed
ginglis13 opened this issue Aug 4, 2023 · 2 comments
Closed

ci: Build action has been consistently failing macos-arm64-build #137

ginglis13 opened this issue Aug 4, 2023 · 2 comments

Comments

@ginglis13
Copy link
Contributor

ginglis13 commented Aug 4, 2023

The Build action has been consistently failing for the last month: https://github.com/runfinch/finch-core/actions/workflows/release.yaml

The log lines in step Make and release deps before timeout have been:

if [ "Darwin" != "Linux" -a ! -e "/opt/homebrew/bin/nerdctl" ]; then ln -sf nerdctl.lima "/opt/homebrew/bin/nerdctl"; fi
if [ "Darwin" != "Linux" -a ! -e "/opt/homebrew/bin/apptainer" ]; then ln -sf apptainer.lima "/opt/homebrew/bin/apptainer"; fi
sudo may prompt for password to run FileMonitor
Error: The operation was canceled. # <-- timeout, cancelled workflow

This message is coming from

print "sudo may prompt for password to run FileMonitor\n";

Still looking to verify but the smoking gun is that the script is hanging on a prompt for password.

e: On my machine macOS Ventura 13.4 M1 chip:

./bin/lima-and-qemu.pl                                            
ls: /opt/homebrew/bin/limactl: No such file or directory
Missing argument in sprintf at ./bin/lima-and-qemu.pl line 213.
sudo may prompt for password to run FileMonitor
Password:
@vsiravar
Copy link
Contributor

vsiravar commented Aug 4, 2023

GitHub runners use passwordless sudo. However runners provisioned via finch infra don't allow passwordless sudo.

@ginglis13
Copy link
Contributor Author

@vsiravar thanks, moving this over to runfinch/infrastructure#367 for tracking since this appears to be an issue w/ the ASG/instances

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