hi,

On Wed, Sep 20, 2023 at 12:25:36PM +0000, Holger Levsen wrote:
> so I've powercycled the machine and also disabled the armhf workers now.
> (under the (weak) assumption that this bug is mostly trigged when running
> diffoscope on 32bit .debs...)

so on Sep 23rd I made diffoscope run under ionice -n6, and so far the machine
has gone down on its knees yet. 

and on Sep 25th I said this on #debian-reproducible:

when i made diffoscope run under ionice i was wondering if there were changes 
in the linux 
scheduler causing the probs we saw... now not seeing the machine go down to its 
knees 
within 60h uptime i'm saying this to "provoke" the problem coming back
however, looking at 
jenkins.debian.net/munin/static/dynazoom.html?cgiurl_graph=/munin-cgi/munin-cgi-graph&plugin_name=debian.net/jenkins.debian.net/uptime&size_x=800&size_y=400&start_epoch=1661108749&stop_epoch=1695668749
I can that the highest uptime was 15 days..
(since upgrading to bookworm which is when the probs started)
it could also be kernel related, with switching to bookworm
we switched from 5.10.0 to 6.1.0...
so my next stabs c/would be: 
a.) increase swap 
b.) upgrade to kernel 6.4.0 from bpo
c.) something else

Today someone also suggested to use zram to compress swap...

and, fwiw, https://tests.reproducible-builds.org/debian/index_performance.html
still doesnt look good for yesterday...


-- 
cheers,
        Holger

 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁  holger@(debian|reproducible-builds|layer-acht).org
 ⢿⡄⠘⠷⠚⠋⠀  OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C
 ⠈⠳⣄

I don't want to see your smile.
I want to see your intelligence, compassion, integrity, and consideration.
(@1goodtern)

Attachment: signature.asc
Description: PGP signature

Reply via email to