Closed gitchomik closed 4 years ago
their are no CI servers set up for the arm build so might have regressed. Also the arm port is not complete . But it should be building. @benpye will surely know and help u .
Are you sure ? http://dotnet-ci.cloudapp.net/job/dotnet_coreclr_arm_linux_debug/
Still in progress, but who knows, maybe soon ... https://github.com/dotnet/dotnet-ci/issues/49
That is probably a test build that @mmitche was trying, to setup the CI server . And yes i am 200 % sure.
OK, probably you are right, but I just make this issue because rev. d5d41105716703845d61a6f8c26724381b959c7d even not start, for example rev. c3efa1e9cc7953e50496d494de0cd0e2a1cc337f is starting to build something, that it is difference.
@mmitche got into some other issues too when he was trying to setup the CI server. If you can fix these issues it will be great. as the arm port is all until now a community effort. And you did the right thing to create the issue :smile:
Yeah I added that yesterday. I still need to formalize the rootfs on the machines (I got it working in a local test). That will happen today and then it should start passing as part of the outerloop testing when the strike fix goes in (which I think a couple community members were just about to fix)
Yep, though it's currently broken. I think that's a different issue though
file : /coreclr/src/ToolBox/SOS/Strike/CMakeLists.txt revis issue : d5d41105716703845d61a6f8c26724381b959c7d lines : 79-82