Icedove 78.10.0 build stuck at 'unpack' phase

  • Done
  • quality assurance status badge
Details
5 participants
  • bo0od
  • Jonathan Brielmaier
  • Leo Famulari
  • Ludovic Courtès
  • Mark H Weaver
Owner
unassigned
Submitted by
bo0od
Severity
normal
B
B
bo0od wrote on 7 May 2021 08:43
(address . bug-guix@gnu.org)
f03811e1-1b41-a5e9-3941-3bea10ddf7ce@riseup.net
Hi There,

I have installed icedove previous version so as icecat very smoothly
went, But this icedove version seems to be having problems.

After JSON issue (#48152) got fixed, The error went off but another
issue appeared which is the process stuck on 'unpack' phase (see the
uploaded image for more clarification) whether by upgrading the previous
icedove version to the current one or by installing it freshly.

ThX!
Attachment: icedove.png
L
L
Leo Famulari wrote on 8 May 2021 17:48
(name . bo0od)(address . bo0od@riseup.net)(address . 48273@debbugs.gnu.org)
YJayubL5QiKCVySl@jasmine.lan
On Fri, May 07, 2021 at 06:43:09AM +0000, bo0od wrote:
Toggle quote (5 lines)
> After JSON issue (#48152) got fixed, The error went off but another issue
> appeared which is the process stuck on 'unpack' phase (see the uploaded
> image for more clarification) whether by upgrading the previous icedove
> version to the current one or by installing it freshly.

Thanks for the report.

Please try again with '--verbosity=3' [0] so that we can see what it's
doing.

[0]
B
B
bo0od wrote on 8 May 2021 21:19
(name . Leo Famulari)(address . leo@famulari.name)(address . 48273@debbugs.gnu.org)
bbf8c583-3b87-4200-34b3-ab9fccc8dcc7@riseup.net
Toggle quote (2 lines)
> Please try again with '--verbosity=3' [0] so that we can see what it's

stuck here:

"s|PACKAGES/icecat|PACKAGES/firefox|g;
s/GNU Public/Mozilla Public/g;
s/GNU Foundation/Mozilla Foundation/g;
s/GNU Corporation/Mozilla Corporation/g;
s/icecat\.com\>/firefox.com/g;
s/IceCat-Spdy/Firefox-Spdy/g;
s/icecat-accounts/firefox-accounts/g;
s/IceCatAccounts/FirefoxAccounts/g;
s|https://www\.mozilla\.org/icecat/?utm_source=synceol|https://www.mozilla.org/firefox/?utm_source=synceol|g;

s|www\.gnu\.org/software/gnuzilla/icecat-help|libreplanet.org/wiki/Group:IceCat/Help|g;
' '{}' ';'"

(check the uploaded logs, i have done 2 attempts of installing icedove
and both stopped at the same place)



Leo Famulari:
Toggle quote (14 lines)
> On Fri, May 07, 2021 at 06:43:09AM +0000, bo0od wrote:
>> After JSON issue (#48152) got fixed, The error went off but another issue
>> appeared which is the process stuck on 'unpack' phase (see the uploaded
>> image for more clarification) whether by upgrading the previous icedove
>> version to the current one or by installing it freshly.
>
> Thanks for the report.
>
> Please try again with '--verbosity=3' [0] so that we can see what it's
> doing.
>
> [0]
> https://guix.gnu.org/manual/devel/en/html_node/Common-Build-Options.html
>
Attachment: icedovelog
Attachment: icedovelog2
M
M
Mark H Weaver wrote on 8 May 2021 21:59
(address . 48273@debbugs.gnu.org)
87zgx5j8sa.fsf@netris.org
Hi,

In your original bug report, you stated that the build was stuck in the
'unpack' phase of the 'icedove' package, and you attached a screenshot
showing that phase in-progress.

In this later followup message, you're stating something different: that
it's getting stuck in an earlier package build, namely while building
the 'icecat' source tarball.

Note that the 'icedove' package build cannot even begin until after the
'icecat' source tarball has been successfully built, so it seems that
you had a fully built 'icecat' source tarball on your system at some
point.

bo0od <bo0od@riseup.net> writes:

Toggle quote (20 lines)
> > Please try again with '--verbosity=3' [0] so that we can see what it's
>
> stuck here:
>
> "s|PACKAGES/icecat|PACKAGES/firefox|g;
> s/GNU Public/Mozilla Public/g;
> s/GNU Foundation/Mozilla Foundation/g;
> s/GNU Corporation/Mozilla Corporation/g;
> s/icecat\.com\>/firefox.com/g;
> s/IceCat-Spdy/Firefox-Spdy/g;
> s/icecat-accounts/firefox-accounts/g;
> s/IceCatAccounts/FirefoxAccounts/g;
> s|https://www\.mozilla\.org/icecat/?utm_source=synceol|https://www.mozilla.org/firefox/?utm_source=synceol|g;
>
> s|www\.gnu\.org/software/gnuzilla/icecat-help|libreplanet.org/wiki/Group:IceCat/Help|g;
> ' '{}' ';'"
>
> (check the uploaded logs, i have done 2 attempts of installing icedove
> and both stopped at the same place)

This part of the process takes a long time, but at least on my Thinkpad
X200 system (Core 2 Duo, 4 GB RAM, 8 GB swap), it _does_ eventually
finish.

Did the build attempt fail on its own, or did you abort it?

Thanks,
Mark

--
Disinformation flourishes because many people care deeply about injustice
but very few check the facts. Ask me about https://stallmansupport.org.
B
B
bo0od wrote on 11 May 2021 02:21
(address . 48273@debbugs.gnu.org)
493738bf-1a3b-259d-8314-6d8791cf7dcc@riseup.net
Toggle quote (1 lines)
> In your original bug report, you stated that the build was stuck in the
> 'unpack' phase of the 'icedove' package, and you attached a screenshot
> showing that phase in-progress.

Good thanks for the notification, I didnt expect it takes really long
time for it to move from one stage to another thus you see report and
the uploaded text are different in what they are saying (because i
actually run it and leave for half hour to couple of hours)

Since you said these are giving 2 different readings then the issue is
with timing, So i kept it for like 24 hour (or more) and now i hope the
log make more sense since there are too many fail,warnings..etc


(I couldnt upload the txt file due to size limitation forced on emails)

Mark H Weaver:
Toggle quote (46 lines)
> Hi,
>
> In your original bug report, you stated that the build was stuck in the
> 'unpack' phase of the 'icedove' package, and you attached a screenshot
> showing that phase in-progress.
>
> In this later followup message, you're stating something different: that
> it's getting stuck in an earlier package build, namely while building
> the 'icecat' source tarball.
>
> Note that the 'icedove' package build cannot even begin until after the
> 'icecat' source tarball has been successfully built, so it seems that
> you had a fully built 'icecat' source tarball on your system at some
> point.
>
> bo0od <bo0od@riseup.net> writes:
>
>> > Please try again with '--verbosity=3' [0] so that we can see what it's
>>
>> stuck here:
>>
>> "s|PACKAGES/icecat|PACKAGES/firefox|g;
>> s/GNU Public/Mozilla Public/g;
>> s/GNU Foundation/Mozilla Foundation/g;
>> s/GNU Corporation/Mozilla Corporation/g;
>> s/icecat\.com\>/firefox.com/g;
>> s/IceCat-Spdy/Firefox-Spdy/g;
>> s/icecat-accounts/firefox-accounts/g;
>> s/IceCatAccounts/FirefoxAccounts/g;
>> s|https://www\.mozilla\.org/icecat/?utm_source=synceol|https://www.mozilla.org/firefox/?utm_source=synceol|g;
>>
>> s|www\.gnu\.org/software/gnuzilla/icecat-help|libreplanet.org/wiki/Group:IceCat/Help|g;
>> ' '{}' ';'"
>>
>> (check the uploaded logs, i have done 2 attempts of installing icedove
>> and both stopped at the same place)
>
> This part of the process takes a long time, but at least on my Thinkpad
> X200 system (Core 2 Duo, 4 GB RAM, 8 GB swap), it _does_ eventually
> finish.
>
> Did the build attempt fail on its own, or did you abort it?
>
> Thanks,
> Mark
>
L
L
Leo Famulari wrote on 11 May 2021 03:30
(name . bo0od)(address . bo0od@riseup.net)
YJneGm9xmJ6lJjZC@jasmine.lan
On Tue, May 11, 2021 at 12:21:33AM +0000, bo0od wrote:
Toggle quote (2 lines)
> (I couldnt upload the txt file due to size limitation forced on emails)

Just FYI, if you compress your file with XZ it shrinks to 2 MB:

$ xz icedovefinel.txt
$ du -sh icedovefinel.txt.xz
2.0M icedovefinel.txt.xz
L
L
Leo Famulari wrote on 11 May 2021 03:31
(name . bo0od)(address . bo0od@riseup.net)
YJnejY2qRWqR89KZ@jasmine.lan
On Tue, May 11, 2021 at 12:21:33AM +0000, bo0od wrote:
Toggle quote (4 lines)
> Since you said these are giving 2 different readings then the issue is with
> timing, So i kept it for like 24 hour (or more) and now i hope the log make
> more sense since there are too many fail,warnings..etc

I see on line 422929 this error:

231:25.01 g++: internal compiler error: Killed (program cc1plus)

That usually means that you ran out of memory / RAM.

I've attached the compressed log file so that others can read it.
Attachment: icedovefinel.txt.xz
M
M
Mark H Weaver wrote on 13 May 2021 20:36
(address . 48273@debbugs.gnu.org)
87y2cijx9e.fsf@netris.org
Hi Leo,

Leo Famulari <leo@famulari.name> writes:

Toggle quote (9 lines)
> On Tue, May 11, 2021 at 12:21:33AM +0000, bo0od wrote:
>> Since you said these are giving 2 different readings then the issue is with
>> timing, So i kept it for like 24 hour (or more) and now i hope the log make
>> more sense since there are too many fail,warnings..etc
>
> I see on line 422929 this error:
>
> 231:25.01 g++: internal compiler error: Killed (program cc1plus)

Thanks, Leo, for finding the relevant line and attaching the build log.

Toggle quote (2 lines)
> That usually means that you ran out of memory / RAM.

Agreed. Note that I've never actually tried to build 'icedove' from
source, so I don't know if 4GB RAM + 8GB swap is enough to build it.

It might possibly be relevant that our 'icecat' package uses a different
build method than our 'icedove' package. Our 'icecat' package uses the
GNU build system approach of running './configure' and 'make', whereas
'icedove' uses the Mozilla-preferred approach of creating a '.mozconfig'
file and running './mach'.

These different approaches might result in different numbers of
concurrent build processes being run during the build. On my system
(Thinkpad X200, Core 2 Duo), the 'icecat' build system runs 2 processes
concurrently during the build. This is the most that my 4 GB of RAM can
support, and even then I must shut down other memory intensive processes
(such as modern web browsers) in order for it to work.

When building 'icedove', after the 'build' phase has started compiling
code with GCC or Rustc, can you see how many compile jobs are running at
once? If it's more than 2, that's likely to be the problem.

If 'icedove' does not honor the Guix --cores option, that should be
fixed.

Regards,
Mark

--
Disinformation flourishes because many people care deeply about injustice
but very few check the facts. Ask me about https://stallmansupport.org.
B
B
bo0od wrote on 13 May 2021 21:28
(address . 48273@debbugs.gnu.org)
6e57faef-a1fb-f66e-e841-19c9fb6ad700@riseup.net
Toggle quote (1 lines)
> When building 'icedove', after the 'build' phase has started compiling
> code with GCC or Rustc, can you see how many compile jobs are running at
> once? If it's more than 2, that's likely to be the problem.

Included several output readings from ps command hope it helps.


Toggle quote (43 lines)
> Hi Leo,
>
> Leo Famulari <leo@famulari.name> writes:
>
>> On Tue, May 11, 2021 at 12:21:33AM +0000, bo0od wrote:
>>> Since you said these are giving 2 different readings then the issue is with
>>> timing, So i kept it for like 24 hour (or more) and now i hope the log make
>>> more sense since there are too many fail,warnings..etc
>>
>> I see on line 422929 this error:
>>
>> 231:25.01 g++: internal compiler error: Killed (program cc1plus)
>
> Thanks, Leo, for finding the relevant line and attaching the build log.
>
>> That usually means that you ran out of memory / RAM.
>
> Agreed. Note that I've never actually tried to build 'icedove' from
> source, so I don't know if 4GB RAM + 8GB swap is enough to build it.
>
> It might possibly be relevant that our 'icecat' package uses a different
> build method than our 'icedove' package. Our 'icecat' package uses the
> GNU build system approach of running './configure' and 'make', whereas
> 'icedove' uses the Mozilla-preferred approach of creating a '.mozconfig'
> file and running './mach'.
>
> These different approaches might result in different numbers of
> concurrent build processes being run during the build. On my system
> (Thinkpad X200, Core 2 Duo), the 'icecat' build system runs 2 processes
> concurrently during the build. This is the most that my 4 GB of RAM can
> support, and even then I must shut down other memory intensive processes
> (such as modern web browsers) in order for it to work.
>
> When building 'icedove', after the 'build' phase has started compiling
> code with GCC or Rustc, can you see how many compile jobs are running at
> once? If it's more than 2, that's likely to be the problem.
>
> If 'icedove' does not honor the Guix --cores option, that should be
> fixed.
>
> Regards,
> Mark
>
Attachment: aux.txt
Attachment: axjf.txt
Attachment: axms.txt
Attachment: pstree.txt
B
B
bo0od wrote on 13 May 2021 21:33
(address . 48273@debbugs.gnu.org)
2ef98720-cbc4-8057-dd99-ab7446b629ab@riseup.net
reuploaded the text files to make them only included as files not
fetched in the website. (easier to download and read i think)

Mark H Weaver:
Toggle quote (43 lines)
> Hi Leo,
>
> Leo Famulari <leo@famulari.name> writes:
>
>> On Tue, May 11, 2021 at 12:21:33AM +0000, bo0od wrote:
>>> Since you said these are giving 2 different readings then the issue is with
>>> timing, So i kept it for like 24 hour (or more) and now i hope the log make
>>> more sense since there are too many fail,warnings..etc
>>
>> I see on line 422929 this error:
>>
>> 231:25.01 g++: internal compiler error: Killed (program cc1plus)
>
> Thanks, Leo, for finding the relevant line and attaching the build log.
>
>> That usually means that you ran out of memory / RAM.
>
> Agreed. Note that I've never actually tried to build 'icedove' from
> source, so I don't know if 4GB RAM + 8GB swap is enough to build it.
>
> It might possibly be relevant that our 'icecat' package uses a different
> build method than our 'icedove' package. Our 'icecat' package uses the
> GNU build system approach of running './configure' and 'make', whereas
> 'icedove' uses the Mozilla-preferred approach of creating a '.mozconfig'
> file and running './mach'.
>
> These different approaches might result in different numbers of
> concurrent build processes being run during the build. On my system
> (Thinkpad X200, Core 2 Duo), the 'icecat' build system runs 2 processes
> concurrently during the build. This is the most that my 4 GB of RAM can
> support, and even then I must shut down other memory intensive processes
> (such as modern web browsers) in order for it to work.
>
> When building 'icedove', after the 'build' phase has started compiling
> code with GCC or Rustc, can you see how many compile jobs are running at
> once? If it's more than 2, that's likely to be the problem.
>
> If 'icedove' does not honor the Guix --cores option, that should be
> fixed.
>
> Regards,
> Mark
>
Attachment: aux.text
Attachment: axjf.text
Attachment: axms.text
Attachment: pstree.text
M
M
Mark H Weaver wrote on 14 May 2021 18:13
(address . 48273@debbugs.gnu.org)
87v97ljnse.fsf@netris.org
Hi,

Thanks for including the necessary info in the email itself. From the
listings you provided, I can see that it's running 3 concurrent build
processes on your system.

Based on my experience compiling IceCat, I would _guess_ that 6 GB of
RAM and 12 GB of swap would be sufficient, *if* you do not run any other
memory intensive processes at the same time.

How much RAM and swap do you have on the system where this compilation
failed?

Were you running any other builds, or other memory intensive processes
(such as modern web browsers) at the same time?

If you have only 4 GB of RAM, then in general it should be helpful to
pass --cores=2 to either guix-daemon itself or the 'guix' client.

Unfortunately, not all of our package definitions respect the --cores
option. Our 'icecat' package does, but I can see now that our 'icedove'
package does _not_ respect it. It would be good to fix that.

Regards,
Mark


Toggle quote (179 lines)
> Mark H Weaver:
>> Hi Leo,
>>
>> Leo Famulari <leo@famulari.name> writes:
>>
>>> On Tue, May 11, 2021 at 12:21:33AM +0000, bo0od wrote:
>>>> Since you said these are giving 2 different readings then the issue is with
>>>> timing, So i kept it for like 24 hour (or more) and now i hope the log make
>>>> more sense since there are too many fail,warnings..etc
>>>
>>> I see on line 422929 this error:
>>>
>>> 231:25.01 g++: internal compiler error: Killed (program cc1plus)
>>
>> Thanks, Leo, for finding the relevant line and attaching the build log.
>>
>>> That usually means that you ran out of memory / RAM.
>>
>> Agreed. Note that I've never actually tried to build 'icedove' from
>> source, so I don't know if 4GB RAM + 8GB swap is enough to build it.
>>
>> It might possibly be relevant that our 'icecat' package uses a different
>> build method than our 'icedove' package. Our 'icecat' package uses the
>> GNU build system approach of running './configure' and 'make', whereas
>> 'icedove' uses the Mozilla-preferred approach of creating a '.mozconfig'
>> file and running './mach'.
>>
>> These different approaches might result in different numbers of
>> concurrent build processes being run during the build. On my system
>> (Thinkpad X200, Core 2 Duo), the 'icecat' build system runs 2 processes
>> concurrently during the build. This is the most that my 4 GB of RAM can
>> support, and even then I must shut down other memory intensive processes
>> (such as modern web browsers) in order for it to work.
>>
>> When building 'icedove', after the 'build' phase has started compiling
>> code with GCC or Rustc, can you see how many compile jobs are running at
>> once? If it's more than 2, that's likely to be the problem.
>>
>> If 'icedove' does not honor the Guix --cores option, that should be
>> fixed.
>>
>> Regards,
>> Mark
>>
> USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
> root 1 0.0 0.7 80992 30188 ? Sl 20:49 0:01 /gnu/store/18hp7flyb3yid3yp49i6qcdq0sbi5l1n-guile-3.0.2/bin/guile --no-auto-compile /gnu/store/655wq4zm0j9fh05xzzr1hc6a2z5y8dra-shepherd-0.8.1/bin/shepherd --config /gnu/store/vvl2afhp95r652jhz15kzylvnb4882yl-shepherd.conf
> root 2 0.0 0.0 0 0 ? S 20:49 0:00 [kthreadd]
> root 3 0.0 0.0 0 0 ? I< 20:49 0:00 [rcu_gp]
> root 4 0.0 0.0 0 0 ? I< 20:49 0:00 [rcu_par_gp]
> root 6 0.0 0.0 0 0 ? I< 20:49 0:00 [kworker/0:0H-events_highpri]
> root 8 0.0 0.0 0 0 ? I< 20:49 0:00 [mm_percpu_wq]
> root 9 0.0 0.0 0 0 ? S 20:49 0:00 [rcu_tasks_rude_]
> root 10 0.0 0.0 0 0 ? S 20:49 0:00 [rcu_tasks_trace]
> root 11 0.0 0.0 0 0 ? S 20:49 0:01 [ksoftirqd/0]
> root 12 0.0 0.0 0 0 ? I 20:49 0:01 [rcu_sched]
> root 13 0.0 0.0 0 0 ? S 20:49 0:00 [migration/0]
> root 14 0.0 0.0 0 0 ? I 20:49 0:00 [kworker/0:1-events]
> root 15 0.0 0.0 0 0 ? S 20:49 0:00 [cpuhp/0]
> root 16 0.0 0.0 0 0 ? S 20:49 0:00 [cpuhp/1]
> root 17 0.0 0.0 0 0 ? S 20:49 0:00 [migration/1]
> root 18 0.0 0.0 0 0 ? S 20:49 0:00 [ksoftirqd/1]
> root 20 0.0 0.0 0 0 ? I< 20:49 0:00 [kworker/1:0H-events_highpri]
> root 21 0.0 0.0 0 0 ? S 20:49 0:00 [cpuhp/2]
> root 22 0.0 0.0 0 0 ? S 20:49 0:00 [migration/2]
> root 23 0.0 0.0 0 0 ? S 20:49 0:00 [ksoftirqd/2]
> root 25 0.0 0.0 0 0 ? I< 20:49 0:00 [kworker/2:0H-events_highpri]
> root 26 0.0 0.0 0 0 ? S 20:49 0:00 [kdevtmpfs]
> root 27 0.0 0.0 0 0 ? I< 20:49 0:00 [netns]
> root 28 0.0 0.0 0 0 ? I< 20:49 0:00 [inet_frag_wq]
> root 29 0.0 0.0 0 0 ? S 20:49 0:00 [kauditd]
> root 30 0.0 0.0 0 0 ? S 20:49 0:00 [khungtaskd]
> root 31 0.0 0.0 0 0 ? S 20:49 0:00 [oom_reaper]
> root 32 0.0 0.0 0 0 ? I< 20:49 0:00 [writeback]
> root 33 0.0 0.0 0 0 ? S 20:49 0:00 [kcompactd0]
> root 34 0.0 0.0 0 0 ? SN 20:49 0:00 [ksmd]
> root 35 0.0 0.0 0 0 ? SN 20:49 0:00 [khugepaged]
> root 41 0.4 0.0 0 0 ? I 20:49 0:07 [kworker/1:1-mm_percpu_wq]
> root 79 0.0 0.0 0 0 ? I< 20:49 0:00 [kintegrityd]
> root 80 0.0 0.0 0 0 ? I< 20:49 0:00 [kblockd]
> root 81 0.0 0.0 0 0 ? I< 20:49 0:00 [blkcg_punt_bio]
> root 82 0.0 0.0 0 0 ? I< 20:49 0:00 [tpm_dev_wq]
> root 83 0.0 0.0 0 0 ? I< 20:49 0:00 [ata_sff]
> root 84 0.0 0.0 0 0 ? I< 20:49 0:00 [md]
> root 85 0.0 0.0 0 0 ? I< 20:49 0:00 [edac-poller]
> root 86 0.0 0.0 0 0 ? I< 20:49 0:00 [devfreq_wq]
> root 87 0.0 0.0 0 0 ? S 20:49 0:00 [watchdogd]
> root 88 0.2 0.0 0 0 ? I 20:49 0:03 [kworker/u6:1-events_unbound]
> root 89 0.0 0.0 0 0 ? I< 20:49 0:00 [kworker/0:1H-kblockd]
> root 91 0.0 0.0 0 0 ? I 20:49 0:00 [kworker/2:1-events]
> root 92 0.4 0.0 0 0 ? S 20:49 0:05 [kswapd0]
> root 93 0.0 0.0 0 0 ? S 20:49 0:00 [ecryptfs-kthrea]
> root 95 0.0 0.0 0 0 ? I< 20:49 0:00 [kthrotld]
> root 96 0.0 0.0 0 0 ? I< 20:49 0:00 [acpi_thermal_pm]
> root 97 0.0 0.0 0 0 ? S 20:49 0:00 [xenbus]
> root 98 0.0 0.0 0 0 ? S 20:49 0:00 [xenwatch]
> root 99 0.0 0.0 0 0 ? S 20:49 0:00 [khvcd]
> root 100 0.0 0.0 0 0 ? I< 20:49 0:00 [nvme-wq]
> root 101 0.0 0.0 0 0 ? I< 20:49 0:00 [nvme-reset-wq]
> root 102 0.0 0.0 0 0 ? I< 20:49 0:00 [nvme-delete-wq]
> root 103 0.0 0.0 0 0 ? S 20:49 0:00 [scsi_eh_0]
> root 104 0.0 0.0 0 0 ? I< 20:49 0:00 [scsi_tmf_0]
> root 105 0.0 0.0 0 0 ? S 20:49 0:00 [scsi_eh_1]
> root 106 0.0 0.0 0 0 ? I< 20:49 0:00 [scsi_tmf_1]
> root 107 0.4 0.0 0 0 ? I 20:49 0:06 [kworker/u6:2-flush-202:0]
> root 108 0.0 0.0 0 0 ? I< 20:49 0:00 [ipv6_addrconf]
> root 109 0.0 0.0 0 0 ? I< 20:49 0:00 [kstrp]
> root 110 0.0 0.0 0 0 ? I< 20:49 0:00 [zswap-shrink]
> root 111 0.0 0.0 0 0 ? I< 20:49 0:00 [kworker/u7:0]
> root 117 0.0 0.0 0 0 ? I< 20:49 0:00 [kworker/2:1H-kblockd]
> root 118 0.0 0.0 0 0 ? I< 20:49 0:00 [charger_manager]
> root 120 0.0 0.0 0 0 ? I 20:49 0:00 [kworker/0:2-rcu_gp]
> root 121 0.0 0.0 0 0 ? I< 20:49 0:00 [uas]
> root 130 0.0 0.0 0 0 ? S 20:49 0:01 [jbd2/xvda1-8]
> root 131 0.0 0.0 0 0 ? I< 20:49 0:00 [ext4-rsv-conver]
> root 137 0.0 0.1 5156 4056 ? Ss 20:49 0:00 /gnu/store/aza259fsrb841zwb4rjzfzs2nrsf28f1-eudev-3.2.9/sbin/udevd
> root 155 0.0 0.0 0 0 ? I< 20:49 0:00 [cryptd]
> root 158 0.0 0.0 0 0 ? I< 20:49 0:00 [ttm_swap]
> root 183 0.0 0.0 0 0 ? I 20:49 0:00 [kworker/1:2-events]
> root 190 0.0 0.0 541544 712 ? Ssl 20:49 0:00 /gnu/store/ksy2b6fwfmz40gjajvspl87ia4vsfzj7-glibc-2.31/sbin/nscd -f /gnu/store/gh3xhwgh927md5ifzdmg0cgpqc0as1sh-nscd.conf --foreground
> root 199 0.0 0.1 11996 4932 ? Ss 20:49 0:00 /gnu/store/jbm45plkq6fc9ypb05lm3jp6c5v6jvfn-guix-1.2.0-21.4dff6ec/bin/guix-daemon --build-users-group guixbuild --max-silent-time 0 --timeout 0 --log-compression bzip2 --discover=no --substitute-urls https://ci.guix.gnu.org
> root 202 0.0 0.0 2892 116 ? S 20:49 0:00 /gnu/store/lgdqnib88jsdp57gp129qxdvzsyzlg2j-inetutils-1.9.4/libexec/syslogd --rcfile /gnu/store/y5nrfbj52vlnj77iyki9hbji8qjwk86d-syslog.conf
> root 206 0.0 0.0 2388 204 tty6 Ss+ 20:49 0:00 /gnu/store/39qv4jy5ifamblf7jhqbng5ijp72g8jw-mingetty-1.08/sbin/mingetty --nohangup tty6
> root 207 0.0 0.0 2388 208 tty5 Ss+ 20:49 0:00 /gnu/store/39qv4jy5ifamblf7jhqbng5ijp72g8jw-mingetty-1.08/sbin/mingetty --nohangup tty5
> root 208 0.0 0.0 2388 204 tty4 Ss+ 20:49 0:00 /gnu/store/39qv4jy5ifamblf7jhqbng5ijp72g8jw-mingetty-1.08/sbin/mingetty --nohangup tty4
> root 209 0.0 0.0 2388 208 tty3 Ss+ 20:49 0:00 /gnu/store/39qv4jy5ifamblf7jhqbng5ijp72g8jw-mingetty-1.08/sbin/mingetty --nohangup tty3
> root 211 0.0 0.0 2388 204 tty2 Ss+ 20:49 0:00 /gnu/store/39qv4jy5ifamblf7jhqbng5ijp72g8jw-mingetty-1.08/sbin/mingetty --nohangup tty2
> root 212 0.0 0.0 2388 208 tty1 Ss+ 20:49 0:00 /gnu/store/39qv4jy5ifamblf7jhqbng5ijp72g8jw-mingetty-1.08/sbin/mingetty --nohangup tty1
> message+ 225 0.0 0.0 4400 3468 ? Ss 20:49 0:00 /gnu/store/28flqf4lglhkz58bj3kzc6ca53sx0dx9-dbus-1.12.16/bin/dbus-daemon --nofork --system --syslog-only
> root 227 0.0 0.0 8988 1792 ? Ss 20:49 0:00 /gnu/store/ck4j7hyr9xqjlcrb9ncr3q262vwva34j-wpa-supplicant-2.9/sbin/wpa_supplicant -P/var/run/wpa_supplicant.pid -B -s -u
> root 228 0.0 0.2 244068 8900 ? Ssl 20:49 0:00 /gnu/store/hc1512ha9vfr7fpz1asymcsambh429dq-network-manager-1.24.0/sbin/NetworkManager --config=/gnu/store/3cp48fvxfivj2255bbxj7363qj33ajs9-NetworkManager.conf --no-daemon
> ntpd 229 0.0 0.1 75108 4124 ? Ssl 20:49 0:00 /gnu/store/f7zx7xffnp6dr3hdrr1m71v3kxsksqyf-ntp-4.2.8p15/bin/ntpd -n -c /gnu/store/ghh3m9wzraszf7p4ynac006x96svddbq-ntpd.conf -u ntpd -g
> root 230 0.0 0.0 4040 2796 ? Ss 20:49 0:00 /gnu/store/hqs1ndwqasvfc78kx70gpk4k1rmqb64s-elogind-243.7/libexec/elogind/elogind
> root 232 0.0 0.1 238084 7284 ? Ssl 20:49 0:00 /gnu/store/yl5ygy2gh4511dyidcmglacbczz4vfj5-upower-0.99.11/libexec/upowerd
> root 237 0.0 0.0 0 0 ? I< 20:49 0:00 [kworker/1:1H-kblockd]
> avahi 244 0.0 0.0 3900 2204 ? S 20:49 0:00 avahi-daemon: running [host.local]
> avahi 246 0.0 0.0 3724 232 ? S 20:49 0:00 avahi-daemon: chroot helper
> root 248 0.0 0.2 232756 8412 ? Ssl 20:50 0:00 /gnu/store/l4kkj31rc5c8f0a5mx4qcwnfhf4lp8hv-gdm-3.34.1/bin/gdm
> root 252 0.0 0.1 230332 5956 ? Sl 20:50 0:00 /gnu/store/pq03r4vp6ffjjazvzfvp6q43wskrfr0s-accountsservice-0.6.50/libexec/accounts-daemon
> root 253 0.0 0.4 114204 16176 ? Ssl 20:50 0:00 /gnu/store/18hp7flyb3yid3yp49i6qcdq0sbi5l1n-guile-3.0.2/bin/guile --no-auto-compile /gnu/store/icj1dc1v9mxrc3hl0z87ab81wrvwq86z-mcron-1.2.0/bin/mcron /gnu/store/bsld7mk5368rq8p2wx0rr1blhywqr32n-mcron-job /gnu/store/yz8jw5pgjlxf20avn8bzski6bza7zjcq-mcron-job
> polkitd 261 0.0 0.4 1607492 16832 ? Sl 20:50 0:00 /gnu/store/sljc6riz423v24jqh6ib6b9fiq3kdlca-polkit-0.116/lib/polkit-1/polkitd --no-debug
> root 265 0.0 0.2 237268 8048 ? Sl 20:50 0:00 /gnu/store/w7ks7bgwsngxi7varvn3psh50llm3aml-modem-manager-1.12.10/sbin/ModemManager
> root 280 0.0 0.1 162132 6504 ? Sl 20:50 0:00 /gnu/store/l4kkj31rc5c8f0a5mx4qcwnfhf4lp8hv-gdm-3.34.1/libexec/gdm-session-worker
> gdm 287 0.0 0.2 179208 10368 tty7 Ssl+ 20:50 0:00 /gnu/store/l4kkj31rc5c8f0a5mx4qcwnfhf4lp8hv-gdm-3.34.1/libexec/gdm-x-session --register-session /gnu/store/ygqjfsnhhhjijw18jb7y2sc9c7ynhkwk-gnome-session-3.34.2/bin/gnome-session --autostart /gnu/store/l4kkj31rc5c8f0a5mx4qcwnfhf4lp8hv-gdm-3.34.1/share/gdm/greeter/autostart
> gdm 289 0.0 0.6 936876 25016 tty7 Sl+ 20:50 0:00 /gnu/store/frrnhs5fq1lcrvdizlcb4pxvsgrpgibn-xorg-server-1.20.11/bin/X -xkbdir /gnu/store/7qmfc4ghl1cbrxjjzrqgk8yfcmkyy9ga-xkeyboard-config-2.31/share/X11/xkb -config /gnu/store/kxcd91v9n3d5jjnxq98lgy5590acgfwz-xserver.conf -configdir /gnu/store/8bpqdcpqd9h5dsdm5j6srnrv3v571bwl-xorg.conf.d vt7 -displayfd 3 -auth /run/user/983/gdm/Xauthority -nolisten tcp -background none -noreset -keeptty -verbose 3
> gdm 314 0.0 0.0 3840 2952 tty7 S+ 20:50 0:00 /gnu/store/8aqzpznammf432w76a3p1cj7qhf04d7j-gdm-dbus-wrapper --print-address 4 --session
> gdm 318 0.0 0.3 477848 14024 tty7 Sl+ 20:50 0:00 /gnu/store/ygqjfsnhhhjijw18jb7y2sc9c7ynhkwk-gnome-session-3.34.2/libexec/gnome-session-binary --autostart /gnu/store/l4kkj31rc5c8f0a5mx4qcwnfhf4lp8hv-gdm-3.34.1/share/gdm/greeter/autostart
> gdm 334 0.0 0.1 230952 6536 tty7 Sl+ 20:50 0:00 /gnu/store/5d2l3xiqnfqw7a3kw75wb7iviyy0vgzx-at-spi2-core-2.34.0/libexec/at-spi-bus-launcher
> gdm 338 0.0 0.0 3564 2644 tty7 S+ 20:50 0:00 /gnu/store/3ihnqrwp9g8m4hr7ib3j4wzjlggjxkr9-dbus-1.12.16/bin/dbus-daemon --config-file=/gnu/store/5d2l3xiqnfqw7a3kw75wb7iviyy0vgzx-at-spi2-core-2.34.0/share/defaults/at-spi2/accessibility.conf --nofork --print-address 3
> gdm 365 0.6 5.8 3289080 222496 tty7 Sl+ 20:50 0:09 /gnu/store/fcmq64988vcgc02fdfndmc65iiy6pvm1-gnome-shell-3.34.5/bin/.gnome-shell-real
> gdm 398 0.0 0.0 679096 3740 ? Sl 20:50 0:00 /gnu/store/w3jcfr59n9x8haay25y3qxb59w7v5bnc-pulseaudio-14.0/bin/pulseaudio --start --log-target=syslog
> gdm 399 0.0 0.1 235576 5848 ? Sl 20:50 0:00 /gnu/store/w3jcfr59n9x8haay25y3qxb59w7v5bnc-pulseaudio-14.0/libexec/pulse/gsettings-helper
> gdm 413 0.0 0.1 380948 6764 tty7 Sl 20:50 0:00 /gnu/store/wlfljdvysxpjqssgpdxdmlvgydp8icd2-ibus-1.5.22/bin/ibus-daemon --panel disable -r --xim
> gdm 418 0.0 0.1 232800 4788 tty7 Sl 20:50 0:00 /gnu/store/p62nmzqxdpmx49dzyrb48smfwf7yg8fs-ibus-1.5.22/libexec/ibus-dconf
> gdm 420 0.0 0.4 182272 18656 tty7 Sl 20:50 0:00 /gnu/store/wlfljdvysxpjqssgpdxdmlvgydp8icd2-ibus-1.5.22/libexec/ibus-x11 --kill-daemon
> gdm 429 0.0 0.1 157936 6816 tty7 Sl+ 20:50 0:00 /gnu/store/5d2l3xiqnfqw7a3kw75wb7iviyy0vgzx-at-spi2-core-2.34.0/libexec/at-spi2-registryd --use-gnome-session
> gdm 437 0.0 0.2 461872 7832 tty7 Sl+ 20:50 0:00 /gnu/store/grz27bzpsvv70jkpq1ssm6hrwybigd3p-gnome-settings-daemon-3.34.1/libexec/gsd-sharing
> gdm 438 0.0 0.4 329588 19100 tty7 Sl+ 20:50 0:00 /gnu/store/grz27bzpsvv70jkpq1ssm6hrwybigd3p-gnome-settings-daemon-3.34.1/libexec/gsd-wacom
> gdm 440 0.0 0.5 552828 19484 tty7 Sl+ 20:50 0:00 /gnu/store/grz27bzpsvv70jkpq1ssm6hrwybigd3p-gnome-settings-daemon-3.34.1/libexec/gsd-color
> gdm 441 0.0 0.1 311996 6588 tty7 Sl+ 20:50 0:00 /gnu/store/grz27bzpsvv70jkpq1ssm6hrwybigd3p-gnome-settings-daemon-3.34.1/libexec/gsd-wwan
> gdm 442 0.0 0.4 403292 18468 tty7 Sl+ 20:50 0:00 /gnu/store/grz27bzpsvv70jkpq1ssm6hrwybigd3p-gnome-settings-daemon-3.34.1/libexec/gsd-keyboard
> gdm 444 0.0 0.2 313648 10424 tty7 Sl+ 20:50 0:00 /gnu/store/grz27bzpsvv70jkpq1ssm6hrwybigd3p-gnome-settings-daemon-3.34.1/libexec/gsd-print-notifications
> gdm 446 0.0 0.5 329740 20988 tty7 Sl+ 20:50 0:00 /gnu/store/grz27bzpsvv70jkpq1ssm6hrwybigd3p-gnome-settings-daemon-3.34.1/libexec/gsd-xsettings
> gdm 448 0.0 0.1 455020 6232 tty7 Sl+ 20:50 0:00 /gnu/store/grz27bzpsvv70jkpq1ssm6hrwybigd3p-gnome-settings-daemon-3.34.1/libexec/gsd-rfkill
> gdm 453 0.0 0.1 312724 6428 tty7 Sl+ 20:50 0:00 /gnu/store/grz27bzpsvv70jkpq1ssm6hrwybigd3p-gnome-settings-daemon-3.34.1/libexec/gsd-smartcard
> gdm 454 0.0 0.3 334644 13860 tty7 Sl+ 20:50 0:00 /gnu/store/grz27bzpsvv70jkpq1ssm6hrwybigd3p-gnome-settings-daemon-3.34.1/libexec/gsd-datetime
> gdm 455 0.0 0.5 882564 19900 tty7 Sl+ 20:50 0:00 /gnu/store/grz27bzpsvv70jkpq1ssm6hrwybigd3p-gnome-settings-daemon-3.34.1/libexec/gsd-media-keys
> gdm 458 0.0 0.1 233588 5588 tty7 Sl+ 20:50 0:00 /gnu/store/grz27bzpsvv70jkpq1ssm6hrwybigd3p-gnome-settings-daemon-3.34.1/libexec/gsd-screensaver-proxy
> gdm 461 0.0 0.1 311540 7008 tty7 Sl+ 20:50 0:00 /gnu/store/grz27bzpsvv70jkpq1ssm6hrwybigd3p-gnome-settings-daemon-3.34.1/libexec/gsd-sound
> gdm 462 0.0 0.0 158980 2604 tty7 Sl 20:50 0:00 /gnu/store/p62nmzqxdpmx49dzyrb48smfwf7yg8fs-ibus-1.5.22/libexec/ibus-engine-simple
> gdm 468 0.0 0.1 307672 6132 tty7 Sl+ 20:50 0:00 /gnu/store/grz27bzpsvv70jkpq1ssm6hrwybigd3p-gnome-settings-daemon-3.34.1/libexec/gsd-a11y-settings
> gdm 472 0.0 0.2 307900 8268 tty7 Sl+ 20:50 0:00 /gnu/store/grz27bzpsvv70jkpq1ssm6hrwybigd3p-gnome-settings-daemon-3.34.1/libexec/gsd-housekeeping
> gdm 473 0.0 0.5 404908 19324 tty7 Sl+ 20:50 0:00 /gnu/store/grz27bzpsvv70jkpq1ssm6hrwybigd3p-gnome-settings-daemon-3.34.1/libexec/gsd-power
> gdm 506 0.0 0.3 331636 12604 tty7 Sl+ 20:50 0:00 /gnu/store/grz27bzpsvv70jkpq1ssm6hrwybigd3p-gnome-settings-daemon-3.34.1/libexec/gsd-printer
> colord 510 0.0 0.2 234544 7808 ? Sl 20:50 0:00 /gnu/store/11rdc77gw7zninsvmamp165xxzzahxrd-colord-1.4.5/libexec/colord
> root 550 0.0 0.1 162264 6524 ? Sl 20:50 0:00 /gnu/store/l4kkj31rc5c8f0a5mx4qcwnfhf4lp8hv-gdm-3.34.1/libexec/gdm-session-worker
> user 557 0.0 0.2 179208 10260 tty8 Ssl+ 20:50 0:00 /gnu/store/l4kkj31rc5c8f0a5mx4qcwnfhf4lp8hv-gdm-3.34.1/libexec/gdm-x-session --register-session --run-script startxfce4
> user 559 1.9 1.4 979128 55612 tty8 Sl+ 20:50 0:26 /gnu/store/frrnhs5fq1lcrvdizlcb4pxvsgrpgibn-xorg-server-1.20.11/bin/X -xkbdir /gnu/store/7qmfc4ghl1cbrxjjzrqgk8yfcmkyy9ga-xkeyboard-config-2.31/share/X11/xkb -config /gnu/store/kxcd91v9n3d5jjnxq98lgy5590acgfwz-xserver.conf -configdir /gnu/store/8bpqdcpqd9h5dsdm5j6srnrv3v571bwl-xorg.conf.d vt8 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -nolisten tcp -background none -noreset -keeptty -verbose 3
> user 584 0.0 0.0 3900 2916 tty8 S+ 20:50 0:00 /gnu/store/8aqzpznammf432w76a3p1cj7qhf04d7j-gdm-dbus-wrapper --print-address 4 --session
> user 588 0.0
This message was truncated. Download the full message here.
B
B
bo0od wrote on 15 May 2021 06:07
(address . 48273@debbugs.gnu.org)
29dd0419-c986-8ff3-43c2-fc434b0aea98@riseup.net
Toggle quote (1 lines)
> How much RAM and swap do you have on the system where this compilation
> failed?
my machine is 4GB RAM , 8 GB swap.
> Were you running any other builds, or other memory intensive processes
> (such as modern web browsers) at the same time?
No just guix install icedove alone. (you can see my uploaded .txt)
> Unfortunately, not all of our package definitions respect the --cores
> option. Our 'icecat' package does, but I can see now that our 'icedove'
> package does _not_ respect it. It would be good to fix that.
yes hopefully, otherwise guix will only work fully/properly on only high
resources computers.
Mark H Weaver:
Toggle quote (201 lines)
> Hi,
>
> Thanks for including the necessary info in the email itself. From the
> listings you provided, I can see that it's running 3 concurrent build
> processes on your system.
>
> Based on my experience compiling IceCat, I would _guess_ that 6 GB of
> RAM and 12 GB of swap would be sufficient, *if* you do not run any other
> memory intensive processes at the same time.
>
> How much RAM and swap do you have on the system where this compilation
> failed?
>
> Were you running any other builds, or other memory intensive processes
> (such as modern web browsers) at the same time?
>
> If you have only 4 GB of RAM, then in general it should be helpful to
> pass --cores=2 to either guix-daemon itself or the 'guix' client.
>
> Unfortunately, not all of our package definitions respect the --cores
> option. Our 'icecat' package does, but I can see now that our 'icedove'
> package does _not_ respect it. It would be good to fix that.
>
> Regards,
> Mark
>
>
>> Mark H Weaver:
>>> Hi Leo,
>>>
>>> Leo Famulari <leo@famulari.name> writes:
>>>
>>>> On Tue, May 11, 2021 at 12:21:33AM +0000, bo0od wrote:
>>>>> Since you said these are giving 2 different readings then the issue is with
>>>>> timing, So i kept it for like 24 hour (or more) and now i hope the log make
>>>>> more sense since there are too many fail,warnings..etc
>>>>
>>>> I see on line 422929 this error:
>>>>
>>>> 231:25.01 g++: internal compiler error: Killed (program cc1plus)
>>>
>>> Thanks, Leo, for finding the relevant line and attaching the build log.
>>>
>>>> That usually means that you ran out of memory / RAM.
>>>
>>> Agreed. Note that I've never actually tried to build 'icedove' from
>>> source, so I don't know if 4GB RAM + 8GB swap is enough to build it.
>>>
>>> It might possibly be relevant that our 'icecat' package uses a different
>>> build method than our 'icedove' package. Our 'icecat' package uses the
>>> GNU build system approach of running './configure' and 'make', whereas
>>> 'icedove' uses the Mozilla-preferred approach of creating a '.mozconfig'
>>> file and running './mach'.
>>>
>>> These different approaches might result in different numbers of
>>> concurrent build processes being run during the build. On my system
>>> (Thinkpad X200, Core 2 Duo), the 'icecat' build system runs 2 processes
>>> concurrently during the build. This is the most that my 4 GB of RAM can
>>> support, and even then I must shut down other memory intensive processes
>>> (such as modern web browsers) in order for it to work.
>>>
>>> When building 'icedove', after the 'build' phase has started compiling
>>> code with GCC or Rustc, can you see how many compile jobs are running at
>>> once? If it's more than 2, that's likely to be the problem.
>>>
>>> If 'icedove' does not honor the Guix --cores option, that should be
>>> fixed.
>>>
>>> Regards,
>>> Mark
>>>
>> USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
>> root 1 0.0 0.7 80992 30188 ? Sl 20:49 0:01 /gnu/store/18hp7flyb3yid3yp49i6qcdq0sbi5l1n-guile-3.0.2/bin/guile --no-auto-compile /gnu/store/655wq4zm0j9fh05xzzr1hc6a2z5y8dra-shepherd-0.8.1/bin/shepherd --config /gnu/store/vvl2afhp95r652jhz15kzylvnb4882yl-shepherd.conf
>> root 2 0.0 0.0 0 0 ? S 20:49 0:00 [kthreadd]
>> root 3 0.0 0.0 0 0 ? I< 20:49 0:00 [rcu_gp]
>> root 4 0.0 0.0 0 0 ? I< 20:49 0:00 [rcu_par_gp]
>> root 6 0.0 0.0 0 0 ? I< 20:49 0:00 [kworker/0:0H-events_highpri]
>> root 8 0.0 0.0 0 0 ? I< 20:49 0:00 [mm_percpu_wq]
>> root 9 0.0 0.0 0 0 ? S 20:49 0:00 [rcu_tasks_rude_]
>> root 10 0.0 0.0 0 0 ? S 20:49 0:00 [rcu_tasks_trace]
>> root 11 0.0 0.0 0 0 ? S 20:49 0:01 [ksoftirqd/0]
>> root 12 0.0 0.0 0 0 ? I 20:49 0:01 [rcu_sched]
>> root 13 0.0 0.0 0 0 ? S 20:49 0:00 [migration/0]
>> root 14 0.0 0.0 0 0 ? I 20:49 0:00 [kworker/0:1-events]
>> root 15 0.0 0.0 0 0 ? S 20:49 0:00 [cpuhp/0]
>> root 16 0.0 0.0 0 0 ? S 20:49 0:00 [cpuhp/1]
>> root 17 0.0 0.0 0 0 ? S 20:49 0:00 [migration/1]
>> root 18 0.0 0.0 0 0 ? S 20:49 0:00 [ksoftirqd/1]
>> root 20 0.0 0.0 0 0 ? I< 20:49 0:00 [kworker/1:0H-events_highpri]
>> root 21 0.0 0.0 0 0 ? S 20:49 0:00 [cpuhp/2]
>> root 22 0.0 0.0 0 0 ? S 20:49 0:00 [migration/2]
>> root 23 0.0 0.0 0 0 ? S 20:49 0:00 [ksoftirqd/2]
>> root 25 0.0 0.0 0 0 ? I< 20:49 0:00 [kworker/2:0H-events_highpri]
>> root 26 0.0 0.0 0 0 ? S 20:49 0:00 [kdevtmpfs]
>> root 27 0.0 0.0 0 0 ? I< 20:49 0:00 [netns]
>> root 28 0.0 0.0 0 0 ? I< 20:49 0:00 [inet_frag_wq]
>> root 29 0.0 0.0 0 0 ? S 20:49 0:00 [kauditd]
>> root 30 0.0 0.0 0 0 ? S 20:49 0:00 [khungtaskd]
>> root 31 0.0 0.0 0 0 ? S 20:49 0:00 [oom_reaper]
>> root 32 0.0 0.0 0 0 ? I< 20:49 0:00 [writeback]
>> root 33 0.0 0.0 0 0 ? S 20:49 0:00 [kcompactd0]
>> root 34 0.0 0.0 0 0 ? SN 20:49 0:00 [ksmd]
>> root 35 0.0 0.0 0 0 ? SN 20:49 0:00 [khugepaged]
>> root 41 0.4 0.0 0 0 ? I 20:49 0:07 [kworker/1:1-mm_percpu_wq]
>> root 79 0.0 0.0 0 0 ? I< 20:49 0:00 [kintegrityd]
>> root 80 0.0 0.0 0 0 ? I< 20:49 0:00 [kblockd]
>> root 81 0.0 0.0 0 0 ? I< 20:49 0:00 [blkcg_punt_bio]
>> root 82 0.0 0.0 0 0 ? I< 20:49 0:00 [tpm_dev_wq]
>> root 83 0.0 0.0 0 0 ? I< 20:49 0:00 [ata_sff]
>> root 84 0.0 0.0 0 0 ? I< 20:49 0:00 [md]
>> root 85 0.0 0.0 0 0 ? I< 20:49 0:00 [edac-poller]
>> root 86 0.0 0.0 0 0 ? I< 20:49 0:00 [devfreq_wq]
>> root 87 0.0 0.0 0 0 ? S 20:49 0:00 [watchdogd]
>> root 88 0.2 0.0 0 0 ? I 20:49 0:03 [kworker/u6:1-events_unbound]
>> root 89 0.0 0.0 0 0 ? I< 20:49 0:00 [kworker/0:1H-kblockd]
>> root 91 0.0 0.0 0 0 ? I 20:49 0:00 [kworker/2:1-events]
>> root 92 0.4 0.0 0 0 ? S 20:49 0:05 [kswapd0]
>> root 93 0.0 0.0 0 0 ? S 20:49 0:00 [ecryptfs-kthrea]
>> root 95 0.0 0.0 0 0 ? I< 20:49 0:00 [kthrotld]
>> root 96 0.0 0.0 0 0 ? I< 20:49 0:00 [acpi_thermal_pm]
>> root 97 0.0 0.0 0 0 ? S 20:49 0:00 [xenbus]
>> root 98 0.0 0.0 0 0 ? S 20:49 0:00 [xenwatch]
>> root 99 0.0 0.0 0 0 ? S 20:49 0:00 [khvcd]
>> root 100 0.0 0.0 0 0 ? I< 20:49 0:00 [nvme-wq]
>> root 101 0.0 0.0 0 0 ? I< 20:49 0:00 [nvme-reset-wq]
>> root 102 0.0 0.0 0 0 ? I< 20:49 0:00 [nvme-delete-wq]
>> root 103 0.0 0.0 0 0 ? S 20:49 0:00 [scsi_eh_0]
>> root 104 0.0 0.0 0 0 ? I< 20:49 0:00 [scsi_tmf_0]
>> root 105 0.0 0.0 0 0 ? S 20:49 0:00 [scsi_eh_1]
>> root 106 0.0 0.0 0 0 ? I< 20:49 0:00 [scsi_tmf_1]
>> root 107 0.4 0.0 0 0 ? I 20:49 0:06 [kworker/u6:2-flush-202:0]
>> root 108 0.0 0.0 0 0 ? I< 20:49 0:00 [ipv6_addrconf]
>> root 109 0.0 0.0 0 0 ? I< 20:49 0:00 [kstrp]
>> root 110 0.0 0.0 0 0 ? I< 20:49 0:00 [zswap-shrink]
>> root 111 0.0 0.0 0 0 ? I< 20:49 0:00 [kworker/u7:0]
>> root 117 0.0 0.0 0 0 ? I< 20:49 0:00 [kworker/2:1H-kblockd]
>> root 118 0.0 0.0 0 0 ? I< 20:49 0:00 [charger_manager]
>> root 120 0.0 0.0 0 0 ? I 20:49 0:00 [kworker/0:2-rcu_gp]
>> root 121 0.0 0.0 0 0 ? I< 20:49 0:00 [uas]
>> root 130 0.0 0.0 0 0 ? S 20:49 0:01 [jbd2/xvda1-8]
>> root 131 0.0 0.0 0 0 ? I< 20:49 0:00 [ext4-rsv-conver]
>> root 137 0.0 0.1 5156 4056 ? Ss 20:49 0:00 /gnu/store/aza259fsrb841zwb4rjzfzs2nrsf28f1-eudev-3.2.9/sbin/udevd
>> root 155 0.0 0.0 0 0 ? I< 20:49 0:00 [cryptd]
>> root 158 0.0 0.0 0 0 ? I< 20:49 0:00 [ttm_swap]
>> root 183 0.0 0.0 0 0 ? I 20:49 0:00 [kworker/1:2-events]
>> root 190 0.0 0.0 541544 712 ? Ssl 20:49 0:00 /gnu/store/ksy2b6fwfmz40gjajvspl87ia4vsfzj7-glibc-2.31/sbin/nscd -f /gnu/store/gh3xhwgh927md5ifzdmg0cgpqc0as1sh-nscd.conf --foreground
>> root 199 0.0 0.1 11996 4932 ? Ss 20:49 0:00 /gnu/store/jbm45plkq6fc9ypb05lm3jp6c5v6jvfn-guix-1.2.0-21.4dff6ec/bin/guix-daemon --build-users-group guixbuild --max-silent-time 0 --timeout 0 --log-compression bzip2 --discover=no --substitute-urls https://ci.guix.gnu.org
>> root 202 0.0 0.0 2892 116 ? S 20:49 0:00 /gnu/store/lgdqnib88jsdp57gp129qxdvzsyzlg2j-inetutils-1.9.4/libexec/syslogd --rcfile /gnu/store/y5nrfbj52vlnj77iyki9hbji8qjwk86d-syslog.conf
>> root 206 0.0 0.0 2388 204 tty6 Ss+ 20:49 0:00 /gnu/store/39qv4jy5ifamblf7jhqbng5ijp72g8jw-mingetty-1.08/sbin/mingetty --nohangup tty6
>> root 207 0.0 0.0 2388 208 tty5 Ss+ 20:49 0:00 /gnu/store/39qv4jy5ifamblf7jhqbng5ijp72g8jw-mingetty-1.08/sbin/mingetty --nohangup tty5
>> root 208 0.0 0.0 2388 204 tty4 Ss+ 20:49 0:00 /gnu/store/39qv4jy5ifamblf7jhqbng5ijp72g8jw-mingetty-1.08/sbin/mingetty --nohangup tty4
>> root 209 0.0 0.0 2388 208 tty3 Ss+ 20:49 0:00 /gnu/store/39qv4jy5ifamblf7jhqbng5ijp72g8jw-mingetty-1.08/sbin/mingetty --nohangup tty3
>> root 211 0.0 0.0 2388 204 tty2 Ss+ 20:49 0:00 /gnu/store/39qv4jy5ifamblf7jhqbng5ijp72g8jw-mingetty-1.08/sbin/mingetty --nohangup tty2
>> root 212 0.0 0.0 2388 208 tty1 Ss+ 20:49 0:00 /gnu/store/39qv4jy5ifamblf7jhqbng5ijp72g8jw-mingetty-1.08/sbin/mingetty --nohangup tty1
>> message+ 225 0.0 0.0 4400 3468 ? Ss 20:49 0:00 /gnu/store/28flqf4lglhkz58bj3kzc6ca53sx0dx9-dbus-1.12.16/bin/dbus-daemon --nofork --system --syslog-only
>> root 227 0.0 0.0 8988 1792 ? Ss 20:49 0:00 /gnu/store/ck4j7hyr9xqjlcrb9ncr3q262vwva34j-wpa-supplicant-2.9/sbin/wpa_supplicant -P/var/run/wpa_supplicant.pid -B -s -u
>> root 228 0.0 0.2 244068 8900 ? Ssl 20:49 0:00 /gnu/store/hc1512ha9vfr7fpz1asymcsambh429dq-network-manager-1.24.0/sbin/NetworkManager --config=/gnu/store/3cp48fvxfivj2255bbxj7363qj33ajs9-NetworkManager.conf --no-daemon
>> ntpd 229 0.0 0.1 75108 4124 ? Ssl 20:49 0:00 /gnu/store/f7zx7xffnp6dr3hdrr1m71v3kxsksqyf-ntp-4.2.8p15/bin/ntpd -n -c /gnu/store/ghh3m9wzraszf7p4ynac006x96svddbq-ntpd.conf -u ntpd -g
>> root 230 0.0 0.0 4040 2796 ? Ss 20:49 0:00 /gnu/store/hqs1ndwqasvfc78kx70gpk4k1rmqb64s-elogind-243.7/libexec/elogind/elogind
>> root 232 0.0 0.1 238084 7284 ? Ssl 20:49 0:00 /gnu/store/yl5ygy2gh4511dyidcmglacbczz4vfj5-upower-0.99.11/libexec/upowerd
>> root 237 0.0 0.0 0 0 ? I< 20:49 0:00 [kworker/1:1H-kblockd]
>> avahi 244 0.0 0.0 3900 2204 ? S 20:49 0:00 avahi-daemon: running [host.local]
>> avahi 246 0.0 0.0 3724 232 ? S 20:49 0:00 avahi-daemon: chroot helper
>> root 248 0.0 0.2 232756 8412 ? Ssl 20:50 0:00 /gnu/store/l4kkj31rc5c8f0a5mx4qcwnfhf4lp8hv-gdm-3.34.1/bin/gdm
>> root 252 0.0 0.1 230332 5956 ? Sl 20:50 0:00 /gnu/store/pq03r4vp6ffjjazvzfvp6q43wskrfr0s-accountsservice-0.6.50/libexec/accounts-daemon
>> root 253 0.0 0.4 114204 16176 ? Ssl 20:50 0:00 /gnu/store/18hp7flyb3yid3yp49i6qcdq0sbi5l1n-guile-3.0.2/bin/guile --no-auto-compile /gnu/store/icj1dc1v9mxrc3hl0z87ab81wrvwq86z-mcron-1.2.0/bin/mcron /gnu/store/bsld7mk5368rq8p2wx0rr1blhywqr32n-mcron-job /gnu/store/yz8jw5pgjlxf20avn8bzski6bza7zjcq-mcron-job
>> polkitd 261 0.0 0.4 1607492 16832 ? Sl 20:50 0:00 /gnu/store/sljc6riz423v24jqh6ib6b9fiq3kdlca-polkit-0.116/lib/polkit-1/polkitd --no-debug
>> root 265 0.0 0.2 237268 8048 ? Sl 20:50 0:00 /gnu/store/w7ks7bgwsngxi7varvn3psh50llm3aml-modem-manager-1.12.10/sbin/ModemManager
>> root 280 0.0 0.1 162132 6504 ? Sl 20:50 0:00 /gnu/store/l4kkj31rc5c8f0a5mx4qcwnfhf4lp8hv-gdm-3.34.1/libexec/gdm-session-worker
>> gdm 287 0.0 0.2 179208 10368 tty7 Ssl+ 20:50 0:00 /gnu/store/l4kkj31rc5c8f0a5mx4qcwnfhf4lp8hv-gdm-3.34.1/libexec/gdm-x-session --register-session /gnu/store/ygqjfsnhhhjijw18jb7y2sc9c7ynhkwk-gnome-session-3.34.2/bin/gnome-session --autostart /gnu/store/l4kkj31rc5c8f0a5mx4qcwnfhf4lp8hv-gdm-3.34.1/share/gdm/greeter/autostart
>> gdm 289 0.0 0.6 936876 25016 tty7 Sl+ 20:50 0:00 /gnu/store/frrnhs5fq1lcrvdizlcb4pxvsgrpgibn-xorg-server-1.20.11/bin/X -xkbdir /gnu/store/7qmfc4ghl1cbrxjjzrqgk8yfcmkyy9ga-xkeyboard-config-2.31/share/X11/xkb -config /gnu/store/kxcd91v9n3d5jjnxq98lgy5590acgfwz-xserver.conf -configdir /gnu/store/8bpqdcpqd9h5dsdm5j6srnrv3v571bwl-xorg.conf.d vt7 -displayfd 3 -auth /run/user/983/gdm/Xauthority -nolisten tcp -background none -noreset -keeptty -verbose 3
>> gdm 314 0.0 0.0 3840 2952 tty7 S+ 20:50 0:00 /gnu/store/8aqzpznammf432w76a3p1cj7qhf04d7j-gdm-dbus-wrapper --print-address 4 --session
>> gdm 318 0.0 0.3 477848 14024 tty7 Sl+ 20:50 0:00 /gnu/store/ygqjfsnhhhjijw18jb7y2sc9c7ynhkwk-gnome-session-3.34.2/libexec/gnome-session-binary --autostart /gnu/store/l4kkj31rc5c8f0a5mx4qcwnfhf4lp8hv-gdm-3.34.1/share/gdm/greeter/autostart
>> gdm 334 0.0 0.1 230952 6536 tty7 Sl+ 20:50 0:00 /gnu/store/5d2l3xiqnfqw7a3kw75wb7iviyy0vgzx-at-spi2-core-2.34.0/libexec/at-spi-bus-launcher
>> gdm 338 0.0 0.0 3564 2644 tty7 S+ 20:50 0:00 /gnu/store/3ihnqrwp9g8m4hr7ib3j4wzjlggjxkr9-dbus-1.12.16/bin/dbus-daemon --config-file=/gnu/store/5d2l3xiqnfqw7a3kw75wb7iviyy0vgzx-at-spi2-core-2.34.0/share/defaults/at-spi2/accessibility.conf --nofork --print-address 3
>> gdm 365 0.6 5.8 3289080 222496 tty7 Sl+ 20:50 0:09 /gnu/store/fcmq64988vcgc02fdfndmc65iiy6pvm1-gnome-shell-3.34.5/bin/.gnome-shell-real
>> gdm 398 0.0 0.0 679096 3740 ? Sl 20:50 0:00 /gnu/store/w3jcfr59n9x8haay25y3qxb59w7v5bnc-pulseaudio-14.0/bin/pulseaudio --start --log-target=syslog
>> gdm 399 0.0 0.1 235576 5848 ? Sl 20:50 0:00 /gnu/store/w3jcfr59n9x8haay25y3qxb59w7v5bnc-pulseaudio-14.0/libexec/pulse/gsettings-helper
>> gdm 413 0.0 0.1 380948 6764 tty7 Sl 20:50 0:00 /gnu/store/wlfljdvysxpjqssgpdxdmlvgydp8icd2-ibus-1.5.22/bin/ibus-daemon --panel disable -r --xim
>> gdm 418 0.0 0.1 232800 4788 tty7 Sl 20:50 0:00 /gnu/store/p62nmzqxdpmx49dzyrb48smfwf7yg8fs-ibus-1.5.22/libexec/ibus-dconf
>> gdm 420 0.0 0.4 182272 18656 tty7 Sl 20:50 0:00 /gnu/store/wlfljdvysxpjqssgpdxdmlvgydp8icd2-ibus-1.5.22/libexec/ibus-x11 --kill-daemon
>> gdm 429 0.0 0.1 157936 6816 tty7 Sl+ 20:50 0:00 /gnu/store/5d2l3xiqnfqw7a3kw75wb7iviyy0vgzx-at-spi2-core-2.34.0/libexec/at-spi2-registryd --use-gnome-session
>> gdm 437 0.0 0.2 461872 7832 tty7 Sl+ 20:50 0:00 /gnu/store/grz27bzpsvv70jkpq1ssm6hrwybigd3p-gnome-settings-daemon-3.34.1/libexec/gsd-sharing
>> gdm 438 0.0 0.4 329588 19100 tty7 Sl+ 20:50 0:00 /gnu/store/grz27bzpsvv70jkpq1ssm6hrwybigd3p-gnome-settings-daemon-3.34.1/libexec/gsd-wacom
>> gdm 440 0.0 0.5 552828 19484 tty7 Sl+ 20:50 0:00 /gnu/store/grz27bzpsvv70jkpq1ssm6hrwybigd3p-gnome-settings-daemon-3.34.1/libexec/gsd-color
>> gdm 441 0.0 0.1 311996 6588 tty7 Sl+ 20:50 0:00 /gnu/store/grz27bzpsvv70jkpq1ssm6hrwybigd3p-gnome-settings-daemon-3.34.1/libexec/gsd-wwan
>> gdm 442 0.0 0.4 403292 18468 tty7 Sl+ 20:50 0:00 /gnu/store/grz27bzpsvv70jkpq1ssm6hrwybigd3p-gnome-settings-daemon-3.34.1/libexec/gsd-keyboard
>> gdm 444 0.0 0.2 313648 10424 tty7 Sl+ 20:50 0:00 /gnu/store/grz27bzpsvv70jkpq1ssm6hrwybigd3p-gnome-settings-daemon-3.34.1/libexec/gsd-print-notifications
>> gdm 446 0.0 0.5 329740 20988 tty7 Sl+ 20:50 0:00 /gnu/store/grz27bzpsvv70jkpq1ssm6hrwybigd3p-gnome-settings-daemon-3.34.1/libexec/gsd-xsettings
>> gdm 448 0.0 0.1 455020 6232 tty7 Sl+ 20:50 0:00 /gnu/store/grz27bzpsvv70jkpq1ssm6hrwybigd3p-gnome-settings-daemon-3.34.1/libexec/gsd-rfkill
>> gdm 453 0.0 0.1 312724 6428 tty7 Sl+ 20:50 0:00 /gnu/store/grz27bzpsvv70jkpq1ssm6hrwybigd3p-gnome-settings-daemon-3.34.1/libexec/gsd-smartcard
>> gdm 454 0.0 0.3 334644 13860 tty7 Sl+ 20:50 0:00 /gnu/store/grz27bzpsvv70jkpq1ssm6hrwybigd3p-gnome-settings-daemon-3.34.1/libexec/gsd-datetime
>> gdm 455 0.0 0.5 882564 19900 tty7 Sl+ 20:50 0:00 /gnu/store/grz27bzpsvv70jkpq1ssm6hrwybigd3p-gnome-settings-daemon-3.34.1/libexec/gsd-media-keys
>> gdm 458 0.0 0.1 233588 5588 tty7 Sl+ 20:50 0:00 /gnu/store/grz27bzpsvv70jkpq1ssm6hrwybigd3p-gnome-settings-daemon-3.34.1/libexec/gsd-screensaver-proxy
>> gdm 461 0.0 0.1 311540 7008 tty7 Sl+ 20:50 0:00 /gnu/store/grz27bzpsvv70jkpq1ssm6hrwybigd3p-gnome-settings-daemon-3.34.1/libexec/gsd-sound
>> gdm 462 0.0 0.0 158980 2604 tty7 Sl 20:50 0:00 /gnu/store/p62nmzqxdpmx49dzyrb48smfwf7yg8fs-ibus-1.5.22/libexec/ibus-engine-simple
>> gdm 468 0.0 0.1 307672 6132 tty7 Sl+ 20:50 0:00 /gnu/store/grz27bzpsvv70jkpq1ssm6hrwybigd3p-gnome-settings-daemon-3.34.1/libexec/gsd-a11y-settings
>> gdm 472 0.0 0.2 307900 8268 tty7 Sl+ 20:50 0:00 /gnu/store/grz27bzpsvv70jkpq1ssm6hrwybigd3p-gnome-settings-daemon-3.34.1/libexec/gsd-housekeeping
>> gdm 473 0.0 0.5 404908 19324 tty7 Sl+ 20:50 0:00 /gnu/store/grz27bzpsvv70jkpq1ssm6hrwybigd3p-gnome-settings-daemon-3.34.1/libexec/gsd-power
>> gdm 506 0.0 0.3 331636 12604 tty7 Sl+ 20:50 0:00 /gnu/store/grz27bzpsvv70jkpq1ssm6hrwybigd3p-gnome-settings-daemon-3.34.1/libexec/gsd-printer
>> colord 510 0.0 0.2 234544 7808 ?
This message was truncated. Download the full message here.
J
J
Jonathan Brielmaier wrote on 4 Jun 2021 11:43
Icedove 78.10.0 build stuck at 'unpack' phase
(address . 48273@debbugs.gnu.org)(name . Mark H Weaver)(address . mhw@netris.org)
7726464e-4722-1d7f-816b-1e2bb07df9c0@web.de
Unfortunately, not all of our package definitions respect the
--coresoption. Our 'icecat' package does, but I can see now that our
'icedove'package does _not_ respect it. It would be good to fix that.

@Mark: Yes, it would by nice to fix that. Do we make something special
in Icecat to achieve that? I couldn't find anything obvious on a first
view...
M
M
Mark H Weaver wrote on 5 Jun 2021 02:42
87bl8lgmzw.fsf@netris.org
Hi Jonathan,

I wrote:
Toggle quote (4 lines)
> Unfortunately, not all of our package definitions respect the --cores
> option. Our 'icecat' package does, but I can see now that our
> 'icedove' package does _not_ respect it. It would be good to fix that.

Jonathan Brielmaier <jonathan.brielmaier@web.de> replied:
Toggle quote (4 lines)
> @Mark: Yes, it would by nice to fix that. Do we make something special
> in Icecat to achieve that? I couldn't find anything obvious on a first
> view...

There's nothing special in the IceCat package to achieve it. The
relevant code is in the default 'build' phase from 'gnu-build-system',
here:


_ (define* (build #:key (make-flags '()) (parallel-build? #t)
_________________ #:allow-other-keys)
___ (apply invoke "make"
__________ `(,@(if parallel-build?
__________________ `("-j" ,(number->string (parallel-job-count)))
__________________ '())
____________ ,@make-flags)))

The problem is that the 'icedove' package has a custom 'build' phase
that does not honor (parallel-job-count).

Ultimately, the relevant difference between the two packages is that the
'icecat' package uses the 'gnu-build-system' approach of running
"./configure", "make" and "make install", whereas the 'icedove' package
uses the (Mozilla-preferred) approach of creating a ".mozconfig" file
and running "./mach configure", "./mach build" and "./mach install".

If I remember correctly (from when I looked at the process listings
provided in this bug report), "./mach build" seems to be passing a
"-j<N>" argument to "make", but at present we have no control over the
<N> is.

The best solution would be to find a way to tell "./mach build" to pass
a specific value of <N>. Ideally, <N> should be (parallel-job-count) if
'parallel-build?' is #t, otherwise it should be 1.

What do you think?

Thanks,
Mark

--
Disinformation flourishes because many people care deeply about injustice
but very few check the facts. Ask me about https://stallmansupport.org.
J
J
Jonathan Brielmaier wrote on 8 Jun 2021 19:38
[PATCH] gnu: icedove: Respect parallel-job-count while building.
(address . 48273@debbugs.gnu.org)(name . Jonathan Brielmaier)(address . jonathan.brielmaier@web.de)
20210608173806.20185-1-jonathan.brielmaier@web.de
* gnu/packages/gnuzilla.scm (icedove)[arguments]: Add MOZ_MAKE_FLAGS
with parallel-job-count to mozconfig.
---
gnu/packages/gnuzilla.scm | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)

Toggle diff (14 lines)
diff --git a/gnu/packages/gnuzilla.scm b/gnu/packages/gnuzilla.scm
index c63809c20c..b6b4a01362 100644
--- a/gnu/packages/gnuzilla.scm
+++ b/gnu/packages/gnuzilla.scm
@@ -1496,7 +1496,8 @@ standards of the IceCat project.")
"ac_add_options --with-system-nspr\n"
"ac_add_options --with-system-nss\n"
"ac_add_options --with-system-zlib\n"
- "ac_add_options --with-user-appdir=\\.icedove\n"))))
+ "ac_add_options --with-user-appdir=\\.icedove\n"
+ "mk_add_options MOZ_MAKE_FLAGS=-j" (number->string (parallel-job-count)) "\n"))))
(display (getcwd))
(newline)
(display "mach configure")
--
2.31.1
L
L
Ludovic Courtès wrote on 18 Jun 2021 11:34
(name . Jonathan Brielmaier)(address . jonathan.brielmaier@web.de)(address . 48273@debbugs.gnu.org)
871r8zikic.fsf@gnu.org
Hi,

Jonathan Brielmaier <jonathan.brielmaier@web.de> skribis:

Toggle quote (3 lines)
> * gnu/packages/gnuzilla.scm (icedove)[arguments]: Add MOZ_MAKE_FLAGS
> with parallel-job-count to mozconfig.

[...]

Toggle quote (3 lines)
> + "ac_add_options --with-user-appdir=\\.icedove\n"
> + "mk_add_options MOZ_MAKE_FLAGS=-j" (number->string (parallel-job-count)) "\n"))))

Please split the line. :-)

Otherwise LGTM, thanks!

Ludo’.
J
J
Jonathan Brielmaier wrote on 24 Jun 2021 11:15
(name . Ludovic Courtès)(address . ludo@gnu.org)(address . 48273-done@debbugs.gnu.org)
bff3a5a1-688d-24a3-4192-dbf45a728857@web.de
On 18.06.21 11:34, Ludovic Courtès wrote:>> +
"ac_add_options --with-user-appdir=\\.icedove\n"
Toggle quote (4 lines)
>> + "mk_add_options MOZ_MAKE_FLAGS=-j" (number->string (parallel-job-count)) "\n"))))
>
> Please split the line. :-)

Pushed as 84780ff427364fdd2f158b1f7439debee2bf3799 with this line splitted.
Closed
?