I maintain the perl-WWW-Mechanize-Chrome package, which is noarch. Currently, I have build tests disabled because there were several issues with the tests themselves, but a developer has been cleaning them up. The tests use chromium-headless, but I realized that that's not built on s390x.
AFAIK building a noarch RPM can happen on any Fedora arch, so enabling tests would fail if it gets assigned to an s390x host. Is there a way to avoid that, other than making the RPM arch and using ExclsiveArch (and then matching what the chromium SRPM sets)? The SRPM does have (when tests are enabled) BuildRequires: chromium, would that keep it from being assigned to an arch that doesn't have chromium available? There also still some issues that only seem to happen on ppc64le (but not sure how to debug that). The person working on the upstream code to fix things asked if I could give them access to a system, but they're not a Fedora packager, and I don't have such hardware. I tried an emulated VM but that had different errors during test (I guess maybe there's some race conditions that the very different environment triggers?). -- Chris Adams <[email protected]> -- _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected] Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
