Bug#867643: [DRE-maint] Bug#867643: schleuder: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: expect(output).to include("98769E8A1091F36BD88403ECF71A3F8412D83889 was fetched (new key)")
On 17-07-08 21:05:36, Lucas Nussbaum wrote: > On 08/07/17 at 19:37 +0200, Georg Faerber wrote: > > Unfortunately, I can't reproduce this locally. Besides the sbuild > > options used which are shown in the log file, is there a .sbuildrc in > > place, with non-default options? If so, could you share it? > > Have you tried diffing your log with mine? Not yet, but all the tests work for me. I strongly suspect gnupg2 / dirmngr to cause trouble, I'm however unsure, how to reproduce that. > > Additionally, I've got a question regarding the network configuration of > > the VM on which the build was run: At the moment of the build, were the > > only configured network interfaces localhost and / or loopback? > > no. Hm, alright. I've suspected [1] to apply here as well, but it seems there has to be a different problem. > Also, I've just tried on another machine (that has Internet access). In > that case the test suite hangs at: > > user sends a plain text message > from thunderbird > > Schleuder::ListBuilder That sounds like low entropy: Ensure that haveged is running or that the entropy pool is filled via some other technique / method. Cheers, Georg [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856152 signature.asc Description: Digital signature
Bug#867643: [DRE-maint] Bug#867643: schleuder: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: expect(output).to include("98769E8A1091F36BD88403ECF71A3F8412D83889 was fetched (new key)")
On 08/07/17 at 19:37 +0200, Georg Faerber wrote: > Hi, > > Unfortunately, I can't reproduce this locally. Besides the sbuild > options used which are shown in the log file, is there a .sbuildrc in > place, with non-default options? If so, could you share it? Have you tried diffing your log with mine? > Additionally, I've got a question regarding the network configuration of > the VM on which the build was run: At the moment of the build, were the > only configured network interfaces localhost and / or loopback? no. Also, I've just tried on another machine (that has Internet access). In that case the test suite hangs at: user sends a plain text message from thunderbird Schleuder::ListBuilder Lucas
Bug#867643: [DRE-maint] Bug#867643: schleuder: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: expect(output).to include("98769E8A1091F36BD88403ECF71A3F8412D83889 was fetched (new key)")
Hi, Unfortunately, I can't reproduce this locally. Besides the sbuild options used which are shown in the log file, is there a .sbuildrc in place, with non-default options? If so, could you share it? Additionally, I've got a question regarding the network configuration of the VM on which the build was run: At the moment of the build, were the only configured network interfaces localhost and / or loopback? Thanks, Georg signature.asc Description: Digital signature
Bug#867643: [DRE-maint] Bug#867643: schleuder: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: expect(output).to include("98769E8A1091F36BD88403ECF71A3F8412D83889 was fetched (new key)")
On 08/07/17 at 12:16 +0200, Georg Faerber wrote: > Hi Lucas, > > Thanks for the report: > > On 17-07-08 08:28:30, Lucas Nussbaum wrote: > > > > [...] > > > > 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. > > Was a wrapper used, like pbuilder or sbuild? Yes, sbuild Lucas
Bug#867643: [DRE-maint] Bug#867643: schleuder: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: expect(output).to include("98769E8A1091F36BD88403ECF71A3F8412D83889 was fetched (new key)")
Hi Lucas, Thanks for the report: On 17-07-08 08:28:30, Lucas Nussbaum wrote: > > [...] > > 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. Was a wrapper used, like pbuilder or sbuild? Thanks, Georg signature.asc Description: Digital signature
