CMake Error: file failed to open for reading (Permission denied) in extensions.cmake when running Twister in CI/CD pipeline #93903
Replies: 3 comments 1 reply
-
Hi Team, Just following up on the issue reported regarding the CMake permission error encountered while running Zephyr's Twister test framework in our Windows-based CI/CD pipeline. As a quick recap: Zephyr Version: 3.6 Thanks again for your support! Best regards, |
Beta Was this translation helpful? Give feedback.
-
Hi Zephyr Team, I hope this message finds you well. I wanted to follow up on my discussion posted last week regarding a CMake permission error we're experiencing with Twister in our Windows CI/CD environment. Quick Summary: Issue: CMake Error at zephyr/cmake/modules/extensions.cmake:1080 - file failed to open for reading (Permission denied) This issue is blocking our automated testing pipeline, and any guidance on Windows-specific configurations or potential workarounds would be greatly appreciated. I understand the community is busy, but if anyone has encountered similar permission issues with Twister on Windows or has suggestions for troubleshooting, I'd be very grateful for your insights. Thank you for your time and continued support of the Zephyr project! Best regards, |
Beta Was this translation helpful? Give feedback.
-
The first thing that comes to my mind is that the file paths becoming too long for Windows to properly handle. I suggest you to check the |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Problem
I'm encountering a CMake permission error when running Zephyr's Twister test framework in my CI/CD pipeline. The test execution fails with the following error:
CMake Error at zephyr/cmake/modules/extensions.cmake:1080 (file):
file failed to open for reading (Permission denied):
Environment
OS: Windows (CI/CD Runner)
Zephyr Version: 3.6
Twister Command: python zephyr/scripts/twister --device-testing --hardware-map "map.yml" -T app/examples -e build -O app/twister-out -c -vv
Expected Behavior
Twister should successfully build and run tests in the CI/CD pipeline without permission errors.
Support Required:
What configuration or workaround is required to resolve the windows permission issues with Twister in CI/CD
Thanks in advance for your support!
Beta Was this translation helpful? Give feedback.
All reactions