Opened 13 years ago

Last modified 12 years ago

#19128 new defect

mpab timeout on port builds

Reported by: dweber@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: contrib Version:
Keywords: Cc: febeling@…
Port: mpab

Description (last modified by blb@…)

I was running mpab until it hit a snag on a port that was failing in an infinite loop (guile or something). It looks like mpab needs a process to monitor the time of each port build with a timeout limit to kill a build and move on to the next build.

Change History (4)

comment:1 Changed 13 years ago by blb@…

Description: modified (diff)

Having some sort of watchdog would be nice, but difficult to do properly. Since it just kicks off a port process for each build, it isn't watching processes come and go directly, so it can only watch that one port process. A simple timeout would be bad for ports that are known to take time (eg, ghc, the gcc* ports, etc) as we may otherwise be stopping a build that was going just fine.

Perhaps some sort of monitoring of the log file being created, as output should be going there on a regular basis, and if not then it may very well be stalled. Are there ports which, even in debug mode, output very little during a successful build?

comment:2 Changed 12 years ago by (none)

Milestone: Port Bugs

Milestone Port Bugs deleted

comment:3 Changed 12 years ago by tobypeterson

Component: portsbase
Keywords: mpab timeout infinite loop removed
Version: 1.7.0

This should be a base bug, I think...

comment:4 Changed 12 years ago by jmroot (Joshua Root)

Component: basecontrib
Note: See TracTickets for help on using tickets.