RIOT
RIOT copied to clipboard
RIOT-OS
CI: Automatic testing of native on different platforms
I would like to see automatic testing of the native platform on other systems than Debian+Linux+x86(or x86_64).
Suggestions for tests:
- FreeBSD
- OSX
- armv7a-hardfloat-linux-gnueabihf (Cortex-A* linux)
- ~~AArch64 (armv8) (64 bit ARM)~~
This is planned anyways.
- armv7a-hardfloat-linux-gnueabihf (Cortex-A* linux)
AFAIK it is possible to build native on Raspberry Pi, so this should be easy.
- AArch64 (armv8) (64 bit ARM)
We don't even have (and probably never will) support for x86_64 Linux (I'm not even sure if that would make sense currently, since all real hardware platforms we target only go up to 32bit), so why add support for this platform.
@cgundogan, @smlng, @kaspar030, this is currently happening in the CI TF, right?
Yes, macOS is WIP for Jenkins see #6341, and I just created #6371 to activate native compile on Raspberry Pi ...
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you want me to ignore this issue, please mark it with the "State: don't stale" label. Thank you for your contributions.
![stale[bot] avatar](https://avatars.githubusercontent.com/in/1724?v=4 "Published by a pub.dev verified publisher"){kind=small}
We still could consider testing on FreeBSD, as native was originally developed with support for it.
We still could consider testing on FreeBSD, as
nativewas originally developed with support for it.
And let's not forget armhf. There are plenty of RasPi's that could test something.
@kaspar030's argument is to me more to the point than my (IMHO very weak) argument, so I think we should re-open.
hmm, every time I brought this up (test on other platforms and compilers) someone told me that riot docker is the reference and we cannot test on more - at least for now. Also there is and was no movement in changing this for a long time.
hmm, every time I brought this up (test on other platforms and compilers) someone told me that riot docker is the reference and we cannot test on more - at least for now. Also there is and was no movement in changing this for a long time.
I at least disagree with that sentiment (but don't have the time or resources atm to put it in place myself). However, see https://github.com/RIOT-OS/riotdocker/issues/66
okay then we need to clarify this a bit, what would be the goal? Something like, nightlies on more platforms? I think that is possible but for every PR might be a bit out-of-scope and also above the available resources. Also MacOS is out for now.
Which platforms do we primarily want (bc ideally: all of them):
- BSD
- ARM (like Raspi, which one?)
- other Linux-Distros: CentOS, Fedora, Debian, Arch?
And then: which compiler, the one from the official repos or newest from third-party repos or even latest gcc/lvm build from scratch?
okay then we need to clarify this a bit, what would be the goal? Something like, nightlies on more platforms? I think that is possible but for every PR might be a bit out-of-scope and also above the available resources. Also MacOS is out for now.
Agreed on both points.
Which platforms do we primarily want (bc ideally: all of them):
- BSD
- ARM (like Raspi, which one?)
- other Linux-Distros: CentOS, Fedora, Debian, Arch?
as you said: Ideally all of them, however I think Raspi should have priority, then some non-apt Linux distro (given that many of us use Arch I'd say that and maybe Fedora). BSD, though it would be great to have, should have the least priority, as the current state is unclear (I think it was last tested when native was implemented).
And then: which compiler, the one from the official repos or newest from third-party repos or even latest gcc/lvm build from scratch?
Official compiler should have first priority.
@kaspar030 Does the pifleet also test
native(that is, on Linux/ARM)?
Nope, not at the moment. They're also not really equipped to compile much themselves.