Chromium: Snapshot vs. Continuous

OK, once and for all N00bs ;]

…every time there are any substantial code-changes (about twice a day),
an automated build of Chromium is created.

Once the compilation process succeeds (minimal unit-tests mostly..),
the build is then copied to the snapshot tree (which may be downloaded by you freely from here: but keep in mind, it is quite buggy..)

The build is than ran-through a quite huge (python managed) test-suit…

where the majority of the tests are for ppapi, v8 and sandbox’ing features, some profiling for CPU/GPU and memory is next and there is a h-u-g-e part for third-party components (skia and ffmpeg and openh264 for x264 encoding, woff2 support, webgl, polymer and even zlib…) which are all integrated into the browser, since most of the components are to be native to ChromiumOS- it really is the best choice. Some OS-rendering Quirks (MacOS and Windows), JavaScript tests with mojojs, UI tests (“ash”) and native-client are the last to run. Also, here is a list of related-sources for tests if you are interested in those things..
Passing successfully (which is pretty rare.. mostly one build every two weeks) means that the build is than stable enough to be copied to the continuous tree.

Continuous builds may be downloaded from here:

If you wish to find-out just the latest build,
you may send-out a request to the LAST_CHANGE file (no, there is no “latest” hot-link build..)

For example here is a link to the latest VERSION (!) [not build itself] for several OS:


The most visited builds are:


Several of the least visited ones are the ones built for Android (generic or with ARM variations)


Perhaps because the APK (for Android),
is built mostly for tests, so it is in two parts (the engine and the “shell”/”frame”/ a.k.a what was known in old Mozilla as “chrome” [small-caps ‘C’])

Oh well…

Do you want to try ChromiumOS? (it really is awesome! amm.. well at-least in a VM)


And just a note for the ones ending with “Git”:


They WILL include the latest features,
but some overlapping/interleaved old components
(either not disabled or simply as a kind-of a linked-resource,
and are mostly useful for “post-fails” tests, it simply makes diff.
much more clear :]
So, although it will probably won’t do any harm,
avoid using those…
It is similar to the case of “jQuery-edge” with that “migrate thing”, and the git-build version, which has the migrate-code re-integrated into the whole thing again, for the same reasons… – so it’s like this.. :]