On Sat, 2009-11-21 at 12:06 -0800, Evan Martin wrote: > I'd say we break the automated Ubuntu builds every couple of weeks > (and get an additional report from users at about that same rate).
I don't mind when my automated daily builds break once in a while, but when the same error stays there for several days unnoticed by anyone else, it's a problem. Even if fixes are often trivial, downstream patches for dailies proved difficult to maintain as patches choke far too often, creating unnecessary packaging work. So i prefer to report that to the irc channel, most of the time, someone else got it first, but not always. I often get user complains like "hey, chromium is broken once again!" "what's wrong?" "i didn't get an update in a while", and a while is often just 2 or 3 days :P To avoid catching just one error per build = per day, i build with --keep-going, and if often catch 1 or 2 errors, like today (3): http://paste.ubuntu.com/324804/ (with 1 that has been there for 3 days, unfixed). If you could just make a global werror variable in gyp that could be passed via GYP_DEFINES, that would sure help. I'd like then keep -Werror for my dev distro (now lucid, future 10.04 LTS) and disable it for the other (released) distros, or let you decide based on your whitelisted compilers. /Fabien -- Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev
