## Overview
* **Coverage on recent changesets** - A list of recent changesets and
the percent of new lines covered by tests.
https://firefox-code-coverage.herokuapp.com
* **Coverage addon** - Use it to show coverage on your patches in
Bugzilla -
*# 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/
You can try ActiveData, which stores all test results from the past few
weeks. Here is an example query that shows the chunk number for each
run/build combo in the past day. ActiveData is sometimes more than a
day behind
https://activedata.allizom.org/tools/query.html#query_id=4HHuBgDu
{
7-06 21:37, Kyle Lahnakoski wrote:
>
>
>
> ## 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
## 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
##
On 2017-06-09 15:14, Kyle Lahnakoski wrote:
>
> ## 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 runnin
## 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
##
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
WVR9w/edit#
[3] Kyle Lahnakoski email: klahnako...@mozilla.org irc: ekyle on
#at...@irc.mozilla.org
[4] grcov https://github.com/marco-c/grcov
[5] (Co)de (Co)verage UI preview -
https://ericdesj.github.io/moz-coco-w17-preview/
[5b] CoCo is on Github - https://github.com/mozilla/moz-coco
[6]
It was pointed out that my email address did not have enough "L"s in
it. Here is my real email address:
klahnako...@mozilla.org
Forwarded Message
Subject:CodeCoverage: First Monthly Update
Date: Thu, 2 Mar 2017 21:29:10 -0500
From: Kyle Lahnakoski
Capstone Open Source Projects)http://ucosp.ca/
[2] The actual plan:
https://docs.google.com/document/d/1dOWi18qrudwaOThNAYoCMS3e9LzhxGUiMLLrQ_WVR9w/edit#
[3] Kyle Lahnakoski email: klahnako...@mozila.org irc: ekyle on
#at...@irc.mozilla.org
___
dev
On 2017-02-16 18:21, Jean-Yves Avenard wrote:
>
>
> On 17/02/17 00:17, Jeff Gilbert wrote:
>> If there are so many parens that we require an editor to disambiguate
>> them, it's too dense. Add whitespace or decompose the expression until
>> readable.
>>
> I'd love to know how adding any
Al,,
ActiveData[1] is warehouse of our test times, build times, and whatever
other properties or measures I can get my hands on. It has a primitive
query tool[2] that a human can use to send queries to the public service
[3]. The `unittest` table has results from all tests that emit
13 matches
Mail list logo
