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
This will be the hardest nut to crack, and basically a fantasy in my mind, but ideally you would be able to:
cross-compile for a different platform (hard)
deploy the tests to that platform (hellish)
remote the results back (hard)
One possible way to do this would be to basically take the deployment/remoting out of our own hands and require the user to figure out by just emitting binaries and some kind of manifest file. Then the user is responsible for deploying+running the binaries, which will attempt to write to some file. Then the file can be brought back to native world and fed into us for final reporting (if that output file isn't good enough).
The text was updated successfully, but these errors were encountered:
I would love for this to be possible as we've run into so many ABI mismatches between the Xtensa ports of GCC and LLVM/Rust, and it would be really cool to be able to automatically validate them against each other. Unfortunately building Linux binaries for it is a right hassle right now with GCC, and I think not really possible yet with LLVM/Clang, so being able to run the binaries manually on-device somehow would be useful here.
This will be the hardest nut to crack, and basically a fantasy in my mind, but ideally you would be able to:
One possible way to do this would be to basically take the deployment/remoting out of our own hands and require the user to figure out by just emitting binaries and some kind of manifest file. Then the user is responsible for deploying+running the binaries, which will attempt to write to some file. Then the file can be brought back to native world and fed into us for final reporting (if that output file isn't good enough).
The text was updated successfully, but these errors were encountered: