On Mon, Jan 21, 2013 at 6:45 PM, Luis R. Rodriguez <mcgrof@xxxxxxxxxxxxx> wrote: > On Mon, Jan 21, 2013 at 5:15 PM, Luis R. Rodriguez <mcgrof@xxxxxxxxxxxxx> wrote: >> If we hit CTRL the signal handler should remove that directory. The >> directory should also be nuked when it completes. > > Another thing you could do to debug is to tail -f the log file for each kernel: > > tail -f .tmp.ckmake/2.6.24/ckmake.n.log > > If that doesn't ever move you know something is going wrong. On a slow > box this might happen but the only reason why I suspect this might > happen on a slow box is the heuristics for the number of job processes > running at the same time to do compilation is too high. Right now use > use make -j $NUM_CPUS and this is computed by cpu_info_build_jobs() on > ckmake. I just ran this on compat-drivers on a Fedora 16 box and it completed just fine. It did take 55 minutes as its not the monster build server we have for compat test builds though, but it did finish. So what we do not have is a progress bar for each kernel -- and that'd be nice but not even sure how to beging writing that. Maybe we should have another thread that measures the number of lines on the kernel build log file.. or something like that.. not sure, and display that on the right column instead of just an empty box while things move on. Luis -- To unsubscribe from this list: send the line "unsubscribe backports" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
