Source: openjdk-6 Version: 6b23~pre5-1 Severity: serious Hi,
Your package was in an infite loop while building on sparc. I had this: buildd 26534 99.8 1.2 651768 50208 ? R Aug10 14177:30 java The tail of the log at that tiem showed: Test tools/apt/Scanners/scanner.sh has timed out and is not responding after 8,506,000 interrupts Test tools/apt/Scanners/scanner.sh has timed out and is not responding after 8,507,000 interrupts Test tools/apt/Scanners/scanner.sh has timed out and is not responding after 8,508,000 interrupts Test tools/apt/Scanners/scanner.sh has timed out and is not responding after 8,509,000 interrupts I killed that process and it continued the regression tests. It is not acceptable that you keep the buildd keep that process around that long. The buildd software has a mechanism to kill the process for cases like this. It will look if it's still producing output, and will kill if it doesn't output anything for a long time. If this is the effect of a script to prevent that, either put a time limit in that script, or stop using it and instead ask us to increase the timeout. Kurt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
