I working on parallel at the moment, which should help if we can get it to work. We could certainly setup nightly, but I don't really think that is great, b/c these really are mainstream tests. I suspect most of our overhead is simply due to running map reduce jobs.
On Dec 8, 2011, at 8:42 AM, Sebastian Schelter wrote: > 4. and 5. already run on toy data. > > I have some rather excessive 'integration'-like tests that execute > Hadoop in a local JVM. The tests take very long but are also very > helpful in finding subtle bugs. > > Maybe there is a way to execute these tests only once a day or so? > > --sebastian > > On 08.12.2011 14:36, Grant Ingersoll wrote: >> MAHOUT-916 and 917 are attempts to address the running time of our tests. >> As Sean rightfully pointed out, there are probably opportunities to simply >> cut down the sizes of some of these tests w/o effecting there correctness. >> To that end, if people can take a look at: >> https://builds.apache.org/job/Mahout-Quality/1237/testReport/junit/ >> >> You can get a sense as to which tests are taking a long time. The main >> culprits are: >> 1. Vectorizer >> 2. SSVD >> 3. K-Means >> 4. taste.hadoop.item >> 5. taste.hadoop.als >> 6. PFPGrowth >> >> >> -Grant >> >> -------------------------------------------- >> Grant Ingersoll >> http://www.lucidimagination.com >> >> >> >> >
