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
{{ message }}
Repository navigation
Windows arm64 failing on installing certs. #143271
c:\opt\s\w\ir\cache\certs\install.ps1 : File C:\opt\s\w\ir\cache\certs\install.ps1 cannot be loaded because running
scripts is disabled on this system. For more information, see about_Execution_Policies at
https:/go.microsoft.com/fwlink/?LinkID=135170.
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.
Activity
Move Windows arm64 tests to bringup true
Move Windows arm64 tests to bringup true (#143272)
zanderso commentedon Feb 10, 2024
I moved the Windows arm64 tests to
bringup: true: #143272 cc @godofredoc @loic-sharmaloic-sharma commentedon Feb 10, 2024
Error is:
Looks like one or more Windows Arm64 machines need to be configured to allow running arbitrary PowerShell scripts. Relevant docs: https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.security/set-executionpolicy?view=powershell-7.4#examples
/cc @yusuf-goog
yusuf-goog commentedon Feb 12, 2024
We added 4 new win arm machines last week (win-17..20).
Due to differences in the windows installation, there are security policies that look to be causing these problems.
We are quarantining these bots and are looking to making the necessary policy changes in the OS.
vashworth commentedon Feb 12, 2024
#143180 was the same issue
ricardoamador commentedon Feb 12, 2024
Closing this issue in favor of #143180 where the work is being tracked.
github-actions commentedon Feb 26, 2024
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.