It looks like the tests are expecting ForgeActivity to be installed. Try running ./update.sh first, then run the tests again.
Tim Sent from my iPhone On May 20, 2013, at 4:58 AM, Edit Mera <[email protected]> wrote: > Yes, it is strange the number of failures > number of tests for the > ForgeTracker tool. For other tools this does not happen. > So my question is: do I have to do anything else besides what is described > here http://sourceforge.net/p/allura/git/ci/master/tree/README.markdown to > make the existing tests pass (for Allura and other Allura tools which come > with it) ? > Did I run the tests correctly: "ALLURA_VALIDATION=none ./run_tests" for > Allura > and "python setup.py nosetests" for ForgeTracker/ForgeWiki tools? > > > > > On Fri, May 17, 2013 at 9:30 PM, Olemis Lang <[email protected]> wrote: > >> On 5/17/13, Olemis Lang <[email protected]> wrote: >>> On 5/17/13, Edit Mera <[email protected]> wrote: >>>> Hi, >>> >>> :) >>> >>> [...] >>>> >>>> ---------------------------------------------------------------------- >>>> Ran 105 tests in 34.943s >>>> >>>> FAILED (errors=108) >>>> >>>> What could be the problem? How can I make these tests pass? >>> >>> That's lokking something weird . Test failures > Total tests ? Is it a >>> big in unittest module ? >> >> big => bug ... sorry ... >> :-$ >> >> -- >> Regards, >> >> Olemis. >> >> Apache™ Bloodhound contributor >> http://issues.apache.org/bloodhound >> >> Blog ES: http://simelo-es.blogspot.com/ >> Blog EN: http://simelo-en.blogspot.com/ >> >> Featured article: >>
