[SERVER-53042] Update Powercycle to support Windows Created: 24/Nov/20 Updated: 29/Oct/23 Resolved: 18/Feb/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Robert Guo (Inactive) | Assignee: | Mikhail Shchatko |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Sprint: | STM 2021-01-25, STM 2021-02-08, STM 2021-02-22 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 36 | ||||||||||||
| Story Points: | 2 | ||||||||||||
| Description |
|
Once we finish all the other work for powercycle, we can come back to fix Windows. The POC was able to successfully run Windows but there is an issue with getting diagnostics data back to the Evergreen machine. We should audit all code paths used by Evergreen and try to make them explicit and consistent with how DSI handles paths. There are about a dozen functions (defined in buildscripts/powercycle/plugins.py) that could interact with paths; debugging will be much easier once we support running powercycle locally outside of the CI. |
| Comments |
| Comment by Githook User [ 18/Feb/21 ] |
|
Author: {'name': 'Mikhail Shchatko', 'email': 'mikhail.shchatko@mongodb.com', 'username': 'MikhailShchatko'}Message: |
| Comment by Brooke Miller [ 01/Feb/21 ] |
|
Pushing this to next sprint in favor of TIG-2827 to un-block perf team. |