Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[wtp-releng] Troubles and consequences


(Sounds likes a good soap opera title?)

Once I finally started thinking maybe something really was wrong with our builds as Carl had been trying to tell me ... seeing the I build was taking over 12 hours! ... I looked, and there was some "stuck" processes related to the signing of jars. I'm not sure what the root cause of the problem was, but the long term solution is to put more error checking and "unknown state" emergency exit codes in our build scripts.

In the mean time, I've turn off the signing of jars ... only for our I builds and XSL Incubator builds. Once we get closer to a milestone, I will turn it back on, but in the mean time, it's causing too much work on the poor 'ol build machine.

I have left signing "on" for our 3.0.2 M builds ... since we are close to a release, we should be testing the most accurate code possible. But, I suspect part of the root cause mentioned above isn't the signing per se, but its signing from 3 different threads (or more) all at the same time. So ... we'll try just one thread for a while and keep our fingers crossed that helps.

Just wanted to let every one know the little I know!



Back to the top