38166 2010-04-26 21:13:21 -0700 REGRESSION(r58283): "Appears to have broken every build." (Requested by eseidel on #webkit). 2010-04-26 21:37:26 -0700 1 1 1 Unclassified WebKit New Bugs 528+ (Nightly build) Other OS X 10.5 RESOLVED FIXED P2 Normal --- 38163 1 webkit.review.bot webkit-unassigned abarth barraclough eric oliver oldest_to_newest 217484 0 webkit.review.bot 2010-04-26 21:13:21 -0700 http://trac.webkit.org/changeset/58283 broke the build: "Appears to have broken every build." (Requested by eseidel on #webkit). This is an automatic bug report generated by the sheriff-bot. If this bug report was created because of a flaky test, please file a bug for the flaky test (if we don't already have one on file) and dup this bug against that bug so that we can track how often these flaky tests case pain. "Only you can prevent forest fires." -- Smokey the Bear 217485 1 oliver 2010-04-26 21:14:01 -0700 why the hell is there a bug for build breakage? 217487 2 abarth 2010-04-26 21:15:12 -0700 (In reply to comment #1) > why the hell is there a bug for build breakage? Because our process to create bugs for the changes we make to the code. 217488 3 eric 2010-04-26 21:16:06 -0700 Sherriffbot was supposed to add a rollout patch to this bug, but failed to do so due to a regression earlier today. Sorry for the noise. 217489 4 oliver 2010-04-26 21:17:21 -0700 (In reply to comment #2) > (In reply to comment #1) > > why the hell is there a bug for build breakage? > > Because our process to create bugs for the changes we make to the code. Hasn't ever been required for trivial build fixes. 217491 5 abarth 2010-04-26 21:18:48 -0700 > Hasn't ever been required for trivial build fixes. Indeed. Thanks for fixing the build. We didn't see you on IRC or on bugs.webkit.org, so we weren't sure what the status of this issue was, hence we created this issue to track the problem. 217493 6 oliver 2010-04-26 21:22:01 -0700 (In reply to comment #5) > > Hasn't ever been required for trivial build fixes. > > Indeed. Thanks for fixing the build. We didn't see you on IRC or on > bugs.webkit.org, so we weren't sure what the status of this issue was, hence we > created this issue to track the problem. I am always on irc, just not in #webkit due to the ever decreasing signal/noise ratio, a pm would also have reached me, and i figured fixing the build was more important than commenting about fixing it :D 217499 7 abarth 2010-04-26 21:37:26 -0700 > I am always on irc, just not in #webkit due to the ever decreasing signal/noise > ratio, a pm would also have reached me, and i figured fixing the build was more > important than commenting about fixing it :D That's good to know for the future. There were a bunch of folks on #webkit wondering what to do about the failure, so it might be useful to let someone know you're alive and aware of the problem so we can avoid duplicating effort. In the past, we've had trouble with folks breaking the tree and disappearing, so it's good to be clear about who's going to fix failures.