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
I have a x64 machine which I develop on, and a Raspberry Pi for testing ARM related changes. The documents for working across different machines with different architectures is very lacking (or I couldn't find them); Some I could find were just the cross building part.
When I was working on some PRs involving changes in CoreCLR, I just had to copy testhost and the JIT test binary, then run the binary using corerun; However, for library tests, it can't be done that way easily because of all the command-line arguments passed through the script and without deep understanding of where artifacts go / how things work in general it's not straightforward to make those changes. Previously I just relied on the PR validation CI runs, but this isn't always easy because the library tests don't run automatically unless there's a change in CoreCLR part of the runtime, and this means I need someone from the team to trigger the run manually. This really slows me down because my timezone doesn't match up with Redmond's, the run takes hours to finish and often I don't need to run all of the tests.
It would be nice if I could get some tips / documents regarding workflow for ARM related changes, especially with running the tests on a different machine. It would be really nice if there's a script could somehow SSH into the remote machine, send all the necessary files and run the tests or something but that's just my thought.
On an additional note, How does one use altjit to get the JIT output / dump? I couldn't seem to find much info about it, and it sounds like it would be very useful for making changes in the JIT.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I have a x64 machine which I develop on, and a Raspberry Pi for testing ARM related changes. The documents for working across different machines with different architectures is very lacking (or I couldn't find them); Some I could find were just the cross building part.
When I was working on some PRs involving changes in CoreCLR, I just had to copy
testhost
and the JIT test binary, then run the binary usingcorerun
; However, for library tests, it can't be done that way easily because of all the command-line arguments passed through the script and without deep understanding of where artifacts go / how things work in general it's not straightforward to make those changes. Previously I just relied on the PR validation CI runs, but this isn't always easy because the library tests don't run automatically unless there's a change in CoreCLR part of the runtime, and this means I need someone from the team to trigger the run manually. This really slows me down because my timezone doesn't match up with Redmond's, the run takes hours to finish and often I don't need to run all of the tests.It would be nice if I could get some tips / documents regarding workflow for ARM related changes, especially with running the tests on a different machine. It would be really nice if there's a script could somehow SSH into the remote machine, send all the necessary files and run the tests or something but that's just my thought.
On an additional note, How does one use altjit to get the JIT output / dump? I couldn't seem to find much info about it, and it sounds like it would be very useful for making changes in the JIT.
Beta Was this translation helpful? Give feedback.
All reactions