> > Do you mean a system to test SRPM on aarch64? or a system to test a > > open source code? > > Do you mean CI testing system or an aarch64 server for adhoc test? > > I don't know why it matters, but I'm testing dynamic micro-architecture > selection added to a library I've packaged. Because there are some proper choices depending on the situation. * Test by mock command (aarch64 qemu environment). (SRPM, adhoc) https://github.com/rpm-software-management/mock/wiki/Feature-forcearch * Test by Koji (aarch64 native) (SRPM, a kind of CI) * Test by Copr (aarch64 native or qemu. I am not sure) * Test by Packit service (aarch64 native, maybe) (SRPM, CI) * Test qemu-user-static RPM and aarch64 container * on local (Source, adhoc) * with CI services (Source, CI) * Test with Travis CI with qemu (aarch64 qemu environment) (Source, CI) * Test with native aarch64 supporting CI (Source CI) * only CI: Shippable CI, Drone CI, * Works on ARM (free aarch64 server for open source) (Source, adhoc or CI) For 2nd half, below documents might be helpful for you. * https://github.com/junaruga/fedora-workshop-multiarch * https://github.com/junaruga/ci-multi-arch-test Jun _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
