[weekly-issue-activity] Weekly Summary - 2026-08-03 #10393
Closed
Replies: 1 comment
|
This discussion has been marked as outdated by Weekly Issue Summary. A newer discussion is available at Discussion #10536. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
📊 Weekly Overview
During the week of Jul 27 – Aug 2, 2026, 45 issues were opened and 34 were closed, leaving a net of +11 new open items and an estimated running total of ~76 open issues. Compared to the prior week (Jul 20–26), opening activity held nearly steady (48 → 45), but closures dropped significantly (62 → 34), meaning the backlog grew slightly. The bulk of this week's activity continues to be automation-generated issues from agentic workflows (30 of 45 opened by
github-actions[bot]), covering code quality, performance, test-gap detection, and tech-debt — with a handful of genuine bug reports and feature requests from human contributors.📈 Issue Activity Trends
Weekly Activity Patterns
Issue volume has moderated from the W01 peak (86 opened) and is settling into the 38–57 range over the past 5 weeks. Opened and closed counts have been remarkably balanced overall — the running open total has stayed between 54 and 79 across all 12 weeks, indicating healthy throughput. W10 (Jul 20) saw the highest closure week (62) which brought the backlog down sharply; W11 reversed that with closures falling to 34.
Resolution Time Analysis
The vast majority of issues close within a day (median 0.7 days), driven by the high volume of automation-generated issues that are resolved quickly. The average is pulled up by occasional long-lived issues. Spikes around Jul 11 and Jul 17 (avg ~6–7 days) reflect batches that took a few extra days to close. The last two days of July show a slight uptick (Aug 1–2: avg 7–13 days) as some human-filed issues landed just before the weekend.
🔑 Key Trends
github-actions[bot]via agentic workflows for test-gap detection, performance improvements, tech-debt tracking, and code simplification — a consistent pattern across all 12 weeks.[Retry]discarding attempts, message bus drain, TRX artifact gaps, Azure DevOps extension crash), feature requests, and infrastructure (OneLocBuild blockage, vendored-sync drift).type/automation(29),type/tech-debt(15), andtype/test-gap(11) are the top three labels, reflecting the team's investment in automated quality tooling.[Retry]attempts are discarded before they reach the platform, so in-process retries are invisible everywhere #10292,--retry-failed-testsleaves only the last attempt's report in the results directory, so TRX/CTRF/JUnit under-report the run #10293,--publish-azdo-test-resultscreates one Azure DevOps test run per--retry-failed-testsattempt instead of one run per build #10360) all concern--retry-failed-testsbehavior — MSTest retry attempts being discarded, incomplete reports from the retry extension, and one Azure DevOps run created per retry attempt instead of per build.📋 Summary Statistics
Full Issue List — Week of Jul 27–Aug 2 (45 issues)
@github-actions][vendored-sync]platform-llm-environment-detector drift —area-vendored-syncgh aw compilesilently corrupts two pinned actions in generated.lock.ymlfiles #10258 [@Evangelink] Localgh aw compilesilently corrupts pinned actions in generated.lock.yml—area/infrastructurearea/agentic-workflows@Evangelink] Add analyzer and telemetry support for[DependsOn]—type/tech-debt@github-actions][perf-improver]perf: use GetUpperCaseName in InternalSyncLog —area/performancetype/automation@picolino] Add option to include exception messages in Microsoft.Testing.Extensions —area/mtp-extensions@github-actions][file-diet]Refactor TestContextImplementation.cs (988 lines) —type/tech-debttype/automation@github-actions] Analyzer coverage gaps in the Condition Attribute ecosystem —type/tech-debttype/automation@github-actions][test-improver]Add edge-case tests for SharedFileSystemPathInTestAnalyzer —type/test-gaptype/automation[Retry]attempts are discarded before they reach the platform, so in-process retries are invisible everywhere #10292 [@Evangelink] MSTest[Retry]attempts discarded before reaching the platform —area/mtparea/mstest--retry-failed-testsleaves only the last attempt's report in the results directory, so TRX/CTRF/JUnit under-report the run #10293 [@Evangelink]--retry-failed-testsleaves only last attempt's report in results dir —area/mtp-extensions@github-actions][file-diet]Refactor TestDependencyGraph.cs (967 lines) —type/tech-debttype/automation@github-actions] Repository Quality: MSTest Retry Attribute Analyzer Coverage Gaps —type/tech-debttype/automation@github-actions][test-improver]Add edge-case tests for SharedFileSystemPathInTestAnalyzer (round 2) —type/test-gaptype/automation@github-actions][duplicate-code]Duplicate Attribute-Query Methods in IReflectionOperations —type/tech-debttype/automation@Evangelink] Complete MSTEST0077 test coverage:[DoNotParallelize]opt-out —type/test-gap@Evangelink] Browser/WASI console output device silently discards test/session files —area/mtparea/terminal-reporter@Evangelink] TRX per-test file artifact not emitted as ResultFile on net462 —area/trxtype/test-gap@Evangelink] Azure DevOps report extension throws PlatformNotSupportedException on browser —area/mtp-extensions@Evangelink] Complete MSTEST0077 test coverage: remaining File.* allowlist entries —type/test-gap@github-actions][code-simplifier]Simplify array initialization in TestDependencyGraph —type/tech-debttype/automation@github-actions][perf-improver]Cache summary text in GetSingleActiveOrSummaryTask —area/performancetype/automation@Evangelink] Official build blocked: OneLocBuild GitHub check-in rejected —area/localizationarea/infrastructure@github-actions][file-diet]Refactor TrxResultStreamingStore —type/tech-debttype/automation@github-actions] Repository Quality: Warning Suppression Technical Debt Audit —type/tech-debttype/automation@github-actions][test-improver]Add edge-case tests for CultureMutationUnderParallelizationAnalyzer —type/test-gaptype/automation@ViktorHofer] Allow passing environment variables to test process from InvokeTestingPlatform — (no labels)@github-actions][code-simplifier]Simplify null-filtering and null-conditional patterns —type/tech-debttype/automationCtrfReportMerger.cs(777 lines) into focused modules #10347 [@github-actions][file-diet]Refactor CtrfReportMerger.cs (777 lines) —type/tech-debttype/automation@github-actions] Repository Quality: Assert API Interpolated String Handler Coverage Gap —type/tech-debttype/automation@github-actions][test-improver]Add edge-case tests for CurrentDirectoryMutationUnderParallelizationAnalyzer —type/test-gaptype/automation@Evangelink] Message bus is never drained or disabled when a run is cancelled — (no labels)--publish-azdo-test-resultscreates one Azure DevOps test run per--retry-failed-testsattempt instead of one run per build #10360 [@DanielGilOrtiz]--publish-azdo-test-resultscreates one Azure DevOps test run per retry attempt —needs/triageis not nullinstead of!= nullin new files from PR #10353 #10361 [@github-actions][code-simplifier]Useis not nullinstead of!= nullin new files —type/tech-debttype/automation@github-actions][perf-improver]Cache TestMethodIdentifierProperty per TestMethod —area/performancetype/automation@github-actions][file-diet]Refactor TerminalTestReporter.Summary.cs (715 lines) —type/tech-debttype/automation@github-actions] Repository Quality: NuGet Package Discoverability and Metadata Completeness —type/tech-debttype/automation@github-actions][test-improver]Add fixture-method edge-case tests for CurrentDirectoryMutationUnderParallelizationAnalyzer —type/test-gaptype/automation@github-actions][perf-improver]Cache TestMethodIdentifierProperty for parameterless tests —area/performancetype/automation@github-actions][efficiency-improver]Monthly Activity 2026-08 —area/performancetype/automation@github-actions][test-improver]Add multiple-provider edge cases for MSTEST0081 —type/test-gaptype/automation@github-actions][perf-improver]Monthly Activity 2026-08 —area/performancetype/automation@github-actions][efficiency-improver]Monthly Activity 2026-08 —area/performancetype/automation@github-actions][test-improver]Add edge-case tests for MSTEST0054 and MSTEST0044 —type/test-gaptype/automation@github-actions][test-improver]Monthly Activity 2026-08 —type/test-gaptype/automation@Evangelink] Add new TerminalTestReporter partials to dotnet/sdk vendored-files manifest — (no labels)💡 Recommendations for Upcoming Week
[Retry]attempts are discarded before they reach the platform, so in-process retries are invisible everywhere #10292,--retry-failed-testsleaves only the last attempt's report in the results directory, so TRX/CTRF/JUnit under-report the run #10293,--publish-azdo-test-resultscreates one Azure DevOps test run per--retry-failed-testsattempt instead of one run per build #10360): Three interrelated issues about--retry-failed-testsbehavior landed this week. Grouping them for a focused fix in one PR would prevent them from aging into tech debt and improve the retry reporting story end-to-end.needs/triagequeue:--publish-azdo-test-resultscreates one Azure DevOps test run per--retry-failed-testsattempt instead of one run per build #10360 (AzDO retry run count) is from an external contributor and should be triaged before it gets buried. Check the broaderneeds/triagebacklog (TRX default output directory changed between MSTest.Sdk 4.2.3 and 4.3.0? #10116, Analyzer to detect not awaited async calls in a test case #9816, Replacement for deprecated MSTestDiscoverer #9809) for similarly stale items.github-actions[bot]this week, it's worth a periodic sweep of open automation issues to close any that were superseded or are no longer actionable.@ViktorHofer(allow env vars in InvokeTestingPlatform), this feature request has no labels and no triage assignment; tagging it and assigning a milestone would help it not fall through the cracks.Add this agentic workflow to your repo
To install this agentic workflow, run
All reactions