This is still happening. VERY annoying. ANYONE who is disabling tests, marking them flaky, etc needs to take the 30 seconds required to svn blame the file and cc people the relevant people.
On Tue, Sep 22, 2009 at 2:33 PM, Aaron Boodman <[email protected]> wrote: > > Seriously. In a project as big as Chrome, tests are *critical* and a > disabled test can hurt a team within just a few days. This has > happened to me a few times and it is terrifying to find out a test > that you think was proving you are working had actually been disabled. > > Disabling bad tests is super important, and I'm not arguing against > that. Just make sure that someone knows that it was done who can take > action on it. > > - a > > On Tue, Sep 22, 2009 at 12:40 PM, John Abd-El-Malek <[email protected]> > wrote: > > It only takes a few moments to figure out this information, and ensures > that > > the bug lands on the right person's desk. > > http://src.chromium.org/viewvc/chrome/trunk/src/ can show who wrote the > > initial test > > For commits before we moved to the open source repository, look > > at http://chrome-corpsvn.mtv/viewvc/trunk/?root=chrome (internal only) > > > > Thanks > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
