Version: 67
Hi.
After building this version on stretch today 201 times, with different
autobuilders, the result was 200 successful builds and one sbuild hang.
Compared to the previous 10% failure rate, the sbuild hang is most
likely a completely different issue, so I hereby declare this bug as
On Fri, Jan 06, 2017 at 01:43:43PM +, Holger Levsen wrote:
> On Thu, Jan 05, 2017 at 11:36:17PM +0100, Santiago Vila wrote:
> > But let's see again when the package reaches testing.
>
> you could build that package against testing today?! once or a hundred
> times ;)
Not trivially using
On Thu, Jan 05, 2017 at 11:36:17PM +0100, Santiago Vila wrote:
> But let's see again when the package reaches testing.
you could build that package against testing today?! once or a hundred
times ;)
--
cheers,
Holger
signature.asc
Description: Digital signature
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
Маша Глухова:
> 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
>
Маша Глухова wrote:
> It seems likely that one of the changes fixed this bug as a side effect,
> but I cannot yet tell which one.
My hunch is that its the libvirt 2.5.0-2 that was upload to unstable on 22nd
Feb. The timeline fits better and nothing has really changed in the guestfs
code... :)
I should add, I also had failures with diffoscope version 64 and older, but
no failures on newer versions. It seems likely that
one of the changes fixed this bug as a side effect, but I cannot yet tell
which one.
___
Reproducible-builds mailing list
Hi.
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).
If you do not remember what kind of change may have fixed this,
then there must be some broken
On Mon, Dec 26, 2016 at 07:37:55PM +, Chris Lamb wrote:
> Santiago Vila wrote:
>
> > If I do "python3 -m pytest" afterwards this is what it's shown:
> […]
> > Note: This is still diffoscope_63 in stretch, not sure if I should
> > better try the version in unstable and forget completely about
Santiago Vila wrote:
> If I do "python3 -m pytest" afterwards this is what it's shown:
[…]
> Note: This is still diffoscope_63 in stretch, not sure if I should
> better try the version in unstable and forget completely about this
> version.
Please do so; the icc tests were fixed later and there
On Sat, 24 Dec 2016, Ximin Luo wrote:
> For all you people that already have single-CPU KVM VMs set up, can you
> please try to reduce your test cases that still reproduce the bug?
>
> For example, can you still reproduce it with `debian/rules clean build`? What
> about `python3 -m pytest`?
11 matches
Mail list logo
