On 2014-02-18 09:15, Christopher Armstrong wrote:
> This change was recently merged: > > https://review.openstack.org/#/c/69133/ [1] > > Unfortunately it didn't enable lazy translations for the unit tests, so it > didn't catch the many places in Heat that won't work when lazy translations > are enabled. Notably there are a lot of cases where the code adds the result > of a call to _() with another string, and Message objects (which are returned > from _ when lazy translations are enabled) can't be added, resulting in an > exception being raised. > > I think the best course of action would be to revert this change, and then > reintroduce it along with patches to fix all the problems, while enabling it > for the unit tests so bugs won't be reintroduced in the future. Agreed. That behavior was intentional because we shouldn't be adding translated strings that way, but obviously it needs to be fixed before lazy translation is enabled. :-) > Interestingly it also didn't fail any of the tempest tests, I'm not sure why. That is kind of concerning. I see that the error does show up in the logs a couple of times though: http://logs.openstack.org/33/69133/5/gate/gate-tempest-dsvm-full/d6aa1bd/logs/screen-h-api.txt.gz#_2014-02-17_17_38_25_521 Maybe this is something that would need the new error message test enabled to be caught? > -- > > IRC: radix Christopher Armstrong > > _______________________________________________ > OpenStack-dev mailing list > [email protected]http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > [2] Links: ------ [1] https://review.openstack.org/#/c/69133/ [2] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
