Hey, I figure we are doing this to get higher coverage values/more real/catch some tiny more issues, but I'm not sure it's worth it. Might be a good idea to make it sane (default, or at least info, not debug). I know, things might break without us noticing in some debug paths, but it's not worth. A better idea, would maybe, if we really want it, to have a "make debug-coverage" that can be used on the buildbot, I don't know. Though it's really annoying for clients, and they should, if they wanna test for coverage in that case, just set the env var.
Any thoughts? -- Tom. ------------------------------------------------------------------------------ Put Bad Developers to Shame Dominate Development with Jenkins Continuous Integration Continuously Automate Build, Test & Deployment Start a new project now. Try Jenkins in the cloud. http://p.sf.net/sfu/13600_Cloudbees _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
