Hello, On Mon, Apr 14, 2014 at 7:44 PM, Stefan Schmidt <[email protected]> wrote: > On Sun, 2014-04-13 at 12:53, Tom Hacohen wrote: >> 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. > > Eveything we don't run regulary will bitrot. E.g. I just tried to run > make examples in efl triggered due to T1161 and I get a different > error with missing evas_table.eo.legacy.h which basically means we > will ahve at leats two problem in make examples right now. > > This should be no blame but showing that everything that gets not run > at least a day will bitrot. > > If you think the debug paths are not worth to run them we should go > ahead and remove them instead of having code nobody uses.
I fully agree with you here. If a code path is not to be tested for whatever reason, it is going to bitrot. The point of this bot is to make sure that most of our code don't bitrot. Especially if debug build is completely useless by now, I do thing that should be fixed instead of working around. -- Cedric BAIL ------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/NeoTech _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
