IRC channel logs

2025-12-31.log

back to list of logs

<oliverD>I
<nmeum>what's the best way to debug failing system-tests? can I somehow configure marionette to let me log into the VM and get an interactive shell?
<oliverD>* I've been using Ethernet but its a bit inconvenient
<FuncProgLinux>oliverD: I think that device requires nonfree blobs :/
<oliverD>FuncProgLinux: Ok
<Rutherther>nmeum: what system test are you looking into?
<moorhuhn>Nananananana
<moorhuhn>Nanananananana
<moorhuhn>Thunder
<nmeum>Rutherther: system tests for a new services that I was working on: https://codeberg.org/guix/guix/pulls/5260 but was generally looking for advice regarding debugging marionette test failures. would be great if marionette could be configured to drop into a REPL on test failures
<Rutherther>nmeum: yeah, I don't know how to well debug them. But the regular way they're run doesn't allow for any debugging as they're ran as derivation builds and you cannot really use stdin with the guix-daemon
<nmeum>right, that's why I was wondering how others approach debugging of these tests
<nmeum>I ultimately ended up using print debugging
<cbaines>nmeum, if you make the module evaluate to an <operating-system>, then you can use guix system vm to run it and then debug
<cbaines>note that this doesn't run the tests, so you'll need to replicate what they do if that's necessary to reproduce the issue
<Rutherther>hey, could someone start the ci cuirass web frontend?
<cbaines>Rutherther, it was running, it had just stopped listening on it's port
<cbaines>I've restarted it
<Rutherther>thank you. How does that happen?
<cbaines>I'm not sure, I potentially had the same issue with the build coordinator
<cbaines>I wasn't able to determine the cause, so I just added a fiber to monitor itself https://codeberg.org/guix/build-coordinator/src/branch/trunk/guix-build-coordinator/utils/fibers.scm#L30-L54
<cbaines>I think this is also prior to switching from the fibers web server to the knots web server, so maybe the issue isn't present now
<Rutherther>hmm, interesting
<Rutherther>I've never seen a service just stop listening :D
<Rutherther>btw I was wondering, would it be possible to add information about state of the inputs to data.qa pages? https://data.qa.guix.gnu.org/gnu/store/kmly92l72k6k2dpb983shzbmsldhzfyh-webkitgtk-2.50.3.drv for example it could say as a single letter succeeded / scheduled / canceled in the same color as is the "Build status"
<cbaines>Rutherther, could do, although maybe it would be better to have that on the bffe pages, rather than in the data service
<cbaines>e.g. on here instead https://bordeaux.guix.gnu.org/build/7699b328-5965-44f4-a1a5-67e6401cbd96
<cbaines>the information is already exposed by the build coordinator in the JSON response https://bordeaux.guix.gnu.org/build/7699b328-5965-44f4-a1a5-67e6401cbd96.json
<cbaines>so all that needs doing is the bffe code needs to display the inputs and there build status https://codeberg.org/guix/bffe/src/branch/trunk/bffe/view/build.scm
<Rutherther>yeah, that seems simpler then
<Rutherther>I am wondering, though. Can it happen sometimes that there are no builds scheduled, yet? And in those cases it wouldn't be possible to check what' missing?
<cbaines>Rutherther, if you're interested in hacking this together, you should be able to run the bffe locally, pointing at bordeaux.guix.gnu.org, and I think the build pages should work
<Rutherther>I will definitely try to, but probably not in the next few days. But I will see
<Rutherther>thanks for the pointers
<cbaines>that can happen, but you'd see this in the data service, there wouldn't be a link to a build
<cbaines>maybe there are other reasons why builds havent happened, e.g. setup failures, but that's another benefit of doing this in the bffe, as it's easier to get data from the build coordinator there to show on the page
<Rutherther>cbaines: yeah, which means you won't be able to check the state of the inputs in such cases, right? I am not sure how exactly the scheduling works, if it schedules all or does it somehow look if most inputs are built already to schedule something?
<cbaines>Rutherther, the bordeaux build coordinator is setup to only allocate builds to agents if all the inputs have been built
<Rutherther>hmm, how is it possible then that webkitgtk is scheduled, despite at least one of the inputs not being built yet? gtk to be specific
<cbaines>it's scheduled, but that doesn't mean it's allocated to an agent
<Rutherther>okay, I meant when the scheduling happens, not allocation
<cbaines>like Cuirass, all builds start in the scheduled state
<Rutherther>okay, great
<Rutherther>so I would definitely be satisfied with the solution you proposed then. I will try to take a look into collecting the data and showing them nicely. I think we can just show the 'best' result rather than showing all the builds of the dependencies if there are multiple - ie. if they got canceled or some failed, but something succeeded
<cbaines>great, do let me know if you've got any questions :)
<loopified>So, I have installed 1.5 and, after unlocking the system, things seem to be working great. But, as was the case before, I still have issues related to my keyboard layout and disk decryption.
<Rutherther>loopified: what issues and are they reported already?
<loopified>I set my keyboard to us english and the layout to dvorak. After restarting, I have to use qwerty to type my password once, and then type it again in dvorak. This isn't new.
<loopified>Rutherther: Sorry, I'm running with new years stuff and haven't looked it up. Thought it was best if I at least said something here for now. I can look it up properly later.
<Rutherther>loopified: and that is the only issue?
<Rutherther>just checking... since you've said issues, so I am not sure if this is the only one or there is more
<loopified>Also, if I make a mistake once in the first prompt, it already drops me at grub "repl". I'd expect it to give me a couple more chances to type the password. And, if I exit the grub repl, it crashes.
<Rutherther>yeah and in the second prompt if you do 3 mistakes, it also becomes sort of irrecoverable :(
<loopified>Rutherther: yep. Was about to say that.
<loopified>Again, I've looked at the issue years ago. I don't have any recollection of my findings at the time though. I'll take a better look at this issue later.
<loopified>Rutherther: I have to go now but, again, besides that, everything went by smoothly so far. Thanks again and happy new year!
<Rutherther>thanks for the report, happy new year to you as well
<SirNeon>Have you considered using a keyboard that supports QMK firmware?
<SirNeon>I'm also an alternative layout guy and having it stored in the keyboard itself has been super convenient.
<loopified>SirNeon: I use a zsa moonlander. I always have a fallback qwerty at hand, so I can at least work around the issue to a certain degree.
<SirNeon>I just flashed my layout into my Corne board and now I never bother with switching keyboard layouts on the actual OS.
<loopified>Same, unless I need to use my notebook without my external keyboard, that is.
<loopified>gtg! :D
<loopified>o/
<SirNeon>Take care. o/
<bdju>Does anyone use libratbag/piper on Guix System? Does it need any special setup? I just got a Logitech G305 mouse and Piper says it can't see the mouse, but I've never actually tried to use Piper on here before that I can remember, so maybe it's just the program that's broken. Nothing found with ratbagctl list either. The mouse itself seems to be working.
<tusharhero>I am trying to build emacs-next-pgkt on the master branch with this command:
<tusharhero>guix shell emacs-next-pgtk --with-source=emacs-next-pgtk=$PWD
<tusharhero>(I have a checkout of the master branch)
<tusharhero>but it fails with this error in the log
<tusharhero>./autogen.sh: line 325: git: command not found
<tusharhero>entire log: http://dpaste.com/2CQJZX7H3
<identity>i assume autogen.sh needs patching
<tusharhero>which package contains the `glib-compile-schemas' command?
<tusharhero>glib doesnt' seem to contain it
<Rutherther>tusharhero: it is glib. But the bin output
<tusharhero>how do I get that in a guix shell?
<tusharhero>I am trying to build emacs
<Rutherther>what is your invocation?
<tusharhero>I have a manifest.scm that looks like this http://dpaste.com/EGR5X7D8X
<Rutherther>then add "glib:bin" specification
<tusharhero>thanks