deploy steam: steamcmd "Failed to commit build : Failure" (exit 6) is a false negative - build was uploaded and registered

Aperta
  • Qualcosa non va?
#310 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
52/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
typescript
Ambito
cli

Direzione di ricerca

Start with parse-steamcmd-output.ts and trace how its success checks feed the Steam deployment command. Reproduce or examine the reported output where content uploads and registers despite the commit error, then determine how that case should be distinguished from a real failure. Done means tests cover the reported output and a genuine failure, without treating an unconfirmed upload as successful.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Observed behavior

game-ci deploy steam (v0.1.75) intermittently fails with:

[ERROR] Error: Steam deployment failed: exit code 6: . 72.9MB (94%) | . | [timestamp]: ERROR! Failed to commit build for AppID 3570680 : Failure | Unloading Steam API...OK |

...while the build was uploaded and registered successfully: it appears in the Steamworks build manager, and a manually set-live build from this run is serving on the default branch. The same workflow/CLI was fully green on a release a few weeks earlier (Successfully finished), with the steam-deploy plugin code byte-identical between v0.1.72 and v0.1.75 (git diff v0.1.72...v0.1.75 touches no steam files), so this is a steamcmd-side reporting race, not a code regression.

A second attempt minutes later re-uploaded instantly (chunk dedup) and failed at the commit step the same way, yet that build also registered.

Impact

parse-steamcmd-output.ts requires /Successfully finished/ or exit 0, so this benign-but-reported failure aborts multi-app deploy jobs (we lost the demo and playtest deploys because they run after the full deploy in the same job), and blind retries create duplicate builds in the build manager.

Suggestion

When steamcmd reports the commit failure after depot content uploaded successfully, surface a warning instead of a hard error - or optionally poll the build status (e.g. via the partner web API) to confirm registration before failing. As-is, operators must choose between silent duplicates and missed downstream deploys.

Lingua principale
TypeScript
Stelle
20
Fork
11
Merge medio
5h 28m
PR unite (30g)
4

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di game-ci/cli

Tutte le issue di game-ci/cli

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.