[Webkit-unassigned] [Bug 74776] Commit queue building & running tests on Chromium shouldn't land JSC or WK2 changes

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=74776





--- Comment #14 from Csaba Osztrogonac <ossy at webkit.org>  2013-01-10 15:17:28 PST ---
(In reply to comment #11)

> Me neither. What happened was an unfortunate and unavoidable set of actions:
> 1. Patch A lands. Breaks some build system.
> 2. Patch B is evaluated for EWS to fix build A and it's correct. Waiting to land via commit-queue.
> 3. Patch C reverts A and it's landed faster (manually or maybe commit-queue prioritization of commits if any).
> 4. Patch B lands. But without A, it makes no sense and breaks everything.
> 
> So the best thing to do (tm) is to just poke the author of patch A and ask it to fix, or just poke on the original bug, rather than creating a separate bug to fix it. I'm still missing how 4th step could be avoided by any heuristic.

The easiest way to avoid this problems is the following: Add a comment to 
the bug that you are fixing the build soon and land the fix manually not via
(sometimes slow) commit queue. Buildfixes are very important, all delay is 
pain for developers. (But I agree with rniwa, it is unrelated to this bug.)

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.