*# Q3 Codecoverage! update *
/If you //want to hear more about an//y of the//s//e items, please
contact me and I will get you more detailed information/*
*
*## Overview *
We can show the code coverage on new lines added by changeset!
* *Link* - http://firefox-code-coverage.herokuapp.com/
*
The patch providing coverage in rust landed here:
https://github.com/rust-lang/rust/pull/42433
If I understood correctly, we are waiting for rust 1.20 to be able to
use it.
Sylvestre
Le 10/08/2017 à 22:03, Chris Peterson a écrit :
> Kyle, do you know if Rust code coverage is blocked on any re
Kyle, do you know if Rust code coverage is blocked on any remaining Rust
toolchain issues?
chris
On 2017-08-10 11:31 AM, Kyle Lahnakoski wrote:
Did you have that sense you were missing something? Well, you were
right: You were missing your ...
# *Monthly CodeCoverage! update! \o/ *
/If
Did you have that sense you were missing something? Well, you were
right: You were missing your ...
# *Monthly CodeCoverage! update! \o/ *
/If you //want to hear more about an//y of the//s//e items, please
contact me and I will get you more detailed information/*
*
*## **Summary of July*
*
## Summary of Past Quarter
Coverage is enabled for nearly all tests, and scheduled every push [1]!!
* All c/c++ test suites have coverage enabled
* talos coverage is enabled
* jsvm[7] coverage is enabled, and running
* codecov.io [2] shows the results, broken down by directory
## Plans
A couple of nice people noticed my link to the Rust coverage was wrong:
Here is the main tracking bug:
https://bugzilla.mozilla.org/show_bug.cgi?id=1335518
Plus Github issues tracking the specific work:
https://github.com/rust-lang/rust/pull/38608
https://github.com/rust-lang/rust/pull/42433
O
## Summary of the past month
Coverage is enabled for nearly all tests, and scheduled every night [1]!!
* All c/c++ test suites have coverage enabled and are running nightly
* jsvm[7] coverage is enabled, and running
* codecov.io [2] shows the results, broken down by directory
## Complicat
On Tue, May 9, 2017, at 05:48 AM, Henri Sivonen wrote:
> On Thu, Apr 6, 2017 at 6:26 AM, Kyle Lahnakoski
> wrote:
> > * Getting Rust to emit coverage artifacts is important:
> > https://bugzilla.mozilla.org/show_bug.cgi?id=1335518
>
> Is there a plan to factor "cargo test" of individual vendored
On Thu, Apr 6, 2017 at 6:26 AM, Kyle Lahnakoski wrote:
> * Getting Rust to emit coverage artifacts is important:
> https://bugzilla.mozilla.org/show_bug.cgi?id=1335518
Is there a plan to factor "cargo test" of individual vendored crates
into the coverage of Rust code? For example, for encoding_rs
No, currently not, but we can build one ourselves using their API (which
we might to do with codecov.io anyway, since we expect to have custom
needs).
- Marco.
Il 04/05/17 08:22, Chris Peterson ha scritto:
On 2017-05-03 8:44 PM, Kyle Lahnakoski wrote:
* Daily coverage reports on coveralls
On 2017-05-03 8:44 PM, Kyle Lahnakoski wrote:
* Daily coverage reports on coveralls.io [1] and on codecov.io[2].
Which do you like?
Does coveralls.io have a top-down coverage view like codecov.io? That
view seems more useful for both people that want a global view and
developers that wa
It is the first Wednesday for the month! Time to write an update!
## Summary of Activity
* Daily coverage reports on coveralls.io [1] and on codecov.io[2].
Which do you like?
* You can now use one-click loaners to generate coverage locally
(thanks maja and mcastelluccio!)
* We me
This is the second monthly update on our CodeCoverage effort:
## The Progress to Date
* Coverage is scheduled to run daily on central.
https://treeherder.mozilla.org/#/jobs?repo=mozilla-central&filter-searchStr=cov
* The UCOSP[1] students have completed their term, and can show
aggregate statist
13 matches
Mail list logo
