yade-dev team mailing list archive

[Václav Šmilauer <eudoxos@xxxxxxxx>]

Ubuntu 8.04 is supported for 0.20.

No reason to use vmware or whatever, just use pbuilder
http://yade.wikia.com/wiki/DebianPackages which is made just for that.
We already run scripts/regression-tests.py from debian/rules, no need to
duplicate that by hand using fancy cronjobs.  The cron script I use for
testing is piece of crap, if you want to make something proper, don't
reinvent the wheel and tell they IT guys in grenoble to install buildbot
on some server with appropriate chroots for different distros. Besides,
I don't think it is that important to test every commit on all distros.
We do it now just for the heck of releasing something that works.

Please tell people to write tests in py/tests. It is nice to TALK about
unit tests, regression tests, QA etc all the time, but if no one DOES
it, it's not going to happen. Py/tests doesn't depend on any distro and
once it starts to fill up, it will test about any aspect of yade you
wish.

** Changed in: yade
       Status: New => Invalid

-- 
we need a testing suite for all supported distros.
https://bugs.launchpad.net/bugs/418179
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.

Status in Yet Another Dynamic Engine: Invalid

Bug description:
OK. doing a fresh install of ubuntu 9.04 just to verify some bug is a hassle. This must be automated.

First let's make a list of supported distros, I would say that we are probably aiming at:

- debian lenny
- debian squeeze
- ubuntu 9.04
- ubuntu 8.04 ???
- ubuntu 9.10 ?

Vaclav, please paste here your cronjob that is doing your automated test. That's a start.

Then we would need (ideally) a script that installs in User Mode Linux, or VirtualBox or VMWare a clean install of all of those linux distributions, downloads and compiles yade.

A partially hand solution currently possible for me is to do a clean install of all of those distributions under vmware. Then set on all of them a cronjob that inside VMware is downloading and compiling all that stuff.

Above is a no-brainer. Just click-and-wait solution.

A next step for which I need to figure out how to remotely start VMWare (I bet it is possible, because there is some VMware console that I never used) is a HOST PC cronjob that resores VMware image from just after linux distro was installed, starts VMware, then performs as usual: downloads yade inside vmware and compiles it.