Hi Shash. I have had a problem on my Linux system where Tomcat won't shutdown in Keel. It started early this week. I have to issue a KILL command to Tomcat to kill it. I have been debating opening a Bug Report on it, but have not had the time to actually follow or chase this issue, yet. Looks like SF is having the same problem.
If you need access to a Linux system, let me know and I will set you up with an account on my server. Its safely sandboxed, so unless I assign you trusted or root privileges, you won't have access to any secured areas. Also, I have not had the time to set anything up, but if you want to set up an automated job to download, build and test Keel on a Linux platform, let me know. I will be happy to set up the Cron entry to do this. I also don't have a problem with you setting up scripts for any routine type jobs (such as emailing reports). Webserver is also active, if you want to just make the reports available to the web. Regards, Steve -- Java/J2EE Developer/Integrator Currently "On the Road" 214-724-7741 Platform Independance Rules. Give me a stable platform, and I will give you stable code. ----- Original Message ----- From: Sasvata (Shash) Chatterjee Sent: 10/3/2003 7:42:46 AM To: [EMAIL PROTECTED] Subject: [Keelgroup] Keel nightly build on SourceForge > Mike & All, > > Attached is a snapshot of the build results from a CRON job at the > SourceForge compile farm. > I am working on setting up on both Mac and Solaris, the attached is the > Solaris output. > > You'll notice that a couple of builds failed. The builds, and the unit > tests. actually work fine (all of them) on both Solaris and Mac. The > reason the couple failed was that from a previous functional test, > Tomcat continued to run. Since Tomcat locked the server directory.and > the next build couldn't delete and create the new deployment., the build > errored out > > The functional tests wouldn't work, because the client couldn't connect > to the HTTP port. On a shared machine, 8080 was already used up. It's > easy to specify the port in Tomcat, but I have no idea how to pick a > port that is guaranteed to be free (probably, could make it much less > likely, but not absolutely guaranteed). Does anybody have any ideas? > Same for the OpenJMS port. I hope we don't have to give up running > functional tests on the compile farm. > > Also, how can we get the reports out to the keel site automatically? > From the compile farm, I can only get in and out using SSH (and scp, > sftp). So, one option might be to take the report tarball and copy it > out to the Sourceforge shell machines and place it on the Keel project > directory. Then have a cron job that uncompresses/tars the received > reports. For all the contributor-run test reports I think we could do > the same, except have those reports come in to the Keel sourceforge > account via FTP. Any ideas? > > Shash > http://keelframework.org/documentation Keelgroup mailing list [EMAIL PROTECTED] http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com
