[SERVER-31424] Speed up or skip key generation when running tests Created: 05/Oct/17 Updated: 30/Oct/23 Resolved: 09/Oct/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication, Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.6.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Misha Tyulenev |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding 2017-10-23 |
| Participants: |
| Description |
|
Since changing ReplicaSetTests to wait until they generate their keys for signing cluster times, the execution time of the replica_sets_WT suite has almost doubled Most of our javascript tests, except for the ones that are explicitly testing the key signing behavior, don't need to be doing the key signing. We should either skip generating keys entirely, or hard code the key we generate in test mode, or some other way win back the lost test execution time for tests that don't need strong keys. |
| Comments |
| Comment by Githook User [ 06/Oct/17 ] |
|
Author: {'email': 'misha@mongodb.com', 'name': 'Misha Tyulenev', 'username': 'mikety'}Message: |