Skip to content

[release/9.0-staging] Reduce EncryptedXml encoded DTD test workload#131211

Open
github-actions[bot] wants to merge 1 commit into
release/9.0-stagingfrom
backport/pr-131091-to-release/9.0-staging
Open

[release/9.0-staging] Reduce EncryptedXml encoded DTD test workload#131211
github-actions[bot] wants to merge 1 commit into
release/9.0-stagingfrom
backport/pr-131091-to-release/9.0-staging

Conversation

@github-actions

@github-actions github-actions Bot commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

Backport of #131091 to release/9.0-staging

/cc @mrek-msft @eiriktsarpalis

Customer Impact

  • Customer reported
  • Found internally

[Select one or both of the boxes. Describe how this issue impacts customers, citing the expected and actual behaviors and scope of the issue. If customer-reported, provide the issue number.]

Regression

  • Yes
  • No

Test introduced by internal fix fails.

[If yes, specify when the regression was introduced. Provide the PR or commit if known.]

Testing

[How was the fix verified? How was the issue missed previously? What tests were added?]

Risk

Low. Test only change.

[High/Medium/Low. Justify the indication by mentioning how risks were measured and addressed.]

IMPORTANT: If this backport is for a servicing release, please verify that:

  • For .NET 8 and .NET 9: The PR target branch is release/X.0-staging, not release/X.0.
  • For .NET 10+: The PR target branch is release/X.0 (no -staging suffix).

Package authoring no longer needed in .NET 9

IMPORTANT: Starting with .NET 9, you no longer need to edit a NuGet package's csproj to enable building and bump the version.
Keep in mind that we still need package authoring in .NET 8 and older versions.

The encoded DTD payload used 111 transforms, causing tests that execute the chain to time out. Keep it at 21 transforms, one above the default limit, and assert that boundary in the test.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Copilot-Session: 21e761a9-3212-499c-b2b6-28d666f5bebd
@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
Successfully started running 3 pipeline(s).
13 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant