Bug#848403: diffoscope: FTBFS randomly (Fatal Python error: deallocating None)
On Thu, 5 Jan 2017, Ximin Luo wrote: > I've uploaded version 67 with that commit reverted: > > https://people.debian.org/~infinity0/apt/pool/main/d/diffoscope/ Tried 100 times in sid. Built ok 100 times. This is also what happened to version 66, so I'm not surprised. But let's see again when the package reaches testing. Thanks. ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
Bug#848403: diffoscope: FTBFS randomly (Fatal Python error: deallocating None)
Маша Глухова: > I can switch between being able/unable to reproduce this bug by just doing > git checkout 64/65, without touching any dependencies. git-bisect, with > test being running build 100 times, points me to the > commit 0c3c88fc930f3755e6f4fb0879783e2585863e85 as the first one after > which builds do not fail anymore. Manual testing confirms as much: I am > able to reproduce the bug before, but not after, said commit. > I am not sure what to make of it: the commit does not seem like it might > cause significant change. > I could also add that the bug does not seem to be connected with virual > machines or number of CPUs. I reproduced it both on 1-CPU KVM/QEMU and real > system (on two different computers with different numbers of CPUs). > Hope that information would provide someone with some insight. Santiago Vila: > I have built version 66 one hundred times in unstable. > The builds were made on 19 different autobuilders. > The number of failed builds has been zero. > (Previously it failed 10% of the time). I've uploaded version 67 with that commit reverted: https://people.debian.org/~infinity0/apt/pool/main/d/diffoscope/ Would be good if you people could test it to see if the test failures appear again. I agree it's unlikely that this commit is the direct cause, but it's possible that it is interacting with some lower-level stuff that either hides or reveals the bad behaviour. So the bug is probably still present, just hidden. In which case we should still keep a record of it. X -- GPG: ed25519/56034877E1F87C35 GPG: rsa4096/1318EFAC5FBBDBCE https://github.com/infinity0/pubkeys.git ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
Bug#850284: reprotest: add a mode to automatically attempt to detect which variations cause unreproducibility
Package: reprotest
Version: 0.4
Severity: wishlist
Dear Maintainer,
One idea that was brought up at RWS2 in Berlin (I forgot who came up with it
now, sorry) is to add a mode to automatically attempt to detect which
variations cause a package to be unreproducible.
For example, given variations {a, b, c}, if varying none of these results in a
reproducible build, but varying all of them makes it unreproducible, then
reprotest could automatically try to figure out which combinations of {a, b, c}
"cause" the unreproducibility.
Note that this is not as simple as a "bisect" algorithm which assumes that the
items to be tested are in some linear order. In fact, it's unclear if we can
make the algorithm (using the above example) more efficient than the brute
force method of "test a, test b, test c".
X
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable-debug'), (500,
'testing-debug'), (300, 'unstable'), (200, 'experimental'), (1,
'experimental-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages reprotest depends on:
ii apt-utils 1.4~beta2
ii diffoscope 63
ii libdpkg-perl 1.18.18
ii procps 2:3.3.12-3
ii python3-debian 0.1.29
ii python3-pkg-resources 32.0.0-1
pn python3:any
Versions of packages reprotest recommends:
ii disorderfs 0.5.1-1
ii locales-all 2.24-8
Versions of packages reprotest suggests:
ii autodep8 0.8
ii qemu-system 1:2.7+dfsg-3+b1
ii qemu-utils 1:2.7+dfsg-3+b1
ii schroot 1.6.10-2+b2
-- no debconf information
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
Re: [rb-general] Next Reproducible Builds IRC meeting on Tue Jan 17 2017 at 18:00 UTC
Chris Lamb wrote on Thu, Jan 05, 2017 at 11:13:59 +: > b) Please add any agenda items to: > > https://pad.riseup.net/p/reproducible-irc-meeting-7 > > Items should be suffixed with your name. Please try to add agenda items ahead of the meeting (at least 24 hours earlier, the more the better) so other participants can familiarize themselves with the agenda items ahead of time. ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
Processed: tagging 850055
Processing commands for cont...@bugs.debian.org: > tags 850055 + pending Bug #850055 [diffoscope] diffoscope: Comparing a device with a regular file fails Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 850055: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850055 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
Next Reproducible Builds IRC meeting on Tue Jan 17 2017 at 18:00 UTC
Dear all, Thanks to all who attended the IRC meeting on Tuesday and apologies for this email not being more forthcoming. The minutes and logs are available here: http://meetbot.debian.net/reproducible-builds/2017/reproducible-builds.2017-01-03-18.00.html The next meeting will be held at: http://time.is/compare/1800_17_Jan_2017_in_UTC $ date -d 'Tue Jan 17 18:00:00 UTC 2017' The meeting will be held on #reproducible-builds on OFTC, will start promptly and will last no longer than 1 hour. The meeting will be logged. The audience is for anyone interested in the Reproducible Builds effort, regardless of the project(s) they contribute to. :) What you need to do === a) Convert the above time in your timezone and add to your diary/planner. To reliably translate with respect to DST changes I suggest using a link such as: http://time.is/compare/1800_17_Jan_2017_in_UTC/Hobart b) Please add any agenda items to: https://pad.riseup.net/p/reproducible-irc-meeting-7 Items should be suffixed with your name. c) Forward this email to anyone you feel would be interested. d) If you cannot make it (but would have liked to) please add your name to the "Apologies" section on the agenda above. Thanks again and looking forward to see you there. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
