You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
The text was updated successfully, but these errors were encountered:
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 becauseninja
(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.The text was updated successfully, but these errors were encountered: