Jinja Problems

[Michael Pedersen]

I've been trying to debug this particular error, but my lack of knowledge about Jinja is hindering me here.

On jenkins ( http://jenkins.turbogears.org/view/TurboGears%20Hosted/ ), we've got build failures. When checking the logs, it turns out that jinja is not finding all of the templates that it should. When I check locally, and run "python setup.py nosetests", I get the same failures.

I've tried renaming .html to .jinja for the jinja templates, but that makes the problem worse (from 3 errors to 7). Can anybody help me figure this out, so we can have this working properly for the 2.2 release in the next few weeks?

--
Michael J. Pedersen

My Online Resume: http://www.icelus.org/ -- Google+ http://plus.ly/pedersen

Google Talk: m.ped...@icelus.org -- Twitter: pedersentg

[Alessandro Molina]

Sorry, my fault.
I forgot to rename the templates in the test suite.

The strange thing is that I didn't receive any email fron jenkins
reporting the failed builds.

> --
> You received this message because you are subscribed to the Google Groups
> "TurboGears Trunk" group.
> To post to this group, send email to turbogea...@googlegroups.com.
> To unsubscribe from this group, send email to
> turbogears-tru...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/turbogears-trunk?hl=en.

[Alessandro Molina]

> On Fri, Apr 20, 2012 at 6:31 AM, Michael Pedersen <m.ped...@icelus.org> wrote:
>> Can anybody help me figure this out,
>> so we can have this working properly for the 2.2 release in the next few
>> weeks?
>>

To avoid forgetting those, we also need to upgrade some dependencies
in 2.2 to fix a few issues:
- tgext.crud & tgext.admin need to be 0.5.1 to work correctly with
jinja quickstart
- sprox must be 0.8 to work correctly with tw2
- tw2 must be the latest release to solve an issue with the middleware
preventing streamed responses

Hope I didn't forget anything

[Christoph Zwerschke]

Am 20.04.2012 10:34, schrieb Alessandro Molina:
> Sorry, my fault.
> I forgot to rename the templates in the test suite.
>
> The strange thing is that I didn't receive any email fron jenkins
> reporting the failed builds.

See the console output:

Sending e-mails to: turbogea...@googlegroups.com
ERROR: Invalid Addresses
...
Caused by: com.sun.mail.smtp.SMTPAddressFailedException: 550 5.7.1
<turbogea...@googlegroups.com>: Relay access denied

Looks like we need to configure Jenkins with a different mail server as
the current one does not replay any more.

-- Christoph

[Michael Pedersen]

I saw that the other day. Problem is that Google Groups *really* doesn't want to allow an unvalidated member to post to our group, so I was using my own email address to have jenkins send. Only now, that server has blocked that option.

I don't have answers, not yet, but I've got ideas. Will try to implement them soon.

On Fri, Apr 20, 2012 at 10:57 AM, Christoph Zwerschke <ci...@online.de> wrote:

Am 20.04.2012 10:34, schrieb Alessandro Molina:

Sorry, my fault.
I forgot to rename the templates in the test suite.

The strange thing is that I didn't receive any email fron jenkins
reporting the failed builds.

See the console output:

Sending e-mails to: turbogears-trunk@googlegroups.com
ERROR: Invalid Addresses
...
Caused by: com.sun.mail.smtp.SMTPAddressFailedException: 550 5.7.1 <turbogears-trunk@googlegroups.com>: Relay access denied

Looks like we need to configure Jenkins with a different mail server as the current one does not replay any more.

-- Christoph

--
You received this message because you are subscribed to the Google Groups "TurboGears Trunk" group.

To post to this group, send email to turbogears-trunk@googlegroups.com.
To unsubscribe from this group, send email to turbogears-trunk+unsubscribe@googlegroups.com.

For more options, visit this group at http://groups.google.com/group/turbogears-trunk?hl=en.