phasmantistes

15 ms·

121.
by phasmantistes 11y ago
Very little goes through google's servers, actually. "Casting" something from your phone/tablet to the chromecast is just sending it a url (and a timestamp if you were already watching on your phone). Then it streams loc
122.
by phasmantistes 11y ago
This is fantastic. Thanks, Keybase! I've kept my private key on a single device because that's the easiest way for me to secure it... but it means that I haven't used keybase to actually secure communications much because tha
123.
by phasmantistes 11y ago
I think this is the best tracking bug: https://code.google.com/p/chromium/issues/detail?id=465929 There are three things going on: 1) Rietveld exists 2) A new Polymer-based UI for Rietveld exists 3) Gerrit ex
124.
by phasmantistes 11y ago
There are no branches in the golden-source-of-truth repository (except for release branches, but those are never merged back into master and no development is done directly on them). The only branches that exist are on the developer's
125.
by phasmantistes 11y ago
The commit queue can only be bypassed by people who are 'committers' and therefore have direct push access to the repo. Becoming a committer requires landing multiple changes, demonstrating competence and desire to continue to con
126.
by phasmantistes 11y ago
As the article states, Chromium uses run-time checks (feature toggles) extensively. This lets half-baked features land and start undergoing testing before the feature is ready to be shown to the world. But we don't say "oh no, thi
127.
by phasmantistes 11y ago
Heh, that's a contentious topic. Personally, I would like to do so. I think I speak correctly when I say that most of the Infrastructure team would like to do so, to increase security/auditability and ease the maintenance burden o
128.
by phasmantistes 11y ago
A nit to pick here: Google releases Chrome, not Chromium. We only provide Chromium as a source repository, not binaries. Other independent entities (such as Linux distros) can provide releases of Chromium, but Google does not. That said, Go
129.
by phasmantistes 11y ago
Well, we don't use perforce (we use Git), so I assume you're asking for your own benefit. The buildbot masters watch the source repository for new commits. When they see a new commit appear, they tell all of their builders (each o
130.
by phasmantistes 11y ago
The difference is that, in our flow, the merge conflicts are on the scale of a a single developer making a single self-contained commit. In a flow with feature branches, the merge conflicts are on a scale of the entire branch conflicting wi
131.
by phasmantistes 11y ago
We actually are working on systems which re-run the failing tests on all CLs within a failing batch. Unfortunately, we haven't been able to do this previously due to resource constraints. In particular, if a batch had 10 commits in it,
132.
by phasmantistes 11y ago
Engineers base their local development branches on top of origin/master. They can make as many local commits on that branch as they like. Then they upload the diff of that entire branch vs. its upstream (origin/master, unless they
133.
by phasmantistes 11y ago
I don't think any of our decisions are driven by or dependent upon the caliber of our engineers. For example: a) No merges; and the only branches are release branches. This makes sense in almost any context. Whether your team is big or
134.
by phasmantistes 11y ago
Since all I've worked on for the last three years is the infrastructure, and not the binary that lands on your desktop/phone, I'm not really qualified to answer that. (Which is just a fancy way of saying I've got no eart
135.
by phasmantistes 11y ago
We are working on a few things. The first is automatic retries of fast tests. If a test runs quickly and fails, it costs us little to try again just to make sure. Most of our unit tests are configured to run up to 3 times. Another thing is
136.
by phasmantistes 11y ago
Chromium is open source, and will run try jobs for anyone from anywhere around the world (we won't accept your commit without lots of checks, but we'll run your tests). That means that we don't get to rely on a lot of Google-
137.
by phasmantistes 11y ago
Chromium continuous build infrastructure engineer here. As he says, this is slightly out of date: we forked WebKit to make Blink in 2013, and actually merged Blink into Chromium proper just this week! It is no longer managed by gclient&#x2F
138.
by phasmantistes 11y ago
Wow, that's an uncharitable opinion of design and designers. They're highly-trained professionals too, and redesigns like this aren't done just for the heck of it -- according to the blog post, this measurably increases perfo