Now I'm getting a build failure when running mvn install from the trunk.

Its regarding the FileDataModelTest. I'm getting 9 errors. All pretty much
the same format testXXX:

testItem(org.apache.mahout.cf.taste.impl.model.file.FileDataModelTest)  Time
elapsed: 0.003 sec  <<< ERROR!
java.io.IOException
    at
org.apache.mahout.cf.taste.impl.model.file.FileDataModelTest.setUp(FileDataModelTest.java:67)
    at junit.framework.TestCase.runBare(TestCase.java:128)
    at junit.framework.TestResult$1.protect(TestResult.java:106)
    at junit.framework.TestResult.runProtected(TestResult.java:124)
    at junit.framework.TestResult.run(TestResult.java:109)
    at junit.framework.TestCase.run(TestCase.java:120)
    at junit.framework.TestSuite.runTest(TestSuite.java:230)
    at junit.framework.TestSuite.run(TestSuite.java:225)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at
org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:213)
    at
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140)
    at
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:165)
    at org.apache.maven.surefire.Surefire.run(Surefire.java:107)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at
org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:289)
    at
org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1005)

Any ideas on how to fix this???

-- Matt

On Wed, Apr 22, 2009 at 12:09 AM, Sean Owen <[email protected]> wrote:

> Yes, you can call setPreference() on FileDataModel or GenericDataModel
> now. These methods have caveats -- the change is lost in FileDataModel
> once a file reloads. The operation is a little slow, and most
> importantly not really thread-safe, so you should synchronize.
>
> Calling refresh() from the Recommender updates everything -- data
> model, and, the recommender to use the new data. It will be slow for
> slope one so do it infrequently.
>
> Pass 'null' as an argument.
>
> On Wed, Apr 22, 2009 at 3:02 AM, Matthew Roberson <[email protected]>
> wrote:
> > So, with the added change, I can add new preferences for a user directly
> to
> > the GenericDataModel using setPreference() and then update the
> Recommender
> > periodically.
> >
> > Would this be done by refreshing the recommender via a call to refresh()
> > (within the Recommender class)?
> >
> > If this is the case, I am not clear as to what is passed to the refresh()
> > method, i.e. "Collection<Refreshable>"?
> >
> > -- Matt
> >
>

Reply via email to