I was distracted from this thread, but a belated thanks for your response, Niphlod. To clarify, the error I posted was from Travis CI's remote process. I have no problem running my tests locally, but in that case I can start a web2py instance normally as part of the testing process. The problem on Travis is precisely how to get web2py's libraries in the path. I can't see a way, but I'm not experienced with Travis so I was wondering whether someone else might have more experience.
By the way, Richard, I think this *is* a relevant (web2py) question for the forum because the question is whether web2py's specific architecture is compatible with a particular (common) testing tool. The answer may be 'no', but I don't think the question is off-topic. On Monday, April 13, 2015 at 3:18:56 PM UTC-4, Niphlod wrote: > > take from the lack of response that if it doesn't run on your machine, > it's not going to run on travis-ci .... > For starters, it seems that gluon is not importable.... > how do you fetch web2py's libraries and put them into the path ? > > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
