19 days ago
Project: adorable-magic · env: production · service "web" (5ceaa1f8-f233-4b59-9d3d-7cc2b51eeafa)
Builder: Railpack (buildEnvironment V3) · repo wherelucho95/ai-career-builder · branch main
The same commit (bb4487e) fails at BUILD_IMAGE ~45s after SNAPSHOT_CODE, with ZERO build
log lines and only "Failed to build an image":
-
web: cdd2a51e-f067-4dcd-8c5d-a916625affaf, 8e941160-2c74-45dc-b243-13f7c5f4e812,
2b4a2ddb-fbb3-490e-b09b-f0e4a3b1f2af
-
temp service tmp-bisect-new: 08e31d76-8bab-4e8f-bc81-0ae17e377a4d
But the SAME commit built successfully end-to-end (pip install + image export) on temp
service tmp-bisect-old (5fddd637-5912-45ae-8e4c-9d64b58be8a3), deployment
a24e2930-47e4-46dd-90e7-86096bd327c2. The previous web build 0b8ada7c (commit 090a9d7)
succeeded today at 04:57Z.
Ruled out: dependency resolution (all wheels resolve for linux/py3.12), binary asset
corruption, repo size (~1 MB), config changes, status-page incidents.
Same tree builds on one service and fails pre-log on others -> looks builder-side.
Production is still on the previous healthy deploy, but we can't ship. Please investigate.
2 Replies
19 days ago
We're sorry for the trouble. We're aware of an issue affecting Builds across all regions (US West, US East, EU West and Southeast Asia), "Elevated Build Failure Rate", which causes builds to fail unexpectedly, and we're working on it. Follow updates at the incident page.
Status changed to Awaiting User Response Railway • 19 days ago
11 days ago
I still have the problem. please hekp
Status changed to Awaiting Railway Response Railway • 11 days ago
Status changed to Awaiting User Response Railway • 11 days ago
3 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 3 days ago