dgilmore changed the topic of #fedora-riscv to: Fedora on RISC-V https://fedoraproject.org/wiki/Architectures/RISC-V || Logs: https://libera.irclog.whitequark.org/fedora-riscv || Alt Arch discussions are welcome in #fedora-alt-arches
iooi has joined #fedora-riscv
iooi has quit [Read error: Connection reset by peer]
iooi has joined #fedora-riscv
iooi has quit [Ping timeout: 260 seconds]
iooi has joined #fedora-riscv
iooi has quit [Read error: Connection reset by peer]
iooi has joined #fedora-riscv
iooi has quit [Read error: Connection reset by peer]
iooi has joined #fedora-riscv
iooi has quit [Read error: Connection reset by peer]
iooi has joined #fedora-riscv
iooi has quit [Read error: Connection reset by peer]
iooi has joined #fedora-riscv
iooi has quit [Read error: Connection reset by peer]
iooi has joined #fedora-riscv
iooi has quit [Read error: Connection reset by peer]
iooi has joined #fedora-riscv
iooi has quit [Read error: Connection reset by peer]
iooi has joined #fedora-riscv
iooi has quit [Read error: Connection reset by peer]
iooi has joined #fedora-riscv
iooi has quit [Read error: Connection reset by peer]
iooi has joined #fedora-riscv
iooi has quit [Read error: Connection reset by peer]
iooi has joined #fedora-riscv
bkeys has joined #fedora-riscv
iooi has quit [Read error: Connection reset by peer]
iooi has joined #fedora-riscv
iooi has quit [Read error: Connection reset by peer]
iooi has joined #fedora-riscv
iooi has quit [Read error: Connection reset by peer]
iooi has joined #fedora-riscv
iooi has quit [Read error: Connection reset by peer]
iooi has joined #fedora-riscv
iooi has quit [Read error: Connection reset by peer]
iooi has joined #fedora-riscv
<davidlt[m]> djdelorie: how is your board?
<djdelorie> seems ok, why?
<djdelorie> temp 50C
<davidlt[m]> It wasn't running a build I submitted thus I wonder what happened
<djdelorie> logins taking a while
<davidlt[m]> I will test it by sending another job, I guess
<djdelorie> kcompactd0 is using 100% of cpu?
<djdelorie> I don't even know what that is
<davidlt[m]> what is that :?
<davidlt[m]> Sounds like an issue
<djdelorie> looks like "memory compaction" kernel daemon
<davidlt[m]> There was a bug report some time ago (3 years ago): https://bugzilla.redhat.com/show_bug.cgi?id=1694305
<djdelorie> 2004 minutes of cpu time though...
<davidlt[m]> The only thing I find on the internet is: echo 0 > /proc/sys/vm/compaction_proactiveness
<davidlt[m]> reboot?
<djdelorie> sure
<djdelorie> this might take a while, I bet the reboot is fighting with kcompactd
iooi has quit [Read error: Connection reset by peer]
iooi has joined #fedora-riscv
iooi has quit [Read error: Connection reset by peer]
iooi has joined #fedora-riscv
<davidlt[m]> ok
<davidlt[m]> I am AFK, time for the morning walk before sun melts me
iooi has quit [Read error: Connection reset by peer]
iooi has joined #fedora-riscv
iooi has quit [Read error: Connection reset by peer]
iooi has joined #fedora-riscv
<djdelorie> there were a bunch of kernel backtraces on the console. I tried power cycling it and it didn't look like it was coming back up, so I just powered it off for now
<djdelorie> I'll look at it more when I have a bit more time (it's late night atm)
iooi has quit [Read error: Connection reset by peer]
iooi has joined #fedora-riscv
iooi has quit [Read error: Connection reset by peer]
iooi has joined #fedora-riscv
iooi has quit [Read error: Connection reset by peer]
iooi has joined #fedora-riscv
iooi has quit [Read error: Connection reset by peer]
iooi has joined #fedora-riscv
iooi has quit [Read error: Connection reset by peer]
iooi has joined #fedora-riscv
<davidlt[m]> I see
<davidlt[m]> Yeah, sounds like kernel might have decided to have a break :)
<davidlt[m]> Finally! Clang just finished and is now being packaged.
iooi has quit [Read error: Connection reset by peer]
<davidlt[m]> I had to restart this one so many times...
iooi has joined #fedora-riscv
jcajka has joined #fedora-riscv
pierosimonet has joined #fedora-riscv
pierosimonet has quit [Ping timeout: 260 seconds]
pierosimonet has joined #fedora-riscv
pierosimonet has quit [Remote host closed the connection]
masami has joined #fedora-riscv
masami has quit [Quit: Leaving]
bkeys has quit [Remote host closed the connection]
jcajka has quit [Quit: Leaving]
bkeys has joined #fedora-riscv
bkeys has quit [Remote host closed the connection]
bkeys has joined #fedora-riscv
davidlt has joined #fedora-riscv
<davidlt[m]> Conan Kudo: is there any process in Fedora that automatically ensures that packages can still build?
<Eighth_Doctor> Koschei
<davidlt[m]> How often does it attempt to re-build package to see that build process still works?
<defolos> davidlt: it tries if any of the transitive dependencies change
<davidlt[m]> I get impression that's nothing checks that packages continues to build.
<defolos> but there's an internal rate limit iirc
<davidlt[m]> E.g. glibc 2.36 mount header issues.
<Eighth_Doctor> we do rebuilds on dependency drift
<Eighth_Doctor> and we do mass builds
<Eighth_Doctor> but we don't do anything else currently
<davidlt[m]> I wonder why libcxxabi-14.0.5 kept failing and one fixed that one :/
esv has quit [Remote host closed the connection]
Esmil[m] has quit [Quit: You have been kicked for being idle]
<rwmjones> davidlt[m]: I get lots of messages from koschei and do look at them
<rwmjones> unfortunately there are many false positives
<rwmjones> occasionally it does find problems though, we had one a few days ago
<rwmjones> was found by koschei
<davidlt[m]> Btw, what happened to LLVM/Clang 15 in F37?
<rwmjones> I can understand if packagers ignore it though because SNR is quite low
<rwmjones> ?
<davidlt[m]> Could be, but it's annoying sometimes to patch packages that simply don't even build on x86_64 anymore.
<davidlt[m]> This was approved IIRC: https://fedoraproject.org/wiki/Changes/LLVM-15
<davidlt[m]> I don't see any builds or anything on dist-git
<davidlt[m]> That would incl. fixes for glibc 2.36 fs / mount headers.
<rwmjones> best to complain about them in BZ or on the mailing list rather than shouting at clouds
<davidlt[m]> Code Completion stage was reached thus this is probably F38 material now?
<rwmjones> a package shouldn't be broken on x86-64, at least only very rarely
<davidlt[m]> Nah, just not a productive week for me :)
<davidlt[m]> and I wish the official Koji wouldn't prune the logs from failed builds (I think, it keeps it for ~month)
davidlt has quit [Ping timeout: 268 seconds]
bkeys has quit [Remote host closed the connection]
cyberpear has quit [Quit: Connection closed for inactivity]
xxxxen0n has joined #fedora-riscv
guerby_ has joined #fedora-riscv
guerby has quit [*.net *.split]
xen0n has quit [*.net *.split]
<djdelorie> my board gets as far as "reached target initrd boot device" then eventually prints "bug: soft lockup, cpu#1 blah blah 22 seconds"
xxxxen0n is now known as xen0n