Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Capistrano only outputs it's git:wrapper line when using airbrush #853

Open
nesl247 opened this issue Dec 7, 2018 · 5 comments
Open

Capistrano only outputs it's git:wrapper line when using airbrush #853

nesl247 opened this issue Dec 7, 2018 · 5 comments

Comments

@nesl247
Copy link

nesl247 commented Dec 7, 2018

When using airbrush (the default formatter), only the git:wrapper line is output. After that, it keeps running but nothing shows up.

I'm aware of #529, but we are using the latest release of both capistrano and airbrush.

@casperisfine
Copy link
Contributor

And then it's stuck?

@nesl247
Copy link
Author

nesl247 commented Dec 7, 2018

It's still running actually, but I believe shipit eventually kills the job because it says it hasn't received any output in X amount of minutes.

@byroot
Copy link
Contributor

byroot commented Dec 9, 2018

Right, that's what I meant by "stuck".

Just a guess, but usually when this happens it's because capistrano is asking for an input, possibly airbrush is causing this, it's hard to tell without being able to inspect the process. I'd recommend trying the classics, starting with strace.

But overall it's extremely unlikely that it's Shipit causing this. It might be Shipit's PTY that is throwing Airbrake off, but even if that's the case the fix would need to be in Airbrake.

Alternatively you can disable Airbrake when capistrano is invoke on Shipit by looking at ENV['SHIPIT']

@nesl247
Copy link
Author

nesl247 commented Dec 10, 2018

It is definitely airbrush related, its in the original comment as well. I do not know though if it is airbrush having a but or shipit's interaction with airbrush that has this bug, hence why I posted here as we use airbrush just fine in Jenkins.

@byroot
Copy link
Contributor

byroot commented Dec 10, 2018

Right. The possible difference between Shipit and Jenkins is that it tries to act a bit like a terminal using PTY.spawn which sometimes trick some programs into thinking they are spawned by a human and can ask for input.

Did you try strace? It would make it relatively easy to figure what blocks the process.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants