microsoft / microsoft/aspire

[CI Failure] TypeScript SDK Validation fails on both Node 22.x and 24.x for PRs not touching polyglot SDK code

Open
#19,923 1 comment 0 reactions 0 assignees View on GitHub
ci-failure-cause
Dominant language
C#
Stars
6.3k
Forks
991
Avg merge
2d 15h
Merged PRs (30d)
196

Description

## Build Information

Build: https://github.com/microsoft/aspire/actions/runs/33814653161
Build error leg: Tests / No-package tests (regular, Aspire.Hosting.Radius.Tests, Hosting.Radius, Hosting.Radius, tests/Asp... / Hosting.Radius (windows-latest)
Pull request: #19877

## Error Message

```
Job logs unavailable ('Failed to fetch logs for job'); both Node matrix legs (22.x, 24.x) of 'TypeScript SDK Validation' plus the downstream 'Polyglot Validation Results' aggregation job fail simultaneously on a PR that only modifies VS Code extension debugger/e2e files, indicating an environment/dependency issue unrelated to PR changes.
```

## Description

TypeScript SDK Validation fails on both Node 22.x and 24.x for PRs not touching polyglot SDK code

**Type**: infra-failure

## Occurrences

| Date | Build | Job | PR |
|------|-------|-----|----|
| 2026-09-03 | [33814653161](https://github.com/microsoft/aspire/actions/runs/33814653161) | Tests / No-package tests (regular, Aspire.Hosting.Radius.Tests, Hosting.Radius, Hosting.Radius, tests/Asp... / Hosting.Radius (windows-latest) | #19877 |

Contributor guide

Open the contributing guide

Research direction

Start with workflow configuration for the TypeScript SDK Validation matrix and the linked run 33814653161; inspect why both Node 22.x and 24.x legs and Polyglot Validation Results fail, noting that logs are currently unavailable. The work is done when validation no longer fails on PRs that do not modify polyglot SDK code, including the scenario represented by PR #19877.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, node.js, typescript
Domain
ci-cd
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.