The perf dashboard now tracks byte sizes of (some) key built targets.
Scroll to the bottom of the dashboard for the thumbnails.
This is primitive, but provides a place to start adding more sophisticated
tracking. Let me know what you'd like to see.
Right now, it just tracks the size of various
Thanks! This is awesome.
Since Where are the perf graphs? is one the most asked questions, I will
answer it even before someone asks:
Go to the waterfall (http://build.chromium.org), click on the perf link in
the top left corner.
To find the size graphs, scroll down to the bottom of the page.
+1 It's great that we can track this info now, thanks for doing this!
Nicolas: Could you possibly add the contents of your email to the wiki?
sgk: How about adding links from the top of the page to the size graphs?
Since they're way down at the bottom of the page it's easy to miss them. It
would
I am trying to improve the UI automation framework with the goal of
reducing disabled UI test from 42 to 10 and running time (xp release)
from 400s to 200s. Following is a list of issues I found so far (I am
still studying them):
1. Many UI commands are executed asynchronously, and test client
I'm reading this on a Fedora 10 build. Just follow the instructions on
how to build in Linux, and do not ignore the fonts. They need to be
installed.
On Apr 16, 2:34 pm, rrwinterton rrwinter...@gmail.com wrote:
Hi,
I have build and ran the latest (10 Apr 09) source on Ubuntu. I then
tried
If you don't build on Linux, then you can stop reading now.
I will be checking in this CL
(http://codereview.chromium.org/60009)
that will require gconf as a build dependency for Linux.
You need to do:
sudo apt-get install libgconf2-dev
(or equivalent for your distro)
and if you are on a 64bits
Not to make more things complicated, but shouldn't it be possible to
only use gconf if it's available, otherwise don't get the proxy
settings?
I am just worried that we are slowing sucking in the whole world into
our dependency list.
I guess we obviously need the headers for building, but at
Sorry, re: creating the symlink, afaict that was automatically done. Am I
misinterpreting what you posted?
root@mymachine:/usr/lib32# ls -la libgconf*
lrwxrwxrwx 1 root root 15 Apr 8 19:11 libgconf-2.so - libgconf-2.so.4
lrwxrwxrwx 1 root root 19 Dec 1 17:30 libgconf-2.so.4 -
On Fri, Apr 17, 2009 at 8:25 PM, Stephane Doyon sdo...@chromium.org wrote:
On Fri, 17 Apr 2009, Dean McNamee wrote:
Not to make more things complicated, but shouldn't it be possible to
only use gconf if it's available, otherwise don't get the proxy
settings?
I am just worried that we are
I added DirectoryWatcher so that you could edit a script on disk and
Chromium would automatically refresh its in-memory cache of scripts.
In the extensions world, do you still use this pattern? Do you need
to watch subdirectories as well?
We have this bug to follow the Windows behavior
We want to watch directories recursively for extensions, but not for
user scripts. So ideally, we'd like it to be an option. If I had to
choose one, I'd say I want recursive, because it's more important to
have extensions work well than to have the user script directory not
work as well.
- a
On
?
This directory is not cleaned up. It's a real mess in fact. :) Note
that these are small memory dumps, not the full ones.
Making the dumps available would mean to add a step to copy the dump
back to the main server and let these files live on the server.
Patches are welcome but I don't see a
dpkg: /usr/lib32/libgconf-2.so not found.
Using ghardy.
On Fri, Apr 17, 2009 at 12:06 PM, Stephane Doyon sdo...@chromium.orgwrote:
On Fri, 17 Apr 2009, Ian Fette wrote:
Sorry, re: creating the symlink, afaict that was automatically done. Am I
misinterpreting what you posted?
I think we can simplify code in another way: if the recursive watch
doesn't have to add watches for newly created directories in the subtree and
remove watches for deleted dirs (so we just scan the subtree when adding
initial watch, and don't react to dorectory structure changes), then the
code is
Erik—
I don't understand why in http://codereview.chromium.org/17243 you defined
Extension() to have a leading dot. It's easier to add a dot than take one
off, and I don't understand why you insist on the equivalence you describe.
How is ensuring that you could append the string values of the
Very nice work, uhm can we create a navigation bar to the perf page :) It
seems there are too many.
On Fri, Apr 17, 2009 at 11:44 AM, Jeremy Moskovich jer...@chromium.orgwrote:
+1 It's great that we can track this info now, thanks for doing this!
Nicolas: Could you possibly add the contents
Right it is generated but then next UI test case will clean up the
directory to detect new crashes. It is easy to change the behavior to
something like backing up crash dumps at the end of each test case.
What we need is some place in try server or buildbot to save the crash
dumps and adding a
17 matches
Mail list logo
