EngineeringProductivity/Projects/Stockwell/Meetings/2016-10-25: Difference between revisions

m
→‎Discussion Topics: - try push link
(create initial page)
 
m (→‎Discussion Topics: - try push link)
Line 10: Line 10:
** Purgatory (frequent intermittent tests) - what is the point of running these if the job will always be orange?  could we detect if a regression was introduced?  Would we disable tests if they stayed here too long (say 30 days)?
** Purgatory (frequent intermittent tests) - what is the point of running these if the job will always be orange?  could we detect if a regression was introduced?  Would we disable tests if they stayed here too long (say 30 days)?
** Quarantine (new/edited tests) - All tests which are edited/added would run for 2 weeks to ensure it isn't intermittent.  If intermittent, would we move to Purgatory, backout original patch?
** Quarantine (new/edited tests) - All tests which are edited/added would run for 2 weeks to ensure it isn't intermittent.  If intermittent, would we move to Purgatory, backout original patch?
*** example [[https://treeherder.mozilla.org/#/jobs?repo=try&revision=9666ec40dfced1237aa6d5c269c9cfdb2f901ac9 try push]]
** Sanity (quick, very safe - 100% green) vs longer more complex/slightly intermittent.  How would we define these safe tests?  would we backout if any test here was intermittent? criteria for moving to main test suites (<10 intermittents total)?
** Sanity (quick, very safe - 100% green) vs longer more complex/slightly intermittent.  How would we define these safe tests?  would we backout if any test here was intermittent? criteria for moving to main test suites (<10 intermittents total)?
** Making these changes will help keep our test jobs very green, without a purpose and workflow, these will add more confusion.
** Making these changes will help keep our test jobs very green, without a purpose and workflow, these will add more confusion.
Confirmed users
3,376

edits