Re: C++ performance test harness?
On 05/07/2017 16:31, William Lachance wrote: > We do run these tests in automation, you can track the results in > perfherder under the platform_microbench framework: > > https://treeherder.mozilla.org/perf.html#/graphs?series=%5Bautoland,2aa20d42dc00d0a953f871f76056d8d217dc569e,1,6%5D&series=%5Bmozilla-inbound,2aa20d42dc00d0a953f871f76056d8d217dc569e,1,6%5D&selected=%5Bmozilla-inbound,2aa20d42dc00d0a953f871f76056d8d217dc569e,220714,290981367,6%5D There was talk about turning them off some time ago: https://groups.google.com/forum/#!topic/mozilla.dev.platform/u4tUwHJg-Dc Are they still maintained? Gabriele signature.asc Description: OpenPGP digital signature ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: Phabricator Update, July 2017
On 14/07/2017 05:39, Boris Zbarsky wrote: > I should note that with GitHub what this means is that you get > discussion on the PR that should have gone in the issue, with the result > that people following the issue don't see half the relevant discussion. > In particular, it's common to go off from "reviewing this line of code" > to "raising questions about what the desired behavior is", which is > squarely back in issue-land, not code-review land. > > Unfortunately, I don't know how to solve that problem without > designating a "central point where all discussion happens" and ensuring > that anything outside it is mirrored there... Yeah, we frequently had that problem with Gaia issues as part of Firefox OS. Reviews were done on GitHub's PR so the bugzilla entries were often empty (even for bugs with huge, complex patch-sets). To gather any kind of information one had to go and check the comments on the PR itself which not only was less-than-optimal but made life a lot harder for those not directly involved with development. It's not a dealbreaker for me but it's something that should be kept in mind. Gabriele signature.asc Description: OpenPGP digital signature ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: More Rust code
On 13/07/2017 01:06, Eric Rahm wrote: > * *using breakpad* - was the problem that creating wrappers to access > the c/c++ code was too tedious? Could bindgen help with that, if not > it would be interesting gather some details about why it wouldn't > work and file bugs against it. There were multiple reasons: I had no experience in writing Rust bindings and we wanted to have it ready quickly; additionally we're in the process of rewriting this part of Breakpad functionality in Rust so we decided that it would all become Rust at a later point and writing bindings wouldn't have been a good use of the time. > * *pingsender* - was something like https://hyper.rs/ not around when > you were working on it or is this a case of finding the things you > want can be difficult in rust-land? Either way it might be a good > idea for us to put together a list of "sanctioned" crates for > various tasks. hyper.rs was already available but it's a big dependency and I didn't feel like pulling it into mozilla-central just for the pingsender. I believe we'll have HTTP functionality available from Rust code at some point in the future so when it's ready I might as well port the pingsender to it. As Mike said though the program is very small and self-contained at this point so it would be nice to keep it that way even after a Rust rewrite if possible. Gabriele signature.asc Description: OpenPGP digital signature ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
