summaryrefslogtreecommitdiff
path: root/Tools
diff options
context:
space:
mode:
authorMark Linimon <linimon@FreeBSD.org>2010-03-30 21:19:36 +0000
committerMark Linimon <linimon@FreeBSD.org>2010-03-30 21:19:36 +0000
commit7fc55a84af8ab18b21884bff1d146190061ad794 (patch)
treeeae649d1dfd015abd16b924bfeb18bdaa10bd52d /Tools
parentAdd an entry for the "truncated distfiles" problem; improve one other entry. (diff)
Add a case to detect a transient problem that shows up on all package
nodes, but most regularly on sparc64. (Occasionally, on amd64 and ia64). For reasons I haven't been quite able to track down, on some occasions a pkg_add command is unable to extract a dependency; the tarfile shows up as being truncated. This does not seem to be due to disk-low or memory-low conditions, nor is it a problem with scp; the md5 on the file is fine when examined afterwards. The only clue so far is that it seems to happen on systems with the most package builds running simultaneously -- and thus, possibly more than one pkg_add running in parallel.
Notes
Notes: svn path=/head/; revision=251857
Diffstat (limited to 'Tools')
-rwxr-xr-xTools/portbuild/scripts/processonelog3
1 files changed, 3 insertions, 0 deletions
diff --git a/Tools/portbuild/scripts/processonelog b/Tools/portbuild/scripts/processonelog
index dfe737223dc8..bce337599b3d 100755
--- a/Tools/portbuild/scripts/processonelog
+++ b/Tools/portbuild/scripts/processonelog
@@ -99,6 +99,9 @@ elif bzgrep -qE "(conflicts with installed package|is already installed - perhap
reason="depend_object"; tag="dependobj"
elif bzgrep -q "core dumped" $1; then
reason="coredump"; tag="coredump"
+# linimon would _really_ like to understand how to fix this problem
+elif bzgrep -q "pkg_add: tar extract.*failed!" $1; then
+ reason="truncated_distfile"; tag="truncated_distfile"
# below here are the less common items