IRC channel logs

<mange>Is there a way to run a Cuirass remote worker which will run builds with --cores set? I haven't looked hard, but I didn't find anything obvious in the Guix configuration options.

<roptat>hi guix!

<roptat>do you know how I can "touch" a file in guile?

<roptat>I want to reset the modification date, not change the content

<identity>(system* "touch" filename) is definitely one way to go about it

<roptat>ah, when looking with the correct keywords, the manual gives "utime"

<ekaitz>hi

<yarl>hi

<janneke>o/

<ekaitz>make-mesboot0's build is frozen in riscv64

<ekaitz>it's reproducible

<ekaitz>basically: suspended shell linux

<janneke>ekaitz: is that a regression of some sort?

<ekaitz>janneke: i've seen that happen before, but it happened earlier in the bootstrapping chain

<ekaitz> https://codeberg.org/ekaitz-zarraga/commencement.scm/src/branch/master/commencement.scm#L303 I had this comment here for long time

<ekaitz>but that produces a circular dependency and it's problematic

<ekaitz>locally i can use it, but we need to sort that out in order to merge the riscv bootstrap

<janneke>ekaitz: hmm, is there a bug report @ codeberg about this?

<janneke>hmm

<coopi>Finally managed to to fix a longstanding bug within my system!!

<coopi> https://codeberg.org/coopi/velcelis/src/branch/main/src/hosts/futamichi.org#headline-26

<coopi>I couldn't figure out why my audio was broken

<coopi>turns out the culprit was (the lack of) sof-firmware

<janneke>coopi: yeah, bah; even sound needs non-free code (or a non-free signature on otherwise free code to load?)

<janneke>ekaitz: is there a bug report @ codeberg on this?

<coopi>janneke: ive kinda just given up on the "free-ness" of modern hardware :')

<coopi>right now im just ecstatic to fix an issue which was personally one of the most annoying one i'd faced

<ekaitz>janneke: not yet. I'm building it in my laptop, virtualized, trying to reproduce

<janneke>coopi: well, what i mean is that it would be good to know about these "hidden" problems

<janneke>ekaitz: yeah, a reproducer would be great

<ekaitz>janneke: it reproduces in a visionfive2, but a virtualized reproducer is key here

<yelninei>janneke: I just found c86448f38b74b2da8f76ebbf3bdfaa43053bb3a8 , did the fibers test work for you before? the preemption tests hangs for me because something is not implemented https://codeberg.org/guix/guix/issues/2471#issuecomment-9550127

<yelninei>or was this just for the cross patch?

<janneke>yelninei: i believe i only looked at the cross-build for fibers, yes

<janneke>ekaitz: right

<janneke>yelninei: re: https://codeberg.org/guix/guix/issues/2471#issuecomment-9550127, so is it clear to you wether this is a hurd glibc bug (hurd glibc missing feature?), or a fibers bug (depending on an optional feature in glibc, that is missing on the hurd?)

<yelninei>janneke: yes the hurd glibc does not support the feature that fibers uses for scheduling interrupts (clock_nanosleep with a clock from pthread-getcpuclockid)

<yelninei>This is not a problem for shepherd because it disables preemption, but causes the fibers test to hang because the expected interrupt never happens

<janneke>yelninei: that sounds as if it warrants a bug report for fibers?

<yelninei>janneke: I'll forward the issue to fibers. Should the test be skipped in the meantime?

<janneke>yelninei: lovely, thanks! and sure; let's skip the test in the mean time

<janneke>you can add a comment referencing the issue(s) in the code skpping the test

<yelninei>there is another test failing afterwards because the heap grows 4x instead of the "allowed" 2x

<janneke>maybe use same recipe, i.e., another fibers bug mentioning this?

<janneke>yelninei: without having looked at the details, if the test demands memory usage to be less, and it isn't, something is wrong :)

<janneke>the fiber developers may well defer this bug to guile again, but i don't see that a as a problem

IRC channel logs

2026-02-15.log