Repository navigation
Description
Activity for August 2026
Suggested Actions for Maintainer
No suggested actions at this time.
Energy Efficiency Backlog
| Priority | Focus Area | Opportunity | Estimated Impact |
|---|---|---|---|
| LOW | Code-Level | TestExecutionManager MethodLevel parallel array-per-test in setup |
One-time setup cost |
| LOW | Code-Level | TestContextImplementation.SanitizeName: Array.IndexOf per char |
Only on first TestTempDirectory access |
| LOW-MEDIUM | Code-Level | Executable-condition analyzer (#10634) recursive walk | Compile-time/IDE-only, bounded by Roslyn's own incremental model — disposition: not a viable target |
| LOW | Code-Level | VideoProduction.cs ProducePerTestVideosAsync O(tests×segments) overlap scan |
Runs once at end-of-run (cold path), not worth changing |
| LOW | Test Infra | test/Utilities/Microsoft.Testing.TestInfrastructure: regex-on-error-retry, tiny-collection LINQ, bounded retry-delete loops |
All cold/low-frequency/negligible-scale; not worth a PR |
Repo continues to be actively self-optimized by maintainers/Copilot coding agent. No new HIGH/MEDIUM opportunities identified this run — Microsoft.Testing.Extensions.AzureFoundry, Microsoft.Testing.Platform.AI, and Microsoft.Testing.Extensions.OpenTelemetry all reviewed, no genuine hot-path issues found (measurement/tag-forwarding code shows explicit prior optimization attention). Reviewed ~24 commits since last run — all maintainer/Copilot-authored feature/infra/dependency-bump/localization work, no new hot-path efficiency regressions spotted.
Discovered Commands
| Command | Purpose |
|---|---|
./build.sh |
Full restore + build |
./build.sh -test |
Run unit tests |
./build.sh -pack |
Build + produce NuGet packages |
./build.sh -pack -test -integrationTest |
Full pipeline incl. acceptance tests |
Performance runner: test/Performance/MSTest.Performance.Runner/. Nightly timing workflow: .github/workflows/perf-timing-nightly.yml (Phase 1 artifact collection + Phase 2 regression detection, merged via PR #10720).
Run History
2026-08-31 21:44 UTC - Run
- 🔍 Scanned
Microsoft.Testing.Extensions.AzureFoundry,Microsoft.Testing.Platform.AI, andMicrosoft.Testing.Extensions.OpenTelemetry(previously flagged priority areas) — no HIGH/MEDIUM opportunities; chat-client providers are cold/startup-only paths, OpenTelemetry measurement/tag-forwarding code already shows explicit prior optimization (untagged fast-path, array-reuse comments). - 💬 Task 5: re-checked [RFC] Agent/LLM-efficient test output for Microsoft.Testing.Platform #8824 — new maintainer comment since last review (2026-07-14) was a state-reconciliation summary, not a new ask; no action needed from us. No other open efficiency/performance-labeled issues found needing comment.
- 🔧 Task 4: confirmed no open
[efficiency-improver]-prefixed PRs — nothing to maintain. - 📊 No new PR created — pure monitoring pass; reviewed ~24 commits since last run (2026-08-30), all maintainer/Copilot-authored feature/infra/dependency-bump/localization work, no new hot-path efficiency regressions or opportunities spotted.
2026-08-30 21:41 UTC - Run
- 🔍 Scanned
src/Adapter/MSTestAdapter.PlatformServices(drift re-check since 2026-08-21) andtest/Utilities/Microsoft.Testing.TestInfrastructure(first-time scan, 29 files) — no HIGH/MEDIUM opportunities; only LOW-priority cold/low-frequency items found (error-retry regex, tiny-collection LINQ, bounded retry-delete loops, dev-only debugger polling). - 💬 Task 5: checked [RFC] Agent/LLM-efficient test output for Microsoft.Testing.Platform #8824 — no new comments since 2026-07-14, not re-engaged; no other open efficiency/performance-labeled issues found needing comment.
- 🔧 Task 4: confirmed all ~31 historical
[efficiency-improver]-titled PRs are closed — no open PRs to maintain. - 📊 No new PR created — pure monitoring pass; repo commit volume very low since last run (only dependency/localization/infra commits).
2026-08-29 22:12 UTC - Run
- 🔍 Scanned
Microsoft.Testing.Extensions.Telemetry(OpenTelemetry) andMSTest.Analyzers(non-CodeFix analyzers) — no genuine HIGH/MEDIUM opportunities found; telemetry ingestion is already batched/async, analyzer symbol lookups already cached viaConcurrentDictionary. - 💬 Task 5: no open efficiency/performance/energy-labeled issues found requiring comment.
- 🔧 Task 4: no open
[efficiency-improver]-prefixed PRs exist — nothing to maintain. - 📊 No new PR created — pure monitoring pass; repo commit volume very low since last run (1 commit, Cache generated acceptance test builds #10811 CI/build-cache infra, outside our focus areas).
2026-08-28 22:16 UTC - Run
- 🔍 Scanned
Microsoft.Testing.Extensions.VideoRecorder(for similar O(n2) patterns near the recently-fixed pruning bug), the sole new commit a7ea9ab ("Authorize extension pipes for sandboxed test hosts"), andHosts//ServerMode/— no genuine HIGH/MEDIUM opportunities found. - ✅ Confirmed our prior run's finding (VideoRecorder pruning O(n2)) was independently fixed by maintainer PR Cache failed-test windows during video pruning #10837 "Cache failed-test windows during video pruning" (merged 2026-08-28, resolves [efficiency-improver] Cache failed-test windows incrementally in VideoRecorderSessionHandler pruning #10823).
2026-08-26 22:33 UTC - Run
- 🔍 Reviewed ~53 commits since 2026-08-25: all maintainer/Copilot-authored feature/infra/dedup/localization/dependency-bump work; no new hot-path efficiency regressions spotted.
- 🔍 Scanned JUnitReport, GitHubActionsReport, and newly-split AzureDevOpsReport client — no genuine hot-path inefficiencies found.
2026-08-25 21:49 UTC - Run
- ✅ Resolved: issue [efficiency-improver] Add regression gating to nightly PlainProcess performance timing pipeline #10549 (Task 6's regression-gating proposal, open since 2026-08-10) closed via maintainer PR Add nightly performance regression detection #10720 "Add nightly performance regression detection".
- 🔍 Reviewed ~40 commits since 2026-08-24: all maintainer/Copilot-authored feature/infra/dedup/test work; no new hot-path efficiency regressions spotted.
2026-08-19 - Run
- 🔧 Created PR (draft,
efficiency/cache-regex-matches): cache compiled Regex inAssert.MatchesRegex/DoesNotMatchRegex— ~300x per-call reduction (5.12μs → 0.016μs). Superseded by maintainer PR Cache regex assertion patterns safely #10661 with a more thorough FIFO-bounded cache.
2026-08-18 - Run
- 🔧 Created PR (draft,
efficiency/trx-reparse-point-syscall): combinedDirectory.Exists+File.GetAttributesinto one syscall in TRX reparse-point ancestor walk.> 🤖 Automated content by GitHub Copilot. Generated by the Efficiency Improver workflow. · auto · 105.3 AIC · ⌖ 3.82 AIC · ⊞ 20.5K · [◷]( · ◷)
Add this agentic workflow to your repo
To install this agentic workflow, run
gh aw add githubnext/agentics/workflows/efficiency-improver.md@main
Closing out August — moving to a new September tracking issue since the month has rolled over.> 🤖 Automated content by GitHub Copilot. Generated by the Efficiency Improver workflow. · auto · 81.2 AIC · ⌖ 3.38 AIC · ⊞ 20.5K · [◷]( · ◷)
Add this agentic workflow to your repo
To install this agentic workflow, run
gh aw add githubnext/agentics/workflows/efficiency-improver.md@main
Activity
Evangelink commentedon Aug 3, 2026
Reviewed and cleared, the same way #10381 / #9604 were cleared by #10384.
First, a consolidation note: this issue and #10377 are both "Monthly Activity 2026-08". The 2026-08-01 run created #10377 and the 2026-08-02 run created this one instead of updating it, and the two carry different backlogs - each dropped two rows the other kept. #10377 is closed as a duplicate and its unique rows are merged into the list below, so nothing is lost.
Consolidated August backlog and disposition
GetTestInitialInfo:Properties.OfType<TestMetadataProperty>()inside a yield iteratorDynamicDataShouldBeValidAnalyzer:candidateMethods.Where(...).ToImmutableArray()per[DynamicData]attributeTerminalTestReporter.TotalTests:_assemblies.Values.Sum()"on every display refresh"GetSuiteNamewalks the bag separately fromSetResultDetailsTestExecutionManagerMethodLevel parallel:Select(t => new[] { t })What #10397 changes
GetTestInitialInfowalked the property bag three times per test on the OTel path - twoSingleOrDefault<T>()calls plusOfType<TestMetadataProperty>(), the last of which materializes aTProperty[]purely to enumerate it once. It now uses the struct enumerator: one pass for the two singleton properties, one for the metadata. The metadata pass stays separate on purpose - those tags are emitted after the identifier and file-location blocks, and buffering them to collapse into a single pass would reintroduce exactly the allocation being removed. The duplicate-property detectionSingleOrDefaultgave for free is kept explicitly (matching the guardsSetResultDetailsalready has right below it) and is now covered by tests; it is reachable, sincePropertyBagonly rejects duplicate property instances, not two distinct instances of the same type.DynamicDataShouldBeValidAnalyzer.TryGetMemberCorescanned the members twice and allocated anImmutableArrayper attribute; a singleswitchnow resolves the property, the first method and the more-than-one-method case in one pass. The backlog called this "compile-time only" - worth noting analyzers re-run on every keystroke in the IDE, so it isn't.Why the other four are dropped
TerminalTestReporter.TotalTests- the entry says theSum()runs on every display refresh. It doesn't.TotalTestshas no callers insrc/at all; the only references are inTerminalTestReporterTests. Progress rendering (TerminalTestReporter.Formatting.cs) and the summary (TerminalTestReporter.Summary.cs,TestDiscovery.cs) compute their own totals and never touch this property. There is no hot path here to optimize.GetSuiteName- folding it into theSetResultDetailspass would require reordering_testCaseResultCount.Addrelative to the span tagging (changing what is recorded when a malformed bag throws) and buffering the metadata/artifact properties. It is a non-allocating linked-list walk over a handful of properties, on an opt-in path. Not a good trade.TestExecutionManagerMethodLevelSelect(t => new[] { t })- the queue element type isIEnumerable<UnitTestElement>, so dropping the one-element array means changing that type and the class-level branch next to it. One-time setup cost of one small array per test, on a path that then allocates a queue node per entry anyway.That leaves the August efficiency backlog empty.
Two process issues worth fixing in the workflow
[efficiency]and [efficiency-improver] Monthly Activity 2026-08 #10377 carries[[efficiency]]; [perf-improver] Monthly Activity 2026-08 #10381 carries[performance]and [perf-improver] Monthly Activity 2026-07 #9604 carries[area/performance,type/automation]andperformance. These come from a labels string being applied instead of a list. The repo has picked up 13 such junk labels across roughly 70 issue associations ([type/tech-debt],[type/tech-debt,type/automation],[type/automation,type/test-gap],[type/test-gap,[testing],[performance],[efficiency],[[efficiency]],[area/performance,performance,efficiency). I have removed them from the four improver tracking issues; the label definitions themselves still need deleting, which is a destructive repo-wide change I have left to a maintainer.github-actions commentedon Aug 8, 2026
2026-08-08 21:55 UTC - Run
a6010ba, dependency/skills bump) — no efficiency-relevant hot-path code changes..github/workflows/perf-timing-nightly.ymlcollects nightly PlainProcess timing viaMSTest.Performance.Runneron Windows+Linux, artifact-only (no regression gating yet) — a candidate for a future Task 6 follow-up if maintainers want automated regression detection.(Note: this run's
update_issuequota was already used to close the duplicate #10419, so this run's summary is appended as a comment rather than a full body rewrite. The Suggested Actions item for closing #10419 can be removed on the next full body update.)Add this agentic workflow to your repo
To install this agentic workflow, run