unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: bo0od <bo0od@riseup.net>
To: Mark H Weaver <mhw@netris.org>, Tobias Geerinckx-Rice <me@tobias.gr>
Cc: 47717@debbugs.gnu.org
Subject: bug#47717: guix outrageously exhaust itself (freeze) when there is package build failure
Date: Fri, 16 Apr 2021 03:08:08 +0000	[thread overview]
Message-ID: <ae83cce7-fcde-c0d9-3a72-052615fb3d25@riseup.net> (raw)
In-Reply-To: <878s5jiann.fsf@netris.org>

 > Many people are happily using it, and are quite enthusiastic about it,
 > so evidently it's "usable".  That doesn't imply that it's good for
 > everyone.  Perhaps you would prefer a more traditional distro, or one
 > that has had more time to mature.  If so, that's okay.

I can say that on almost any dying distro like slackware or so. But we 
need to overcome the issues which are leading to dead projects/distros.

The above issue is one of them if left without solution.

Mark H Weaver:
> bo0od <bo0od@riseup.net> writes:
> 
>>   > I mean the ‘outrageously’ part.  When Linux runs out of memory, it
>>   > freezes up.  Moral judgment is futile.  Better to adopt raingloom's
>>   > earlyoom suggestion or similar.
>>
>> Im using default guix system nothing special, If this package usable to
>> solve these stuff i suggest then to include it by default.
> 
> 'earlyoom' behavior is not necessarily desirable.  I, for one, have a
> fairly old computer by today's standards, and sometimes I ask it to do
> intensive things that are at the edge of its capabilities, such as
> compiling GNU IceCat.  An aggressive 'earlyoom' might prematurely abort
> jobs that could have completed, and thereby make it impossible for me to
> continue using this old computer for development.
> 
> With that in mind, it's far from clear that 'earlyoom' should be our
> default behavior.  It's good to have it as an option, though.
> 
>>   > 4 GiB is absolutely not enough to build an outrageous amount of ‘modern’
>>   > software, especially in parallel (so not using --cores=1 --max-jobs=1)
>>   > to make use of those expensive cores.
>>   >
>>   > I'm disgusted too.
>>
>> Yes it is, But you know this cant be a way of life with guix for end
>> user no? Something by default should solve this matter otherwise this is
>> not usable distro.
> 
> Many people are happily using it, and are quite enthusiastic about it,
> so evidently it's "usable".  That doesn't imply that it's good for
> everyone.  Perhaps you would prefer a more traditional distro, or one
> that has had more time to mature.  If so, that's okay.
> 
>        Regards,
>          Mark
> 




  reply	other threads:[~2021-04-16 16:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-12  5:39 bug#47717: guix outrageously exhaust itself (freeze) when there is package build failure bo0od
2021-04-12 18:04 ` bug#47717: guix becomes unresponsive while building the 'vigra' package Leo Famulari
2021-04-13 11:03   ` bo0od
2021-04-13 17:35     ` Leo Famulari
2021-04-14 16:06       ` bo0od
2021-04-14  8:21     ` Mark H Weaver
2021-04-14 17:08       ` bo0od
2021-04-12 18:41 ` bug#47717: guix outrageously exhaust itself (freeze) when there is package build failure Tobias Geerinckx-Rice via Bug reports for GNU Guix
2021-04-12 22:59   ` raingloom
2021-04-13 11:34   ` bo0od
2021-04-14  0:40     ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2021-04-14 16:54       ` bo0od
2021-04-15 19:56         ` Mark H Weaver
2021-04-16  3:08           ` bo0od [this message]
2021-04-21  1:35           ` Maxim Cournoyer
2021-04-22 18:34             ` Mark H Weaver
2021-04-25  8:14               ` Efraim Flashner

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=ae83cce7-fcde-c0d9-3a72-052615fb3d25@riseup.net \
    --to=bo0od@riseup.net \
    --cc=47717@debbugs.gnu.org \
    --cc=me@tobias.gr \
    --cc=mhw@netris.org \
    /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).