Your message dated Tue, 07 Oct 2014 22:04:26 +0200
with message-id <87h9zfprxx....@msgid.hilluzination.de>
and subject line Re: Bug#746456: FTBFS as test does not terminate
has caused the Debian Bug report #746456,
regarding FTBFS as test does not terminate
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
746456: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746456
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: google-perftools
Version: 2.1-2
Severity: serious
Usertags: goto-cc

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

1001     29447  0.0  0.0  11068  1080 ?        S    Apr29   0:00  | \_ 
/usr/bin/make -f debian/rules build
1001     63731  0.0  0.0  11824  1880 ?        S    Apr29   0:00  |     \_ 
/usr/bin/make -C . check
1001     64795  0.0  0.0  11720  1728 ?        S    Apr29   0:00  |         \_ 
/usr/bin/make check-TESTS
1001     65296  0.0  0.0  13880  1484 ?        S    Apr29   0:00  |             
\_ /bin/bash -c failed=0; all=0; xfail=0; xpass=0; skip=0; \ srcdir=.; export 
srcdir; \ list=' low_level_alloc_unittest atomicops_unittest 
stacktrace_unittest tcmalloc_minimal_unittest tcmalloc_minimal_large_unittest 
tcmalloc_minimal_large_heap_fragmentation_unittest  addressmap_unittest 
system_alloc_unittest packed_cache_test frag_unittest markidle_unittest 
current_allocated_bytes_test malloc_hook_test malloc_extension_test  
memalign_unittest page_heap_test pagemap_unittest realloc_unittest 
stack_trace_table_test thread_dealloc_unittest tcmalloc_minimal_debug_unittest 
malloc_extension_debug_test memalign_debug_unittest realloc_debug_unittest 
debugallocation_test.sh tcmalloc_unittest.sh tcmalloc_both_unittest 
tcmalloc_large_unittest tcmalloc_large_heap_fragmentation_unittest 
raw_printer_test sampler_test sampling_test.sh heap-profiler_unittest.sh 
simple_compat_test heap-checker_unittest.sh heap-checker-death_unittest.sh 
tcmalloc_debug_unittest sampler_debug_test sampling_debug_test.sh 
heap-profiler_debug_unittest.sh heap-checker_debug_unittest.sh getpc_test 
profiledata_unittest profile_handler_unittest profiler_unittest.sh 
tcmalloc_and_profiler_unittest '; \ red=; grn=; lgn=; blu=; std=; \ if test -n 
"$list"; then \   for tst in $list; do \     if test -f ./$tst; then dir=./; \  
   elif test -f $tst; then dir=; \     else dir="./"; fi; \     if 
PPROF_PATH=./src/pprof TCMALLOC_SAMPLE_PARAMETER=524288 BINDIR=. 
TMPDIR=/tmp/perftools ${dir}$tst; then \       all=`expr $all + 1`; \       
case "  " in \       *[\ \?]$tst[\ \?]*) \ ?xpass=`expr $xpass + 1`; \ 
?failed=`expr $failed + 1`; \ ?col=$red; res=XPASS; \       ;; \       *) \ 
?col=$grn; res=PASS; \       ;; \       esac; \     elif test $? -ne 77; then \ 
      all=`expr $all + 1`; \       case "  " in \       *[\ \?]$tst[\ \?]*) \ 
?xfail=`expr $xfail + 1`; \ ?col=$lgn; res=XFAIL; \       ;; \       *) \ 
?failed=`expr $failed + 1`; \ ?col=$red; res=FAIL; \       ;; \       esac; \   
  else \       skip=`expr $skip + 1`; \       col=$blu; res=SKIP; \     fi; \   
  echo "${col}$res${std}: $tst"; \   done; \   if test "$all" -eq 1; then \     
tests="test"; \     All=""; \   else \     tests="tests"; \     All="All "; \   
fi; \   if test "$failed" -eq 0; then \     if test "$xfail" -eq 0; then \      
 banner="$All$all $tests passed"; \     else \       if test "$xfail" -eq 1; 
then failures=failure; else failures=failures; fi; \       banner="$All$all 
$tests behaved as expected ($xfail expected $failures)"; \     fi; \   else \   
  if test "$xpass" -eq 0; then \       banner="$failed of $all $tests failed"; 
\     else \       if test "$xpass" -eq 1; then passes=pass; else 
passes=passes; fi; \       banner="$failed of $all $tests did not behave as 
expected ($xpass unexpected $passes)"; \     fi; \   fi; \   dashes="$banner"; 
\   skipped=""; \   if test "$skip" -ne 0; then \     if test "$skip" -eq 1; 
then \       skipped="($skip test was not run)"; \     else \       
skipped="($skip tests were not run)"; \     fi; \     test `echo "$skipped" | 
wc -c` -le `echo "$banner" | wc -c` || \       dashes="$skipped"; \   fi; \   
report=""; \   if test "$failed" -ne 0 && test -n 
"google-perfto...@googlegroups.com"; then \     report="Please report to 
google-perfto...@googlegroups.com"; \     test `echo "$report" | wc -c` -le 
`echo "$banner" | wc -c` || \       dashes="$report"; \   fi; \   dashes=`echo 
"$dashes" | sed s/./=/g`; \   if test "$failed" -eq 0; then \     col="$grn"; \ 
  else \     col="$red"; \   fi; \   echo "${col}$dashes${std}"; \   echo 
"${col}$banner${std}"; \   test -z "$skipped" || echo "${col}$skipped${std}"; \ 
  test -z "$report" || echo "${col}$report${std}"; \   echo 
"${col}$dashes${std}"; \   test "$failed" -eq 0; \ else :; fi
1001     57988  0.0  0.0  11664   676 ?        S    Apr29   0:00  |             
    \_ /bin/sh ./debugallocation_test.sh
1001     57993  0.0  0.0  11664   128 ?        S    Apr29   0:00  |             
        \_ /bin/sh ./debugallocation_test.sh
1001     57997  0.3  0.0  36888  2072 ?        S    Apr29   5:50  |             
            \_ 
/srv/jenkins-slave/workspace/sid-goto-cc-google-perftools/google-perftools-2.1/.libs/lt-debugallocation_test
 0
1001     57999  0.0  0.0  11664   132 ?        S    Apr29   0:00  |             
            \_ /bin/sh ./debugallocation_test.sh

That is, all the listed processes were started on April 29th hours, while the
current time on the system is now 09:06:35 on April 30th. The problem was fully
reproducible, i.e., this is the result of the second attempt of building
google-perftools.

The full build log is attached.

Best,
Michael


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

Attachment: pgpN3e8Nx6azX.pgp
Description: PGP signature


--- End Message ---
--- Begin Message ---
Control: fixed -1 2.2.1-0.2

* Santiago Ruano Rincón:

> Source: google-perftools
> Followup-For: Bug #746456
>
> I've successfuly build 2.2.1-0.2 with my cowbuilder. It even passes all
> 46 tests:
>
> [...]
> 
> I think you can close this bug.

I'll do that. Thank you very much for reviewing the issue.

Cheers,
-Hilko

--- End Message ---

Reply via email to