Bug#878255: [Qa-jenkins-dev] Bug#878255: reproducible: increase the diffoscope timeout

2017-10-11 Thread Jens Reyer 
Hi Holger,

thanks for the quick answer.  Of course I understand you have to
prioritize overall performance over specific packages.


On 10/11/2017 07:46 PM, Holger Levsen wrote:
> I think you are better off with requesting the builds artifacts from our tests
> and then running diffoscope yourself.

I already tried with two local builds, unfortunately my machine ran out
of space and/or memory then.

But I'd be very happy if someone else could send me a diffoscope log of
wine(-development).  Should I manage that on my own, I'll update this
bug here.

Greets
jre

Bug#878255: [Qa-jenkins-dev] Bug#878255: reproducible: increase the diffoscope timeout

2017-10-11 Thread Holger Levsen 
severity 878255 wishlist
user jenkins.debian@packages.debian.org
usertag 878255 reproducible
thanks

Hi Jens, 

thanks for filing this bug report!

On Wed, Oct 11, 2017 at 07:30:45PM +0200, Jens Reyer wrote:
> as discussed on irc yesterday, I'd like to ask to increase the timeout
> of diffoscope from 120 minutes to something more, e.g. 6 hours.
>
> Reasoning is that the wine and wine-development packages always run into
> this, probably just because they are quite big.

I dont think that a very few packages being too unreproducible warrants this,
also I fear the effect we had with diffing build logs, where a few logs 
took very long to diff (and one full core…) and that resulted in the 
whole machine being slow…

> I understood you might look into splitting diffoscope into a separate
> job first, or make other changes so that this scales better.  Since this
> needs time to discuss, I don't expect an answer soon.  Whatever, it
> would be great to see results for Wine sometimes again.

I think you are better off with requesting the builds artifacts from our tests
and then running diffoscope yourself. You could also eg blog and publish the
diffoscope log that way.

(and btw, I dont think we should splitt diffoscope into a seperate job,
but rather run it on a different host then jenkins. And we plan to do this,
by moving to jenkins.d.org, at which point jenkins.d.net will become
profitrbricks-build0-amd64.debian.net and which will continue to run
diffoscope (but not all the other jenkins jobs anymore…)


-- 
cheers,
Holger


signature.asc
Description: PGP signature

Bug#878255: reproducible: increase the diffoscope timeout

2017-10-11 Thread Jens Reyer 
Package: jenkins.debian.org
Severity: normal

Hi all,

as discussed on irc yesterday, I'd like to ask to increase the timeout
of diffoscope from 120 minutes to something more, e.g. 6 hours.

Reasoning is that the wine and wine-development packages always run into
this, probably just because they are quite big.

I understood you might look into splitting diffoscope into a separate
job first, or make other changes so that this scales better.  Since this
needs time to discuss, I don't expect an answer soon.  Whatever, it
would be great to see results for Wine sometimes again.

Thanks and greets!
jre