Unverified50% confidenceFactExact time
By default, GitLab CI treats a non-zero exit code as a job failure and immediately stops the job's subsequent commands; if allow_failure: false is configured (the default), the failure also blocks jobs in the same stage and subsequent stages.
1
Sources
50%
Confidence
Long-term
Relevance
10/26/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedIn Unix convention, exit code 0 indicates success, and any non-zero value is interpreted by GitHub Actions as a failure, interrupting the pipeline.75% similarUnverified在主节点故障场景下，GitHub 选择一致性（拒绝服务直到确认新主库）而非可用性，导致任务卡在 Queued 状态而非被错误地重复分配71% similarUnverifiedIntent conflicts produce no conflict warnings during a Git merge, the code compiles successfully, but the runtime behavior has been broken, constituting a silent failure.70% similarUnverifiedIn the GitLab Jobs API, `finished_at` being null usually indicates that the Job is still running or has not yet started, and no conclusion should be drawn from this.67% similarUnverifiedGitHub Actions 的调度系统需要保证任务不会被重复执行（exactly-once 语义），本质上要求强一致性保证66% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1101543API
curl https://kongchang.com/api/v1/knowledge/claims/1101543MCP
get_claim(id=1101543)