[SERVER-46643] eslint running for 30+ minutes in Commit Queue for enterprise only changes Created: 05/Mar/20 Updated: 29/Oct/23 Resolved: 11/Mar/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 4.4.0-rc0, 4.7.0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | David Bradford (Inactive) | Assignee: | David Bradford (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Backport Requested: |
v4.4
|
||||
| Sprint: | DAG 2020-03-23 | ||||
| Participants: | |||||
| Story Points: | 2 | ||||
| Description |
|
We are frequently seeing eslint take over 30 minutes in the commit queue. Looking at recent occurrences of this, it appears to happen for enterprise only changes. My guess is that since there are no changes to the mongo repository, it is linting the entire repository. As a server engineer, AC:
|
| Comments |
| Comment by Githook User [ 11/Mar/20 ] |
|
Author: {'username': 'dbradf', 'name': 'David Bradford', 'email': 'david.bradford@mongodb.com'}Message: (cherry picked from commit ac9caedb40dd0616a10b38db7efdc404052527bb) |
| Comment by Githook User [ 11/Mar/20 ] |
|
Author: {'username': 'dbradf', 'name': 'David Bradford', 'email': 'david.bradford@mongodb.com'}Message: |
| Comment by David Bradford (Inactive) [ 11/Mar/20 ] |