-
Notifications
You must be signed in to change notification settings - Fork 380
Closed
Labels
CriticalKnown Build ErrorOps - ComplianceFirst-responder-style issues handled by the Operations V-Team due to prioritization or urgency levelFirst-responder-style issues handled by the Operations V-Team due to prioritization or urgency level
Description
As seen in recent helix-machines pipelines,
2022-11-07T23:42:20.932Z INFO interval(67) set_abort_after_timer Set the timer's abort_after to 1260 seconds from now: abort_after = 2022-11-08 00:03:20.932918
2022-11-07T23:42:21.051Z ERROR executor(729) _execute_command_in_container Exception: Install pypiwin32 package to enable npipe:// support
2022-11-07T23:42:21.052Z INFO interval(67) set_abort_after_timer Set the timer's abort_after to 180 seconds from now: abort_after = 2022-11-07 23:45:21.052565
This has been consistently occurring since 11/5 with no obvious changes between when it repros and doesn't; I am investigating.
EDIT: This is occurring everywhere in production too so I've added the critical tag and known build error labels
Report
Summary
| 24-Hour Hit Count | 7-Day Hit Count | 1-Month Count |
|---|---|---|
| 0 | 0 | 0 |
Release Note Description
Fix issue with Windows Helix Docker scenarios failing with no logging and '999' exit code (caused by updated pywin32 package)
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
CriticalKnown Build ErrorOps - ComplianceFirst-responder-style issues handled by the Operations V-Team due to prioritization or urgency levelFirst-responder-style issues handled by the Operations V-Team due to prioritization or urgency level