From: Rostislav Svoboda <rostislav.svoboda@gmail.com>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: 51304@debbugs.gnu.org
Subject: bug#51304: guix upgrade fails on qutebrowser
Date: Wed, 20 Oct 2021 16:06:21 +0200 [thread overview]
Message-ID: <CAEtmmew=UpWzRY0EMAaotL59ns_tDq20g=XSoiQdrDK5bt_6OQ@mail.gmail.com> (raw)
In-Reply-To: <871r4fiz7f.fsf@nckx>
[-- Attachment #1: Type: text/plain, Size: 1757 bytes --]
Ha, you're right:
[Wed Oct 20 12:46:30 2021] Out of memory: Killed process 31394 (cc1plus)
total-vm:1523016kB, anon-rss:1436000kB, file-rss:0kB, shmem-rss:0kB,
UID:999 pgtables:2908kB oom_score_adj:0
[Wed Oct 20 12:47:09 2021] Out of memory: Killed process 31401 (cc1plus)
total-vm:1673940kB, anon-rss:1600700kB, file-rss:0kB, shmem-rss:0kB,
UID:999 pgtables:3240kB oom_score_adj:0
[Wed Oct 20 12:47:27 2021] Out of memory: Killed process 31413 (cc1plus)
total-vm:1803984kB, anon-rss:1700556kB, file-rss:0kB, shmem-rss:0kB,
UID:999 pgtables:3448kB oom_score_adj:0
which, in turn, surprises me, since I have 32GB of RAM. (And I thought
already I bought too much, ugh :)
BTW jpoiret advised me to use swap [1]. IMO swap should be present in the
default OS configuration, since recompilation happens by default, like 2 or
3 times out of 5 times I do `guix upgrade`.
Anyway thanks for the bug analysis.
Kind regards
Bost
[1] https://logs.guix.gnu.org/guix/2021-10-20.log#133303
Le mer. 20 oct. 2021 à 15:48, Tobias Geerinckx-Rice <me@tobias.gr> a écrit :
> Rostislav,
>
> Rostislav Svoboda 写道：
> > Ehm, sorry. The file is attached.
>
> Thanks! Hm. I might've oversold things with ‘useful’ in my
> previous message…
>
> The log just ends, without an error message as far as I can tell.
> I can only guess: maybe you ran out of memory? Does dmesg (or
> /var/log/messages, if you've since rebooted) contain any matches
> for "Out of memory"?
>
> One unsatisfying work-around for that is to build with
> --{max-jobs,cores}=1 to limit the number of build & make jobs if
> you were previously building in parallel. It will make the build
> take even longer, though…
>
> Sorry,
>
> T G-R
>
[-- Attachment #2: Type: text/html, Size: 3238 bytes --]
next prev parent reply other threads:[~2021-10-20 14:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <875ypw9c4w.fsf.ref@aol.com>
2021-10-20 11:37 ` bug#51304: guix upgrade fails on qutebrowser Rostislav Svoboda
2021-10-20 12:29 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2021-10-20 13:23 ` Rostislav Svoboda
2021-10-20 13:45 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2021-10-20 14:06 ` Rostislav Svoboda [this message]
2021-10-21 20:00 ` Leo Famulari
2022-02-03 15:56 ` Adam Maleszka via Bug reports for GNU Guix
2022-02-03 16:16 ` Leo Famulari
2022-02-05 22:08 ` Adam Maleszka via Bug reports for GNU Guix
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAEtmmew=UpWzRY0EMAaotL59ns_tDq20g=XSoiQdrDK5bt_6OQ@mail.gmail.com' \
--to=rostislav.svoboda@gmail.com \
--cc=51304@debbugs.gnu.org \
--cc=me@tobias.gr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).