EngineeringProductivity/Projects/Stockwell/Meetings/2017-01-17: Difference between revisions
(initial page) |
(→Status: linux32 debug -> linux32 debug devtools) |
||
| (7 intermediate revisions by 2 users not shown) | |||
| Line 2: | Line 2: | ||
= Status = | = Status = | ||
Shorter meeting today due to Mozilla previously scheduled monthly internal meeting | |||
* [gbrown] - Orange Factor review | |||
** [https://brasstacks.mozilla.com/orangefactor/?display=OrangeFactor&endday=2017-01-16&startday=2017-01-09&tree=trunk&branch=trunk last week's OF]: 14.75 | |||
** [https://brasstacks.mozilla.com/orangefactor/?display=OrangeFactor&endday=2017-01-16&startday=2016-12-16&tree=trunk&branch=trunk last month's OF]: 12.17 | |||
* {{bug|1328351}} - [jmaher] add BUG_COMPONENT to all files in-tree- maybe 1/3 done | * {{bug|1328351}} - [jmaher] add BUG_COMPONENT to all files in-tree- maybe 1/3 done | ||
* {{bug|1323044}} - [malayaleecoder] add a lint job for mochitest (about 20% done) | * {{bug|1323044}} - [malayaleecoder] add a lint job for mochitest (about 20% done) | ||
* {{bug|1322433}} - [wlach] - make it easier to retrigger a job with options (precursor to rr- | * {{bug|1322433}} - [wlach] - make it easier to retrigger a job with options (precursor to rr-chaos in a test-lint job) | ||
* test- | * {{bug|1324470}} - [gbrown] - add a mach command to display test results from activedata - prototype complete | ||
* TODO: | * TODO: | ||
** dashboard of test by component | ** dashboard of test by component | ||
** better way to track disabled tests (test-informant might work) | ** better way to track disabled tests (test-informant might work) | ||
** reduce oranges | ** reduce oranges | ||
*** linux32 debug tests disabled due to too many timeouts | *** linux32 debug devtools tests disabled due to too many timeouts | ||
*** almost fixed all the leaks (after displaying leaks as failures per {{bug|1325148}}) | |||
= Discussion Topics = | = Discussion Topics = | ||
* | * Infrastructure intermittents? | ||
* | ** we get spikes of 100+ issues while a service is not available for a few minutes (seems to happen once/week or so) | ||
** we cannot 'disable' the builds/tests for infra | |||
** some infra issues are really intermittent and show up every day | |||
** do we force retries for some of these? | |||
** should we annotate these and not report them on orangefactor by default? | |||
= New Ideas to investigate = | = New Ideas to investigate = | ||
Latest revision as of 16:40, 17 January 2017
Previous Action Items
Status
Shorter meeting today due to Mozilla previously scheduled monthly internal meeting
- [gbrown] - Orange Factor review
- last week's OF: 14.75
- last month's OF: 12.17
- bug 1328351 - [jmaher] add BUG_COMPONENT to all files in-tree- maybe 1/3 done
- bug 1323044 - [malayaleecoder] add a lint job for mochitest (about 20% done)
- bug 1322433 - [wlach] - make it easier to retrigger a job with options (precursor to rr-chaos in a test-lint job)
- bug 1324470 - [gbrown] - add a mach command to display test results from activedata - prototype complete
- TODO:
- dashboard of test by component
- better way to track disabled tests (test-informant might work)
- reduce oranges
- linux32 debug devtools tests disabled due to too many timeouts
- almost fixed all the leaks (after displaying leaks as failures per bug 1325148)
Discussion Topics
- Infrastructure intermittents?
- we get spikes of 100+ issues while a service is not available for a few minutes (seems to happen once/week or so)
- we cannot 'disable' the builds/tests for infra
- some infra issues are really intermittent and show up every day
- do we force retries for some of these?
- should we annotate these and not report them on orangefactor by default?
New Ideas to investigate
Action Items
- Discussion topics for next time