CodeCoverage Monthly Update

[Kyle Lahnakoski]

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 met the nice people working on coverage for iOS [4] (thanks isabel!)
  * e10s coverage builds are working! (thanks mcastelluccio!) [8]
  * Listed the use cases we will be solving for in the short term, and
the long term [5]

## Some bad news

  * Rust code coverage will probably not be available until July, or
later.  Work is progressing [6], but the release schedule, CI
integration, and the unknowns, will add delay.
  * JSVM, despite it is working[7], has not been verified and scheduled

## Future Plans

  * e10s coverage will be compared to ensure there are no multiprocess
anomallies
  * More test suites will be enabled for nightly scheduled coverage
  * JSVM coverage work will resume
  * Start identifying the gaps between current visualizations and
Release Management's expectations so we have priority worklist for
end of the quarter

## Meetings

We have weekly CodeCoverage meetings, and you are welcome to attend:

  * When: Held every Friday @ 11:30 EDT (08:30 PDT)
  * Where: Kyle's video room
https://v.mozilla.com/flex.html?roomdirect.html=huhL8WaTwCwC
  * Etherpad: https://public.etherpad-mozilla.org/p/code_coverage_Q1_17


## Reference

[1] coveralls.io https://coveralls.io/github/marco-c/gecko-dev

[2] codecov.io https://codecov.io/gh/marco-c/gecko-dev

[3] Local Coverage
https://developer.mozilla.org/en-US/docs/Mozilla/Testing/Measuring_Code_Coverage_on_Firefox?document_saved=true#Generate_Code_Coverage_report_from_a_try_build_(or_any_other_treeherder_build
)

[4] iOS Coverage
https://codecov.io/gh/mozilla-mobile/firefox-ios/branch/master

[5] User Cases
https://docs.google.com/document/d/1JUEPS8Xdtx4y8fXA4Au_Ggme0fMyJQxZbby0X2e4yDI/edit#heading=h.ddwyjkvxus4-


[6] Rust coverage
https://docs.google.com/document/d/1JUEPS8Xdtx4y8fXA4Au_Ggme0fMyJQxZbby0X2e4yDI/edit#heading=h.ddwyjkvxus4

[7] JSVM coverage: https://bugzilla.mozilla.org/show_bug.cgi?id=1301174

[8] e10s coverage example:
https://treeherder.mozilla.org/#/jobs?repo=try=b6e9cefe95adc3dd281bf8e2a2f897e8f4839e51

[9] Everything:
https://bugzilla.mozilla.org/showdependencytree.cgi?id=1278393

___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

We want to hear from you

[Konstantina Papadea]

Hello all,
my name is Konstantina Papadea and I work for the Open Innovation Team as
the Community Manager of the Reps program.

I am forwarding an e-mail sent earlier to all vouched Mozillians about a
survey we launched today. This is a really important survey that was will
help us shape Mozilla's strategy.

Thank you,
Konstantina

-

Hello,

You are receiving this email because you have been involved with Mozilla or
one of its sponsored projects.

We invite you to participate in a research that will shape the future of
open source and other collaborative practices at Mozilla.

I am asking for 10 minutes of your valuable time before May 15th to
complete the following survey about your experience with Mozilla and/or
Mozilla’s sponsored projects:

* Survey in English: https://qsurvey.mozilla.com/s3
/communities-contributors-2017-en

* Encuesta en español: https://qsurvey.mozilla.com/s3
/communities-contributors-2017-es

* Pesquisa em Português: https://qsurvey.mozilla.com/s3
/communities-contributors-2017-pt

* Umfrage auf Deutsch: https://qsurvey.mozilla.com/s3
/communities-contributors-2017-de

* Étude en français: https://qsurvey.mozilla.com/s3
/communities-contributors-2017-fr

https://qsurvey.mozilla.com/s3/communities-contributors-2017-ar  :طلب كشف
باللغة العربية *

We will publish our findings once the initial analysis is complete (and
will email them to you if you indicate your interest when completing the
survey) and we will make at least some aggregated data publicly available.
Please visit this page [1] or get in touch to learn about other ways you
can follow and participate in this research.

A final note: I realize that we at Mozilla often ask for contributor’s time
to provide feedback, and we may even have asked you recently. Also, we have
run contributor research projects in the past without complete follow-up.
This project is different. It’s more extensive than anything we’ve done, it
will shape Mozilla’s strategy with respect to open practices, and we will
be publishing the results. I hope this will encourage your participation.

Thank you!

Rubén Martín
https://mozillians.org/u/nukeador/
Mozilla Open Innovation Team

[1] https://discourse.mozilla-community.org/t/revitalize-partici
pation-by-understanding-our-communities/15172
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Re: Updating a particular vendored crate by minor version

[Henri Sivonen]

On Tue, May 2, 2017 at 3:11 PM, Kartikaya Gupta  wrote:
> You can update a specific crate to a specific version like so:
>
> cd toolkit/library/rust
> cargo update -p encoding_rs --precise 
> cd ../gtest/rust
> cargo update -p encoding_rs --precise 
> cd ../../../../
> mach vendor rust

Thank you. This works.

Filed https://bugzilla.mozilla.org/show_bug.cgi?id=1361734 to get mach
vendor to perform those steps.

-- 
Henri Sivonen
hsivo...@hsivonen.fi
https://hsivonen.fi/
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Fwd: Web Compatibility Testing Survey

[David Burns]

Hi All,

If you are working on web exposed features could you please take a few
minutes to complete the survey. This will help us prioritize work on Web
Platform Tests which helps us with our web compatibility story.

David
-- Forwarded message --
From: 
Date: 28 April 2017 at 14:19
Subject: Web Compatibility Testing Survey
To: dev-platform@lists.mozilla.org


I've invited you to fill in the following form:
Web Platform Tests Survey

To fill it in, visit:
https://docs.google.com/forms/d/e/1FAIpQLScsbrVikqdnH32Qs-hV
8YWgBi6kb5QRJtYG3KGqHba2eO2Dzw/viewform?c=0w=1usp=mail_form_link

Hi All,

The Product Integrity Automation Harnesses team would like your help
prioritizing web compatibility work.

We are trying to understand how people test web-exposed features they are
working on.

Please can you fill in the following survey[1], it shouldn’t take more than
5 minutes. It will help us ensure that we focus on the projects that will
have the greatest impact on gecko development.

Thanks

David

Google Forms: Create and analyse surveys.
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Sheriff Statistics for April 2017

[Carsten Book]

Hi,

We will be more active in 2017 and inform more and since its already
May..lets go :)

*April 2017:*

*Autoland Tree:*

Total Servo Sync Pushes: 251
Total Pushes: 1783
Total Number of commits 3544
Total number of commits without Servo 3281
Total Backouts: 161
Total of Multi-bug pushes 16 (merges from m-c to autoland)
Total number of bugs changed 1663
Percentage of backout against bugs: 9.68129885749
Percentage of backouts: 9.02972518228
Percentage of backouts without Servo: 10.5091383812 (compared to March
that's ~ +1 % higher - with a slightly higher rate of pushes)

*Mozilla-inbound*

Total Servo Sync Pushes: 0
Total Pushes: 1008
Total Number of commits 3374
Total number of commits without Servo 3374
Total Backouts: 134
Total of Multi-bug pushes 161
Total number of bugs changed 1294
Percentage of backout against bugs: 10.3554868624
Percentage of backouts: 13.2936507937
Percentage of backouts without Servo: 13.2936507937  (compared with March
that's ~ +0,5 % higher with around the same rate of commits)


So Sheriffs managed and monitored on the Integration Trees in April 2017 ~
2800 pushes and 295 backouts.

Beside this Sheriffs took park in doing uplifts and checkin-needed bugs.

The Current Orangefactor is 7.51 (5674 failures in 755 pushes in the last 7
days). You can find the list of top Intermittent
failure bugs here https://brasstacks.mozilla.com/orangefactor/

You can find more statistics here:
https://futurama.theautomatedtester.co.uk/

Let us know when you have any Question or Feedback about Sheriffing.

Cheers and have a great May!,
-Tomcat
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform