On 9/28/14, 7:03 PM, David Suárez wrote: > Source: ooniprobe > Version: 1.1.1-1 > Severity: serious > Tags: jessie sid > User: debian...@lists.debian.org > Usertags: qa-ftbfs-20140926 qa-ftbfs > Justification: FTBFS on amd64 > > Hi, > > During a rebuild of all packages in sid, your package failed to build on > amd64. > > The full build log is available from: > > http://aws-logs.debian.net/ftbfs-logs/2014/09/26/ooniprobe_1.1.1-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.
Hi David, Thanks for reporting this bug! It appears that there is something on the machine that is running the test that has already binded to port 9999. Since you say that this is run on a "clean, minimal" EC2 instance, this behavior is quite peculiar. Nonetheless the unittest should figure out that something is listening on that port and pick another random port. I am going to issue a fix for this and probably do a new release of ooniprobe today (it was already scheduled to be done today, so this is very good timing). ~ Art. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
