- 
                Notifications
    You must be signed in to change notification settings 
- Fork 15
test(prof)!: fix fuzzer, stop sorting label ids #1026
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
Conversation
| BenchmarksComparisonBenchmark execution time: 2025-04-16 03:36:20 Comparing candidate commit b82f0a6 in PR branch  Found 0 performance improvements and 0 performance regressions! Performance is the same for 52 metrics, 2 unstable metrics. CandidateCandidate benchmark detailsGroup 1
 
 
 Group 2
 
 
 Group 3
 
 
 Group 4
 
 
 Group 5
 
 
 Group 6
 
 
 Group 7
 
 
 Group 8
 
 
 Group 9
 
 
 Group 10
 
 
 Group 11
 
 
 Group 12
 
 
 Group 13
 
 
 BaselineOmitted due to size. | 
| Artifact Size Benchmark Reportaarch64-alpine-linux-musl
 aarch64-unknown-linux-gnu
 libdatadog-x64-windows
 libdatadog-x86-windows
 x86_64-alpine-linux-musl
 x86_64-unknown-linux-gnu
 | 
| Codecov ReportAttention: Patch coverage is  
 Additional details and impacted files@@            Coverage Diff             @@
##             main    #1026      +/-   ##
==========================================
- Coverage   71.56%   71.52%   -0.04%     
==========================================
  Files         339      339              
  Lines       50683    50751      +68     
==========================================
+ Hits        36270    36300      +30     
- Misses      14413    14451      +38     
 🚀 New features to boost your workflow:
 | 
1f5c379    to
    b82f0a6      
    Compare
  
    | A windows job and also the buildx bake job are failing regularly enough I can't get this CI green. I'm going to merge this, I'd still like a review. | 
PROF-11530
What does this PR do?
Fixes #958 tests by:
Label.keyfrom the start (rather than checking later that they are unique, and failing).LabelSetno longer sortsLabelIds so that the input to output order to remains the same.This also:
pubfrom the fuzzer items, since nothing outside the modules uses them (the module isn't public, either). This allows lints likewarn(dead_code)to work.This PR is technically a breaking change; see additional notes.
Motivation
Fuzzer failures were found in CI in
fuzz_add_sample_with_fixed_sample_length.Additional Notes
Since
LabelSetno longer sorts theLabelIds before deduplicating the whole set, you need to be sure that your profiler always adds labels in the same order. The order doesn't matter, what matters is that it's consistent.How to test the change?
Update your code to add labels in the same order every time, and then test as usual (no other changes).