Hi Chris, christopher_dearb...@dell.com (christopher_dearb...@dell.com) wrote: > I took a look at this issue, and the problem is that translation is not > working properly in the Travis test setup. > > A new migration was added that creates the default network barclamp > deployment. In that migration, I initially used > Barclamp::DEFAULT_DEPLOYMENT_NAME for the name of the deployment. I later > used the same constant to look up the default deployment. This failed in the > dev test environment because the I18n.t call was failing during the database > migration and defaulting to "default", while it was succeeding in the I18n.t > call while the unit tests were running, which caused it to try to look up a > deployment with the name "Default". This caused the lookup to fail, and > resulted in errors in the dev test environment that were identical to those > seen in Travis. To work around this problem (I think translation failing > during DB migration is probably understandable - correct me if you think > otherwise), I hard coded the Deployment name to "Default" in the DB > migration, and everything worked. > > What we are seeing in the Travis errors are exactly the opposite problem. > The network barclamp default deployment name is hard coded to "Default" in > the DB migration. When the Barclamp::DEFAULT_DEPLOYMENT_NAME constant is > used while the unit tests are running, the I18n.t translation is failing and > defaulting the name to "default". As a result, the deployment lookup by name > fails which causes the unit tests to fail.
Thanks again for spending time on this! > At any rate, I can easily fix this by not using I18n.t() to get/set the name > of the deployment, which is probably fine in this instance since the network > barclamp can have only one deployment, and its name will most likely not be > shown in the GUI as a result. But, I think we have a bigger issue here in > that translation is not working when running unit tests on Travis. > Unfortunately, I know very little about Travis or how translation is set up. I can't help with translation but don't hesitate to fire any Travis questions my way. However hopefully it should be very simple to understand because Travis isn't really doing anything significantly different from "./dev tests run". There's just a small amount of trickery to assemble all the code from the various repositories into a single unified tree which has the same structure as /tmp/crowbar-dev-test/opt/dell/crowbar_framework/ Details here in case you didn't see yet: https://github.com/crowbar/crowbar/blob/master/doc/devguide/testing/travis.md _______________________________________________ Crowbar mailing list Crowbar@dell.com https://lists.us.dell.com/mailman/listinfo/crowbar For more information: http://crowbar.github.com/
