[SERVER-24695] burn_in_tests.py should have a mechanism for blacklisting tests and suites similar to resmoke.py Created: 21/Jun/16 Updated: 05/Apr/17 Resolved: 13/Jan/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 3.4.2, 3.5.2 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Crystal Horn | Assignee: | Jonathan Abrahams |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Backport Requested: |
v3.4
|
||||||||||||||||||||
| Sprint: | TIG 2017-01-02 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Linked BF Score: | 0 | ||||||||||||||||||||
| Description |
|
burn_in_tests.py should use a mechanism similar to what resmoke.py does to blacklist tests and whole suites (e.g. jstestfuzz, concurrency) from running. |
| Comments |
| Comment by Githook User [ 17/Jan/17 ] |
|
Author: {u'username': u'hptabster', u'name': u'Jonathan Abrahams', u'email': u'jonathan@mongodb.com'}Message: (cherry picked from commit 91c98db0e50d5a0dcc3a939de4696b2ad2d99967) |
| Comment by Githook User [ 13/Jan/17 ] |
|
Author: {u'username': u'hptabster', u'name': u'Jonathan Abrahams', u'email': u'jonathan@mongodb.com'}Message: |
| Comment by Jonathan Abrahams [ 18/Nov/16 ] |
|
I think we should not blacklist tests that consume resource such that they cannot run concurrently. Those tests should still run in burn-in, but as a single job, so maybe we can have burn-in-concurrent and burn-in. |