Source: libxml-security-java Version: 1.5.8-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170128 qa-ftbfs Justification: FTBFS on amd64
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.395 sec - > in javax.xml.crypto.test.dsig.Baltimore18Test > Running javax.xml.crypto.test.dsig.InteropXMLDSig11Test > Tests run: 21, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.476 sec - > in javax.xml.crypto.test.dsig.InteropXMLDSig11Test > Running javax.xml.crypto.test.dsig.IaikSignatureAlgosTest > Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.341 sec - > in javax.xml.crypto.test.dsig.IaikSignatureAlgosTest > Running javax.xml.crypto.test.dsig.dom.DOMValidateContextTest > Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.262 sec - > in javax.xml.crypto.test.dsig.dom.DOMValidateContextTest > Running javax.xml.crypto.test.dsig.SignatureMethodTest > Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.115 sec - > in javax.xml.crypto.test.dsig.SignatureMethodTest > Running javax.xml.crypto.test.dsig.CreateBaltimore23Test > HMACOutputLength must not be less than 160 > Tests run: 16, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.661 sec - > in javax.xml.crypto.test.dsig.CreateBaltimore23Test > Running javax.xml.crypto.test.dsig.JSRForbiddenReferenceTest > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.372 sec - > in javax.xml.crypto.test.dsig.JSRForbiddenReferenceTest > Running javax.xml.crypto.test.dsig.PKSignatureAlgorithmTest > E: Build killed with signal TERM after 150 minutes of inactivity The full build log is available from: http://aws-logs.debian.net/2017/01/28/libxml-security-java_1.5.8-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. __ This is the maintainer address of Debian's Java team <http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers>. Please use debian-j...@lists.debian.org for discussions and questions.
