Re: Testing packages with mock and Xnest?
On Fri, Apr 20, 2012 at 12:15:45PM -0500, Richard Shaw wrote: Here's the draft: https://fedoraproject.org/wiki/Packaging/Testing Comments/additions welcomed! Cool. Ive read the draft now. I thought it was going to be about using Xnest with graphical unittests. Oops. Doesn't 100% fit in the Packaging Guidelines but perhaps we can link to it when we mention that reviewers should test that a package functions as intended. /me notices that although that instruction is in the ReviewGuidelines we dont seem to have it on the main Guidelines page. -Toshio pgpABxr9YaOvX.pgp Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Testing packages with mock and Xnest?
On Wed, Apr 25, 2012 at 10:46 AM, Toshio Kuratomi a.bad...@gmail.com wrote: On Fri, Apr 20, 2012 at 12:15:45PM -0500, Richard Shaw wrote: Here's the draft: https://fedoraproject.org/wiki/Packaging/Testing Comments/additions welcomed! Cool. Ive read the draft now. I thought it was going to be about using Xnest with graphical unittests. Oops. Doesn't 100% fit in the Packaging Guidelines but perhaps we can link to it when we mention that reviewers should test that a package functions as intended. Hmm... I think that would be quite a bit more complicated. I don't think Xnest would be the right tool for that. I really don't know enough about X to guess. I would think that the build server probably runs without X and even if it could run some sort of headless X just for testing purposes we probably would have to make sure that each package building in parallel that needed this feature (however unlikely) ran on a different display. What's the limit on the number of displays anyway? The main reason I include it under the Packaging Guidelines umbrella is that I use it to run rpmlint on installed packages, especially libraries, where you can find additional problems that rpmlint can't detect from checking the RPMs. I'm not saying we should make it a requirement, but perhaps strongly recommended would be a good idea. /me notices that although that instruction is in the ReviewGuidelines we dont seem to have it on the main Guidelines page. I assume you're talking about? http://fedoraproject.org/wiki/Packaging/Guidelines#rpmlint Thanks, Richard -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Testing packages with mock and Xnest?
On Wed, 2012-04-25 at 14:39 -0500, Richard Shaw wrote: Hmm... I think that would be quite a bit more complicated. I don't think Xnest would be the right tool for that. I really don't know enough about X to guess. I would think that the build server probably runs without X and even if it could run some sort of headless X just for testing purposes we probably would have to make sure that each package building in parallel that needed this feature (however unlikely) ran on a different display. What's the limit on the number of displays anyway? Something on the order of 65536 - 6000. There's a -displayfd feature in our X (and soon in upstream's) to do the much more sensible thing of simply _picking_ an unused display number and handing it back to the launching process, rather than the launcher needing to guess one that's unused. But in any event Xnest would not be suitable for this environment, because Xnest needs another server to display on. Xvfb would work for fully-automated things though. - ajax signature.asc Description: This is a digitally signed message part -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Testing packages with mock and Xnest?
I've occasionally wanted to test a packages built for another release of Fedora and didn't really care to setup a bare metal or VM to do it. I've found I can use mock (or probably any other chroot program/helper) and Xnest to do this. Is there any interest in putting this in the Fedora wiki somewhere? Am I late to the party and everyone already knows how to do this? Short example: $ mock -r fedora-rawhide-x86_64 --init $ mock -r fedora-rawhide-x86_64 --install xclock $ Xnest :1 -ac $ mock -r fedora-rawhide-x86_64 --shell [mock] $ xclock -display :1 Wah-lah! I also sometimes do this (without the Xnest part) for new library packages in order to run rpmlint against the installed package. This catches things like undefined-non-weak-symbols or something like that and a few others that it can't catch from the package alone. Thanks, Richard -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Testing packages with mock and Xnest?
On Fri, Apr 20, 2012 at 10:46 AM, Richard Shaw hobbes1...@gmail.com wrote: Is there any interest in putting this in the Fedora wiki somewhere? Am I late to the party and everyone already knows how to do this? It's a wiki. Be bold! -- Jared Smith -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Testing packages with mock and Xnest?
On Fri, Apr 20, 2012 at 11:11 AM, Jared K. Smith jsm...@fedoraproject.org wrote: On Fri, Apr 20, 2012 at 10:46 AM, Richard Shaw hobbes1...@gmail.com wrote: Is there any interest in putting this in the Fedora wiki somewhere? Am I late to the party and everyone already knows how to do this? It's a wiki. Be bold! I guess the biggest question is where to put it and where to tie it in so that it can be found. That's my biggest beef with most big wiki's. I usually just give up and google it :) Richard -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Testing packages with mock and Xnest?
On Fri, Apr 20, 2012 at 11:15:10AM -0500, Richard Shaw wrote: On Fri, Apr 20, 2012 at 11:11 AM, Jared K. Smith jsm...@fedoraproject.org wrote: On Fri, Apr 20, 2012 at 10:46 AM, Richard Shaw hobbes1...@gmail.com wrote: Is there any interest in putting this in the Fedora wiki somewhere? Am I late to the party and everyone already knows how to do this? It's a wiki. Be bold! I guess the biggest question is where to put it and where to tie it in so that it can be found. That's my biggest beef with most big wiki's. I usually just give up and google it :) Couple choices for you: http://fedoraproject.org/wiki/Packaging_tricks I could also see this going into the main guidelines somewhere under: http://fedoraproject.org/wiki/Packaging:Guidelines (Maybe a new section on testing -- or a new page if it's long enough) For the latter, Just put up a sample doc on the wiki anywhere (I use my namespace a lot: User:Toshio/New_Packaging_Draft ) and then open a ticket on https://fedorahosted.org/fpc/ to ask the FPC to review it and add it to the packaging guidelines. -Toshio pgp4zkODJsbfS.pgp Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Testing packages with mock and Xnest?
Here's the draft: https://fedoraproject.org/wiki/Packaging/Testing Comments/additions welcomed! Thanks, Richard -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
