Package: ceilometer
Version: 2014.1-1
Severity: serious
Usertags: goto-cc

While attempting to rebuild all packages in a clean chroot (using cowbuilder and
pbuilder), the build of ceilometer got stalled for more than 8 hours. This is
the relevant lines of `ps faux`:

1001     22311  0.0  0.0  10824   872 ?        S    03:02   0:00  |  \_ 
/usr/bin/make -f debian/rules build
1001     24128  0.0  0.0  41924 10080 ?        S    03:02   0:00  |      \_ 
/usr/bin/perl -w /usr/bin/dh build --with python2
1001     33372  0.0  0.0  10820   884 ?        S    03:02   0:00  |          \_ 
/usr/bin/make -f debian/rules override_dh_auto_test
1001     35481  0.0  0.0  10780   676 ?        S    03:02   0:00  |             
 \_ /bin/sh -c set -e && \ ?TEMP_REZ=`mktemp -t` && \ ?bash -x 
./setup-test-env.sh testr run --subunit 'tests\.(?!.*test_bin.*)' | tee 
$TEMP_REZ | subunit2pyunit || true ; \ ?cat $TEMP_REZ | subunit-filter -s 
--no-passthrough | subunit-stats || true ; \ ?rm -f $TEMP_REZ ;
1001     35493  0.0  0.0  13832  1420 ?        S    03:02   0:00  |             
     \_ bash -x ./setup-test-env.sh testr run --subunit tests\.(?!.*test_bin.*)
1001     35546  0.3  0.0  79028  4476 ?        S    03:02   1:35  |             
     |   \_ mongod --maxConns 32 --nojournal --noprealloc --smallfiles --quiet 
--noauth --port 29000 --dbpath /tmp/CEILO-MONGODB-1cira --bind_ip localhost 
--config /dev/null
1001     35495  0.0  0.0  10688   384 ?        S    03:02   0:00  |             
     \_ tee /tmp/tmp.K9wTUj6Ns6
1001     35498  0.0  0.0  46160 11816 ?        S    03:02   0:00  |             
     \_ /usr/bin/python /usr/bin/subunit2pyunit

That is, all the listed processes were started at 03:02 hours, while the current
time on the system is now 11:13:34. The problem was fully reproducible, i.e.,
this is the result of the second attempt of building ceilometer.

The full build log is attached.

Best,
Michael

Attachment: build-log.txt.gz
Description: application/gunzip

Attachment: pgptnOYDqShtB.pgp
Description: PGP signature

Reply via email to