7 months ago
Our Github Actions are intermittently failing due to "Failed to stream build logs: Failed to retrieve build log" error. As far as I can tell, all of these deployments are successfully deployed to Railway (as this is manual process of going to Railway dashboard and checking, I might have missed some), I think the issue is really just in streaming the logs.
This has been going on since about new year, but it's getting worse, hence my support ticket. It was always intermittent but in last couple of weeks, around half of the jobs failed due to "Failed to stream build logs". As said, deployments are actually going through.
This has been happening on both environments but I'll select staging in the dropdown, as deployments are more often there.
16 Replies
7 months ago
I've seen https://station.railway.com/questions/been-regularly-receiving-failed-to-stre-2b788c2e but we are installing Railway CLI anew for each job with `npm i -g @railway/cli` just before `railway up -s jamboo -e staging`, so we are getting the latest version of CLI.
Status changed to Awaiting User Response Railway • 7 months ago
7 months ago
In last couple of days since the introduction of --detach our pipeline hasn't failed but I don't think that's the solution we want. We wish to see status of deployment from the from status of pipeline.
Status changed to Awaiting Railway Response Railway • 7 months ago
7 months ago
Thanks for the feature request. I will raise it with the team. It's also recommended to create a feature request here: https://station.railway.com/feedback
Thanks again
Status changed to Awaiting User Response Railway • 7 months ago
7 months ago
I think there's miscommunication here.
We would like to deploy to Railway via Github Actions and we are currently doing that as described here: https://blog.railway.com/p/github-actions. railway up command sometimes fails with error "Failed to stream build logs: Failed to retrieve build log" and we would like to understand how to fix or work around it. Using --detach flag isn't an option because it detaches from the deployment process and we never get an update about the status of the deployment.
7 months ago
Hello!
We're acknowledging your issue and attaching a ticket to this thread.
We don't have an ETA for it, but, our engineering team will take a look and you will be updated as we update the ticket.
Please reply to this thread if you have any questions!
7 months ago
Hi Matic, apologies for the misunderstanding! As you can see above ^ I've gone ahead and attached a ticket to this thread for our team to triage and review. Any updates on there should flow through here to you.
6 months ago
🛠️ The internal ticket CLI: Deploy fails with "Failed to stream build logs" has been marked as backlog.
6 months ago
Is there an estimate of when this ticket will be picked up? This is currently failing our CI pipelines intermittently which is getting quite annoying. Using detach isn't really a solution. Thanks
6 months ago
I'd like to chime in and say this is failing our CI pipelines as well.
3 months ago
Experiencing this too
3 months ago
Hello!
We've escalated your issue to our engineering team.
We aim to provide an update within 1 business day.
Please reply to this thread if you have any questions!
Status changed to Awaiting User Response Railway • 3 months ago
3 months ago
🛠️ The ticket Deployment error with build logs has been marked as triage.
3 months ago
🛠️ The ticket Deployment issue with build logs has been marked as todo.
3 months ago
🛠️ The ticket Deployment issue with build logs has been marked as in progress.
3 months ago
✅ The ticket Deployment issue with build logs has been marked as completed.
3 months ago
This has been fixed in version 4.7.3 of the CLI. https://github.com/railwayapp/cli/releases/tag/v4.7.3
Status changed to Solved jr • 3 months ago