Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CI: Automatic testing of native on different platforms #3392

Open
jnohlgard opened this issue Jul 14, 2015 · 17 comments
Open

CI: Automatic testing of native on different platforms #3392

jnohlgard opened this issue Jul 14, 2015 · 17 comments
Assignees
Labels
Area: CI Area: Continuous Integration of RIOT components Area: tests Area: tests and testing framework State: don't stale State: Tell state-bot to ignore this issue Type: new feature The issue requests / The PR implemements a new feature for RIOT

Comments

@jnohlgard
Copy link
Member

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)
@jnohlgard jnohlgard added Area: tests Area: tests and testing framework Feature Request Area: CI Area: Continuous Integration of RIOT components labels Jul 14, 2015
@miri64
Copy link
Member

miri64 commented Jul 14, 2015

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.

@jnohlgard
Copy link
Member Author

@authmillenon fair enough

@miri64 miri64 changed the title Strider: Automatic testing of native on different platforms CI: Automatic testing of native on different platforms Oct 17, 2016
@miri64
Copy link
Member

miri64 commented Oct 17, 2016

Renamed

@miri64
Copy link
Member

miri64 commented Oct 17, 2016

Also some relation to #5201.

@OlegHahm
Copy link
Member

@cgundogan, @smlng, @kaspar030, this is currently happening in the CI TF, right?

@smlng
Copy link
Member

smlng commented Jan 15, 2017

Yes, macOS is WIP for Jenkins see #6341, and I just created #6371 to activate native compile on Raspberry Pi ...

@kYc0o kYc0o mentioned this issue Oct 29, 2017
11 tasks
@miri64 miri64 added the Type: new feature The issue requests / The PR implemements a new feature for RIOT label Sep 30, 2018
@stale
Copy link

stale bot commented Aug 10, 2019

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 stale bot added the State: stale State: The issue / PR has no activity for >185 days label Aug 10, 2019
@miri64 miri64 added the State: don't stale State: Tell state-bot to ignore this issue label Aug 10, 2019
@stale stale bot removed the State: stale State: The issue / PR has no activity for >185 days label Aug 10, 2019
@smlng
Copy link
Member

smlng commented Sep 9, 2019

MacOS is not supported as RIOT native does not run on 64Bit CPUs (yet)

@smlng smlng closed this as completed Sep 9, 2019
@miri64
Copy link
Member

miri64 commented Sep 9, 2019

We still could consider testing on FreeBSD, as native was originally developed with support for it.

@kaspar030
Copy link
Contributor

We still could consider testing on FreeBSD, as native was originally developed with support for it.

And let's not forget armhf. There are plenty of RasPi's that could test something.

@miri64
Copy link
Member

miri64 commented Sep 9, 2019

@kaspar030's argument is to me more to the point than my (IMHO very weak) argument, so I think we should re-open.

@miri64 miri64 reopened this Sep 9, 2019
@smlng
Copy link
Member

smlng commented Sep 9, 2019

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.

@miri64
Copy link
Member

miri64 commented Sep 9, 2019

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 RIOT-OS/riotdocker#66

@smlng
Copy link
Member

smlng commented Sep 9, 2019

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?

@miri64
Copy link
Member

miri64 commented Sep 9, 2019

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.

@maribu
Copy link
Member

maribu commented Sep 16, 2022

@kaspar030 Does the pifleet also test native (that is, on Linux/ARM)?

@kaspar030
Copy link
Contributor

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: CI Area: Continuous Integration of RIOT components Area: tests Area: tests and testing framework State: don't stale State: Tell state-bot to ignore this issue Type: new feature The issue requests / The PR implemements a new feature for RIOT
Projects
None yet
Development

No branches or pull requests

8 participants