[weekly-issue-activity] Weekly Summary - 2026-06-01

[Evangelink]

📊 Weekly Overview

During the week of May 26 – June 1, 2026, 12 new issues were opened in microsoft/testfx, compared to 4 issues the previous week — a notable 3× increase. The uptick is largely driven by automated agentic workflows (duplicate-code detectors, performance improvers, test-gap finders) that produced a batch of issues as part of monthly May 2026 activity runs, alongside a genuine user-reported bug and a new RFC. The repository currently has 87 open issues in total.

⚠️ Data note: The GitHub API for closed issues timed out repeatedly during this run. Closed-issue counts and resolution time data are unavailable for this summary. Charts reflect open-issue counts and age distributions only.

📈 Issue Activity Trends

Weekly Activity Patterns

Issue creation picked up sharply this week relative to the prior period, with 12 issues opened versus 4 the week before. The spike is concentrated on May 26–31 and corresponds to automated monthly activity runs. The running open total stands at 87, suggesting a modest but steady accumulation trend.

Resolution Time Analysis

Because closed-issue data was unavailable, this chart shows the age of currently-open issues by their creation date. Older creation dates naturally show higher ages (issues still unresolved). Recent issues (this week) have low ages, which is expected. No improvement or degradation in resolution speed can be confirmed without closed-issue data.

🔑 Key Trends

• Automated issue generation dominates this week: ~8 of 12 new issues were created by automated workflows ([duplicate-code], [perf-improver], [efficiency-improver], [test-improver], [aw]), reflecting the May 2026 monthly batch runs.
• Tech-debt and automation labels are most active: type/automation and type/tech-debt account for the majority of labeled issues in the past 30 days (10 and 3 issues respectively).
• Agentic workflow issues need attention: Three agentic-workflows labeled issues this week include two failure reports ([aw] Adhoc QA failed, [aw] Build Failure Analysis failed) that likely require investigation.
• One genuine user bug filed: Issue --list-tests json produces no JSON output when running in --server mode #8661 (--list-tests json produces no JSON output in certain scenarios) has no labels yet and needs triage.
• One community RFC submitted: [RFC] Server-initiated session cancellation in the dotnet test IPC protocol #8691 proposes server-initiated session cancellation in the dotnet test protocol — a significant MTP area proposal awaiting triage.

📋 Summary Statistics

Metric	This Week	Last Week	Trend
Issues Opened	12	4	↑
Issues Closed	N/A	N/A	—
Currently Open	87	~79 (est.)	↑
Avg Close Time	N/A	N/A	—

Full Issue List — This Week (May 26 – June 1, 2026)

1. [duplicate-code] Duplicate IPC Message Serialization/Read Logic in NamedPipeClient and NamedPipeServer #8723 — [duplicate-code] Duplicate IPC Message Serialization/Read Loop Logic in NamedPipeClient/NamedPipeServer (labels: type/tech-debt, type/automation)
2. [duplicate-code] Duplicate Code: ICommandLineOptionsProvider Boilerplate Repeated Across 10+ Implementations #8710 — [duplicate-code] Duplicate Code: ICommandLineOptionsProvider Implementations (labels: type/tech-debt, type/automation)
3. [aw] Adhoc QA failed #8703 — [aw] Adhoc QA failed (labels: agentic-workflows)
4. [test-improver] Monthly Activity 2026-05 #8695 — [test-improver] Monthly Activity 2026-05 (labels: type/test-gap, type/automation)
5. [efficiency-improver] Monthly Activity 2026-05 #8693 — [efficiency-improver] Monthly Activity 2026-05 (labels: area/performance, type/automation)
6. [RFC] Server-initiated session cancellation in the dotnet test IPC protocol #8691 — [RFC] Server-initiated session cancellation in the dotnet test protocol (labels: needs/triage, type/rfc, area/mtp)
7. [aw] Build Failure Analysis failed #8685 — [aw] Build Failure Analysis failed (labels: agentic-workflows)
8. [perf-improver] Monthly Activity 2026-05 #8684 — [perf-improver] Monthly Activity 2026-05 (labels: area/performance, type/automation, performance)
9. [duplicate-code] Duplicate Code Detector - Issue Group #8673 — [duplicate-code] Duplicate Code Detector - Issue Group (labels: type/tech-debt, type/automation)
10. [aw] Detection Runs #8667 — [aw] Detection Runs (labels: agentic-workflows)
11. --list-tests json produces no JSON output when running in --server mode #8661 — --list-tests json produces no JSON output when running in certain scenarios (labels: none — needs triage)
12. Async methods are not display/reported correctly in visual studio when displaying code coverage ? #8616 — Async methods are not displayed/reported correctly in Visual Studio (labels: needs/triage, external/code-coverage, type/bug)

💡 Recommendations for Upcoming Week

1. Triage --list-tests json produces no JSON output when running in --server mode #8661 and Async methods are not display/reported correctly in visual studio when displaying code coverage ? #8616 — both are user-reported issues without complete label coverage; assign owners and priority.
2. Review the RFC [RFC] Server-initiated session cancellation in the dotnet test IPC protocol #8691 — server-initiated session cancellation is architecturally impactful; route to the MTP area owners for early feedback.
3. Investigate agentic workflow failures ([aw] Adhoc QA failed #8703, [aw] Build Failure Analysis failed #8685) — two consecutive failures in QA and build-failure analysis suggest a systemic issue with the agentic pipeline that warrants a root-cause investigation.
4. Process the May 2026 batch issues ([duplicate-code] Duplicate Code Detector - Issue Group #8673, [perf-improver] Monthly Activity 2026-05 #8684, [efficiency-improver] Monthly Activity 2026-05 #8693, [test-improver] Monthly Activity 2026-05 #8695, [duplicate-code] Duplicate Code: ICommandLineOptionsProvider Boilerplate Repeated Across 10+ Implementations #8710, [duplicate-code] Duplicate IPC Message Serialization/Read Logic in NamedPipeClient and NamedPipeServer #8723) — these automated issues are ready for developer assignment; prioritize by area (performance, test coverage, tech debt).
5. Enable closed-issue data retrieval — the GitHub API timed out when fetching closed issues, limiting this report. Consider pre-fetching and caching issue data, or using the REST paginated API with smaller page sizes to ensure future summaries include resolution metrics.

Generated by Weekly Issue Summary · sonnet46 1.4M · ◷

Add this agentic workflows to your repo

To install this agentic workflow, run

gh aw add githubnext/agentics/workflows/weekly-issue-activity.md@main

• expires on Jun 8, 2026, 6:27 AM UTC