The UT-1.1.0-mysql-5.1.37 CI job appears to be setup weird. The job is not aware of the various rice modules and it also does not give a detailed test report after the build is complete. When you compare the hudson configuration of that job versus other jobs like UT-1.0.3-mysql or UT-1.1.0-oracle you'll see that they are quite a bit different. Specifically is looks the the UT-1.0.3-mysql job understands that it is building a multi-module maven project and has extra options as a result. The UT-1.1.0-mysql-5.1.37 job does not have these options.
Jeremy suggested deleting the job and creating a new one configured like the rice 1.0.3 jobs.