v6.0.0: fatal: 4f3a... is neither a commit nor blob

Aperta
  • Qualcosa non va?
#856 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
48/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
git, github-actions, typescript
Ambito
build-system, ci-cd

Direzione di ricerca

Start by comparing the v6.0.0 action’s versioning path with v4, since the failure occurs during startup after Semantic versioning is selected. Inspect the GitHub Actions configuration and related TypeScript code that invokes the game-ci CLI; the payload does not name specific files or tests. Reproduce with the supplied Windows host runner settings and identify why the referenced commit is unavailable; done when the v6 build starts successfully under those settings.

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

Descrizione

bug

Bug description

When I upgrade unity-builder in my GitHub actions file from v4 to v6.0.0, it fails during the first 30 seconds of starting. It says it doesn't find a specific commit. With v4, the build succeeds.

How to reproduce

I did not create a MWE yet. I'm running it on a Windows host runner.

Additional details

GitHub runner build log:

Run game-ci/[email protected]
  with:
    targetPlatform: StandaloneWindows64
    buildMethod: CI.InitUPM
    runAsHostUser: true
    unityVersion: auto
    cliVersion: latest
    useHostNetwork: false
    versioning: Semantic
    androidExportType: androidPackage
    androidSymbolType: none
    providerStrategy: local
    dockerIsolationMode: default
    containerRegistryRepository: unityci/editor
    containerRegistryImageVersion: 3
    cacheUnityInstallationOnMac: false
    dockerWorkspacePath: /github/workspace
    skipActivation: false
    linux64RemoveExecutableExtension: false
    enableBuildRetry: false
    localCacheEnabled: false
    localCacheLibrary: true
    localCacheLfs: false
    localCacheMode: tar
  env:
    UNITY_LICENSE: ***
    UNITY_EMAIL: ***
    UNITY_PASSWORD: ***
Cache hit for: game-ci-cli-v0.1.72-linux-x64
Received 0 of 37818942 (0.0%), 0.0 MBs/sec
Received 33624638 of 37818942 (88.9%), 16.0 MBs/sec
Received 33624638 of 37818942 (88.9%), 10.7 MBs/sec
Received 37818942 of 37818942 (100.0%), 9.7 MBs/sec
Cache Size: ~36 MB (37818942 B)
/usr/bin/tar -xf /var/lib/github-actions/_work/_temp/ac3ef459-6b3c-4019-90d2-389f84fc9a5d/cache.tzst -P -C /var/lib/github-actions/_work/Re-Corp/Re-Corp --use-compress-program unzstd
Cache restored successfully
Restored game-ci CLI v0.1.72 from cache
/tmp/game-ci-cli-cache/v0.1.72/game-ci build --targetPlatform=StandaloneWindows64 --buildMethod=CI.InitUPM --versioningStrategy=Semantic --androidExportType=androidPackage --androidSymbolType=none --dockerIsolationMode=default --containerRegistryRepository=unityci/editor --containerRegistryImageVersion=3 --dockerWorkspacePath=/github/workspace --runAsHostUser
[INFO] Versioning strategy: Semantic
true
[WARN] {
  "output": "true\n",
  "error": "",
  "status": {
    "success": true,
    "code": 0
  }
}
[WARN] {
  "output": "",
  "error": "",
  "status": {
    "success": true,
    "code": 0
  }
}
[WARN] {
  "output": "",
  "error": "",
  "status": {
    "success": true,
    "code": 0
  }
}
1
fatal: 4f3a02a1ec44a1a8546125163e5be7721524d39e is neither a commit nor blob
[ERROR] Error: fatal: 4f3a02a1ec44a1a8546125163e5be7721524d39e is neither a commit nor blob

    at <anonymous> (/$bunfs/root/game-ci:14389:41)
    at emit (node:events:98:22)
    at #maybeClose (node:child_process:766:16)
    at #handleOnExit (node:child_process:520:72)
    at processTicksAndRejections (native:7:39)
Error: Build failed with exit code 1
Lingua principale
TypeScript
Stelle
1.1k
Fork
318
Merge medio
23h 20m
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/unity-builder

Tutte le issue di game-ci/unity-builder

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.