Summary: | REGRESSION(r58283): "Appears to have broken every build." (Requested by eseidel on #webkit). | ||
---|---|---|---|
Product: | WebKit | Reporter: | WebKit Review Bot <webkit.review.bot> |
Component: | New Bugs | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED FIXED | ||
Severity: | Normal | CC: | abarth, barraclough, eric, oliver |
Priority: | P2 | ||
Version: | 528+ (Nightly build) | ||
Hardware: | Other | ||
OS: | OS X 10.5 | ||
Bug Depends on: | |||
Bug Blocks: | 38163 |
Description
WebKit Review Bot
2010-04-26 21:13:21 PDT
why the hell is there a bug for build breakage? (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. 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. (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. > 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.
(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 > 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.
|