Open RobertHenry6bev opened 1 year ago
The last time I successfully ran crank on windows arm64 was Aug 31. I haven't tried in the intervening 6 weeks.
I can run ARM64+windows+crank on another "identical" machine in our fleet. So it is looking like something is corrupted on the one server I normally use.
I have sent @LoopedBard3 out-of-band instructions on how to reproduce.
I'm no longer able to run crank +teche on my Windows ARM64 machines. I believe it had run as recently as 2.5 weeks ago. Running crank agent (with some additional logging) produces this stack trace.
I opened an issue https://github.com/dotnet/install-scripts/issues/400 in dotnet/install-scripts after I guessed, probably incorrectly, that the dotnet installation script was not reachable, due to recent changes in the server's configuration.
I do not know what the URL is of the failing request. Given the names of some of the functions on the stack, I wonder if this is somehow the dotnet compiler asking for resources, or, even worse, some underlying dynamic binary translator being run over x86_64 code on this arm64 platform.