Your message dated Thu, 14 May 2020 15:30:05 +0200 with message-id <[email protected]> and subject line gcj is long gone, closing this issue has caused the Debian Bug report #934840, regarding gcc-defaults: Build takes forever in stretch 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 [email protected] immediately.) -- 934840: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934840 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: src:gcc-defaults Version: 1.168 Fixed: 1.181 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in stretch and this is what happened: -------------------------------------------------------------------------------- [...] debian/rules build-indep dh_testdir rm -rf build mkdir -p build sed 's/@gcc_suffix@//' debian/generate-cacerts.pl.in \ > debian/generate-cacerts.pl cd build && perl ../debian/generate-cacerts.pl \ /etc/ssl/certs/ca-certificates.crt GC Warning: Repeated allocation of very large block (appr. size 671092736): May lead to memory leak and poor performance. Exception in thread "main" java.lang.OutOfMemoryError <<No stacktrace available>> keytool error: java.security.cert.CertificateException keytool error: java.security.cert.CertificateException GC Warning: Repeated allocation of very large block (appr. size 671092736): May lead to memory leak and poor performance. Exception in thread "main" java.lang.OutOfMemoryError <<No stacktrace available>> GC Warning: Repeated allocation of very large block (appr. size 671092736): May lead to memory leak and poor performance. Exception in thread "main" java.lang.OutOfMemoryError <<No stacktrace available>> GC Warning: Repeated allocation of very large block (appr. size 671092736): May lead to memory leak and poor performance. Exception in thread "main" java.lang.OutOfMemoryError <<No stacktrace available>> GC Warning: Repeated allocation of very large block (appr. size 671092736): May lead to memory leak and poor performance. Exception in thread "main" java.lang.OutOfMemoryError <<No stacktrace available>> GC Warning: Repeated allocation of very large block (appr. size 671092736): May lead to memory leak and poor performance. Exception in thread "main" java.lang.OutOfMemoryError <<No stacktrace available>> GC Warning: Repeated allocation of very large block (appr. size 671092736): May lead to memory leak and poor performance. Exception in thread "main" java.lang.OutOfMemoryError <<No stacktrace available>> GC Warning: Repeated allocation of very large block (appr. size 671092736): May lead to memory leak and poor performance. Exception in thread "main" java.lang.OutOfMemoryError <<No stacktrace available>> GC Warning: Repeated allocation of very large block (appr. size 671092736): May lead to memory leak and poor performance. Exception in thread "main" java.lang.OutOfMemoryError <<No stacktrace available>> GC Warning: Repeated allocation of very large block (appr. size 671092736): May lead to memory leak and poor performance. Exception in thread "main" java.lang.OutOfMemoryError <<No stacktrace available>> GC Warning: Repeated allocation of very large block (appr. size 671092736): May lead to memory leak and poor performance. Exception in thread "main" java.lang.OutOfMemoryError <<No stacktrace available>> GC Warning: Repeated allocation of very large block (appr. size 671092736): May lead to memory leak and poor performance. Exception in thread "main" java.lang.OutOfMemoryError <<No stacktrace available>> GC Warning: Repeated allocation of very large block (appr. size 671092736): May lead to memory leak and poor performance. Exception in thread "main" java.lang.OutOfMemoryError <<No stacktrace available>> GC Warning: Repeated allocation of very large block (appr. size 671092736): May lead to memory leak and poor performance. Exception in thread "main" java.lang.OutOfMemoryError <<No stacktrace available>> GC Warning: Repeated allocation of very large block (appr. size 671092736): May lead to memory leak and poor performance. Exception in thread "main" java.lang.OutOfMemoryError <<No stacktrace available>> GC Warning: Repeated allocation of very large block (appr. size 671092736): May lead to memory leak and poor performance. Exception in thread "main" java.lang.OutOfMemoryError <<No stacktrace available>> GC Warning: Repeated allocation of very large block (appr. size 671092736): May lead to memory leak and poor performance. Exception in thread "main" java.lang.OutOfMemoryError <<No stacktrace available>> GC Warning: Repeated allocation of very large block (appr. size 671092736): May lead to memory leak and poor performance. Exception in thread "main" java.lang.OutOfMemoryError <<No stacktrace available>> GC Warning: Repeated allocation of very large block (appr. size 671092736): May lead to memory leak and poor performance. Exception in thread "main" java.lang.OutOfMemoryError <<No stacktrace available>> GC Warning: Repeated allocation of very large block (appr. size 671092736): May lead to memory leak and poor performance. Exception in thread "main" java.lang.OutOfMemoryError <<No stacktrace available>> keytool error: java.security.cert.CertificateException GC Warning: Repeated allocation of very large block (appr. size 671092736): May lead to memory leak and poor performance. make: *** wait: No child processes. Stop. make: *** Waiting for unfinished jobs.... make: *** wait: No child processes. Stop. -------------------------------------------------------------------------------- I had to interrupt the build because it was taking too long. The build was tried in a machine with plenty of memory (6.5 GB of RAM). Previously, it was possible to build the package with a lot less of memory, so this seems a regression. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks.
--- End Message ---
--- Begin Message ---gcj is long gone, closing this issue.
--- End Message ---
