User/esg/phase0 fix regression pr

[esgama107]

Fix regression detection: enable Method 2, add key mapping, restore summary columns

TL;DR

Regression detection has been non-functional due to compounding bugs. This PR fixes them. No algorithm changes — just wiring fixes to restore what was already implemented.

---

Background

After a refactored in test IDs from the old format (tput-up-quic) to the new scenario-based format (scenario-upload-quic). This rename broke the key lookup between the regression JSON and the consumer (secnetperf-helpers.psm1), and the regression columns were commented out with:

# TODO: Regression detection is heinously broken. Let's reduce the noise.

Investigation revealed compounding bugs, not just the key mismatch:

Bug: quic.yml — Method 2 never invoked

The regression-detection job runs python regression.py with no --featureint flag. The argparse default is 1, so singular_datapoint_method() is what runs in production. The working sliding_window() method (featureint=2) was implemented but never enabled.

Fix: Pass --featureint 2 to use the sliding window method.

Bug: Test ID key mismatch (3 naming conventions)

The DB, the watermark, and the consumer all use different key formats:

Consumer Key	Old DB ID	New DB ID
upload-quic	tput-up-quic	scenario-upload-quic
download-quic	tput-down-quic	scenario-download-quic
hps-quic	hps-conns-100-quic	scenario-hps-quic
rps-quic	rps-up-512-down-4000-quic	scenario-rps-quic
...	...	...

0/12 consumer keys match any DB key format. The consumer wraps the lookup in try/catch and silently returns "no regression" when the key is missing.

Fix: Added DB_TO_CONSUMER_KEY mapping dict in regression.py and a remap_to_consumer_keys() function that translates DB IDs → consumer keys before writing the JSON output. This avoids touching either the DB schema or the consumer code.

Uncomment Regression columns

The summary table doesn't display it. The CumulativeResult, Baseline, and BestResult columns, let' review the data with the new key-mappings.

---

Changes

File	What changed
pipeline/regression.py	Added DB_TO_CONSUMER_KEY mapping (26 entries), remap_to_consumer_keys() function, applied remap before JSON output in sliding_window().
.github/workflows/quic.yml	regression-detection job now fetches regression.py from main via wget and runs with --featureint 2.
.github/workflows/generate-summary.ps1	Uncommented regression columns (Avg, Noise, Best Ever) in all 4 summary row builders (throughput, download, HPS, RPS) and restored matching table headers.

---

Discovery: sqlite branch architecture concern

During investigation, we discovered an important architectural detail that affects how changes to regression.py take effect:

The regression-detection job checks out ref: sqlite, not main. This means:

• The sqlite branch has its own copy of regression.py (the old unmaintained version)
• The save-test-results job already solves this for sql.py by fetching it from main via wget

This PR adopts the same pattern for regression.py:

- name: Fetch regression.py from main branch
  run: wget https://raw.githubusercontent.com/microsoft/netperf/main/pipeline/regression.py -O regression.py
- run: python regression.py --featureint 2

Branch role summary:

Branch	Purpose	What gets committed
main	Source of truth for code	Pipeline scripts, workflows, dashboard source
sqlite	Data + generated artifacts	netperf.sqlite, regression.json, watermark_regression.json, full_latencies/
deploy	Dashboard deployment	Flattened JSON files for the React dashboard

The stale regression.py on sqlite remains but is now bypassed by the wget.

---

Questions for the team

1. Should regression.py be removed from the sqlite branch entirely? Now that we fetch it from main, the sqlite copy is dead code that could cause confusion. Same question for any other .py files on sqlite.

[esgama107]

@microsoft-github-policy-service agree company="Microsoft"

…

________________________________ From: microsoft-github-policy-service[bot] ***@***.***> Sent: Friday, March 27, 2026 12:33 To: microsoft/netperf ***@***.***> Cc: Erick Javier Sanchez Gama (He/Him) ***@***.***>; mention ***@***.***> Subject: Re: [microsoft/netperf] User/esg/phase0 fix regression pr (PR #827) [https://avatars.githubusercontent.com/in/95686?s=20&v=4]microsoft-github-policy-service[bot] left a comment (microsoft/netperf#827)<#827?email_source=notifications&email_token=BFTQ6GTJTTH4SEQEYYXMVHD4S3JPRA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMJUGQ3TSNZWGEZ2M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJNLQOJPWG33NNVSW45C7N5YGK3S7MNWGSY3L#issuecomment-4144797613> @esgama107<https://github.com/esgama107> please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information. @microsoft-github-policy-service agree [company="{your company}"] Options: * (default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer. @microsoft-github-policy-service agree * (when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer. @microsoft-github-policy-service agree company="Microsoft" Contributor License Agreement Contribution License Agreement This Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”), and conveys certain license rights to Microsoft Corporation and its affiliates (“Microsoft”) for Your contributions to Microsoft open source projects. This Agreement is effective as of the latest signature date below. 1. Definitions. “Code” means the computer software code, whether in human-readable or machine-executable form, that is delivered by You to Microsoft under this Agreement. “Project” means any of the projects owned or managed by Microsoft and offered under a license approved by the Open Source Initiative (www.opensource.org<http://www.opensource.org/>). “Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to any Project, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Project for the purpose of discussing and improving that Project, but excluding communication that is conspicuously marked or otherwise designated in writing by You as “Not a Submission.” “Submission” means the Code and any other copyrightable material Submitted by You, including any associated comments and documentation. 2. Your Submission. You must agree to the terms of this Agreement before making a Submission to any Project. This Agreement covers any and all Submissions that You, now or in the future (except as described in Section 4 below), Submit to any Project. 3. Originality of Work. You represent that each of Your Submissions is entirely Your original work. Should You wish to Submit materials that are not Your original work, You may Submit them separately to the Project if You (a) retain all copyright and license information that was in the materials as You received them, (b) in the description accompanying Your Submission, include the phrase “Submission containing materials of a third party:” followed by the names of the third party and any licenses or other restrictions of which You are aware, and (c) follow any other instructions in the Project’s written guidelines concerning Submissions. 4. Your Employer. References to “employer” in this Agreement include Your employer or anyone else for whom You are acting in making Your Submission, e.g. as a contractor, vendor, or agent. If Your Submission is made in the course of Your work for an employer or Your employer has intellectual property rights in Your Submission by contract or applicable law, You must secure permission from Your employer to make the Submission before signing this Agreement. In that case, the term “You” in this Agreement will refer to You and the employer collectively. If You change employers in the future and desire to Submit additional Submissions for the new employer, then You agree to sign a new Agreement and secure permission from the new employer before Submitting those Submissions. 5. Licenses. * Copyright License. You grant Microsoft, and those who receive the Submission directly or indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license in the Submission to reproduce, prepare derivative works of, publicly display, publicly perform, and distribute the Submission and such derivative works, and to sublicense any or all of the foregoing rights to third parties. * Patent License. You grant Microsoft, and those who receive the Submission directly or indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license under Your patent claims that are necessarily infringed by the Submission or the combination of the Submission with the Project to which it was Submitted to make, have made, use, offer to sell, sell and import or otherwise dispose of the Submission alone or with the Project. * Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement. No additional licenses or rights whatsoever (including, without limitation, any implied licenses) are granted by implication, exhaustion, estoppel or otherwise. 1. Representations and Warranties. You represent that You are legally entitled to grant the above licenses. You represent that each of Your Submissions is entirely Your original work (except as You may have disclosed under Section 3). You represent that You have secured permission from Your employer to make the Submission in cases where Your Submission is made in the course of Your work for Your employer or Your employer has intellectual property rights in Your Submission by contract or applicable law. If You are signing this Agreement on behalf of Your employer, You represent and warrant that You have the necessary authority to bind the listed employer to the obligations contained in this Agreement. You are not expected to provide support for Your Submission, unless You choose to do so. UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING, AND EXCEPT FOR THE WARRANTIES EXPRESSLY STATED IN SECTIONS 3, 4, AND 6, THE SUBMISSION PROVIDED UNDER THIS AGREEMENT IS PROVIDED WITHOUT WARRANTY OF ANY KIND, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY OF NONINFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE. 2. Notice to Microsoft. You agree to notify Microsoft in writing of any facts or circumstances of which You later become aware that would make Your representations in this Agreement inaccurate in any respect. 3. Information about Submissions. You agree that contributions to Projects and information about contributions may be maintained indefinitely and disclosed publicly, including Your name and other information that You submit with Your Submission. 4. Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, and the parties consent to exclusive jurisdiction and venue in the federal courts sitting in King County, Washington, unless no federal subject matter jurisdiction exists, in which case the parties consent to exclusive jurisdiction and venue in the Superior Court of King County, Washington. The parties waive all defenses of lack of personal jurisdiction and forum non-conveniens. 5. Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and supersedes any and all prior agreements, understandings or communications, written or oral, between the parties relating to the subject matter hereof. This Agreement may be assigned by Microsoft. — Reply to this email directly, view it on GitHub<#827?email_source=notifications&email_token=BFTQ6GTJTTH4SEQEYYXMVHD4S3JPRA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMJUGQ3TSNZWGEZ2M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJNLQOJPWG33NNVSW45C7N5YGK3S7MNWGSY3L#issuecomment-4144797613>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BFTQ6GVHAZHKBQP4LGKB54L4S3JPRAVCNFSM6AAAAACXCOLW6GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DCNBUG44TONRRGM>. You are receiving this because you were mentioned.Message ID: ***@***.***>