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 broken due to esp-idf tool 'ninja' extracted as non-executable #485

Open
elipsitz opened this issue Sep 26, 2024 · 2 comments
Open

CI broken due to esp-idf tool 'ninja' extracted as non-executable #485

elipsitz opened this issue Sep 26, 2024 · 2 comments

Comments

@elipsitz
Copy link
Contributor

Following up from here: #479 (comment)

It seems that CI is now broken after a tools update. Manually running the workflow and inspecting the VM, I see that ninja --version fails to run because ninja (the extracted executable) does not have +x permissions.

I suspect this has something to do with changing ninja from a .tar.gz source to a .zip source. Perhaps .tar.gz preserves executable bits, and .zip doesn't.

Here's the relevant bit of esp-idf that extracts zip files:

Here's someone complaining about this issue: https://stackoverflow.com/questions/39296101/python-zipfile-removes-execute-permissions-from-binaries

So this seems to be something that needs to be fixed upstream in esp-idf. Based on tools.json, Ninja is the only tool that uses .zip files on platforms other than Windows.

@elipsitz
Copy link
Contributor Author

Ah -- it seems someone noticed and fixed this in esp-idf, but the fix is only in esp-idf v5.2: espressif/esp-idf@562bb67

@elipsitz
Copy link
Contributor Author

I put up a PR against esp-idf to backport this fix: espressif/esp-idf#14633

But perhaps this project should update CI to use v5.2?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Todo
Development

No branches or pull requests

1 participant