testfarm
hi folks, Slavo asked me to publish my test scripts, so here they're :) You probably need to fix some pathnames. Ah, and a copy of the repo has to be in __repo.git ... cu -- -- Enrico Weigelt, metux IT service -- http://www.metux.de/ cellphone: +49 174 7066481 email: i...@metux.de skype: nekrad666 -- Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme -- testfarm.tar.bz2 Description: Binary data ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: testfarm
Hi! On Mon, 2009-12-14 at 12:34 +0100, Enrico Weigelt wrote: Slavo asked me to publish my test scripts, so here they're :) You probably need to fix some pathnames. Ah, and a copy of the repo has to be in __repo.git ... This looks interesting. Am I correct that this is only a framework for build tests for different combinations of build options (builds / doesn't build) and doesn't have anything to do with functional tests (e.g. works / doesn't work)? Did you consider any other ready made open source testing frameworks for this? As you might already know, I'm building nightlies for all currently supported RH distros (with the exception of EL3) for almost half a year. This has proved to be of great help, but now that I spared some money for new hardware I might consider doing the same for Debian / Ubuntu and running some kind of functional / build testsuite on a daily basis with the results published on the web / mailed to the list in case of failures. It would be nice if we could introduce some officially supported testing framework in /contrib to check for most prominent bugs / general build options coverage etc. I need help though. Keeping this stuff running is already time-consuming enough, so I won't be able to develop tests and keep them up to date. -- Sincerely yours, Yury V. Zaytsev ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: testfarm
Yury V. Zaytsev wrote: Hi! On Mon, 2009-12-14 at 12:34 +0100, Enrico Weigelt wrote: Slavo asked me to publish my test scripts, so here they're :) You probably need to fix some pathnames. Ah, and a copy of the repo has to be in __repo.git ... This looks interesting. Am I correct that this is only a framework for build tests for different combinations of build options (builds / doesn't build) and doesn't have anything to do with functional tests (e.g. works / doesn't work)? Did you consider any other ready made open source testing frameworks for this? As you might already know, I'm building nightlies for all currently supported RH distros (with the exception of EL3) for almost half a year. This has proved to be of great help, but now that I spared some money for new hardware I might consider doing the same for Debian / Ubuntu and running some kind of functional / build testsuite on a daily basis with the results published on the web / mailed to the list in case of failures. It would be nice if we could introduce some officially supported testing framework in /contrib to check for most prominent bugs / general build options coverage etc. I need help though. Keeping this stuff running is already time-consuming enough, so I won't be able to develop tests and keep them up to date. Hello, just for your info, I quite regularly build the newest mc master on ubuntu. Not that I test every feature... Best regards Gergely ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Background jobs: Running only one at a time
Hi, I wrote a (hugly) patch for 4.7.0-pre3 which makes mc background jobs running only one at a time. I'm not a C programmer and the feature only does what I wrote above, but I needed the functionality and now it is. :) I don't know if you already planned to implement that, but if I can help you, I'll be happy. Dany :) ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
