I'm trying to build Chrome this morning and v8_mksnapshot.exe is crashing?
This is a clean build.
Thoughts?
-eric
--~--~-~--~~~---~--~~
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
Unhandled exception at 0x004413be in v8_mksnapshot.exe: 0xC005:
Access violation reading location 0x2522e72c.
v8_mksnapshot.exe!v8::internal::Invoke(bool construct=true,
v8::internal::Handlev8::internal::JSFunction func={...},
v8::internal::Handlev8::internal::Object
Do we plan to live on the edge of the wave once we're entirely unforked, and
never do merges again?
- Pam
On Fri, Feb 20, 2009 at 11:01 AM, Darin Fisher da...@chromium.org wrote:
This sounds good to me as a temporary measure while we are still doing
merges.
We are supposed to be unforked by
Seems to me that the ideal situation down the road would be a buildbot that
lives on tip of tree webkit.org, runs all the tests and every green build
auto-updates the webkit revision we pull.
Even in that case, we will have *at least* a couple build breakages a day
from new tests that we don't
-chromium-reviews, +chromium-dev
Not really sure. It seems to me that we need to send patches upstream to
make InspectorController not depend directly on JSC. It doesn't seem like it
should need to interact so directly with JSC. It's a non-trivial amount of
work. Is there another way we could
Yes. We will have a stable API (a real WebKit layer) that lives in
svn.webkit.org. That will enable us to point the chromium source at either
a stable version of WebKit or the latest tip-of-tree WebKit. The set of
developers who work on WebKit will live on tip-of-tree and ensure that it is
Realistically though, the point at which we have a stable api is at least
another quarter out, right?
So, there are two proposals on the table:
1. From now on, defer any non-security/crash tests we've never passed (i.e.
new tests from webkit merges that fail)
2. Same as proposal 1, except we also
No, I'm working on it now. We need stable APIs ASAP so that we can do the
stable and tip-of-tree separation before we have finished unforking.
We should be able to have a stable third_party/WebKit and a close to
tip-of-tree third_party/WebKit. That will help us do releases in the short
term.
I actually didn't mean to start this conversation. Is there still time
to run away and hide? :)
On a (slightly) more serious note, I agree with your assessment and I
thought at first that there was some work being done on that.
:DG
On Fri, Feb 20, 2009 at 12:25 PM, Ojan Vafai o...@chromium.org
11k directories for me on that path. Awesome find.
ProjectSection(WebsiteProperties) = preProject
Can't we just delete this section? or would VS put it back? if so
maybe we can put some
nonsense there so VS does not re-create it.
On Feb 19, 3:47 pm, Finnur Thorarinsson fin...@chromium.org
10 matches
Mail list logo
