Port hanging (unresponsive to Ctrl+C, need SIGKILL)

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Port hanging (unresponsive to Ctrl+C, need SIGKILL)

Leonardo Brondani Schenkel-2
Hello,

I have been working on an update to the Free42 port, which I just opened
a PR for:
https://github.com/macports/macports-ports/pull/486

However I am experiencing something I never encountered before, which I
have been unable to troubleshoot on my own: once the `xcodebuild`
command completes with BUILD SUCCESSFULL, the `port` command simply
hangs and becomes unresponsive to Ctrl+C. I need to send a SIGKILL from
a different terminal in order to kill it. I cannot figure out why this
is happening.

Can a member of the list help me out with the above? First to see if
this happens to you as well, and then helping me getting to the bottom
of it?

While you're at it, any other comments you may have about the PR are
more than welcome.

Thanks,
// Leonardo.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Port hanging (unresponsive to Ctrl+C, need SIGKILL)

Clemens Lang-2
Hi,

On Wed, May 24, 2017 at 09:50:31PM +0200, Leonardo Brondani Schenkel wrote:

> I have been working on an update to the Free42 port, which I just
> opened a PR for:
> https://github.com/macports/macports-ports/pull/486
>
> However I am experiencing something I never encountered before, which
> I have been unable to troubleshoot on my own: once the `xcodebuild`
> command completes with BUILD SUCCESSFULL, the `port` command simply
> hangs and becomes unresponsive to Ctrl+C. I need to send a SIGKILL
> from a different terminal in order to kill it. I cannot figure out why
> this is happening.
>
> Can a member of the list help me out with the above? First to see if
> this happens to you as well, and then helping me getting to the bottom
> of it?

I've previously seen builds using xcodebuild in particular hanging after
they were apparently done. In the cases I've seen so far xcodebuild
eventually terminated itself after quite a bit of time.

Did you try sending the kill signal to the xcodebuild process only, or
was that already terminated at this point?

--
Clemens
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Port hanging (unresponsive to Ctrl+C, need SIGKILL)

Leonardo Brondani Schenkel-2
On 2017-05-24 23:47, Clemens Lang wrote:
> I've previously seen builds using xcodebuild in particular hanging after
> they were apparently done. In the cases I've seen so far xcodebuild
> eventually terminated itself after quite a bit of time.
>
> Did you try sending the kill signal to the xcodebuild process only, or
> was that already terminated at this point?

It's already terminated. This is the process that remains:
91761 macports /opt/local/libexec/macports/bin/tclsh8.5
/opt/local/bin/port -d install +logo

I can see a single child under it:
91820 macports (sh)
I cannot kill process 91820, even with sudo kill -9.

I just noticed now that if I'm patient and I wait long enough (~3
minutes), the build actually "recovers" and continues.

I'm a bit lost here. The upstream shell build script, which runs a
virtually identical `xcodebuild` command as this port, does not exhibit
this behaviour.

I can provide build logs. I did not attach them here since I'm not sure
if it is regular practice to send attachments to the list.

Any help would be much appreciated,
// Leonardo.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Port hanging (unresponsive to Ctrl+C, need SIGKILL)

Clemens Lang-2
Hi,

On Thu, May 25, 2017 at 09:29:49AM +0200, Leonardo Brondani Schenkel wrote:

> On 2017-05-24 23:47, Clemens Lang wrote:
> > I've previously seen builds using xcodebuild in particular hanging
> > after they were apparently done. In the cases I've seen so far
> > xcodebuild eventually terminated itself after quite a bit of time.
> >
> > Did you try sending the kill signal to the xcodebuild process only,
> > or was that already terminated at this point?
>
> It's already terminated. This is the process that remains:
> 91761 macports /opt/local/libexec/macports/bin/tclsh8.5 /opt/local/bin/port
> -d install +logo
>
> I can see a single child under it:
> 91820 macports (sh)
> I cannot kill process 91820, even with sudo kill -9.
>
> I just noticed now that if I'm patient and I wait long enough (~3
> minutes), the build actually "recovers" and continues.

Yeah, that's pretty much what I've been seeing as well.

> I'm a bit lost here. The upstream shell build script, which runs a
> virtually identical `xcodebuild` command as this port, does not
> exhibit this behaviour.

That's valuable information.

> I can provide build logs. I did not attach them here since I'm not
> sure if it is regular practice to send attachments to the list.

Can you file a ticket, attach them there and post the ticket URL?

--
Clemens
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Port hanging (unresponsive to Ctrl+C, need SIGKILL)

Leonardo Brondani Schenkel-2
On 2017-05-25 11:13, Clemens Lang wrote:

>> I'm a bit lost here. The upstream shell build script, which runs a
>> virtually identical `xcodebuild` command as this port, does not
>> exhibit this behaviour.
>
> That's valuable information.
>
>> I can provide build logs. I did not attach them here since I'm not
>> sure if it is regular practice to send attachments to the list.
>
> Can you file a ticket, attach them there and post the ticket URL?

https://trac.macports.org/ticket/54232
// Leonardo.
Loading...