On Wed, Jan 11, 2017 at 12:35:39AM +0100, Santiago Vila wrote: > The bug should be reproducible with sbuild on a single CPU machine. > > I have described my building environment here: > > https://people.debian.org/~sanvila/my-building-environment.txt
You're build env looks very sane to me, and I trust you do sane things, yes. That said: 1) I wish not to reproduce your setup 1:1 (and should not be needed) 2) the build suceeded during reproducible builds, where some are run under eatmydata in non-sane build environments. > I changed my build setup since August, so to double check I did the > following today: > > Built 23 times with eatmydata and overlayfs -> 23 build failures. > Built 23 times with only overlayfs -> 23 successful builds. > Built 23 times without any of the above -> 23 successful builds. > > (Each one of those 23 times was in a different machine). > > Compared with other things, I agree that this is low priority, but it > seems that it's really eatmydata what makes it to fail. As I said, I trust you when you said it's libeatmydata related, and the message makes it pretty clear :) I'm going to upload the new version done by Valentin and use that flag to disable the ping tests, and close this bug with it (once he releases it), I suppose you'll test again then. Please report back if it still fails. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
signature.asc
Description: PGP signature