Automatically closing tree for unit_tests on XP Tests
http://build.chromium.org/buildbot/waterfall/builders/XP%20Tests/builds/16523
http://build.chromium.org/buildbot/waterfall/waterfall?builder=XP%20Tests
--= Automatically closing tree for unit_tests on XP Tests =--
Revision: 36626
Blame
Greetings, people of Chromium!
Last quarter, the Layout Test Task Force done some pretty good work. I
bragged about it in a separate email. Now it's time to grab the bull by the
horns and kick it up a notch. Isn't idiomatic English great?
This quarter, the LTTF is aiming right at the heart of
Automatically closing tree for unit_tests on Vista Tests
http://build.chromium.org/buildbot/waterfall/builders/Vista%20Tests/builds/15332
http://build.chromium.org/buildbot/waterfall/waterfall?builder=Vista%20Tests
--= Automatically closing tree for unit_tests on Vista Tests =--
Revision:
Automatically closing tree for compile on Chromium XP
http://build.chromium.org/buildbot/waterfall/builders/Chromium%20XP/builds/9782
http://build.chromium.org/buildbot/waterfall/waterfall?builder=Chromium%20XP
--= Automatically closing tree for compile on Chromium XP =--
Revision: 36639,
Automatically closing tree for compile on Chromium Builder (dbg)
http://build.chromium.org/buildbot/waterfall/builders/Chromium%20Builder%20%28dbg%29/builds/15729
http://build.chromium.org/buildbot/waterfall/waterfall?builder=Chromium%20Builder%20%28dbg%29
--= Automatically closing tree for
on it. Sorry.
On Wed, Jan 20, 2010 at 10:52 AM, build...@chromium.org wrote:
http://build.chromium.org/buildbot/waterfall/
Automatically closing tree for compile on Chromium Builder (dbg)
http://build.chromium.org/buildbot/waterfall/builders/Chromium%20Builder%20%28dbg%29/builds/15729
Hi,
It seems I've already found an answer - JS debugger is viable under
test_shell after a small change:
Index: WebViewImpl.cpp
===
--- WebViewImpl.cpp (revision 53449)
+++ WebViewImpl.cpp (working copy)
@@ -234,7 +234,11 @@
I have a local squid proxy and on Windows machines using it the Chrome
installer never finishes (I can download the first, small .exe which
then initializes and tries to download the main installer). When not
using squid it works fine. When using other proxies like tinyproxy, it
also works fine.
This is a heads up that as part of moving all of our resources to
chromium.org (and vanity!), I'll be switching our mailing lists to be under
chromium.org today. I will send an email when it's done, but for now you
may want to update your rules to be either googlegroups.com or
chromium.orgso that
1) if there is a ':' in the URI, you split the URI into scheme and
scheme-specific part.
No. The first check is is this an absolute file path. That check is done
with platform-specific logic:
#if windows
if the path matches letter:\ or \\...
#else
if the path starts with a slash
#endif
Then
Automatically closing tree for unit_tests on XP Tests
http://build.chromium.org/buildbot/waterfall/builders/XP%20Tests/builds/16535
http://build.chromium.org/buildbot/waterfall/waterfall?builder=XP%20Tests
--= Automatically closing tree for unit_tests on XP Tests =--
Revision: 36651, 36652
Just to explain to everyone the steps that I will follow. For each mailing
list, I will:
1) create a corresponding list on chromium.org with the same members
2) subscribe the old list to the new list so that the archives can be
searched in one place
4) disable posting to the old list (only group
On Wed, Jan 20, 2010 at 10:57 AM, Paweł Hajdan, Jr.
phajdan...@chromium.org wrote:
I have a local squid proxy and on Windows machines using it the Chrome
installer never finishes (I can download the first, small .exe which
then initializes and tries to download the main installer). When not
Automatically closing tree for net_unittests on Modules XP (dbg)
http://build.chromium.org/buildbot/waterfall/builders/Modules%20XP%20%28dbg%29/builds/21889
http://build.chromium.org/buildbot/waterfall/waterfall?builder=Modules%20XP%20%28dbg%29
--= Automatically closing tree for net_unittests
Automatically closing tree for compile on Webkit Builder (dbg)
http://build.chromium.org/buildbot/waterfall/builders/Webkit%20Builder%20%28dbg%29/builds/22831
http://build.chromium.org/buildbot/waterfall/waterfall?builder=Webkit%20Builder%20%28dbg%29
--= Automatically closing tree for compile
Automatically closing tree for compile on Linux Perf (1)
http://build.chromium.org/buildbot/waterfall/builders/Linux%20Perf%20%281%29/builds/5173
http://build.chromium.org/buildbot/waterfall/waterfall?builder=Linux%20Perf%20%281%29
--= Automatically closing tree for compile on Linux Perf (1)
Hello,
The chromium-dev mailing list has now been switched to
chromium-...@chromium.org. Please update your filters and address book
accordingly.
Existing members have been subscribed, with the exception of users who don't
permit managers to add them to a group. You can visit the new group at
Automatically closing tree for compile on Linux Builder (ChromiumOS)
http://build.chromium.org/buildbot/waterfall/builders/Linux%20Builder%20%28ChromiumOS%29/builds/2488
http://build.chromium.org/buildbot/waterfall/waterfall?builder=Linux%20Builder%20%28ChromiumOS%29
--= Automatically closing
Note: I've converted chromium-bugs, chromium-checkins, chromium-dev, and
chomium-os-checkins. I'll convert the rest tomorrow.
It seems that there are some issues with groups and I've emailed the team
before I convert any more lists. People who were not receiving email before
might start
On Wed, Jan 20, 2010 at 22:38, Eric Roman ero...@chromium.org wrote:
Omaha doesn't support manual authentication for proxies, so if your
squid proxy is requiring a username/password that could be the
problem.
Yes, I know about this problem (it's documented in the help message
linked when the
Automatically closing tree for update on Webkit
http://build.chromium.org/buildbot/waterfall/builders/Webkit/builds/17270
http://build.chromium.org/buildbot/waterfall/waterfall?builder=Webkit
--= Automatically closing tree for update on Webkit =--
Revision: 36741
Blame list:
21 matches
Mail list logo
