From owner-freebsd-ports-bugs@FreeBSD.ORG Tue Dec 20 04:20:10 2011 Return-Path: Delivered-To: freebsd-ports-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A54DE1065679 for ; Tue, 20 Dec 2011 04:20:10 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 8099B8FC15 for ; Tue, 20 Dec 2011 04:20:10 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id pBK4KACZ065065 for ; Tue, 20 Dec 2011 04:20:10 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id pBK4KAl5065064; Tue, 20 Dec 2011 04:20:10 GMT (envelope-from gnats) Resent-Date: Tue, 20 Dec 2011 04:20:10 GMT Resent-Message-Id: <201112200420.pBK4KAl5065064@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-ports-bugs@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Jan Mikkelsen Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 621B6106566C for ; Tue, 20 Dec 2011 04:19:40 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from red.freebsd.org (red.freebsd.org [IPv6:2001:4f8:fff6::22]) by mx1.freebsd.org (Postfix) with ESMTP id 4573D8FC0C for ; Tue, 20 Dec 2011 04:19:40 +0000 (UTC) Received: from red.freebsd.org (localhost [127.0.0.1]) by red.freebsd.org (8.14.4/8.14.4) with ESMTP id pBK4JdDP037228 for ; Tue, 20 Dec 2011 04:19:39 GMT (envelope-from nobody@red.freebsd.org) Received: (from nobody@localhost) by red.freebsd.org (8.14.4/8.14.4/Submit) id pBK4JdIZ037227; Tue, 20 Dec 2011 04:19:39 GMT (envelope-from nobody) Message-Id: <201112200419.pBK4JdIZ037227@red.freebsd.org> Date: Tue, 20 Dec 2011 04:19:39 GMT From: Jan Mikkelsen To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 Cc: Subject: ports/163467: Ports using python 2.7 and "waf" intermittently hang on build/installation X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Dec 2011 04:20:10 -0000 >Number: 163467 >Category: ports >Synopsis: Ports using python 2.7 and "waf" intermittently hang on build/installation >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-ports-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Dec 20 04:20:10 UTC 2011 >Closed-Date: >Last-Modified: >Originator: Jan Mikkelsen >Release: FreeBSD 9.0-RC3 >Organization: Transactionware >Environment: FreeBSD vanaheim.transactionware.com 9.0-RC3 FreeBSD 9.0-RC3 #0: Mon Dec 19 12:43:57 EST 2011 root@vanaheim.transactionware.com:/home/janm/p4/freebsd-image-std-2011.1/work/base-freebsd/home/janm/p4/freebsd-image-std-2011.1/FreeBSD/src/sys/GENERIC amd64 >Description: During batch builds of ports, I observe hangs in python for ports that use "waf". The process blocks on "usem"; there seems to be a deadlock between two python processes. Example output from "ps aldxHwww" 0 91282 33575 0 52 0 6280 824 wait I 0 0:00.07 | | | `-- make package WRKDIRPREFIX=/ports-work PKGFILE=/ports-packages/talloc-2.0.7.tbz BATCH=yes NODEPENDS=yes PACKAGE_BUILDING=yes 0 91387 91282 0 52 0 14636 580 wait I 0 0:00.00 | | | `-- [sh] 0 91389 91387 0 52 0 152704 7676 usem I 0 0:00.33 | | | |-- python ./buildtools/bin/waf configure --mandir=/usr/local/man --jobs=16 0 91392 91389 0 52 0 93568 8468 usem I 0 0:00.00 | | | | `-- python ./buildtools/bin/waf configure --mandir=/usr/local/man --jobs=16 0 91389 91387 0 52 0 152704 7676 piperd I 0 0:00.00 | | | |-- python ./buildtools/bin/waf configure --mandir=/usr/local/man --jobs=16 0 91389 91387 0 52 0 152704 7676 usem I 0 0:00.00 | | | |-- python ./buildtools/bin/waf configure --mandir=/usr/local/man --jobs=16 0 91389 91387 0 52 0 152704 7676 usem I 0 0:00.00 | | | |-- python ./buildtools/bin/waf configure --mandir=/usr/local/man --jobs=16 0 91389 91387 0 52 0 152704 7676 usem I 0 0:00.00 | | | |-- python ./buildtools/bin/waf configure --mandir=/usr/local/man --jobs=16 0 91389 91387 0 52 0 152704 7676 usem I 0 0:00.00 | | | |-- python ./buildtools/bin/waf configure --mandir=/usr/local/man --jobs=16 0 91389 91387 0 52 0 152704 7676 usem I 0 0:00.00 | | | |-- python ./buildtools/bin/waf configure --mandir=/usr/local/man --jobs=16 0 91389 91387 0 52 0 152704 7676 usem I 0 0:00.00 | | | |-- python ./buildtools/bin/waf configure --mandir=/usr/local/man --jobs=16 0 91389 91387 0 52 0 152704 7676 usem I 0 0:00.00 | | | |-- python ./buildtools/bin/waf configure --mandir=/usr/local/man --jobs=16 0 91389 91387 0 52 0 152704 7676 usem I 0 0:00.00 | | | |-- python ./buildtools/bin/waf configure --mandir=/usr/local/man --jobs=16 0 91389 91387 0 52 0 152704 7676 usem I 0 0:00.00 | | | |-- python ./buildtools/bin/waf configure --mandir=/usr/local/man --jobs=16 0 91389 91387 0 52 0 152704 7676 usem I 0 0:00.00 | | | |-- python ./buildtools/bin/waf configure --mandir=/usr/local/man --jobs=16 0 91389 91387 0 52 0 152704 7676 usem I 0 0:00.00 | | | |-- python ./buildtools/bin/waf configure --mandir=/usr/local/man --jobs=16 0 91389 91387 0 52 0 152704 7676 usem I 0 0:00.00 | | | |-- python ./buildtools/bin/waf configure --mandir=/usr/local/man --jobs=16 0 91389 91387 0 52 0 152704 7676 usem I 0 0:00.00 | | | |-- python ./buildtools/bin/waf configure --mandir=/usr/local/man --jobs=16 0 91389 91387 0 52 0 152704 7676 usem I 0 0:00.00 | | | |-- python ./buildtools/bin/waf configure --mandir=/usr/local/man --jobs=16 0 91389 91387 0 52 0 152704 7676 usem I 0 0:00.00 | | | `-- python ./buildtools/bin/waf configure --mandir=/usr/local/man --jobs=16 I have observed this with devel/talloc and databases/tdb. It does not happen consistently. The child process can be killed and the build fails. This seems to be the same issue as ports/160717, I'm adding this report because of the "usem" information. >How-To-Repeat: Build ports until it fails. >Fix: >Release-Note: >Audit-Trail: >Unformatted: