Re: Attn: Smoketest man!

Steve> That should work. Fine. Steve> Now I'm waiting for it to update again. Mats, how often is it Steve> supposed to update, I can't see any sequence to it... [...] Steve> One run on the 4th, one on the 9th, two on the 10th, one on the Steve> 11th. I don't understand. The idea is that after a change in CVS you would see an updated web-page in an hour (or two ;-) But the data is really confusing (because I have had problems with the automatic build.) You are entitled to an explanation. Here goes: It works like this. Once an hour the build is started if there isn't a job going on already. The build starts with a check out from CVS. If there are no new files the build stops at that point. No need to build anything if there are no new files. After the build completes the web-page is generated from the log- and tail-files. So when there is nothing new in CVS the "updated" time on the web-page will be e few minutes past. When the packages are built the "updated" time will indicate how many minutes the complete build took. So by just looking at the web-page you can normally see if the smoketest is feeling good or not. Now this is when everything goes well. As you might remember I'm having problems with the cronjob hanging. This occurs sometimes when there are build errors. Not all errors cause the job to hang and not for all xemacsen. I haven't found a good way to avoid this so at times I must manually kill hanging xemacs-processes etc. I normally try though to run the build again, this time from a shell, to generate the "real" log. This always work and there is no hanging processes when running the smoketest this way. (Actually this gave me an idea of an alternative way of running the build that would avoid the cron-job-hanging thing.) I also run the build manually at times when I change the build scripts that could cause a new build even though there are no new files in CVS. Steve> Also, Mats, what is you local time in relation to GMT? GMT+1. Server is located in Stockholm. (As of this writing I'm having the first four builds OK so I'm looking forward now to seeing the first all-six-green-builds coming up in a few minutes.) Yours -- %% Mats