Re: Smoketest fails on jde.

Ville> Yep, but building non-mule packages with non-mule isn't :) And Ville> it's good to build with 21.1.14 too. It's a matter of how you want to use the CPU-cycles. Now I build once an hour so anyone doing a check-in can get feed back within one to two hours. Building for more configurations I would have to reduce the frequency or make the build scripts smarter. Maybe fast turn around on a hourly basis and a full build for all interesting configurations once a day or week or so. Ville> Anyway, I have a setup of 21.1.14, 21.4.10 and 21.5.9 (all Ville> mule) for running the smoketests, but I haven't set up an Ville> automatic job to run the tests, mostly because I'm not sure how Ville> I would like the logs handled. I was thinking of a web page with red and green-lights. All of this assumes of course that the people checking in things in the package tree uses this web-page for feed back. (It's silly that I should cut and past things from the log to the mail-list when developers simply can find the info by them selves. Basically all is there now except that there are no fancy web-page. Just visit the latest log in your browser, wait for it to download and read the last few lines.) It would also be an easy thing to just take the tail of the log to se whether the build succeeded or not. With a better log handling we could also do a "make -k" in order to spot more than one error on each build. But we would then need some way to extract or highlight the errors since a normal log is about 3MB. Yours -- %% Mats