[SERVER-25504] burn_in_tests.py should show better diagnostic information on invalid new test configurations Created: 09/Aug/16 Updated: 06/Dec/22 Resolved: 29/Oct/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | 3.3.10 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Michael Grundy | Assignee: | [DO NOT ASSIGN] Backlog - Decision Automation Group (DAG) (Inactive) |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | dag, tig-burnin | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Decision Automation Group
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Steps To Reproduce: | Trigger exception handler in create_test_membership_map() |
||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 0 | ||||||||||||
| Description |
|
When burn_in_tests.py encounters a jstest that has changed but isn't configured to run in any suite it doesn't handle the exception for "Unrecognized jstest". Instead of throwing an exception and exiting it should fail gracefully with an obvious error message containing enough information for an engineer to easily diagnose. |
| Comments |
| Comment by David Bradford (Inactive) [ 29/Oct/18 ] |
|
This error message was improved in |