On Tue, 2020-05-19 at 10:43 -0500, Richard Shaw wrote: > On Tue, May 19, 2020 at 10:31 AM Adam Williamson <adamwill@xxxxxxxxxxxxxxxxx> > wrote: > > > On Tue, 2020-05-19 at 08:49 -0500, Richard Shaw wrote: > > > I think here we need better ways of testing software in Rawhide other > > than > > > well, running Rawhide (VM or bare metal), besides the old mock chroot > > xnest > > > hack. I'm open to suggestion here. > > > > https://docs.fedoraproject.org/en-US/ci/ ? > > > > Ok, so obviously CI can be very helpful, but is part of the expectation for > all packagers to learn how to set this up? If by "set this up" you mean "what to put in place to run some specific test(s) on your package", yes. That's what the docs are for. We're currently working on implementing what we call "generic" testing in Fedora CI - that is, tests that automatically run on every package, the way Taskotron used to do it, as opposed to tests being associated with packages, the way Fedora CI initially expected - but that doesn't seem like the desire here. > It's non-trivial unless it's > something you already know how to do, and in this case we didn't know there > was a problem until an end user ran FreeCAD with the update and noticed the > crash... Well sure, but now you know it's a thing that *can* go wrong, so you want to test it in future. I'm not saying you should have done it already, just that now you know it needs testing, that's one way to go about it...though if you need to do graphical testing Fedora CI is probably not the way... -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net _______________________________________________ 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
