Automatically closing tree for test_shell_tests on Chromium Linux x64
http://build.chromium.org/buildbot/waterfall/builders/Chromium%20Linux%20x64/builds/4019
http://build.chromium.org/buildbot/waterfall/waterfall?builder=Chromium%20Linux%20x64
--= Automatically closing tree for
We have http://crbug.com/4436, and the problem is that if you launch
chrome index.html (with index.html in the current directory) it will
try to navigate to http://index.html/ instead. This behavior is useful
for cases like chrome www.google.com, and generally I don't see a good
solution to this
On Thu, Jan 7, 2010 at 10:18 PM, Fady Samuel fadysam...@gmail.com wrote:
Which brings me back to the original topic of replicated state. Is there
any reason not to have a single monolithic cache (or other similar state)
across all processes other than synchronization issues or fault tolerance?
That's easy to answer:
Copy the code from Firefox that allows it to handle both local paths
and URLs correctly and incorporate that into Chrome.
On Jan 8, 5:15 am, Paweł Hajdan, Jr. phajdan...@chromium.org wrote:
We havehttp://crbug.com/4436, and the problem is that if you launch
chrome
Don't panic with the main waterfal, it's just a hotpatch to fix an
exception that ... generated more exceptions. At least, the original
exception is fixed.
So I'll just restart the master to make sure nothing dangling is left.
M-A
--
Chromium Developers mailing list:
You could partition a monolithic cache by origin or site (to prevent cache
timing attacks) and still get a reduced memory footprint. If Fady's able to
to work out the consistency issues, it'd be nice to only have one in-memory
cache for all my google.com tabs, etc. I bet there's a lot of cases
On Thu, Jan 7, 2010 at 7:44 PM, Nico Weber tha...@chromium.org wrote:
On Thu, Jan 7, 2010 at 5:31 PM, Evan Martin e...@chromium.org wrote:
On Thu, Jan 7, 2010 at 2:31 PM, Nico Weber tha...@chromium.org wrote:
I wrote up a document that's relevant not only for people working on
chromium, but
SVN Gurus,
I have a question about my CL - http://codereview.chromium.org/527016/show.
Mac and Linux trybots are failing at the patch stage due to line
endings. The files in my cl were originally submitted with wrong line-
endings. My CL fixes the line-endings and now patch is failing on mac
and
I would also like to point out that this is *NOT* just for launching
chrome with index.html in the current directory.
It must work for all these cases:
C:\path\to\chrome.exe index.html
C:\path\to\chrome.exe .\index.html
C:\path\to\chrome.exe ..\index.html
C:\path\to\chrome.exe
On Thu, Jan 7, 2010 at 7:42 PM, alokp al...@chromium.org wrote:
SVN Gurus,
I have a question about my CL - http://codereview.chromium.org/527016/show
.
Mac and Linux trybots are failing at the patch stage due to line
endings. The files in my cl were originally submitted with wrong line-
On Fri, Jan 8, 2010 at 9:58 AM, Evan Martin e...@chromium.org wrote:
On Thu, Jan 7, 2010 at 7:44 PM, Nico Weber tha...@chromium.org wrote:
On Thu, Jan 7, 2010 at 5:31 PM, Evan Martin e...@chromium.org wrote:
On Thu, Jan 7, 2010 at 2:31 PM, Nico Weber tha...@chromium.org wrote:
I wrote up a
On Fri, Jan 8, 2010 at 10:25 AM, Alok Priyadarshi al...@google.com wrote:
Yes thats what I did to fix line-endings: svn pset svn:eol-style LF.
But this CL contains other changes as well in addition to fixing
line-endings. Should I do them in separate CLs?
Yes, I would do them in separate
Automatically closing tree for compile on Chromium XP
http://build.chromium.org/buildbot/waterfall/builders/Chromium%20XP/builds/9571
http://build.chromium.org/buildbot/waterfall/waterfall?builder=Chromium%20XP
--= Automatically closing tree for compile on Chromium XP =--
Revision: 35801
Automatically closing tree for compile on Chromium Builder (dbg)
http://build.chromium.org/buildbot/waterfall/builders/Chromium%20Builder%20%28dbg%29/builds/15358
http://build.chromium.org/buildbot/waterfall/waterfall?builder=Chromium%20Builder%20%28dbg%29
--= Automatically closing tree for
Automatically closing tree for compile on Chromium Builder (dbg)
http://build.chromium.org/buildbot/waterfall/builders/Chromium%20Builder%20%28dbg%29/builds/15360
http://build.chromium.org/buildbot/waterfall/waterfall?builder=Chromium%20Builder%20%28dbg%29
--= Automatically closing tree for
Automatically closing tree for compile on Chromium Builder (dbg)
http://build.chromium.org/buildbot/waterfall/builders/Chromium%20Builder%20%28dbg%29/builds/15362
http://build.chromium.org/buildbot/waterfall/waterfall?builder=Chromium%20Builder%20%28dbg%29
--= Automatically closing tree for
Automatically closing tree for compile on Chromium Linux x64
http://build.chromium.org/buildbot/waterfall/builders/Chromium%20Linux%20x64/builds/4039
http://build.chromium.org/buildbot/waterfall/waterfall?builder=Chromium%20Linux%20x64
--= Automatically closing tree for compile on Chromium
Automatically closing tree for unit_tests on Mac10.5 Tests (dbg)(1)
http://build.chromium.org/buildbot/waterfall/builders/Mac10.5%20Tests%20%28dbg%29%281%29/builds/11013
http://build.chromium.org/buildbot/waterfall/waterfall?builder=Mac10.5%20Tests%20%28dbg%29%281%29
--= Automatically closing
Automatically closing tree for compile on Chromium Linux Builder (valgrind)
http://build.chromium.org/buildbot/waterfall/builders/Chromium%20Linux%20Builder%20%28valgrind%29/builds/5559
http://build.chromium.org/buildbot/waterfall/waterfall?builder=Chromium%20Linux%20Builder%20%28valgrind%29
Before heading out for the weekend, I just want to mention this:
rebaseline tool really, really rocks. And yesterday I discovered an
option that I, to my shame, hadn't seen before: -w. This option pulls
baselines from the canary. It's like getting test expectations from
the future!
In other
Do you find that you have time to figure out if rebaselining a test is the
right thing to do while you're actively gardening? Maybe I just work too
slowly, but I often find that if I'm trying to rebaseline on the fly, it
requires that I do at least *some* investigation of the test failure to make
Same here.
On Fri, Jan 8, 2010 at 4:51 PM, Drew Wilson atwil...@chromium.org wrote:
Do you find that you have time to figure out if rebaselining a test is the
right thing to do while you're actively gardening? Maybe I just work too
slowly, but I often find that if I'm trying to rebaseline on
Yeah, me too.
This is what tends to lead to me spending the day after my gardening
rotation doing clean up. Maybe if we had 2 people gardening at the same
time they could do this real time, but on a normal day, I think it is too
much for one person.
This tool is awesome though!
Julie
On Fri,
Automatically closing tree for plugin_tests on XP Perf (dbg)
http://build.chromium.org/buildbot/waterfall/builders/XP%20Perf%20%28dbg%29/builds/17845
http://build.chromium.org/buildbot/waterfall/waterfall?builder=XP%20Perf%20%28dbg%29
--= Automatically closing tree for plugin_tests on XP Perf
On Fri, Jan 8, 2010 at 5:15 AM, Paweł Hajdan, Jr.
phajdan...@chromium.orgwrote:
We have http://crbug.com/4436, and the problem is that if you launch
chrome index.html (with index.html in the current directory) it will
try to navigate to http://index.html/ instead. This behavior is useful
for
Hi,
Can you please tell me if/where is the file to configure chromium's
renderer sandbox?
Thank you.
--
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
26 matches
Mail list logo
