postPortBuild hook question (misbehavior?)
marcuscom at marino.st
Sun Nov 20 07:22:30 EST 2011
On 11/19/2011 7:40 PM, Joe Marcus Clarke wrote:
> The postPortBuild Hook is executed after mark_failed in all required
> cases. I'm finding it odd that you would need to modify this function.
> Under what code path is postPortBuild not being run? By my count,
> mark_failed will run (independent of postPortBuild) under these
> * prePortBuild Hook fails
> * prePortChecksum Hook fails
mark_failed did get executed, but all it does is change the status of
ports dependent on the failed port. I had to add an extra line to cause
the postPortBuild hook to fire under the name of each port that was
marked failed for dependency reasons.
So in my example, there were 3 ports involved: The port in the queue and
two ports that it depended on. The first dependency failed, and the
postPortBuild hook fired for that failure. The other dependency and the
queued port were marked failed (due to dependency reasons) but the
postPortBuild hook did not fire for those two.
So I'm expecting the postPortBuild hook to fire 3 times, but it only
fired once. Does that explanation make sense?
More information about the tinderbox-list