Adding Power support(ppc64le) with ci and testing to the project for architecture independent#292
Adding Power support(ppc64le) with ci and testing to the project for architecture independent#292asellappen wants to merge 1 commit intotheskumar:masterfrom
Conversation
…architecture independent
|
Thank you for the PR but we don't use Travis CI anymore. Is there an easy way to get the package tested on a different architecture? I'm a bit skeptical with regards to the worthiness of testing everything on a different architecture. Since this is a pure-Python package, the risk of it breaking on a different architecture is quite low (although it is non-zero). That being said, if there is a cheap and simple way to get those tests to work on GitHub Actions, I'm open to considering it. |
|
@bbc2 No - there is currently no ability to use GitHub Actions to test on Linux on Power or on Linux on s390x. We do have the ability for you to get your own Linux on Power VM for free from OSU if you want to do some random/occasional testing: osuosl.org/services/powerdev/ . Feel free to list me (Gerrit Huizenga) as your IBM sponsor. For regular CI, Travis on Power is free and will continue to be so, and we are working on other CI solutions (just got TEP approved for tekton CI for containers, fyi). But GitHub Actions depends on .NET which is not an easy port to Power at the moment. On our list, though... No ETA. |
|
Are there any pieces in this project that are specific to a particular hardware platform? If not, my vote for not wasting additional Travis resources then. |
|
All right I'll close this for now. |
I am working for IBM to port cpu arch ppc64le for open sources.
This PR adds CI support for the IBM Power Little Endian (ppc64le) architecture. The idea is to ensure that the builds on this architecture are continuously tested along with the Intel builds (amd64) as this is part of the ubuntu distro
on that architecture as well and detecting (and fixing) any issues or failures early would help to ensure that we are always up to date.
This helps us simplify testing later when distributions are re-building and re-releasing,We typically build applications for customers and
ISVs, and while we don't use this package directly,we do count on all of the packages in debian/ubuntu to build other packages. So we more likely have this as a second or
third level dependency and couldn't tell you explicitly which features we use or our usage model,For more info tag @gerrith3.
Please help to verify and merge.