Sigh. Now from the right email address. On Fri, Dec 11, 2009 at 11:36 AM, Ojan Vafai <o...@google.com> wrote:
> I thought we had agreed on printing out any unexpected failures in > real-time, no? > > Also, I do think it would be worthwhile to print each directory as it > finishes. We're getting to the point where we shard all the big directories, > so the largest shard takes <90 seconds (this is true on the mac release bot > now!). So printing directories as they finish would actually give you decent > insight into what tests have been run. > > Ojan > > > On Fri, Dec 11, 2009 at 9:55 AM, Dirk Pranke <dpra...@chromium.org> wrote: > >> On Fri, Dec 11, 2009 at 12:04 AM, Dirk Pranke <dpra...@chromium.org> >> wrote: >> > The current implementation tells you that tests have failed as it >> > goes, but not which tests (of course, the webkit script doesn't tell >> > you either, apart from which directory the failure might be in). That >> > would be easy to add if there is demand. >> >> It has been pointed out to me that this paragraph is incorrect. The >> webkit scripts do give you the test filename of the failure in real >> time. For some reason I was thinking it just printed an "E" instead of >> a "." . >> >> Thinking about it now, I think I got its output confused with the >> Python and Perl unit testing frameworks ... My apologies for any >> confusion this might've caused, and for saying something without being >> sure it was right ... >> >> -- Dirk >> >> -- >> Chromium Developers mailing list: chromium-dev@googlegroups.com >> View archives, change email options, or unsubscribe: >> http://groups.google.com/group/chromium-dev >> > > -- Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev
