Hi Josh, [+ debbugs, please keep it in CC] Josh <firstname.lastname@example.org> writes:
Toggle quote (7 lines)>>Try using 'guix pull --keep-failed' and inspect the util-linux test>>suite logs in /tmp/guix-build-util-linux-2.35.1.drv-0.>> I don't see much...>> In /tmp/guix-build-util-linux-2.35.1.drv-0/util-linux-2.35.1, the only tests with something in "diff" (which assumes means failures) are the following:
Can you attach/var/log/guix/drvs/c7/0j91pkiv8qyazpv357ccc2jfjz91yw-util-linux-2.35.1.drv.bz2to this bug report? There should be a test suite summary that we can use to corroborate thebelow results with.
Toggle quote (28 lines)> tests/diff/ipcs:> mk-rm-msg.err mk-rm-sem.err mk-rm-shm.err>>> tests/diff/misc:> mbsencode-invalid-utf8 mbsencode-safe-utf8>> tests/diff/script:> replay-live>> And the only ones that appear to indicate an error are these:>> --- /dev/null 2020-05-20 19:14:36.552027894 +0000> +++ /tmp/guix-build-util-linux-2.35.1.drv-0/util-linux-2.35.1/tests/output/ipcs/mk-rm-msg.err 2020-05-20 19:18:45.988022283 +0000> @@ -0,0 +1,2 @@> +ipcrm: failed to parse argument: '0xd6733c2c> +0xd6733c2c'> --- /dev/null 2020-05-20 19:14:36.552027894 +0000> +++ /tmp/guix-build-util-linux-2.35.1.drv-0/util-linux-2.35.1/tests/output/ipcs/mk-rm-sem.err 2020-05-20 19:18:46.040022282 +0000> @@ -0,0 +1,2 @@> +ipcrm: failed to parse argument: '0xd0de0de7> +0xd0de0de7'> --- /dev/null 2020-05-20 19:14:36.552027894 +0000> +++ /tmp/guix-build-util-linux-2.35.1.drv-0/util-linux-2.35.1/tests/output/ipcs/mk-rm-shm.err 2020-05-20 19:18:46.092022281 +0000> @@ -0,0 +1,2 @@> +ipcrm: failed to parse argument: '0x4cec9993> +0x4cec9993'>
Toggle quote (11 lines)>>[+ debbugs, please keep it in CC]>> Will do, sorry about that.>>>Can you attach>>/var/log/guix/drvs/c7/0j91pkiv8qyazpv357ccc2jfjz91yw-util-linux-2.35.1.drv.bz2>>to this bug report?>> Attached. Looks like those three that I mentioned. Anything else look> interesting in there?
Thanks to a great coordinated effort on #guix, we tracked this problemdown to a regression in kernels 5.4.36 through 5.4.41 (or 5.6.8 through5.6.13 for users tracking that branch). You are running 5.4.38 according to the build log. It has been fixed in the latest kernel releases (5.4.42 and 5.6.14). I'm afraid you will have to downgrade your kernel in order to upgradeGuix! :-/
Toggle quote (10 lines)>>I'm afraid you will have to downgrade your kernel in order to upgrade>>Guix! :-/>> Ahh. Thanks for the response!>> How do I do that? I would assume it would be documented here, but I> can't seem to find it anywhere in the manual.>>  https://guix.gnu.org/manual/en/html_node/operating_002dsystem-Reference.html
There are a couple of options. The easiest way is to boot into an oldergeneration before running 'guix pull', if you have any generations withkernel < 5.4.36 lying around. Another is to pin the kernel to an older revision of Guix using an"inferior". You would have to update your system configuration alongthese lines:
Toggle quote (7 lines)>>There are a couple of options. The easiest way is to boot into an older>>generation before running 'guix pull', if you have any generations with>>kernel < 5.4.36 lying around.>> This worked! Thanks for the response. Sorry for the delay.. it took> awhile to update :)