You can use my get_chromium.cmd tool to automatically sync, clean and
build Chromium. I myself use a shortcut that syncs, builds and then switches
off my computer, which I run every day after work. That way I always have a
recent build to play with in the morning (unless the build broke).
I'm
I think you should file bugs if you can repro DCHECKs on trunk.
On Mon, Nov 24, 2008 at 5:47 AM, Berend-Jan Wever [EMAIL PROTECTED] wrote:
You can use my get_chromium.cmd tool to automatically sync, clean and
build Chromium. I myself use a shortcut that syncs, builds and then switches
off my
It might be even more helpful (albeit painful) to run a debug build and
start filing bug reports on all the DCHECKs. I stopped doing this around the
webkit merge, but I'm switching back and hitting a ton of DCHECKs in gmail.
On Wed, Nov 19, 2008 at 1:29 PM, Paul Godavari [EMAIL PROTECTED] wrote:
On Wed, Nov 19, 2008 at 1:15 PM, Ben Goodger (Google) [EMAIL PROTECTED]wrote:
As Chromium developers we should all be using recent trunk builds.
Just using the dev channel isn't good enough, as it doesn't have a
majority of the code changes that have occurred on the trunk, and also
tends to
It would be very helpful to also run these trunk builds with the command
line flag: --new-safe-browsing
This is our new SafeBrowsing storage implementation which we believe greatly
reduces disk IO that some have reported. Please file any bugs you encounter
and assign them to me.
Paul
On Wed, Nov
