[SERVER-18743] Create a "flaky test finder" buildvariant Created: 29/May/15 Updated: 09/Mar/18 Resolved: 19/Aug/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 3.1.7 |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Ian Whalen (Inactive) | Assignee: | Ian Whalen (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Sprint: | QuInt 8 08/28/15 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
Implementation TBD, but one possibility is to start small and simply create a buildVariant to run just jsCore with --repeat=100 and execute every 7 days. Pending completion of EVG-17, this should be all that is required to start identifying tests that are susceptible to weird network conditions, slow AWS machines, etc. |
| Comments |
| Comment by Githook User [ 19/Aug/15 ] |
|
Author: {u'username': u'IanWhalen', u'name': u'Ian Whalen', u'email': u'ian.whalen@gmail.com'}Message: Specifically adding jsCore and jsCore_WT given it's importance
|