[Webkit-unassigned] [Bug 94665] Baseline optimizer should try to optimize per-port if global optimization fails

[bugzilla-daemon at webkit.org]

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





--- Comment #3 from Brady Eidson <beidson at apple.com>  2012-08-21 22:29:42 PST ---
(In reply to comment #0)
> In http://trac.webkit.org/changeset/126225 failing Mountain Lion text results were checked in to platform/mac/ which caused failures on all Chromium ports. 

I'm sorry for the failures.  The explanation is simple - I was working on a rebaselining effort believed to only affect Apple ports.

I (and others at Apple) expected that mac and mac-* were our directories that we owned.  There might be some at Apple that knew that chromium pulled from "our" directory but that knowledge has not been spread here institutionally.

Was there a point in time where chromium started pulling from the mac results, and it hadn't before?

I'm quite curious why this sharing takes place.  While I can believe - for example - that chromium-mountain-lion might differ from the generic results for some tests the exact same way mac-mountain-lion does, I instinctually suspect that chromium would have more differences than commonalities when compared to generic.

I might be completely wrong about this.

Again, apologies for the noise...  Just a warning though.  Now that we have mountain-lion bots chugging away at build.webkit.org there is going to be a concerted effort over the coming days/weeks to continue getting them greener and this type of thing is bound to happen some more.

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