On Dec 23, 7:44 am, Graham Perrin grahamper...@gmail.com wrote:
(… I have taken care to
not confuse the two from the outset.)
Confession: before joining Chrome community I did confuse the two, at
https://bugzilla.mozilla.org/show_bug.cgi?id=135268#c77
Mozilla community helped me to
Before joining chromium-dev I found
http://dev.chromium.org/developers/design-documents/inter-process-communication
then
http://groups.google.com/group/chromium-dev/msg/c8405c87b82d5bfb
http://groups.google.com/group/chromium-dev/msg/429acaedcb75bb78
Additional background: the current topic reference refers to
http://www.google.com/support/chrome/ and that page's only reference
to
Developers
leads to http://www.google.com/support/chrome/bin/topic.py?topic=14683
and that page's reference to
Developer and webmaster support
leads to
On Tue, Dec 23, 2008 at 2:52 AM, Graham Perrin grahamper...@gmail.com wrote:
Yes, but the things are not related to processors services. Let's
shift attention to the thread on provider services :)
Perhaps if you'd describe what you're actually interested in doing, we
could give better answers.
You ask too many questions in an email; I'll answer a few.
Q: Why no #chromium-dev?
A: It's not needed anymore. chromium-dev has archives. You can search
it if you want to know the reason.
Q: Why isn't chromium-dev more discoverable?
A #1: Crowd controlling.
A #2: People that have the potential
The net_unittests started being flaky due to hitting a check in
message_pump_libevent:
[ RUN ] URLRequestTest.Post307RedirectPost
/b/pylibs/zope/__init__.py:19: UserWarning: Module zope was already
imported from /b/pylibs/zope/__init__.pyc, but
Previously on this list, we have been urged to build and use the trunk to
shake out problems. But what if you don't have or don't want to keep a
trunk build updated and running? How can you make things better as a 1.0
release branch user?
If you add --enable-dcheck to your app shortcut, you will
We haven't started upstreaming yet, so I'd say until some time, you
can work on them directly.
This of course will change when the upstreaming starts.
:DG
On Tue, Dec 23, 2008 at 2:51 PM, Adam Barth aba...@chromium.org wrote:
I see. Can I make changes to them in third_party, or should I
For now, just operate the same as you would had these files still resided in
webkit/port. Just don't forget to roll DEPS :)
We'll eventually be updating the merge tracker (
http://build.chromium.org/merge) to indicate the set of files and diffs that
have yet to be upstreamed.
-Darin
On Tue,
Whoops, forgot to cc chromium-dev, also see the reply from dkegel...
-- Forwarded message --
So the CHECK() failing means that MessagePumpLibevent::Init() is returning
false.
This could be the result of failures in:
* Creating the pipe() (line 84)
* Setting either end to
forwarding to chromium-dev...
-- Forwarded message --
From: Dan Kegel
That seems like a good guess to me.
I'm running net_unittests on the mac in a loop now
with log messages around each of the failure points.
It's been running for ten minutes without failure.
Maybe we should
11 matches
Mail list logo
