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

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Jan 10 20:37:39 PST 2013


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





--- Comment #17 from Ryosuke Niwa <rniwa at webkit.org>  2013-01-10 20:39:30 PST ---
(In reply to comment #16)
> > On the other hand, it doesn't make any sense to build & run tests on chromium-linux before landing a JSC/WK2 specific change because chromium-linux doesn't even build JSC or WK2.
> 
> I run the commit-queue on chromium-linux because that's what most convenient for me.  If you'd like to take over running the commit-queue (i.e., providing the resources and administering the machines), then you'd could run them on whatever platform you like.

That's not the problem I'm trying to solve. The problem is that the current system gives an illusion of JSC/WK2 specific patches being tested on commit-queue because it builds and run tests.

It's akin to the problem of only cr-linux and mac EWS bots running tests. Almost every new contributor assumes that all EWS bots run tests unless otherwise told.

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



More information about the webkit-unassigned mailing list