ci: temporarily disable offload tests while artifact publishing is broken

[damyanp]

Summary

Azure Artifacts publishing is currently failing across the entire DirectXShaderCompiler Azure DevOps organization:

##[error]Artifact cannot be uploaded because max quantity has been exceeded
or the payment instrument is invalid. https://aka.ms/artbilling for details.

main is currently red because of this, along with every open PR. This is a temporary measure to get CI green again while the underlying billing issue is sorted out.

Impact

Every run since ~11:25 on 2026-07-30 has failed on the Publish DXC binaries step:

Build	Branch	Started	Result
10659	PR 8672	10:32	last clean run
10660-10664	PRs 8673-8677	11:25-14:52	artifact publish failure
10667	PR 8718	18:04	artifact publish failure
10668	main	18:31	artifact publish failure
10670	PR 8666	19:35	artifact publish failure
10671	PR 8717	20:26	artifact publish failure

On main (10668) it also cascades: the missing artifact fails Download DXC binaries, which takes down both the WARP and lavapipe offload jobs.

Why the pipeline cannot just publish less

Pipeline artifacts are exempt from Azure Artifacts storage billing, so this is not a quota the pipeline can stay under by shrinking or expiring the artifact. The error string covers two conditions, and this is the payment instrument half - an org-level billing problem. Project retention settings are already tight (10 days, PipelineArtifact included in artifactTypesToDelete), so there is no headroom to reclaim there either.

The real fix is under Organization settings > Billing and needs someone with Project Collection Administrator access.

Change

The offload tests hand the built binaries from the Windows build job to the test jobs via a pipeline artifact, so they cannot run at all until publishing works. This adds an enableOffloadTests parameter, defaulted to false, which:

• clears artifactName on the VS2022_Release matrix leg, so the existing ne(variables['artifactName'], '') guard skips both Stage DXC binaries and Publish DXC binaries - the same mechanism VS2022_Debug and VS2022_Release_NoSPIRV already use, so no new logic
• forces the OffloadTests stage condition to false, so it never attempts the download that is guaranteed to fail

OffloadGate still runs. It takes ~6 seconds and always passes, and leaving it in place keeps the published check name stable.

Reverting

One word, once org billing is fixed:

  - name: enableOffloadTests
    default: false   # -> true

Trade-off

This does mean no offload test coverage on main while it is in effect. That is unavoidable given the transport is the thing that is broken, but it is worth restoring promptly rather than letting the flag quietly become permanent.

Release notes

Skipping per CONTRIBUTING.md - infrastructure-only change with no user-visible compiler behavior change.

[Copilot]

Pull request overview

Temporarily restores CI reliability while Azure pipeline artifact publishing is unavailable.

Changes:

• Adds an offload-test feature flag, disabled by default.
• Skips binary artifact publishing and the dependent offload-test stage when disabled.
• Preserves the existing OffloadGate check.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[joaosaffran]

Lavapipe tests only happen if we pass the label run-offload-tests in the PR. To disable the actual uploading, this task should be conditioned, something like:

Suggested change

	- task: PublishPipelineArtifact@1
	condition: eq(parameters.enableOffloadTests, 'true')
	displayName: 'Publish DXC binaries'
	condition: and(succeeded(), ne(variables['artifactName'], ''))
	inputs:
	targetPath: '$(Build.ArtifactStagingDirectory)\dxc'
	artifact: '$(artifactName)'

[joaosaffran]

Or set artifactName to '' should also work

[damyanp]

It looks like I've managed to increase the storage limits - I'll abandon this change once I'm sure that builds are working again.