Hi, On Dec 16, 2010, at 9:42 , DEGREMONT Aurelien wrote:
> Hi > > Robert Read a écrit : >> Hi Aurélien, >> >> Yes, we've noticed Hudson's support for testing is not quite what we need, >> so we're planning to use Hudson to trigger our testing system, but not >> necessarily to manage it. We'd definitely be interested in learning more >> about your experiences, though. > I do not know what you mean by triggering your testing system. But here is > what I set up. I mean that once the build is complete we will notify the test system that new build is ready to be picked up and tested. We haven't yet implemented that part of it. > Hudson has only 1 slave node dedicated to testing Lustre 2. > Hudson will launch a shell script through ssh to it. > > This script: > - retrieves Lustre source (managed by Hudson git plugin) > - compiles it. > - launches acceptance-small with several parameters. > - acceptance-small will connect to other nodes dedicated for these tests. > > acc-sm have been patched: > - to be more error resilient (does not stop at first failure) > - to generate a test report in JUNIT format. > > Hudson fetch the junit report and parse it thanks to its plugin. > Hudson can display in its interface all tests successes and failures. > > Everything goes fine as long as: > - the testsuite leaves the node in a good shape. It is difficult to have a > automatic way to put the node back. Currently, we need to manualy fix that. > - Hudson does not know about the other nodes used by acc-sm. And so can > trigger tests even if some sattelites nodes are unavailable. > > How is you do this on your side? We don't plan to use Hudson to manage our testing results as I don't think it would scale very well for all the testing we might do for each build. We're currently building a more custom results server that's similar (in spirit at least) to the kinds of tools we had at Oracle. We'll make it available once it's in presentable form. Actually, our first step was to replace the acceptance-small.sh driver script with one that has a more sensible user interface for running the standard tests. Since the test-framework.sh on master has already been changed to produce test results in yaml format, the new script collects these with the logs, and is capable of submitting them to the test results server. Currently this is being run manually, though. Automating the test execution and connecting all the pieces will be next step. cheers, robert > > > Aurélien > >> robert >> >> >> >> >> On Dec 16, 2010, at 1:22 , DEGREMONT Aurelien wrote: >> >> >>> Hi Robert, >>> >>> That's very interesting. >>> At CEA we also have a Hudson platform and I'm running acceptance-small for >>> several Lustre branches in it. Hudson is a great tool but it was not design >>> to test tools that run kernel-space that can crash your nodes or, at least, >>> put your kernel in a bad shape. I will be very interested to share Hudson >>> experience testing Lustre and see how you've configured it for your own >>> tests. >>> >>> >>> Aurélien >>> >>> Robert Read a écrit : >>> >>>> Hi, >>>> >>>> As I mentioned the other day, Whamcloud is hosting a Hudson build server >>>> and producing snapshot builds for Centos 5.x (and Ubuntu 10.4 when it >>>> works) for both 1.8.x and 2.x branches. Our intention is for this to be a >>>> resource for the Lustre community to find recent Lustre packages for >>>> variety of Linux distributions. Early next year we'll connect this to our >>>> test system so at least some of the packages can be tested, as well. >>>> >>>> We would be interested in hearing from anyone that would like to >>>> participate producing builds. Hudson is an distributed system, and it's >>>> easy to add more build nodes, even behind firewalls (some of us are >>>> running build VMs on our home machines). If you would like add another >>>> distribution or architecture we don't have yet, or even one we do have >>>> (the more the merrier), we'd be happy to work with you to do that. Please >>>> contact me if you are interested. cheers, >>>> robert >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Lustre-discuss mailing list >>>> Lustre-discuss@lists.lustre.org >>>> http://lists.lustre.org/mailman/listinfo/lustre-discuss >>>> >> >> > _______________________________________________ Lustre-discuss mailing list Lustre-discuss@lists.lustre.org http://lists.lustre.org/mailman/listinfo/lustre-discuss