IRC channel logs

2021-05-30.log

back to list of logs

<oriansj>mihi: well I personally have no problem with tests written in perl. Could I just ask that you restrict yourself to the mini-perl subset that is quite easy to bootstrap?
<oriansj>also your pull request was merged
<oriansj>A final reminder that today (sunday) is the last day to vote. (details here: https://paste.debian.net/1198887/ )
<robin>oriansj, what's the voting process and who is eligible to vote? (i'm behind on scrollback on...a lot of channels, now that i'm on 60+ instead of ~30)
<oriansj>robin: you post (my vote) along with a paste of your vote. Everyone here is eligible to vote.
<robin>oriansj, ty
<siraben>Melg8: Ok, I'm running `sudo nix-shell -I nixpkgs=channel:nixpkgs-unstable -p python3 python38Packages.requests qemu linuxPackages_4_4.kernel --run 'python3 ./rootfs.py --kernel /nix/store/kg5wa8hww2g6zc03yas7llbzrbip4b5b-linux-4.4.267/bzImage --force_timestamps --tmpdir ./temp'` on a real instance of NixOS and it seems to be working
<siraben>At the least it should be possible to adjust it to run in a Docker instance of NixOS (which is quite minimal, but the lack of sudo is a problem when the python program executes)
<siraben>Could not access KVM kernel module: No such file or directoryqemu-system-x86_64: failed to initialize kvm: No such file or directory
<siraben>Ah I have to add
<siraben>boot.kernelModules = [ "kvm-intel" ];
<siraben>virtualisation.libvirtd.enable = true;
<siraben>to my config
<siraben>Looks like since the cloud compute instance doesn't have kvm support, I cannot run live-bootstrap, unfortunately.
<c4droid>Hi, someone have idea about test suites failed for mescc-tools? I got some failed test
<c4droid>the test suites test/test1 throw the Segment fault
***stikonas_ is now known as stikonas
<oriansj>c4droid: they shouldn't be failing, unless the generating binaries are running non-target platforms.
<oriansj>in fact the only failing test in debian: https://buildd.debian.org/status/package.php?p=mescc%2dtools is because vagrantc hasn't since 1/24 commit d792fb4bd24b4c1e2723abc9200065cb66c20271 fixes that single failure.
<oriansj>So the first thing you should check is did you do git submodule init and git submodule update --checkout ?
<oriansj>The second thing you should check is what get_machine --os and get_machine (no options) returns.
<oriansj>because if your architecture isn't amd64 or your OS doesn't show as Linux; then there is nothing that could segfault because the test would just be doing a sha256sum on the generated binary only. Which if the sha256sum matches and the execute bit is set; the only way the test could fail is if your kernel is violating the ELF spec.
<oriansj>but I am more than happy to help you hunt down the exact cause of the segfault. As such behavior is completely unacceptable for mescc-tools
<oriansj>now that is a handy tip for erc
<civodul>hi!
<civodul>glad this channel migrated
<civodul>i inadvertently connected to freenode and was told i was banned from #bootstrappable
<civodul>for other channels it said i needed to be invited
<civodul>weird stuff!
<vagrantc>yeah, freenode, what a mess :/
<vagrantc>i think i fled right before it started to get really crazy
<civodul>yeah, sadness
<stikonas>some channels are still preparing to migrate...
<stikonas>I still have to stay on some channels on Leenode...
<stikonas>hopefully not for too long