-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix Windows Ctrl-c #31857
Fix Windows Ctrl-c #31857
Conversation
Test changes on VMUse this command from test-infra-definitions to manually test this PR changes on a VM: inv aws.create-vm --pipeline-id=50965491 --os-family=ubuntu Note: This applies to commit 7c940ed |
Regression DetectorRegression Detector ResultsMetrics dashboard Baseline: 68f07c6 Optimization Goals: ✅ No significant changes detected
|
perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
---|---|---|---|---|---|---|
➖ | quality_gate_logs | % cpu utilization | +1.92 | [-1.06, +4.91] | 1 | Logs |
➖ | quality_gate_idle_all_features | memory utilization | +1.86 | [+1.74, +1.98] | 1 | Logs bounds checks dashboard |
➖ | tcp_syslog_to_blackhole | ingress throughput | +0.78 | [+0.71, +0.85] | 1 | Logs |
➖ | uds_dogstatsd_to_api_cpu | % cpu utilization | +0.59 | [-0.13, +1.31] | 1 | Logs |
➖ | file_tree | memory utilization | +0.21 | [+0.09, +0.33] | 1 | Logs |
➖ | quality_gate_idle | memory utilization | +0.08 | [+0.03, +0.12] | 1 | Logs bounds checks dashboard |
➖ | file_to_blackhole_0ms_latency_http2 | egress throughput | +0.02 | [-0.78, +0.82] | 1 | Logs |
➖ | file_to_blackhole_1000ms_latency_linear_load | egress throughput | +0.00 | [-0.46, +0.47] | 1 | Logs |
➖ | tcp_dd_logs_filter_exclude | ingress throughput | +0.00 | [-0.01, +0.01] | 1 | Logs |
➖ | uds_dogstatsd_to_api | ingress throughput | -0.00 | [-0.11, +0.11] | 1 | Logs |
➖ | file_to_blackhole_300ms_latency | egress throughput | -0.01 | [-0.64, +0.62] | 1 | Logs |
➖ | file_to_blackhole_100ms_latency | egress throughput | -0.05 | [-0.77, +0.67] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency | egress throughput | -0.07 | [-0.92, +0.79] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency_http1 | egress throughput | -0.08 | [-0.92, +0.77] | 1 | Logs |
➖ | file_to_blackhole_500ms_latency | egress throughput | -0.17 | [-0.93, +0.60] | 1 | Logs |
➖ | otel_to_otel_logs | ingress throughput | -0.60 | [-1.25, +0.04] | 1 | Logs |
➖ | file_to_blackhole_1000ms_latency | egress throughput | -0.79 | [-1.57, -0.01] | 1 | Logs |
Bounds Checks: ✅ Passed
perf | experiment | bounds_check_name | replicates_passed | links |
---|---|---|---|---|
✅ | file_to_blackhole_0ms_latency | lost_bytes | 10/10 | |
✅ | file_to_blackhole_0ms_latency | memory_usage | 10/10 | |
✅ | file_to_blackhole_0ms_latency_http1 | lost_bytes | 10/10 | |
✅ | file_to_blackhole_0ms_latency_http1 | memory_usage | 10/10 | |
✅ | file_to_blackhole_0ms_latency_http2 | lost_bytes | 10/10 | |
✅ | file_to_blackhole_0ms_latency_http2 | memory_usage | 10/10 | |
✅ | file_to_blackhole_1000ms_latency | memory_usage | 10/10 | |
✅ | file_to_blackhole_1000ms_latency_linear_load | memory_usage | 10/10 | |
✅ | file_to_blackhole_100ms_latency | lost_bytes | 10/10 | |
✅ | file_to_blackhole_100ms_latency | memory_usage | 10/10 | |
✅ | file_to_blackhole_300ms_latency | lost_bytes | 10/10 | |
✅ | file_to_blackhole_300ms_latency | memory_usage | 10/10 | |
✅ | file_to_blackhole_500ms_latency | lost_bytes | 10/10 | |
✅ | file_to_blackhole_500ms_latency | memory_usage | 10/10 | |
✅ | quality_gate_idle | memory_usage | 10/10 | bounds checks dashboard |
✅ | quality_gate_idle_all_features | memory_usage | 10/10 | bounds checks dashboard |
✅ | quality_gate_logs | lost_bytes | 10/10 | |
✅ | quality_gate_logs | memory_usage | 10/10 |
Explanation
Confidence level: 90.00%
Effect size tolerance: |Δ mean %| ≥ 5.00%
Performance changes are noted in the perf column of each table:
- ✅ = significantly better comparison variant performance
- ❌ = significantly worse comparison variant performance
- ➖ = no significant change in performance
A regression test is an A/B test of target performance in a repeatable rig, where "performance" is measured as "comparison variant minus baseline variant" for an optimization goal (e.g., ingress throughput). Due to intrinsic variability in measuring that goal, we can only estimate its mean value for each experiment; we report uncertainty in that value as a 90.00% confidence interval denoted "Δ mean % CI".
For each experiment, we decide whether a change in performance is a "regression" -- a change worth investigating further -- if all of the following criteria are true:
-
Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.
-
Its 90.00% confidence interval "Δ mean % CI" does not contain zero, indicating that if our statistical model is accurate, there is at least a 90.00% chance there is a difference in performance between baseline and comparison variants.
-
Its configuration does not mark it "erratic".
CI Pass/Fail Decision
✅ Passed. All Quality Gates passed.
- quality_gate_idle_all_features, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_idle, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_logs, bounds check lost_bytes: 10/10 replicas passed. Gate passed.
// force initialize siginterrupt with signal in python so it can be overwritten by the agent | ||
// This only effects the windows builds as linux already has the sigint handler initialized | ||
// and thus python will ignore it | ||
Py_InitializeEx(1); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This doesn't seem to actually force anything, since this behavior is what we have today by the default:
This function works like Py_Initialize() if initsigs is 1.
(src)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was just making it more explicit, but can go back the the current implantation.
6633aa7
to
5c31b72
Compare
Package size comparisonComparison with ancestor Diff per package
Decision✅ Passed |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, with one suggestion
/merge |
Devflow running:
|
What does this PR do?
Fixes issue on windows where when running
agent.exe run
you could not ctrl-c. This was caused by pythons usage of the POSIX signal library, which reregisters the Console Handler.Motivation
https://datadoghq.atlassian.net/browse/WINA-467
Allows ctrl-c of the agent.exe command when running it manually.
Describe how you validated your changes
Linuxs:
Windows:
Stop-Service datadogagent
& 'C:\Program Files\Datadog\Datadog Agent\bin\agent.exe' run
Possible Drawbacks / Trade-offs
Currently the reregistering of the console handler is done in the GetPlatformModules function, which means it is reregistered for both when agent is run from service interface and manually with run command.
Additional Notes
This currently reregisters the Console Handler on windows, but because it was changed by python all uses of the go
signal.notify
function will no longer be notified of the console events. Updates to cpython would be needed to preventsignal
library on windows from calling POSIX function on import.