glib-2.62.6 build fails i686

  • Done
  • quality assurance status badge
Details
7 participants
  • Bengt Richter
  • Bone Baboon
  • Efraim Flashner
  • Leo Famulari
  • Maxim Cournoyer
  • Mark H Weaver
  • raingloom
Owner
unassigned
Submitted by
Bone Baboon
Severity
normal
B
B
Bone Baboon wrote on 26 Apr 2021 05:35
(address . bug-guix@gnu.org)
874kftd8fl.fsf@disroot.org
On an i686 computer when I run the command `sudo guix system
--no-substitutes --cores=2 reconfigure configuration.scm` I get this
error:

```
building /gnu/store/ynfddvqhhrmjywndfjwgrfs4fj2n0whl-glib-2.62.6.drv...
- 'check' phasebuilder for `/gnu/store/ynfddvqhhrmjywndfjwgrfs4fj2n0whl-glib-2.62.6.drv' failed with exit code 1
build of /gnu/store/ynfddvqhhrmjywndfjwgrfs4fj2n0whl-glib-2.62.6.drv failed
View build log at '/var/log/guix/drvs/yn/fddvqhhrmjywndfjwgrfs4fj2n0whl-glib-2.62.6.drv.bz2'.
cannot build derivation `/gnu/store/wpcg5xlswvfy2zkaldkr54ik8s8b138j-polkit-0.116.drv': 1 dependencies couldn't be built
guix system: error: build of `/gnu/store/wpcg5xlswvfy2zkaldkr54ik8s8b138j-polkit-0.116.drv' failed
```

`guix describe` outputs:

```
Generation 5 Apr 23 2021 21:43:26 (current)
guix 98a7242
branch: master
commit: 98a7242e174b4105c2505e9019ae10d906a9195f
```

The contents of the build log:
```
WARNING: (guile-user): imported module (guix build utils) overrides core binding `delete'
starting phase `set-SOURCE-DATE-EPOCH'
phase `set-SOURCE-DATE-EPOCH' succeeded after 0.0 seconds
starting phase `set-paths'
environment variable `PATH' set to `/gnu/store/b6r7jh5fj3z2h7l7nz2w0y08nz7m1kfz-meson-for-build-0.53.2/bin:/gnu/store/6hnpwxpas0zsswz7yqib8njhansqmhkw-ninja-1.10.0/bin:/gnu/store/4bc7msipq8xa14faq9vndxrs8s22ny2w-gettext-minimal-0.20.1/bin:/gnu/store/7ds6f0fnd3n5zzhcjjnkmry990shrcm8-m4-1.4.18/bin:/gnu/store/26m0d62f34j6bs4x0m4n0b3l4mvmamb5-dbus-1.12.16/bin:/gnu/store/fh8pmj9qqwbr1j1vrjc4zgnlgm08birz-pkg-config-0.29.2/bin:/gnu/store/36p2wpd5pfsq3nyyshi44scxi3gilkam-python-wrapper-3.8.2/bin:/gnu/store/ysk9g469f4pvw7i318kbk1hnrfrydanl-perl-5.30.2/bin:/gnu/store/y9kzwhkz2k1a5i3x1dd3mq2h984z4hg5-libselinux-3.0/sbin:/gnu/store/gww59gv5qxbfijg3vk5y182im7923s06-tar-1.32/bin:/gnu/store/2ayciqwxddkzq183dac82ijljc14j4zj-gzip-1.10/bin:/gnu/store/n1jk0w2wa4vpwmixaqn2y3la1l2sizzi-bzip2-1.0.8/bin:/gnu/store/7p36raqgk6vn47bflxc9bsclqiib3phi-xz-5.2.4/bin:/gnu/store/lpkf3ydcdvxn8gcrzaq9cp3ri05h8qhs-file-5.38/bin:/gnu/store/6gqaw09zqw8w0vcax6simlq71bq7l5r0-diffutils-3.7/bin:/gnu/store/qw20chpgkgbcqmzhs60c8hjl1hmblyc8-patch-2.7.6/bin:/gnu/store/b5y5scfmh2d8kxcpl9p84294z2198cgf-findutils-4.7.0/bin:/gnu/store/9iwlsj7d6ffqhshy8qshf7p4fqwfwrvn-gawk-5.0.1/bin:/gnu/store/q1nfjb24vqjs1cgi8mlnskw34h16y09r-sed-4.8/bin:/gnu/store/4qr6mcvsxyzknxa7x1wny8x30f5i0r3n-grep-3.4/bin:/gnu/store/2v61vg0bizgrhybkqbrki2k7kr094waz-coreutils-8.32/bin:/gnu/store/b7jbh7kzzig0bxfswdj8nfj9bkljyyya-make-4.3/bin:/gnu/store/v1g7f3p4f0851mywrla8qmr9hb8jgfjr-bash-minimal-5.0.16/bin:/gnu/store/dyqxnydqk1810afjfbqzfvh0n83xyl62-ld-wrapper-0/bin:/gnu/store/50lyzn9bz6x4da66648kry29wn8afird-binutils-2.34/bin:/gnu/store/afpgzln8860m6yfhxy6i8n9rywbp85cy-gcc-7.5.0/bin:/gnu/store/z4li262il798hbl0l1h1k3a5g7r6bffa-glibc-2.31/bin:/gnu/store/z4li262il798hbl0l1h1k3a5g7r6bffa-glibc-2.31/sbin:/gnu/store/nlyy80nlkwb9i377h888nl97jfzhaf4r-python-3.8.2/bin:/gnu/store/3x44yvsap0ss63j8d7yv6wm63ngr3j12-libsepol-3.0/bin'
environment variable `PKG_CONFIG_PATH' set to `/gnu/store/26m0d62f34j6bs4x0m4n0b3l4mvmamb5-dbus-1.12.16/lib/pkgconfig:/gnu/store/kiz15vy5mv2jw37365j76cy1a88a3p2a-pcre-8.44/lib/pkgconfig:/gnu/store/pn4bci1x4dsmaafmslx6g61af7n2j0sy-libffi-3.3/lib/pkgconfig:/gnu/store/5ffrqmfh2c0dgmh9ji3lgvnvgsnmlhfp-util-linux-2.35.1-lib/lib/pkgconfig:/gnu/store/y9kzwhkz2k1a5i3x1dd3mq2h984z4hg5-libselinux-3.0/lib/pkgconfig:/gnu/store/pqyqxd5mbvlb22ifxzp4q2skjfq1p8yj-zlib-1.2.11/lib/pkgconfig:/gnu/store/7p36raqgk6vn47bflxc9bsclqiib3phi-xz-5.2.4/lib/pkgconfig:/gnu/store/nlyy80nlkwb9i377h888nl97jfzhaf4r-python-3.8.2/lib/pkgconfig:/gnu/store/3x44yvsap0ss63j8d7yv6wm63ngr3j12-libsepol-3.0/lib/pkgconfig'
environment variable `PYTHONPATH' set to `/gnu/store/b6r7jh5fj3z2h7l7nz2w0y08nz7m1kfz-meson-for-build-0.53.2/lib/python3.8/site-packages:/gnu/store/nlyy80nlkwb9i377h888nl97jfzhaf4r-python-3.8.2/lib/python3.8/site-packages'
environment variable `PERL5LIB' set to `/gnu/store/ysk9g469f4pvw7i318kbk1hnrfrydanl-perl-5.30.2/lib/perl5/site_perl'
environment variable `BASH_LOADABLES_PATH' unset
environment variable `C_INCLUDE_PATH' set to `/gnu/store/4bc7msipq8xa14faq9vndxrs8s22ny2w-gettext-minimal-0.20.1/include:/gnu/store/26m0d62f34j6bs4x0m4n0b3l4mvmamb5-dbus-1.12.16/include:/gnu/store/kiz15vy5mv2jw37365j76cy1a88a3p2a-pcre-8.44/include:/gnu/store/pn4bci1x4dsmaafmslx6g61af7n2j0sy-libffi-3.3/include:/gnu/store/5ffrqmfh2c0dgmh9ji3lgvnvgsnmlhfp-util-linux-2.35.1-lib/include:/gnu/store/y9kzwhkz2k1a5i3x1dd3mq2h984z4hg5-libselinux-3.0/include:/gnu/store/pqyqxd5mbvlb22ifxzp4q2skjfq1p8yj-zlib-1.2.11/include:/gnu/store/n1jk0w2wa4vpwmixaqn2y3la1l2sizzi-bzip2-1.0.8/include:/gnu/store/7p36raqgk6vn47bflxc9bsclqiib3phi-xz-5.2.4/include:/gnu/store/lpkf3ydcdvxn8gcrzaq9cp3ri05h8qhs-file-5.38/include:/gnu/store/9iwlsj7d6ffqhshy8qshf7p4fqwfwrvn-gawk-5.0.1/include:/gnu/store/b7jbh7kzzig0bxfswdj8nfj9bkljyyya-make-4.3/include:/gnu/store/50lyzn9bz6x4da66648kry29wn8afird-binutils-2.34/include:/gnu/store/afpgzln8860m6yfhxy6i8n9rywbp85cy-gcc-7.5.0/include:/gnu/store/z4li262il798hbl0l1h1k3a5g7r6bffa-glibc-2.31/include:/gnu/store/nlyy80nlkwb9i377h888nl97jfzhaf4r-python-3.8.2/include:/gnu/store/3x44yvsap0ss63j8d7yv6wm63ngr3j12-libsepol-3.0/include:/gnu/store/hk7l42fwxmnrnlhyiixvaqf1i1crcckp-linux-libre-headers-5.4.20/include'
environment variable `CPLUS_INCLUDE_PATH' set to `/gnu/store/4bc7msipq8xa14faq9vndxrs8s22ny2w-gettext-minimal-0.20.1/include:/gnu/store/26m0d62f34j6bs4x0m4n0b3l4mvmamb5-dbus-1.12.16/include:/gnu/store/kiz15vy5mv2jw37365j76cy1a88a3p2a-pcre-8.44/include:/gnu/store/pn4bci1x4dsmaafmslx6g61af7n2j0sy-libffi-3.3/include:/gnu/store/5ffrqmfh2c0dgmh9ji3lgvnvgsnmlhfp-util-linux-2.35.1-lib/include:/gnu/store/y9kzwhkz2k1a5i3x1dd3mq2h984z4hg5-libselinux-3.0/include:/gnu/store/pqyqxd5mbvlb22ifxzp4q2skjfq1p8yj-zlib-1.2.11/include:/gnu/store/n1jk0w2wa4vpwmixaqn2y3la1l2sizzi-bzip2-1.0.8/include:/gnu/store/7p36raqgk6vn47bflxc9bsclqiib3phi-xz-5.2.4/include:/gnu/store/lpkf3ydcdvxn8gcrzaq9cp3ri05h8qhs-file-5.38/include:/gnu/store/9iwlsj7d6ffqhshy8qshf7p4fqwfwrvn-gawk-5.0.1/include:/gnu/store/b7jbh7kzzig0bxfswdj8nfj9bkljyyya-make-4.3/include:/gnu/store/50lyzn9bz6x4da66648kry29wn8afird-binutils-2.34/include:/gnu/store/afpgzln8860m6yfhxy6i8n9rywbp85cy-gcc-7.5.0/include/c++:/gnu/store/afpgzln8860m6yfhxy6i8n9rywbp85cy-gcc-7.5.0/include:/gnu/store/z4li262il798hbl0l1h1k3a5g7r6bffa-glibc-2.31/include:/gnu/store/nlyy80nlkwb9i377h888nl97jfzhaf4r-python-3.8.2/include:/gnu/store/3x44yvsap0ss63j8d7yv6wm63ngr3j12-libsepol-3.0/include:/gnu/store/hk7l42fwxmnrnlhyiixvaqf1i1crcckp-linux-libre-headers-5.4.20/include'
environment variable `LIBRARY_PATH' set to `/gnu/store/b6r7jh5fj3z2h7l7nz2w0y08nz7m1kfz-meson-for-build-0.53.2/lib:/gnu/store/4bc7msipq8xa14faq9vndxrs8s22ny2w-gettext-minimal-0.20.1/lib:/gnu/store/26m0d62f34j6bs4x0m4n0b3l4mvmamb5-dbus-1.12.16/lib:/gnu/store/ysk9g469f4pvw7i318kbk1hnrfrydanl-perl-5.30.2/lib:/gnu/store/kiz15vy5mv2jw37365j76cy1a88a3p2a-pcre-8.44/lib:/gnu/store/pn4bci1x4dsmaafmslx6g61af7n2j0sy-libffi-3.3/lib:/gnu/store/5ffrqmfh2c0dgmh9ji3lgvnvgsnmlhfp-util-linux-2.35.1-lib/lib:/gnu/store/y9kzwhkz2k1a5i3x1dd3mq2h984z4hg5-libselinux-3.0/lib:/gnu/store/pqyqxd5mbvlb22ifxzp4q2skjfq1p8yj-zlib-1.2.11/lib:/gnu/store/n1jk0w2wa4vpwmixaqn2y3la1l2sizzi-bzip2-1.0.8/lib:/gnu/store/7p36raqgk6vn47bflxc9bsclqiib3phi-xz-5.2.4/lib:/gnu/store/lpkf3ydcdvxn8gcrzaq9cp3ri05h8qhs-file-5.38/lib:/gnu/store/9iwlsj7d6ffqhshy8qshf7p4fqwfwrvn-gawk-5.0.1/lib:/gnu/store/50lyzn9bz6x4da66648kry29wn8afird-binutils-2.34/lib:/gnu/store/z4li262il798hbl0l1h1k3a5g7r6bffa-glibc-2.31/lib:/gnu/store/rzk3v28mhi4m7sh0qippp9a5rzy03rkg-glibc-2.31-static/lib:/gnu/store/x6i3vfg4gaqd42cqb6mzk52v4lds1467-glibc-utf8-locales-2.31/lib:/gnu/store/nlyy80nlkwb9i377h888nl97jfzhaf4r-python-3.8.2/lib:/gnu/store/3x44yvsap0ss63j8d7yv6wm63ngr3j12-libsepol-3.0/lib'
environment variable `GUIX_LOCPATH' set to `/gnu/store/x6i3vfg4gaqd42cqb6mzk52v4lds1467-glibc-utf8-locales-2.31/lib/locale'
phase `set-paths' succeeded after 0.0 seconds
starting phase `install-locale'
using 'en_US.utf8' locale for category "LC_ALL"
phase `install-locale' succeeded after 0.0 seconds
starting phase `unpack'
glib-2.62.6/
glib-2.62.6/.dir-locals.el
glib-2.62.6/AUTHORS
glib-2.62.6/CONTRIBUTING.md
glib-2.62.6/COPYING
glib-2.62.6/HACKING
glib-2.62.6/INSTALL.in
glib-2.62.6/NEWS
glib-2.62.6/NEWS.pre-1-3
glib-2.62.6/README
glib-2.62.6/README.md
glib-2.62.6/README.rationale
glib-2.62.6/README.win32
glib-2.62.6/README.win32.md
glib-2.62.6/check-abis.sh
glib-2.62.6/docs/
glib-2.62.6/docs/CODEOWNERS
glib-2.62.6/docs/debugging.txt
glib-2.62.6/docs/macros.txt
glib-2.62.6/docs/reference/
glib-2.62.6/docs/reference/.gitignore
glib-2.62.6/docs/reference/AUTHORS
glib-2.62.6/docs/reference/COPYING
glib-2.62.6/docs/reference/NEWS
glib-2.62.6/docs/reference/gio/
glib-2.62.6/docs/reference/gio/.gitignore
glib-2.62.6/docs/reference/gio/concat-files-helper.py
glib-2.62.6/docs/reference/gio/gapplication.xml
glib-2.62.6/docs/reference/gio/gdbus-codegen.xml
glib-2.62.6/docs/reference/gio/gdbus.xml
glib-2.62.6/docs/reference/gio/gio-docs-unix.xml
glib-2.62.6/docs/reference/gio/gio-docs-win32.xml
glib-2.62.6/docs/reference/gio/gio-docs.xml
glib-2.62.6/docs/reference/gio/gio-querymodules.xml
glib-2.62.6/docs/reference/gio/gio-sections-common.txt
glib-2.62.6/docs/reference/gio/gio-sections-win32.txt
glib-2.62.6/docs/reference/gio/gio.xml
glib-2.62.6/docs/reference/gio/glib-compile-resources.xml
glib-2.62.6/docs/reference/gio/glib-compile-schemas.xml
glib-2.62.6/docs/reference/gio/gresource.xml
glib-2.62.6/docs/reference/gio/gsettings.xml
glib-2.62.6/docs/reference/gio/gvfs-overview.odg
glib-2.62.6/docs/reference/gio/gvfs-overview.png
glib-2.62.6/docs/reference/gio/menu-example.png
glib-2.62.6/docs/reference/gio/menu-model.png
glib-2.62.6/docs/reference/gio/meson.build
glib-2.62.6/docs/reference/gio/migrating-gconf.xml
glib-2.62.6/docs/reference/gio/migrating-gdbus.xml
glib-2.62.6/docs/reference/gio/migrating-gnome-vfs.xml
glib-2.62.6/docs/reference/gio/migrating-posix.xml
glib-2.62.6/docs/reference/gio/overview.xml
glib-2.62.6/docs/reference/gio/version.xml.in
glib-2.62.6/docs/reference/gio/xml/
glib-2.62.6/docs/reference/gio/xml/gtkdocentities.ent.in
glib-2.62.6/docs/reference/gio/xml/meson.build
glib-2.62.6/docs/reference/glib/
glib-2.62.6/docs/reference/glib/Sorted_binary_tree_breadth-first_traversal.svg
glib-2.62.6/docs/reference/glib/Sorted_binary_tree_inorder.svg
glib-2.62.6/docs/reference/glib/Sorted_binary_tree_postorder.svg
glib-2.62.6/docs/reference/glib/Sorted_binary_tree_preorder.svg
glib-2.62.6/docs/reference/glib/building.xml
glib-2.62.6/docs/reference/glib/changes.xml
glib-2.62.6/docs/reference/glib/compiling.xml
glib-2.62.6/docs/reference/glib/cross.xml
glib-2.62.6/docs/reference/glib/file-name-encodings.png
glib-2.62.6/docs/reference/glib/file-name-encodings.sxd
glib-2.62.6/docs/reference/glib/glib-docs.xml
glib-2.62.6/docs/reference/glib/glib-gettextize.xml
glib-2.62.6/docs/reference/glib/glib-overrides.txt
glib-2.62.6/docs/reference/glib/glib-sections.txt
glib-2.62.6/docs/reference/glib/gtester-report.xml
glib-2.62.6/docs/reference/glib/gtester.xml
glib-2.62.6/docs/reference/glib/gvariant-text.xml
glib-2.62.6/docs/reference/glib/gvariant-varargs.xml
glib-2.62.6/docs/reference/glib/mainloop-states.eps
glib-2.62.6/docs/reference/glib/mainloop-states.fig
glib-2.62.6/docs/reference/glib/mainloop-states.gif
glib-2.62.6/docs/reference/glib/mainloop-states.png
glib-2.62.6/docs/reference/glib/meson.build
glib-2.62.6/docs/reference/glib/programming.xml
glib-2.62.6/docs/reference/glib/regex-syntax.xml
glib-2.62.6/docs/reference/glib/resources.xml
glib-2.62.6/docs/reference/glib/running.xml
glib-2.62.6/docs/reference/glib/version.xml.in
glib-2.62.6/docs/reference/glib/xml/
glib-2.62.6/docs/reference/glib/xml/gtkdocentities.ent.in
glib-2.62.6/docs/reference/glib/xml/meson.build
glib-2.62.6/docs/reference/gobject/
glib-2.62.6/docs/reference/gobject/glib-genmarshal.xml
glib-2.62.6/docs/reference/gobject/glib-mkenums.xml
glib-2.62.6/docs/reference/gobject/gobject-docs.xml
glib-2.62.6/docs/reference/gobject/gobject-overrides.txt
glib-2.62.6/docs/reference/gobject/gobject-query.xml
glib-2.62.6/docs/reference/gobject/gobject-sections.txt
glib-2.62.6/docs/reference/gobject/images/
glib-2.62.6/docs/reference/gobject/images/glue.png
glib-2.62.6/docs/reference/gobject/meson.build
glib-2.62.6/docs/reference/gobject/tut_gobject.xml
glib-2.62.6/docs/reference/gobject/tut_gsignal.xml
glib-2.62.6/docs/reference/gobject/tut_gtype.xml
glib-2.62.6/docs/reference/gobject/tut_howto.xml
glib-2.62.6/docs/reference/gobject/tut_intro.xml
glib-2.62.6/docs/reference/gobject/tut_tools.xml
glib-2.62.6/docs/reference/gobject/version.xml.in
glib-2.62.6/docs/reference/gobject/xml/
glib-2.62.6/docs/reference/gobject/xml/gtkdocentities.ent.in
glib-2.62.6/docs/reference/gobject/xml/meson.build
glib-2.62.6/docs/reference/meson.build
glib-2.62.6/fuzzing/
glib-2.62.6/fuzzing/README.md
glib-2.62.6/fuzzing/driver.c
glib-2.62.6/fuzzing/fuzz.h
glib-2.62.6/fuzzing/fuzz_bookmark.c
glib-2.62.6/fuzzing/fuzz_bookmark.corpus
glib-2.62.6/fuzzing/fuzz_dbus_message.c
glib-2.62.6/fuzzing/fuzz_key.c
glib-2.62.6/fuzzing/fuzz_key.corpus
glib-2.62.6/fuzzing/fuzz_variant_binary.c
glib-2.62.6/fuzzing/fuzz_variant_text.c
glib-2.62.6/fuzzing/fuzz_variant_text.dict
glib-2.62.6/fuzzing/meson.build
glib-2.62.6/gio/
glib-2.62.6/gio/completion/
glib-2.62.6/gio/completion/.gitignore
glib-2.62.6/gio/completion/gapplication
glib-2.62.6/gio/completion/gdbus
glib-2.62.6/gio/completion/gio
glib-2.62.6/gio/completion/gresource
glib-2.62.6/gio/completion/gsettings
glib-2.62.6/gio/data-to-c.py
glib-2.62.6/gio/dbus-daemon.xml
glib-2.62.6/gio/fam/
glib-2.62.6/gio/fam/gfamfilemonitor.c
glib-2.62.6/gio/fam/gfamfilemonitor.map
glib-2.62.6/gio/fam/meson.build
glib-2.62.6/gio/gaction.c
glib-2.62.6/gio/gaction.h
glib-2.62.6/gio/gactiongroup.c
glib-2.62.6/gio/gactiongroup.h
glib-2.62.6/gio/gactiongroupexporter.c
glib-2.62.6/gio/gactiongroupexporter.h
glib-2.62.6/gio/gactionmap.c
glib-2.62.6/gio/gactionmap.h
glib-2.62.6/gio/gappinfo.c
glib-2.62.6/gio/gappinfo.h
glib-2.62.6/gio/gappinfoprivate.h
glib-2.62.6/gio/gapplication-tool.c
glib-2.62.6/gio/gapplication.c
glib-2.62.6/gio/gapplication.h
glib-2.62.6/gio/gapplicationcommandline.c
glib-2.62.6/gio/gapplicationcommandline.h
glib-2.62.6/gio/gapplicationimpl-dbus.c
glib-2.62.6/gio/gapplicationimpl.h
glib-2.62.6/gio/gasynchelper.c
glib-2.62.6/gio/gasynchelper.h
glib-2.62.6/gio/gasyncinitable.c
glib-2.62.6/gio/gasyncinitable.h
glib-2.62.6/gio/gasyncresult.c
glib-2.62.6/gio/gasyncresult.h
glib-2.62.6/gio/gbufferedinputstream.c
glib-2.62.6/gio/gbufferedinputstream.h
glib-2.62.6/gio/gbufferedoutputstream.c
glib-2.62.6/gio/gbufferedoutputstream.h
glib-2.62.6/gio/gbytesicon.c
glib-2.62.6/gio/gbytesicon.h
glib-2.62.6/gio/gcancellable.c
glib-2.62.6/gio/gcancellable.h
glib-2.62.6/gio/gcharsetconverter.c
glib-2.62.6/gio/gcharsetconverter.h
glib-2.62.6/gio/gcocoanotificationbackend.m
glib-2.62.6/gio/gcontenttype-win32.c
glib-2.62.6/gio/gcontenttype.c
glib-2.62.6/gio/gcontenttype.h
glib-2.62.6/gio/gcontenttypeprivate.h
glib-2.62.6/gio/gcontextspecificgroup.c
glib-2.62.6/gio/gcontextspecificgroup.h
glib-2.62.6/gio/gconverter.c
glib-2.62.6/gio/gconverter.h
glib-2.62.6/gio/gconverterinputstream.c
glib-2.62.6/gio/gconverterinputstream.h
glib-2.62.6/gio/gconverteroutputstream.c
glib-2.62.6/gio/gconverteroutputstream.h
glib-2.62.6/gio/gcredentials.c
glib-2.62.6/gio/gcredentials.h
glib-2.62.6/gio/gcredentialsprivate.h
glib-2.62.6/gio/gdatagrambased.c
glib-2.62.6/gio/gdatagrambased.h
glib-2.62.6/gio/gdatainputstream.c
glib-2.62.6/gio/gdatainputstream.h
glib-2.62.6/gio/gdataoutputstream.c
glib-2.62.6/gio/gdataoutputstream.h
glib-2.62.6/gio/gdbus-2.0/
glib-2.62.6/gio/gdbus-2.0/codegen/
glib-2.62.6/gio/gdbus-2.0/codegen/.gitignore
glib-2.62.6/gio/gdbus-2.0/codegen/__init__.py
glib-2.62.6/gio/gdbus-2.0/codegen/codegen.py
glib-2.62.6/gio/gdbus-2.0/codegen/codegen_docbook.py
glib-2.62.6/gio/gdbus-2.0/codegen/codegen_main.py
glib-2.62.6/gio/gdbus-2.0/codegen/config.py.in
glib-2.62.6/gio/gdbus-2.0/codegen/dbustypes.py
glib-2.62.6/gio/gdbus-2.0/codegen/gdbus-codegen.in
glib-2.62.6/gio/gdbus-2.0/codegen/meson.build
glib-2.62.6/gio/gdbus-2.0/codegen/parser.py
glib-2.62.6/gio/gdbus-2.0/codegen/utils.py
glib-2.62.6/gio/gdbus-tool.c
glib-2.62.6/gio/gdbusactiongroup-private.h
glib-2.62.6/gio/gdbusactiongroup.c
glib-2.62.6/gio/gdbusactiongroup.h
glib-2.62.6/gio/gdbusaddress.c
glib-2.62.6/gio/gdbusaddress.h
glib-2.62.6/gio/gdbusauth.c
glib-2.62.6/gio/gdbusauth.h
glib-2.62.6/gio/gdbusauthmechanism.c
glib-2.62.6/gio/gdbusauthmechanism.h
glib-2.62.6/gio/gdbusauthmechanismanon.c
glib-2.62.6/gio/gdbusauthmechanismanon.h
glib-2.62.6/gio/gdbusauthmechanismexternal.c
glib-2.62.6/gio/gdbusauthmechanismexternal.h
glib-2.62.6/gio/gdbusauthmechanismsha1.c
glib-2.62.6/gio/gdbusauthmechanismsha1.h
glib-2.62.6/gio/gdbusauthobserver.c
glib-2.62.6/gio/gdbusauthobserver.h
glib-2.62.6/gio/gdbusconnection.c
glib-2.62.6/gio/gdbusconnection.h
glib-2.62.6/gio/gdbusdaemon.c
glib-2.62.6/gio/gdbusdaemon.h
glib-2.62.6/gio/gdbuserror.c
glib-2.62.6/gio/gdbuserror.h
glib-2.62.6/gio/gdbusinterface.c
glib-2.62.6/gio/gdbusinterface.h
glib-2.62.6/gio/gdbusinterfaceskeleton.c
glib-2.62.6/gio/gdbusinterfaceskeleton.h
glib-2.62.6/gio/gdbusintrospection.c
glib-2.62.6/gio/gdbusintrospection.h
glib-2.62.6/gio/gdbusmenumodel.c
glib-2.62.6/gio/gdbusmenumodel.h
glib-2.62.6/gio/gdbusmessage.c
glib-2.62.6/gio/gdbusmessage.h
glib-2.62.6/gio/gdbusmethodinvocation.c
glib-2.62.6/gio/gdbusmethodinvocation.h
glib-2.62.6/gio/gdbusnameowning.c
glib-2.62.6/gio/gdbusnameowning.h
glib-2.62.6/gio/gdbusnamewatching.c
glib-2.62.6/gio/gdbusnamewatching.h
glib-2.62.6/gio/gdbusobject.c
glib-2.62.6/gio/gdbusobject.h
glib-2.62.6/gio/gdbusobjectmanager.c
glib-2.62.6/gio/gdbusobjectmanager.h
glib-2.62.6/gio/gdbusobjectmanagerclient.c
glib-2.62.6/gio/gdbusobjectmanagerclient.h
glib-2.62.6/gio/gdbusobjectmanagerserver.c
glib-2.62.6/gio/gdbusobjectmanagerserver.h
glib-2.62.6/gio/gdbusobjectproxy.c
glib-2.62.6/gio/gdbusobjectproxy.h
glib-2.62.6/gio/gdbusobjectskeleton.c
glib-2.62.6/gio/gdbusobjectskeleton.h
glib-2.62.6/gio/gdbusprivate.c
glib-2.62.6/gio/gdbusprivate.h
glib-2.62.6/gio/gdbusproxy.c
glib-2.62.6/gio/gdbusproxy.h
glib-2.62.6/gio/gdbusserver.c
glib-2.62.6/gio/gdbusserver.h
glib-2.62.6/gio/gdbusutils.c
glib-2.62.6/gio/gdbusutils.h
glib-2.62.6/gio/gdelayedsettingsbackend.c
glib-2.62.6/gio/gdelayedsettingsbackend.h
glib-2.62.6/gio/gdesktopappinfo.c
glib-2.62.6/gio/gdesktopappinfo.h
glib-2.62.6/gio/gdocumentportal.c
glib-2.62.6/gio/gdocumentportal.h
glib-2.62.6/gio/gdrive.c
glib-2.62.6/gio/gdrive.h
glib-2.62.6/gio/gdtlsclientconnection.c
glib-2.62.6/gio/gdtlsclientconnection.h
glib-2.62.6/gio/gdtlsconnection.c
glib-2.62.6/gio/gdtlsconnection.h
glib-2.62.6/gio/gdtlsserverconnection.c
glib-2.62.6/gio/gdtlsserverconnection.h
glib-2.62.6/gio/gdummyfile.c
glib-2.62.6/gio/gdummyfile.h
glib-2.62.6/gio/gdummyproxyresolver.c
glib-2.62.6/gio/gdummyproxyresolver.h
glib-2.62.6/gio/gdummytlsbackend.c
glib-2.62.6/gio/gdummytlsbackend.h
glib-2.62.6/gio/gemblem.c
glib-2.62.6/gio/gemblem.h
glib-2.62.6/gio/gemblemedicon.c
glib-2.62.6/gio/gemblemedicon.h
glib-2.62.6/gio/gfdonotificationbackend.c
glib-2.62.6/gio/gfile.c
glib-2.62.6/gio/gfile.h
glib-2.62.6/gio/gfileattribute-priv.h
glib-2.62.6/gio/gfileattribute.c
glib-2.62.6/gio/gfileattribute.h
glib-2.62.6/gio/gfiledescriptorbased.c
glib-2.62.6/gio/gfiledescriptorbased.h
glib-2.62.6/gio/gfileenumerator.c
glib-2.62.6/gio/gfileenumerator.h
glib-2.62.6/gio/gfileicon.c
glib-2.62.6/gio/gfileicon.h
glib-2.62.6/gio/gfileinfo-priv.h
glib-2.62.6/gio/gfileinfo.c
glib-2.62.6/gio/gfileinfo.h
glib-2.62.6/gio/gfileinputstream.c
glib-2.62.6/gio/gfileinputstream.h
glib-2.62.6/gio/gfileiostream.c
glib-2.62.6/gio/gfileiostream.h
glib-2.62.6/gio/gfilemonitor.c
glib-2.62.6/gio/gf
This message was truncated. Download the full message here.
R
R
raingloom wrote on 26 Apr 2021 17:26
(name . Bone Baboon via Bug reports for GNU Guix)(address . bug-guix@gnu.org)
20210426172652.005ae12b@riseup.net
On Sun, 25 Apr 2021 23:35:42 -0400
Bone Baboon via Bug reports for GNU Guix <bug-guix@gnu.org> wrote:

Toggle quote (5 lines)
> At the end of the build log this log is mentioned
> `/tmp/guix-build-glib-2.62.6.drv-0/build/meson-logs/testlog.txt`
> but it does not exist.
>

Use the --keep-failed build option, otherwise the /tmp/guix-build-*
directories are deleted when their respective builds fail. Otherwise
they would just waste space.
B
B
Bone Baboon wrote on 27 Apr 2021 21:25
(name . raingloom)(address . raingloom@riseup.net)
87mttjlebl.fsf@disroot.org
raingloom writes:
Toggle quote (4 lines)
> Use the --keep-failed build option, otherwise the /tmp/guix-build-*
> directories are deleted when their respective builds fail. Otherwise
> they would just waste space.

Thank you for mentioning `--keep-failed`.

I did a pull and then ran `sudo guix system --no-substitutes --cores=2 --keep-failed reconfigure configuration.scm` it failed again. The build log refers to this log: `/tmp/guix-build-glib-2.62.6.drv-0/build/meson-logs/testlog.txt`

Using `--keep-failed` has kept the log. The log is in a different directory than the build log says.

The contents of `/tmp/guix-build-glib-2.62.6.drv-0/top/build/meson-logs/testlog.txt` are:

```
Log of Meson test suite run on 2021-04-27T02:17:17.703661

Inherited environment: HOME='/tmp/guix-build-glib-2.62.6.drv-0/build' NIX_BUILD_CORES='3' NIX_BUILD_TOP='/tmp/guix-build-glib-2.62.6.drv-0' NIX_STORE='/gnu/store' PATH='/gnu/store/b6r7jh5fj3z2h7l7nz2w0y08nz7m1kfz-meson-for-build-0.53.2/bin:/gnu/store/6hnpwxpas0zsswz7yqib8njhansqmhkw-ninja-1.10.0/bin:/gnu/store/4bc7msipq8xa14faq9vndxrs8s22ny2w-gettext-minimal-0.20.1/bin:/gnu/store/7ds6f0fnd3n5zzhcjjnkmry990shrcm8-m4-1.4.18/bin:/gnu/store/26m0d62f34j6bs4x0m4n0b3l4mvmamb5-dbus-1.12.16/bin:/gnu/store/fh8pmj9qqwbr1j1vrjc4zgnlgm08birz-pkg-config-0.29.2/bin:/gnu/store/36p2wpd5pfsq3nyyshi44scxi3gilkam-python-wrapper-3.8.2/bin:/gnu/store/ysk9g469f4pvw7i318kbk1hnrfrydanl-perl-5.30.2/bin:/gnu/store/y9kzwhkz2k1a5i3x1dd3mq2h984z4hg5-libselinux-3.0/sbin:/gnu/store/gww59gv5qxbfijg3vk5y182im7923s06-tar-1.32/bin:/gnu/store/2ayciqwxddkzq183dac82ijljc14j4zj-gzip-1.10/bin:/gnu/store/n1jk0w2wa4vpwmixaqn2y3la1l2sizzi-bzip2-1.0.8/bin:/gnu/store/7p36raqgk6vn47bflxc9bsclqiib3phi-xz-5.2.4/bin:/gnu/store/lpkf3ydcdvxn8gcrzaq9cp3ri05h8qhs-file-5.38/bin:/gnu/store/6gqaw09zqw8w0vcax6simlq71bq7l5r0-diffutils-3.7/bin:/gnu/store/qw20chpgkgbcqmzhs60c8hjl1hmblyc8-patch-2.7.6/bin:/gnu/store/b5y5scfmh2d8kxcpl9p84294z2198cgf-findutils-4.7.0/bin:/gnu/store/9iwlsj7d6ffqhshy8qshf7p4fqwfwrvn-gawk-5.0.1/bin:/gnu/store/q1nfjb24vqjs1cgi8mlnskw34h16y09r-sed-4.8/bin:/gnu/store/4qr6mcvsxyzknxa7x1wny8x30f5i0r3n-grep-3.4/bin:/gnu/store/2v61vg0bizgrhybkqbrki2k7kr094waz-coreutils-8.32/bin:/gnu/store/b7jbh7kzzig0bxfswdj8nfj9bkljyyya-make-4.3/bin:/gnu/store/v1g7f3p4f0851mywrla8qmr9hb8jgfjr-bash-minimal-5.0.16/bin:/gnu/store/dyqxnydqk1810afjfbqzfvh0n83xyl62-ld-wrapper-0/bin:/gnu/store/50lyzn9bz6x4da66648kry29wn8afird-binutils-2.34/bin:/gnu/store/afpgzln8860m6yfhxy6i8n9rywbp85cy-gcc-7.5.0/bin:/gnu/store/z4li262il798hbl0l1h1k3a5g7r6bffa-glibc-2.31/bin:/gnu/store/z4li262il798hbl0l1h1k3a5g7r6bffa-glibc-2.31/sbin:/gnu/store/nlyy80nlkwb9i377h888nl97jfzhaf4r-python-3.8.2/bin:/gnu/store/3x44yvsap0ss63j8d7yv6wm63ngr3j12-libsepol-3.0/bin' PWD='/tmp/guix-build-glib-2.62.6.drv-0' TEMP='/tmp/guix-build-glib-2.62.6.drv-0' TEMPDIR='/tmp/guix-build-glib-2.62.6.drv-0' TMP='/tmp/guix-build-glib-2.62.6.drv-0' TMPDIR='/tmp/guix-build-glib-2.62.6.drv-0' bin='/gnu/store/h4ym818rxk6gm8ad3vm54024qq1jz6am-glib-2.62.6-bin' disallowedReferences='/gnu/store/id6xknfpbr1prwvxl90sz6lgkrhlz70y-tzdata-2019c' out='/gnu/store/dsa7a9ydy2y6y5pfgmjxp55yz586vnzm-glib-2.62.6' SOURCE_DATE_EPOCH='1' GUIX_LD_WRAPPER_ALLOW_IMPURITIES='no' PKG_CONFIG_PATH='/gnu/store/26m0d62f34j6bs4x0m4n0b3l4mvmamb5-dbus-1.12.16/lib/pkgconfig:/gnu/store/kiz15vy5mv2jw37365j76cy1a88a3p2a-pcre-8.44/lib/pkgconfig:/gnu/store/pn4bci1x4dsmaafmslx6g61af7n2j0sy-libffi-3.3/lib/pkgconfig:/gnu/store/5ffrqmfh2c0dgmh9ji3lgvnvgsnmlhfp-util-linux-2.35.1-lib/lib/pkgconfig:/gnu/store/y9kzwhkz2k1a5i3x1dd3mq2h984z4hg5-libselinux-3.0/lib/pkgconfig:/gnu/store/pqyqxd5mbvlb22ifxzp4q2skjfq1p8yj-zlib-1.2.11/lib/pkgconfig:/gnu/store/7p36raqgk6vn47bflxc9bsclqiib3phi-xz-5.2.4/lib/pkgconfig:/gnu/store/nlyy80nlkwb9i377h888nl97jfzhaf4r-python-3.8.2/lib/pkgconfig:/gnu/store/3x44yvsap0ss63j8d7yv6wm63ngr3j12-libsepol-3.0/lib/pkgconfig' PYTHONPATH='/gnu/store/b6r7jh5fj3z2h7l7nz2w0y08nz7m1kfz-meson-for-build-0.53.2/lib/python3.8/site-packages:/gnu/store/nlyy80nlkwb9i377h888nl97jfzhaf4r-python-3.8.2/lib/python3.8/site-packages' PERL5LIB='/gnu/store/ysk9g469f4pvw7i318kbk1hnrfrydanl-perl-5.30.2/lib/perl5/site_perl' C_INCLUDE_PATH='/gnu/store/4bc7msipq8xa14faq9vndxrs8s22ny2w-gettext-minimal-0.20.1/include:/gnu/store/26m0d62f34j6bs4x0m4n0b3l4mvmamb5-dbus-1.12.16/include:/gnu/store/kiz15vy5mv2jw37365j76cy1a88a3p2a-pcre-8.44/include:/gnu/store/pn4bci1x4dsmaafmslx6g61af7n2j0sy-libffi-3.3/include:/gnu/store/5ffrqmfh2c0dgmh9ji3lgvnvgsnmlhfp-util-linux-2.35.1-lib/include:/gnu/store/y9kzwhkz2k1a5i3x1dd3mq2h984z4hg5-libselinux-3.0/include:/gnu/store/pqyqxd5mbvlb22ifxzp4q2skjfq1p8yj-zlib-1.2.11/include:/gnu/store/n1jk0w2wa4vpwmixaqn2y3la1l2sizzi-bzip2-1.0.8/include:/gnu/store/7p36raqgk6vn47bflxc9bsclqiib3phi-xz-5.2.4/include:/gnu/store/lpkf3ydcdvxn8gcrzaq9cp3ri05h8qhs-file-5.38/include:/gnu/store/9iwlsj7d6ffqhshy8qshf7p4fqwfwrvn-gawk-5.0.1/include:/gnu/store/b7jbh7kzzig0bxfswdj8nfj9bkljyyya-make-4.3/include:/gnu/store/50lyzn9bz6x4da66648kry29wn8afird-binutils-2.34/include:/gnu/store/afpgzln8860m6yfhxy6i8n9rywbp85cy-gcc-7.5.0/include:/gnu/store/z4li262il798hbl0l1h1k3a5g7r6bffa-glibc-2.31/include:/gnu/store/nlyy80nlkwb9i377h888nl97jfzhaf4r-python-3.8.2/include:/gnu/store/3x44yvsap0ss63j8d7yv6wm63ngr3j12-libsepol-3.0/include:/gnu/store/hk7l42fwxmnrnlhyiixvaqf1i1crcckp-linux-libre-headers-5.4.20/include' CPLUS_INCLUDE_PATH='/gnu/store/4bc7msipq8xa14faq9vndxrs8s22ny2w-gettext-minimal-0.20.1/include:/gnu/store/26m0d62f34j6bs4x0m4n0b3l4mvmamb5-dbus-1.12.16/include:/gnu/store/kiz15vy5mv2jw37365j76cy1a88a3p2a-pcre-8.44/include:/gnu/store/pn4bci1x4dsmaafmslx6g61af7n2j0sy-libffi-3.3/include:/gnu/store/5ffrqmfh2c0dgmh9ji3lgvnvgsnmlhfp-util-linux-2.35.1-lib/include:/gnu/store/y9kzwhkz2k1a5i3x1dd3mq2h984z4hg5-libselinux-3.0/include:/gnu/store/pqyqxd5mbvlb22ifxzp4q2skjfq1p8yj-zlib-1.2.11/include:/gnu/store/n1jk0w2wa4vpwmixaqn2y3la1l2sizzi-bzip2-1.0.8/include:/gnu/store/7p36raqgk6vn47bflxc9bsclqiib3phi-xz-5.2.4/include:/gnu/store/lpkf3ydcdvxn8gcrzaq9cp3ri05h8qhs-file-5.38/include:/gnu/store/9iwlsj7d6ffqhshy8qshf7p4fqwfwrvn-gawk-5.0.1/include:/gnu/store/b7jbh7kzzig0bxfswdj8nfj9bkljyyya-make-4.3/include:/gnu/store/50lyzn9bz6x4da66648kry29wn8afird-binutils-2.34/include:/gnu/store/afpgzln8860m6yfhxy6i8n9rywbp85cy-gcc-7.5.0/include/c++:/gnu/store/afpgzln8860m6yfhxy6i8n9rywbp85cy-gcc-7.5.0/include:/gnu/store/z4li262il798hbl0l1h1k3a5g7r6bffa-glibc-2.31/include:/gnu/store/nlyy80nlkwb9i377h888nl97jfzhaf4r-python-3.8.2/include:/gnu/store/3x44yvsap0ss63j8d7yv6wm63ngr3j12-libsepol-3.0/include:/gnu/store/hk7l42fwxmnrnlhyiixvaqf1i1crcckp-linux-libre-headers-5.4.20/include' LIBRARY_PATH='/gnu/store/b6r7jh5fj3z2h7l7nz2w0y08nz7m1kfz-meson-for-build-0.53.2/lib:/gnu/store/4bc7msipq8xa14faq9vndxrs8s22ny2w-gettext-minimal-0.20.1/lib:/gnu/store/26m0d62f34j6bs4x0m4n0b3l4mvmamb5-dbus-1.12.16/lib:/gnu/store/ysk9g469f4pvw7i318kbk1hnrfrydanl-perl-5.30.2/lib:/gnu/store/kiz15vy5mv2jw37365j76cy1a88a3p2a-pcre-8.44/lib:/gnu/store/pn4bci1x4dsmaafmslx6g61af7n2j0sy-libffi-3.3/lib:/gnu/store/5ffrqmfh2c0dgmh9ji3lgvnvgsnmlhfp-util-linux-2.35.1-lib/lib:/gnu/store/y9kzwhkz2k1a5i3x1dd3mq2h984z4hg5-libselinux-3.0/lib:/gnu/store/pqyqxd5mbvlb22ifxzp4q2skjfq1p8yj-zlib-1.2.11/lib:/gnu/store/n1jk0w2wa4vpwmixaqn2y3la1l2sizzi-bzip2-1.0.8/lib:/gnu/store/7p36raqgk6vn47bflxc9bsclqiib3phi-xz-5.2.4/lib:/gnu/store/lpkf3ydcdvxn8gcrzaq9cp3ri05h8qhs-file-5.38/lib:/gnu/store/9iwlsj7d6ffqhshy8qshf7p4fqwfwrvn-gawk-5.0.1/lib:/gnu/store/50lyzn9bz6x4da66648kry29wn8afird-binutils-2.34/lib:/gnu/store/z4li262il798hbl0l1h1k3a5g7r6bffa-glibc-2.31/lib:/gnu/store/rzk3v28mhi4m7sh0qippp9a5rzy03rkg-glibc-2.31-static/lib:/gnu/store/x6i3vfg4gaqd42cqb6mzk52v4lds1467-glibc-utf8-locales-2.31/lib:/gnu/store/nlyy80nlkwb9i377h888nl97jfzhaf4r-python-3.8.2/lib:/gnu/store/3x44yvsap0ss63j8d7yv6wm63ngr3j12-libsepol-3.0/lib' GUIX_LOCPATH='/gnu/store/x6i3vfg4gaqd42cqb6mzk52v4lds1467-glibc-utf8-locales-2.31/lib/locale' LC_ALL='en_US.utf8' TZDIR='/gnu/store/id6xknfpbr1prwvxl90sz6lgkrhlz70y-tzdata-2019c/share/zoneinfo' XDG_CACHE_HOME='/tmp/guix-build-glib-2.62.6.drv-0/build' MESON_TESTTHREADS='3'

1/259 glib:glib / array-test OK 0.61 s

--- command ---
02:17:17 G_DEBUG='gc-friendly' MALLOC_PERTURB_='115' G_TEST_BUILDDIR='/tmp/guix-build-glib-2.62.6.drv-0/build/glib/tests' G_TEST_SRCDIR='/tmp/guix-build-glib-2.62.6.drv-0/glib-2.62.6/glib/tests' MALLOC_CHECK_='2' /tmp/guix-build-glib-2.62.6.drv-0/build/glib/tests/array-test
--- stdout ---
# random seed: R02S791aefe4e2979bf442a7bfc0b77f2741
1..75
# Start of array tests
ok 1 /array/ref-count
ok 2 /array/clear-func
ok 3 /array/binary-search
# /array/copy-sized summary: Test that copying a newly-allocated sized array works.
ok 4 /array/copy-sized
# Start of new tests
ok 5 /array/new/zero-terminated
# End of new tests
# Start of set-size tests
ok 6 /array/set-size/non-zero-terminated-no-clear
ok 7 /array/set-size/non-zero-terminated-clear
ok 8 /array/set-size/zero-terminated-no-clear
ok 9 /array/set-size/zero-terminated-clear
# Start of sized tests
ok 10 /array/set-size/sized/non-zero-terminated-no-clear
ok 11 /array/set-size/sized/non-zero-terminated-clear
ok 12 /array/set-size/sized/zero-terminated-no-clear
ok 13 /array/set-size/sized/zero-terminated-clear
# End of sized tests
# End of set-size tests
# Start of append-val tests
ok 14 /array/append-val/non-zero-terminated-no-clear
ok 15 /array/append-val/non-zero-terminated-clear
ok 16 /array/append-val/zero-terminated-no-clear
ok 17 /array/append-val/zero-terminated-clear
# End of append-val tests
# Start of prepend-val tests
ok 18 /array/prepend-val/non-zero-terminated-no-clear
ok 19 /array/prepend-val/non-zero-terminated-clear
ok 20 /array/prepend-val/zero-terminated-no-clear
ok 21 /array/prepend-val/zero-terminated-clear
# End of prepend-val tests
# Start of prepend-vals tests
ok 22 /array/prepend-vals/non-zero-terminated-no-clear
ok 23 /array/prepend-vals/non-zero-terminated-clear
ok 24 /array/prepend-vals/zero-terminated-no-clear
ok 25 /array/prepend-vals/zero-terminated-clear
# End of prepend-vals tests
# Start of insert-vals tests
ok 26 /array/insert-vals/non-zero-terminated-no-clear
ok 27 /array/insert-vals/non-zero-terminated-clear
ok 28 /array/insert-vals/zero-terminated-no-clear
ok 29 /array/insert-vals/zero-terminated-clear
# End of insert-vals tests
# Start of remove-index tests
ok 30 /array/remove-index/non-zero-terminated-no-clear
ok 31 /array/remove-index/non-zero-terminated-clear
ok 32 /array/remove-index/zero-terminated-no-clear
ok 33 /array/remove-index/zero-terminated-clear
# End of remove-index tests
# Start of remove-index-fast tests
ok 34 /array/remove-index-fast/non-zero-terminated-no-clear
ok 35 /array/remove-index-fast/non-zero-terminated-clear
ok 36 /array/remove-index-fast/zero-terminated-no-clear
ok 37 /array/remove-index-fast/zero-terminated-clear
# End of remove-index-fast tests
# Start of remove-range tests
ok 38 /array/remove-range/non-zero-terminated-no-clear
ok 39 /array/remove-range/non-zero-terminated-clear
ok 40 /array/remove-range/zero-terminated-no-clear
ok 41 /array/remove-range/zero-terminated-clear
# End of remove-range tests
# Start of copy tests
ok 42 /array/copy/non-zero-terminated-no-clear
ok 43 /array/copy/non-zero-terminated-clear
ok 44 /array/copy/zero-terminated-no-clear
ok 45 /array/copy/zero-terminated-clear
# End of copy tests
# Start of sort tests
ok 46 /array/sort/non-zero-terminated-no-clear
ok 47 /array/sort/non-zero-terminated-clear
ok 48 /array/sort/zero-terminated-no-clear
ok 49 /array/sort/zero-terminated-clear
# End of sort tests
# Start of sort-with-data tests
ok 50 /array/sort-with-data/non-zero-terminated-no-clear
ok 51 /array/sort-with-data/non-zero-terminated-clear
ok 52 /array/sort-with-data/zero-terminated-no-clear
ok 53 /array/sort-with-data/zero-terminated-clear
# End of sort-with-data tests
# End of array tests
# Start of pointerarray tests
ok 54 /pointerarray/add
ok 55 /pointerarray/insert
ok 56 /pointerarray/ref-count
ok 57 /pointerarray/free-func
# /pointerarray/array_copy summary: Check all normal behaviour of stealing elements from one array to append to another, covering different array sizes and element copy functions
ok 58 /pointerarray/array_copy
ok 59 /pointerarray/array_extend
ok 60 /pointerarray/array_extend_and_steal
ok 61 /pointerarray/sort
ok 62 /pointerarray/sort-with-data
ok 63 /pointerarray/steal
# Start of find tests
ok 64 /pointerarray/find/empty
ok 65 /pointerarray/find/non-empty
# End of find tests
# End of pointerarray tests
# Start of bytearray tests
ok 66 /bytearray/append
ok 67 /bytearray/prepend
ok 68 /bytearray/remove
ok 69 /bytearray/remove-fast
ok 70 /bytearray/remove-range
ok 71 /bytearray/ref-count
ok 72 /bytearray/sort
ok 73 /bytearray/sort-with-data
ok 74 /bytearray/new-take
ok 75 /bytearray/free-to-bytes
# End of bytearray tests
-------

2/259 glib:glib / asyncqueue OK 0.60 s

--- command ---
02:17:17 G_DEBUG='gc-friendly' MALLOC_PERTURB_='115' G_TEST_BUILDDIR='/tmp/guix-build-glib-2.62.6.drv-0/build/glib/tests' G_TEST_SRCDIR='/tmp/guix-build-glib-2.62.6.drv-0/glib-2.62.6/glib/tests' MALLOC_CHECK_='2' /tmp/guix-build-glib-2.62.6.drv-0/build/glib/tests/asyncqueue
--- stdout ---
# random seed: R02S8adbee0969a6e0946d9e7d3eaf197071
1..6
# Start of asyncqueue tests
ok 1 /asyncqueue/sort
ok 2 /asyncqueue/destroy
ok 3 /asyncqueue/threads
ok 4 /asyncqueue/timed
ok 5 /asyncqueue/remove
ok 6 /asyncqueue/push_front
# End of asyncqueue tests
-------

3/259 glib:glib / atomic OK 2.33 s

--- command ---
02:17:17 G_DEBUG='gc-friendly' MALLOC_PERTURB_='115' G_TEST_BUILDDIR='/tmp/guix-build-glib-2.62.6.drv-0/build/glib/tests' G_TEST_SRCDIR='/tmp/guix-build-glib-2.62.6.drv-0/glib-2.62.6/glib/tests' MALLOC_CHECK_='2' /tmp/guix-build-glib-2.62.6.drv-0/build/glib/tests/atomic
--- stdout ---
# random seed: R02S3e7cfb21e5ce4ab121786f9782167006
1..2
# Start of atomic tests
ok 1 /atomic/types
ok 2 /atomic/threaded
# End of atomic tests
-------

4/259 glib:glib / base64 OK 0.13 s

--- command ---
02:17:18 G_DEBUG='gc-friendly' MALLOC_PERTURB_='115' G_TEST_BUILDDIR='/tmp/guix-build-glib-2.62.6.drv-0/build/glib/tests' G_TEST_SRCDIR='/tmp/guix-build-glib-2.62.6.drv-0/glib-2.62.6/glib/tests' MALLOC_CHECK_='2' /tmp/guix-build-glib-2.62.6.drv-0/build/glib/tests/base64
--- stdout ---
# random seed: R02S50f849fa71c72abd3c045912535b6548
1..28
# Start of base64 tests
ok 1 /base64/encode
ok 2 /base64/decode
ok 3 /base64/decode-inplace
ok 4 /base64/encode-decode
# Start of full tests
ok 5 /base64/full/1
ok 6 /base64/full/2
ok 7 /base64/full/3
ok 8 /base64/full/4
# End of full tests
# Start of encode tests
ok 9 /base64/encode/empty
# Start of incremental tests
# Start of small-block tests
ok 10 /base64/encode/incremental/small-block/1
ok 11 /base64/encode/incremental/small-block/2
ok 12 /base64/encode/incremental/small-block/3
ok 13 /base64/encode/incremental/small-block/4
# End of small-block tests
# End of incremental tests
# End of encode tests
# Start of incremental tests
# Start of nobreak tests
ok 14 /base64/incremental/nobreak/1
ok 15 /base64/incremental/nobreak/2
ok 16 /base64/incremental/nobreak/3
ok 17 /base64/incremental/nobreak/4-a
ok 18 /base64/incremental/nobreak/4-b
ok 19 /base64/incremental/nobreak/4-c
# End of nobreak tests
# Start of break tests
ok 20 /base64/incremental/break/1
ok 21 /base64/incremental/break/2
ok 22 /base64/incremental/break/3
# End of break tests
# Start of smallblock tests
ok 23 /base64/incremental/smallblock/1
ok 24 /base64/incremental/smallblock/2
ok 25 /base64/incremental/smallblock/3
ok 26 /base64/incremental/smallblock/4
# End of smallblock tests
# End of incremental tests
# Start of decode tests
ok 27 /base64/decode/empty
# End of decode tests
# Start of encode-decode tests
# Vector 0:
# Vector 1: f
# Vector 2: fo
# Vector 3: foo
# Vector 4: foob
# Vector 5: fooba
# Vector 6: foobar
ok 28 /base64/encode-decode/rfc4648
# End of encode-decode tests
# End of base64 tests
-------

5/259 glib:glib / bitlock OK 0.09 s

--- command ---
02:17:18 G_DEBUG='gc-friendly' MALLOC_PERTURB_='115' G_TEST_BUILDDIR='/tmp/guix-build-glib-2.62.6.drv-0/build/glib/tests' G_TEST_SRCDIR='/tmp/guix-build-glib-2.62.6.drv-0/glib-2.62.6/glib/tests' MALLOC_CHECK_='2' /tmp/guix-build-glib-2.62.6.drv-0/build/glib/tests/bitlock
--- stdout ---
# random seed: R02Se75f5250350bb5cde30ba613e8214ef0
1..0
-------

6/259 glib:glib / bookmarkfile OK 0.19 s

--- command ---
02:17:18 G_DEBUG='gc-friendly' MALLOC_PERTURB_='115' G_TEST_BUILDDIR='/tmp/guix-build-glib-2.62.6.drv-0/build/glib/tests' G_TEST_SRCDIR='/tmp/guix-build-glib-2.62.6.drv-0/glib-2.62.6/glib/tests' MALLOC_CHECK_='2' /tmp/guix-build-glib-2.62.6.drv-0/build/glib/tests/bookmarkfile
--- stdout ---
# random seed: R02S5ad149defb64e5d490789f2cf9820a51
1..48
# Start of bookmarks tests
ok 1 /bookmarks/load-from-data-dirs
ok 2 /bookmarks/to-file
ok 3 /bookmarks/move-item
ok 4 /bookmarks/misc
# Start of parse tests
ok 5 /bookmarks/parse/fail-24.xbel
ok 6 /bookmarks/parse/fail-27.xbel
ok 7 /bookmarks/parse/fail-13.xbel
ok 8 /bookmarks/parse/fail-41.xbel
ok 9 /bookmarks/parse/fail-11.xbel
ok 10 /bookmarks/parse/fail-20.xbel
ok 11 /bookmarks/parse/fail-16.xbel
ok 12 /bookmarks/parse/fail-08.xbel
ok 13 /bookmarks/parse/fail-03.xbel
ok 14 /bookmarks/parse/fail-40.xbel
ok 15 /bookmarks/parse/fail-30.xbel
ok 16 /bookmarks/parse/fail-36.xbel
ok 17 /bookmarks/parse/fail-22.xbel
ok 18 /bookmarks/parse/fail-33.xbel
ok 19 /bookmarks/parse/fail-38.xbel
ok 20 /bookmarks/parse/fail-34.xbel
ok 21 /bookmarks/parse/fail-28.xbel
ok 22 /bookmarks/parse/fail-39.xbel
ok 23 /bookmarks/parse/fail-32.xbel
ok 24 /bookmarks/parse/fail-29.xbel
ok 25 /bookmarks/parse/fail-14.xbel
ok 26 /bookmarks/parse/fail-21.xbel
ok 27 /bookmarks/parse/fail-37.xbel
ok 28 /bookmarks/parse/valid-03.xbel
ok 29 /bookmarks/parse/fail-23.xbel
ok 30 /bookmarks/parse/fail-26.xbel
ok 31 /bookmarks/parse/fail-12.xbel
ok 32 /bookmarks/parse/fail-09.xbel
ok 33 /bookmarks/parse/fail-19.xbel
ok 34 /bookmarks/parse/fail-17.xbel
ok 35 /bookmarks/parse/fail-18.xbel
ok 36 /bookmarks/parse/valid-01.xbel
ok 37 /bookmarks/parse/fail-07.xbel
ok 38 /bookmarks/parse/fail-10.xbel
ok 39 /bookmarks/parse/fail-04.xbel
ok 40 /bookmarks/parse/fail-35.xbel
ok 41 /bookmarks/parse/fail-02.xbel
ok 42 /bookmarks/parse/fail-25.xbel
ok 43 /bookmarks/parse/fail-15.xbel
ok 44 /bookmarks/parse/fail-05.xbel
ok 45 /bookmarks/parse/fail-31.xbel
ok 46 /bookmarks/parse/valid-02.xbel
ok 47 /bookmarks/parse/fail-06.xbel
ok 48 /bookmarks/parse/fail-01.xbel
# End of parse tests
# End of bookmarks tests
-------

7/259 glib:glib / bytes OK 0.15 s

--- command ---
02:17:18 G_DEBUG='gc-friendly' MALLOC_PERTURB_='115' G_TEST_BUILDDIR='/tmp/guix-build-glib-2.62.6.drv-0/build/glib/tests' G_TEST_SRCDIR='/tmp/guix-build-glib-2.62.6.drv-0/glib-2.62.6/glib/tests' MALLOC_CHECK_='2' /tmp/guix-build-glib-2.62.6.drv-0/build/glib/tests/bytes
--- stdout ---
# random seed: R02Se87f4a999a6efe0fcd65ad9b8820d38a
1..17
# Start of bytes tests
ok 1 /bytes/new
ok 2 /bytes/new-take
ok 3 /bytes/new-static
ok 4 /bytes/new-with-free-func
ok 5 /bytes/new-from-bytes
ok 6 /bytes/new-from-bytes-slice
ok 7 /bytes/new-from-bytes-shared-ref
ok 8 /bytes/hash
ok 9 /bytes/equal
ok 10 /bytes/compare
ok 11 /bytes/null
# Start of to-data tests
ok 12 /bytes/to-data/transfered
ok 13 /bytes/to-data/two-
This message was truncated. Download the full message here.
M
M
Mark H Weaver wrote on 28 Apr 2021 05:23
(address . 48024@debbugs.gnu.org)
871ravqeg1.fsf@netris.org
Hi,

Bone Baboon via Bug reports for GNU Guix <bug-guix@gnu.org> writes:
Toggle quote (4 lines)
> On an i686 computer when I run the command `sudo guix system
> --no-substitutes --cores=2 reconfigure configuration.scm` I get this
> error:

and in a later message:

Toggle quote (1 lines)
> 40/259 glib:glib / mutex TIMEOUT 60.04 s
[...]
Toggle quote (1 lines)
> 53/259 glib:glib / rec-mutex TIMEOUT 60.04 s
[...]
Toggle quote (1 lines)
> 58/259 glib:glib / rwlock TIMEOUT 60.03 s
[...]
Toggle quote (1 lines)
> 83/259 glib:glib / 1bit-mutex TIMEOUT 60.02 s
[...]
Toggle quote (2 lines)
> 84/259 glib:glib+slow / 1bit-emufutex TIMEOUT 180.03 s

I also build everything locally, and have sometimes run into problems
like this on my slower machines. Overly aggressive test timeouts,
chosen for powerful developer machines, are annoying.

The following patch, applied to your copy of Guix, should work around
the problem:

Toggle snippet (16 lines)
diff --git a/gnu/packages/glib.scm b/gnu/packages/glib.scm
index c04bd334e9..b8f509306d 100644
--- a/gnu/packages/glib.scm
+++ b/gnu/packages/glib.scm
@@ -230,7 +230,8 @@ shared NFS home directories.")
#t)))
;; TODO: Remove the conditional in the next core-updates cycle.
;; Needed to build glib on slower ARM nodes.
- ,@(if (string-prefix? "arm" (%current-system))
+ ,@(if (or (string-prefix? "arm" (%current-system))
+ (string-prefix? "i686" (%current-system)))
`((add-after 'unpack 'increase-test-timeout
(lambda _
(substitute* "meson.build"

To use this patch, you'll need to apply it to a Git checkout of Guix,
build it, and then use "/PATH-TO-GIT-CHECKOUT/pre-inst-env guix ..."
whenever building anything with Guix that depends on glib.
(Incidentally, I *always* use Guix this way, using my own private branch
of Guix, never using "guix pull", and never using substitutes.)

Alternatively, you *might* be able to build 'glib' successfully by not
doing anything else with your machine while it's building 'glib'. I
notice that in your original bug report, only the "1bit-mutex" test
timed out, but in your later build attempt, a total of 5 tests timed
out. These differing results suggest that you might have been running
other programs at the same time.

Regards,
Mark

--
Support Richard Stallman against the vicious disinformation campaign
against him and the FSF. See https://stallmansupport.org for more.
B
B
Bone Baboon wrote on 4 May 2021 00:00
(name . Mark H Weaver)(address . mhw@netris.org)
87fsz3jx58.fsf@disroot.org
Thank you for your helpful response.

Would a patch like this that addresses test timeouts be good to have in
the Guix repository? It would help other Guix users who also run into
test timeouts when building glib.

Mark H Weaver writes:
Toggle quote (4 lines)
> I also build everything locally, and have sometimes run into problems
> like this on my slower machines. Overly aggressive test timeouts,
> chosen for powerful developer machines, are annoying.

What are the benefits of aggressive test timeouts chosen for powerful
developer machines?

Toggle quote (24 lines)
> The following patch, applied to your copy of Guix, should work around
> the problem:
>
> --8<---------------cut here---------------start------------->8---
> diff --git a/gnu/packages/glib.scm b/gnu/packages/glib.scm
> index c04bd334e9..b8f509306d 100644
> --- a/gnu/packages/glib.scm
> +++ b/gnu/packages/glib.scm
> @@ -230,7 +230,8 @@ shared NFS home directories.")
> #t)))
> ;; TODO: Remove the conditional in the next core-updates cycle.
> ;; Needed to build glib on slower ARM nodes.
> - ,@(if (string-prefix? "arm" (%current-system))
> + ,@(if (or (string-prefix? "arm" (%current-system))
> + (string-prefix? "i686" (%current-system)))
> `((add-after 'unpack 'increase-test-timeout
> (lambda _
> (substitute* "meson.build"
> --8<---------------cut here---------------end--------------->8---
>
> To use this patch, you'll need to apply it to a Git checkout of Guix,
> build it, and then use "/PATH-TO-GIT-CHECKOUT/pre-inst-env guix ..."
> whenever building anything with Guix that depends on glib.

Preparation steps taken:
1) cloned the Guix repository
2) ran `./bootstrap`
3) ran `./configure --localstatedir=/var/`
4) checked out a branch
5) applied the patch

Then in the branch of the Guix repository with the patch applied I ran
the following commands which failed with test timeouts.

`./pre-inst-env guix build --no-substitutes glib`
`./pre-inst-env guix build --no-substitutes --cores=2 glib`
`./pre-inst-env guix build --no-substitutes --cores=3 glib`

Toggle quote (7 lines)
> Alternatively, you *might* be able to build 'glib' successfully by not
> doing anything else with your machine while it's building 'glib'. I
> notice that in your original bug report, only the "1bit-mutex" test
> timed out, but in your later build attempt, a total of 5 tests timed
> out. These differing results suggest that you might have been running
> other programs at the same time.

I tried this by having only ssh running so I could connect. Then on a
virtual terminal I ran `guix build --no-substitutes --cores=2 glib`.
This failed with test timeouts.

Toggle quote (3 lines)
> (Incidentally, I *always* use Guix this way, using my own private branch
> of Guix, never using "guix pull", and never using substitutes.)

This is interesting to me.

This is how I think a substitute server workflow could be modified to
use this approach. I would appreciate corrections or suggestions.

On the substitute server

Remove the official Guix substitute server from /etc/guix/acl.

Instead of: `guix pull --no-substitutes`
It would be: `git pull <official-guix-repo>` and merge the updated Guix
repository with the local patched repository.

Instead of: `guix build --no-substitues <package>`
It would be: `/<path-to-patched-repo>/pre-inst-env guix build <package>`

Instead of: `guix publish <options>`
It would be: `/<path-to-patched-repo>/pre-inst-env guix publish
<options>`

Instead of: `sudo guix system --no-substitutes reconfigure
<configuration>`
It would be: `sudo /<path-to-patched-repo>/pre-inst-env guix system
reconfigure <configuration>`

Substitute server clients would have a channel for the patched
repository and no channel for the official Guix repository.

The commands stay the same on the clients of the substitute server.

`guix pull --substitute-urls=<substitute-server-ip>:<port>`

`sudo guix system --subsitute-urls=<substitute-server-ip>:<port>
reconfigure <configuration>`
L
L
Leo Famulari wrote on 4 May 2021 02:38
(name . Bone Baboon via Bug reports for GNU Guix)(address . bug-guix@gnu.org)
YJCXfhX/DzNqXF2D@jasmine.lan
On Mon, May 03, 2021 at 06:00:19PM -0400, Bone Baboon via Bug reports for GNU Guix wrote:
Toggle quote (8 lines)
> Mark H Weaver writes:
> > I also build everything locally, and have sometimes run into problems
> > like this on my slower machines. Overly aggressive test timeouts,
> > chosen for powerful developer machines, are annoying.
>
> What are the benefits of aggressive test timeouts chosen for powerful
> developer machines?

I don't think it's a question of "benefits" as much as "worked on my
machine". Developers don't use slow machines and they've set these
timeouts accordingly.

We do relax the timeouts sometimes, based on reports like yours, because
Guix is a build-from-source distro at heart, and it should be possible
to use it on slow or old computers.
M
M
Mark H Weaver wrote on 4 May 2021 05:01
(name . Bone Baboon)(address . bone.baboon@disroot.org)
87h7jjnqw2.fsf@netris.org
Hi, [added Efraim Flashner to the CC list]

Bone Baboon <bone.baboon@disroot.org> writes:

Toggle quote (6 lines)
> Thank you for your helpful response.
>
> Would a patch like this that addresses test timeouts be good to have in
> the Guix repository? It would help other Guix users who also run into
> test timeouts when building glib.

Good question! The problem is that applying this patch would entail
rebuilding every package that depends on 'glib' for i686-linux, which is
likely on the order of thousands of packages. By policy, we don't make
changes that require so many rebuilds on our 'master' branch. Instead,
such changes must be made on 'core-updates', or possibly 'staging',
which are merged into 'master' a few times a year.

The plan seems to have been to remove the conditional on our
'core-updates' branch, so that the 'increase-test-timeout' phase would
be included on *all* architectures. See the comment above the code:


However, I see now that the 'increase-test-timeout' phase was recently
completely _removed_ by Efraim on our 'core-updates' branch a couple of
weeks ago, in the following commit:


Efraim: What was the rationale for removing that phase?

I think it would be good to keep that phase, for the benefit of users
building 'glib' on slower machines. I think the intent was to remove
the conditional, but to keep the body that's within the conditional.

What do you think?

Regards,
Mark

--
Disinformation flourishes because many people care deeply about injustice
but very few check the facts. Ask me about https://stallmansupport.org.
M
M
Mark H Weaver wrote on 4 May 2021 05:56
(name . Bone Baboon)(address . bone.baboon@disroot.org)
87eeennocl.fsf@netris.org
Hi,

Bone Baboon <bone.baboon@disroot.org> writes:

Toggle quote (32 lines)
> Mark H Weaver writes:
>> The following patch, applied to your copy of Guix, should work around
>> the problem:
>>
>> --8<---------------cut here---------------start------------->8---
>> diff --git a/gnu/packages/glib.scm b/gnu/packages/glib.scm
>> index c04bd334e9..b8f509306d 100644
>> --- a/gnu/packages/glib.scm
>> +++ b/gnu/packages/glib.scm
>> @@ -230,7 +230,8 @@ shared NFS home directories.")
>> #t)))
>> ;; TODO: Remove the conditional in the next core-updates cycle.
>> ;; Needed to build glib on slower ARM nodes.
>> - ,@(if (string-prefix? "arm" (%current-system))
>> + ,@(if (or (string-prefix? "arm" (%current-system))
>> + (string-prefix? "i686" (%current-system)))
>> `((add-after 'unpack 'increase-test-timeout
>> (lambda _
>> (substitute* "meson.build"
>> --8<---------------cut here---------------end--------------->8---
>>
>> To use this patch, you'll need to apply it to a Git checkout of Guix,
>> build it, and then use "/PATH-TO-GIT-CHECKOUT/pre-inst-env guix ..."
>> whenever building anything with Guix that depends on glib.
>
> Preparation steps taken:
> 1) cloned the Guix repository
> 2) ran `./bootstrap`
> 3) ran `./configure --localstatedir=/var/`
> 4) checked out a branch
> 5) applied the patch

Did you also run "make"?

Toggle quote (7 lines)
> Then in the branch of the Guix repository with the patch applied I ran
> the following commands which failed with test timeouts.
>
> `./pre-inst-env guix build --no-substitutes glib`
> `./pre-inst-env guix build --no-substitutes --cores=2 glib`
> `./pre-inst-env guix build --no-substitutes --cores=3 glib`

Hmm. Can you please grep the build log for "TIMEOUT" and
"increase-test-timeout", and show me the matching lines?

Toggle quote (7 lines)
>> Alternatively, you *might* be able to build 'glib' successfully by not
>> doing anything else with your machine while it's building 'glib'. [...]
>
> I tried this by having only ssh running so I could connect. Then on a
> virtual terminal I ran `guix build --no-substitutes --cores=2 glib`.
> This failed with test timeouts.

Oh well, thanks for trying.

Toggle quote (5 lines)
>> (Incidentally, I *always* use Guix this way, using my own private branch
>> of Guix, never using "guix pull", and never using substitutes.)
>
> This is interesting to me.

I outlined how I use Guix in the following message:


However, note that there are some significant caveats and "rough edges"
to this approach. I can't recommend it in good conscience, unless you
truly need the extreme flexibility that it provides.

To avoid the rough edges, I'd suggest using "guix pull --url" as
outlined in the last two paragraphs of the message above. For most
purposes, I suspect you'd be much happier with that approach.

Toggle quote (3 lines)
> This is how I think a substitute server workflow could be modified to
> use this approach. I would appreciate corrections or suggestions.

I'll postpone commenting on most of these, in case you decide to use the
"guix pull --url" method. A few comments though:

Toggle quote (3 lines)
> Substitute server clients would have a channel for the patched
> repository and no channel for the official Guix repository.

I've never used channels, and I'm not sure off-hand how to make them
work with my unusual approach.

Toggle quote (7 lines)
> The commands stay the same on the clients of the substitute server.
>
> `guix pull --substitute-urls=<substitute-server-ip>:<port>`
>
> `sudo guix system --subsitute-urls=<substitute-server-ip>:<port>
> reconfigure <configuration>`

This wouldn't work. It's not enough to merely ask 'guix' to use your
substitute server. If you did this, your clients would use the official
Guix package descriptions from our 'master' branch, but would look for
builds of those official packages on your substitute server.

To make this work, you would _also_ need to pass "--url <YOUR_GIT_REPO>"
each time you run 'guix pull' on your client machines.

Alternatively, if you chose to use my unusual approach, you'd need to
have built git checkouts of your custom branch of Guix on each of your
client machines, and run Guix from those git checkouts.

Regards,
Mark

--
Disinformation flourishes because many people care deeply about injustice
but very few check the facts. Ask me about https://stallmansupport.org.
E
E
Efraim Flashner wrote on 4 May 2021 08:18
(name . Mark H Weaver)(address . mhw@netris.org)
YJDnPqOFdCgf+f/d@3900XT
On Mon, May 03, 2021 at 11:01:22PM -0400, Mark H Weaver wrote:
Toggle quote (41 lines)
> Hi, [added Efraim Flashner to the CC list]
>
> Bone Baboon <bone.baboon@disroot.org> writes:
>
> > Thank you for your helpful response.
> >
> > Would a patch like this that addresses test timeouts be good to have in
> > the Guix repository? It would help other Guix users who also run into
> > test timeouts when building glib.
>
> Good question! The problem is that applying this patch would entail
> rebuilding every package that depends on 'glib' for i686-linux, which is
> likely on the order of thousands of packages. By policy, we don't make
> changes that require so many rebuilds on our 'master' branch. Instead,
> such changes must be made on 'core-updates', or possibly 'staging',
> which are merged into 'master' a few times a year.
>
> The plan seems to have been to remove the conditional on our
> 'core-updates' branch, so that the 'increase-test-timeout' phase would
> be included on *all* architectures. See the comment above the code:
>
> <https://git.sv.gnu.org/cgit/guix.git/tree/gnu/packages/glib.scm?id=b9fb13b28437a254683273094f189396a6e1421d#n231>
>
> However, I see now that the 'increase-test-timeout' phase was recently
> completely _removed_ by Efraim on our 'core-updates' branch a couple of
> weeks ago, in the following commit:
>
> <https://git.sv.gnu.org/cgit/guix.git/commit/?h=core-updates&id=a24562af52d2f318c9e17be73393ddb4bd9e347c>
>
> Efraim: What was the rationale for removing that phase?
>
> I think it would be good to keep that phase, for the benefit of users
> building 'glib' on slower machines. I think the intent was to remove
> the conditional, but to keep the body that's within the conditional.
>
> What do you think?
>
> Regards,
> Mark
>

As part of my powerpc efforts I built glib on my way to building ...
something. This is on an iBook G4 with the original 4200 RPM drive from
~15 years ago, so old hardware.

In glib-2.68 test_timeout and test_timeout_slow are set to 60 and 180
respectively. I initially merged the increase-test-timeout changes to
apply to all architectures, and then changed the time to 240 before
changing it to 1800 during my testing. I've attached the build log from
that round.

As I understand it, the tests which are are tagged '+slow' get the
test_timeout_slow property, with the test taking the longest on that
machine was glib:glib+slow / gvariant, at 65 seconds. By comparison, on
my Ryzen 3900XT machine it took 2.58 seconds. I figured even at double
that time it still fell within the 180 seconds given by default in the
test suite so it was likely safe to remove the substitution entirely.

I don't have other suitably slow hardware to test on, but I am building
it on my aarch64 board too, so I should be able to say in a day or two
if it works there.

--
Efraim Flashner <efraim@flashner.co.il> ????? ?????
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEoov0DD5VE3JmLRT3Qarn3Mo9g1EFAmCQ5zsACgkQQarn3Mo9
g1HA+Q//d7u3hCAX23ur+4c9Xa6dmtFBe8MxK/GqV5ueRf7et01bnxWUWqJYnLRK
uKhuFI5hv26cswIaT8Ua8w0LYyxygs4D0uTwySyvZLHp3c+En5RDwtyh+oRvJAmb
KSqZdDs2qaQE+7NJq0+quS8FRU/NNaa18TekytaTjEh0qRnQDc+wW8fywJZvu2Vt
V7ag+kP+KrAE+FAtxTuPLBsezrbNAhPD19jfmKxbF9599aIhJ3Zo7SgD2MYpcT3N
ht3/DfGGbdA2Wbyr24jPRNSFQigJ5ZE5f/WkQ3jn5r8b8jgmVsdmUnO7QYrkXbmG
AfdDGZwvre9FxV8s5AKSlYURFc3/j37k1A0ottFJDIOVy9JH7yuDE8Tv0kxAsqpd
S+AKcXzM7u94wWITz7uOG0etJU7Gnc3VyHNEgm6hnK3MBaGidXeV0iBrKjI6f8Qh
xvuVXq+Wl1tF6XebaUCJhVI7+RyFkjXzWKsXtCcUrW8epBowgj/56plszLu9yl/p
WRLBz3mGCZsD/2VJbccyDV3CMYLDZKTEb+vwo2LQ00HYlAw/dWvKwwCAQoFe0LVp
hsYUaDO7RH/wmOWRKEvQDtx0oMAcR+ZGsXPuG6QHOizOqqMHoFV9NNx82WCfHhVh
gsB8Ipu7Ohf80/6HXqQQmGcSEndOjEzw6/GGDxY7mZWM/C+wrqc=
=Xvn/
-----END PGP SIGNATURE-----


M
M
Mark H Weaver wrote on 4 May 2021 22:01
(name . Efraim Flashner)(address . efraim@flashner.co.il)
874kfinu7m.fsf@netris.org
Hi Efraim,

Efraim Flashner <efraim@flashner.co.il> writes:
Toggle quote (3 lines)
> In glib-2.68 test_timeout and test_timeout_slow are set to 60 and 180
> respectively.

Right. Unfortunately, these timeouts are too short for many slower
machines, such as 32-bit ARM systems. Bone Baboon has also recently
reported being unable to build 'glib' on a 32-bit i686 system due to
these timeouts, even when making extreme efforts to reduce load from
other processes.

Toggle quote (7 lines)
> As I understand it, the tests which are are tagged '+slow' get the
> test_timeout_slow property, with the test taking the longest on that
> machine was glib:glib+slow / gvariant, at 65 seconds. By comparison, on
> my Ryzen 3900XT machine it took 2.58 seconds. I figured even at double
> that time it still fell within the 180 seconds given by default in the
> test suite so it was likely safe to remove the substitution entirely.

I think that this recently-reported bug (https://bugs.gnu.org/48024)
demonstrates that we can't safely remove the substitution.

Toggle quote (4 lines)
> I don't have other suitably slow hardware to test on, but I am building
> it on my aarch64 board too, so I should be able to say in a day or two
> if it works there.

I don't see how a build test on your aarch64 board is relevant here.
As the comment above the 'increase-test-timeout' phase indicated, the
timeouts were increased for the sake of slower 32-bit ARM boards.

I think that we should re-introduce the 'increase-test-timeout' phase
for all systems on the 'core-updates' branch. Is there a disadvantage,
besides having to wait a couple more minutes if a test fails to
terminate?

What do you think?

Regards,
Mark

--
Disinformation flourishes because many people care deeply about injustice
but very few check the facts. Ask me about https://stallmansupport.org.
M
M
Mark H Weaver wrote on 4 May 2021 22:08
(name . Efraim Flashner)(address . efraim@flashner.co.il)
871ramntvx.fsf@netris.org
Earlier, I wrote:
Toggle quote (3 lines)
> I think that this recently-reported bug (https://bugs.gnu.org/48024)
> demonstrates that we can't safely remove the substitution.

To avoid having to scroll past the very long build log in the initial
bug report, it's probably best to read the bug report starting here:


Mark

--
Disinformation flourishes because many people care deeply about injustice
but very few check the facts. Ask me about https://stallmansupport.org.
B
B
Bone Baboon wrote on 5 May 2021 00:52
(name . Mark H Weaver)(address . mhw@netris.org)
877dkejenh.fsf@disroot.org
Mark H Weaver writes:
Toggle quote (6 lines)
> Right. Unfortunately, these timeouts are too short for many slower
> machines, such as 32-bit ARM systems. Bone Baboon has also recently
> reported being unable to build 'glib' on a 32-bit i686 system due to
> these timeouts, even when making extreme efforts to reduce load from
> other processes.

Here is information on the computer that is having tests timeout when
building glib.

* 4 GiB of RAM installed (the maximum)

* i686 32-bit 1 Core with 2.6 GHz
E
E
Efraim Flashner wrote on 5 May 2021 10:38
(name . Mark H Weaver)(address . mhw@netris.org)
YJJZatN6NQ6DzJn2@3900XT
On Tue, May 04, 2021 at 04:01:54PM -0400, Mark H Weaver wrote:
Toggle quote (32 lines)
> Hi Efraim,
>
> Efraim Flashner <efraim@flashner.co.il> writes:
> > In glib-2.68 test_timeout and test_timeout_slow are set to 60 and 180
> > respectively.
>
> Right. Unfortunately, these timeouts are too short for many slower
> machines, such as 32-bit ARM systems. Bone Baboon has also recently
> reported being unable to build 'glib' on a 32-bit i686 system due to
> these timeouts, even when making extreme efforts to reduce load from
> other processes.
>
> > As I understand it, the tests which are are tagged '+slow' get the
> > test_timeout_slow property, with the test taking the longest on that
> > machine was glib:glib+slow / gvariant, at 65 seconds. By comparison, on
> > my Ryzen 3900XT machine it took 2.58 seconds. I figured even at double
> > that time it still fell within the 180 seconds given by default in the
> > test suite so it was likely safe to remove the substitution entirely.
>
> I think that this recently-reported bug (<https://bugs.gnu.org/48024>)
> demonstrates that we can't safely remove the substitution.
>
> I think that we should re-introduce the 'increase-test-timeout' phase
> for all systems on the 'core-updates' branch. Is there a disadvantage,
> besides having to wait a couple more minutes if a test fails to
> terminate?
>
> What do you think?
>
> Regards,
> Mark

I looked closer at the bug report and I see they are timing out at 60
and 180 for Bone Baboon as they currently are.

Bone Baboon: Can you build the attached test-glib.scm file and send back
the build log? I want to make sure I change the timeout to something
long enough.

You can build it with 'guix build -f test-glib.scm'

--
Efraim Flashner <efraim@flashner.co.il> ????? ?????
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
; vim: set filetype=guix : (use-modules (gnu packages glib) (guix utils) (guix packages)) (package (inherit glib) (replacement #f) (arguments (substitute-keyword-arguments (package-arguments glib) ((#:phases phases) `(modify-phases ,phases (add-after 'unpack 'adjust-test-timeout (lambda _ (substitute* "meson.build" (("test_timeout = 60") "test_timeout = 600") (("test_timeout_slow = 120") "test_timeout_slow = 1200")) #t)))))))
-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEoov0DD5VE3JmLRT3Qarn3Mo9g1EFAmCSWWgACgkQQarn3Mo9
g1E1nxAAq1Z8m1B4n1Ysnt7sWci9E4Zgnod/VdEAqIaxOZvQZxY0G6hngHXI6ldt
OKIwJ4i3jEFnmOsbK01u+gnmk7Oo44IByl2/uMpQLbYCXvM7CYJOJ0zumSA/3dJK
TxL/mNoCK29gIsLwygrhbbCjRdWUbJMV22vjKUBgSjHVRDNnbjzgTLKLjbs9RdYd
upgaf03OwLCVMKxij0KvsoSt3gd3Sb0TLCGOiI9S/mkf8NMP32bOuoY0siZB7Kuc
mA9+AcSIJXFxxVoR1FCNfkGpBXUcjA85wxYOIUJ9o8YeCuBo4ntNW0kJi7GoDnBq
Aww3xjIg4N/Dl9K8Jz5M4Vn56+9o91qdbv/Pz0DbnwZ8rHIdav5erl9tpJIbfgHa
VS55UI3wc2RC1GJBA8SkR/10rxkDuKEBx1W/y3fHnfN9dxTFy3KmqLbJk9Si348y
m/9xBAo8NtGsrdHpa6piAOU7PkSsQ2c9R/wtBp5RPVg55pMolZe4dNpYKE2yIarh
Ex8sMJiqqubazK248mYmAiSMHm7Qr+Xvkl2WdMGZyhQK+GOYqxd8QIJybq/nA3px
VaUjdRALclzlfPOn0hC/pB0zp7MhBUu8TNpQSEGriYYp23moHKTAxDbw7Oxorl0P
5/aq9q1P8nrGq1E5BdUxV7c/UGGx48pY7ZB4Pz5W1mFJTbdSgdM=
=BxOY
-----END PGP SIGNATURE-----


B
B
Bone Baboon wrote on 5 May 2021 18:34
(name . Mark H Weaver)(address . mhw@netris.org)
87y2cti1gp.fsf@disroot.org
Mark H Weaver writes:
Toggle quote (2 lines)
> Did you also run "make"?

I have now.

Toggle quote (3 lines)
> Hmm. Can you please grep the build log for "TIMEOUT" and
> "increase-test-timeout", and show me the matching lines?

"increase-test-timeout":
```
starting phase `increase-test-timeout'
phase `increase-test-timeout' succeeded after 0.1 seconds
```

"TIMEOUT":
```
53/259 glib:glib / rec-mutex TIMEOUT 120.03 s
83/259 glib:glib / 1bit-mutex TIMEOUT 120.02 s
84/259 glib:glib+slow / 1bit-emufutex TIMEOUT 180.05 s
```

Attached is the build log.

Toggle quote (17 lines)
>>> (Incidentally, I *always* use Guix this way, using my own private branch
>>> of Guix, never using "guix pull", and never using substitutes.)
>>
>> This is interesting to me.
>
> I outlined how I use Guix in the following message:
>
> https://lists.gnu.org/archive/html/guix-devel/2021-03/msg00625.html
>
> However, note that there are some significant caveats and "rough edges"
> to this approach. I can't recommend it in good conscience, unless you
> truly need the extreme flexibility that it provides.
>
> To avoid the rough edges, I'd suggest using "guix pull --url" as
> outlined in the last two paragraphs of the message above. For most
> purposes, I suspect you'd be much happier with that approach.

Thank you for sharing this. Also thank you for the warning about 'significant caveats and "rough edges"'.

As a new user of Guix I think I will initially try to use the official
Guix repository.

However the message from Tobias Geerinckx-Rice in
https://issues.guix.gnu.org/48213gives me the idea that your flexible
approach could be very useful if I find myself in a situation where I
have an issue that will not be addressed by an upstream project and
that has too much of a maintenance burden for Guix maintainers to take
on.
B
B
Bone Baboon wrote on 5 May 2021 23:15
(name . Efraim Flashner)(address . efraim@flashner.co.il)
87v97wj319.fsf@disroot.org
Efraim Flashner writes:
Toggle quote (9 lines)
> I looked closer at the bug report and I see they are timing out at 60
> and 180 for Bone Baboon as they currently are.
>
> Bone Baboon: Can you build the attached test-glib.scm file and send back
> the build log? I want to make sure I change the timeout to something
> long enough.
>
> You can build it with 'guix build -f test-glib.scm'

I ran `guix build --file=test-glib.scm` and I was successful.

I was having trouble finding the build log.

I have instead attached the output of the build command.
Attachment: build-output.lz
M
M
Mark H Weaver wrote on 6 May 2021 02:20
87a6p8n24o.fsf@netris.org
Hi,

Bone Baboon <bone.baboon@disroot.org> writes:

Toggle quote (12 lines)
> Efraim Flashner writes:
>> I looked closer at the bug report and I see they are timing out at 60
>> and 180 for Bone Baboon as they currently are.
>>
>> Bone Baboon: Can you build the attached test-glib.scm file and send back
>> the build log? I want to make sure I change the timeout to something
>> long enough.
>>
>> You can build it with 'guix build -f test-glib.scm'
>
> I ran `guix build --file=test-glib.scm` and I was successful.

That's good news!

Toggle quote (2 lines)
> I was having trouble finding the build log.

Here's one way to find it:

$ cd /var/log/guix/drvs
$ ls -ltr */*-glib-2* | tail

The very small log files are the result of grafting derivations.
Look for the most recent one that's more than 1K.

Alternatively, it _might_ work to run:

$ guix build --log-file --file=test-glib.scm

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
Bone Baboon wrote on 6 May 2021 02:35
(name . Mark H Weaver)(address . mhw@netris.org)
87pmy4itrb.fsf@disroot.org
Mark H Weaver writes:
Toggle quote (14 lines)
>> I was having trouble finding the build log.
>
> Here's one way to find it:
>
> $ cd /var/log/guix/drvs
> $ ls -ltr */*-glib-2* | tail
>
> The very small log files are the result of grafting derivations.
> Look for the most recent one that's more than 1K.
>
> Alternatively, it _might_ work to run:
>
> $ guix build --log-file --file=test-glib.scm

Thank you this is helpful.
E
E
Efraim Flashner wrote on 6 May 2021 08:45
(name . Bone Baboon)(address . bone.baboon@disroot.org)
YJOQbHrljFx9KRbX@3900XT
On Wed, May 05, 2021 at 05:15:14PM -0400, Bone Baboon wrote:
Toggle quote (12 lines)
> Efraim Flashner writes:
> > I looked closer at the bug report and I see they are timing out at 60
> > and 180 for Bone Baboon as they currently are.
> >
> > Bone Baboon: Can you build the attached test-glib.scm file and send back
> > the build log? I want to make sure I change the timeout to something
> > long enough.
> >
> > You can build it with 'guix build -f test-glib.scm'
>
> I ran `guix build --file=test-glib.scm` and I was successful.

That was the plan. I bumped the test timeouts to high enough numbers so
that I could see how long it took.

Toggle quote (4 lines)
> I was having trouble finding the build log.
>
> I have instead attached the output of the build command.

It's perfect.

It looks like the two slowest are
83/259 glib:glib / 1bit-mutex OK 85.13 s
84/259 glib:glib+slow / 1bit-emufutex OK 89.22 s

I was thinking of just tripling the duration but test_timeout_slow would
likely have been missed since it was moved from 120 to 180, and
extracting the number so I could multiply it by 3 isn't really the most
readable and could leave the timeout near the edge. I've gone ahead and
multiplied it by 10, if a test would hang forever it's still killed and if
there's high load on a slow machine it should still pass.



--
Efraim Flashner <efraim@flashner.co.il> ????? ?????
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEoov0DD5VE3JmLRT3Qarn3Mo9g1EFAmCTkGwACgkQQarn3Mo9
g1HpjA//a00CjQKeXWsfEd+cndVh9a5gPNKZW1hJTWVEPbHjcPzvps3lx2JG1wP5
trFxhen3Z309XqXY+Nn3fC3WhOW99ZHqUm16tuGF8JHAfIO8DzVnCWy/3xmUv5az
kQl5bQWwA68gVMaet8/smZQcNSLD97UmfU1Wq1btYCyXmubQvJudc7cRFGnTHEjS
GowzDIKZp8fL38U07og6GOWhXkTvFUnUU2c9DEP2RKbMUHscoZmXVbXutuACmbpz
wSCjZksxLiZj6t9qbtV9a3m01FquOUGYMtjRzicG8lkt4nEVGfv7F57t2RVVQ1mw
tryy+Y7QnqWiPgnLbpbqpvjw8ogR5cy0lOFE9glq9Q0/nk/IKEUZzJHB+S9Vzgkm
AosXECDzw5rxfslTDj8USpvJ/WYQJ/DsaZ0IczRM1+EKk+W5aDSyocG+wLQLoKHN
oRHBPnbsFSHArHgCAK/OCClqDWlX1YoapgUoe42BcPhAy9g5ocMMfby37vKjdCPf
Lzr9WCz4ZaTU0dgZaBabgP3qIrL35ZKjs93b5shRIK6E8OMJwzclsKujemyDwB+q
JwimZGGh2yw3KouQHxnCNjCaRO8jmacp2IDDeh8+QjnOiVvl+0IJaZ/++MQJQmHU
uNCJT2OCOd6zHp5WvPQXJOmQjKIiw9Nxf8Ck6MMjIrioDASa/5w=
=WswS
-----END PGP SIGNATURE-----


M
M
Mark H Weaver wrote on 6 May 2021 10:46
(name . Bone Baboon)(address . bone.baboon@disroot.org)
877dkcmeqa.fsf@netris.org
Hi,

Bone Baboon <bone.baboon@disroot.org> writes:

Toggle quote (3 lines)
> Thank you for sharing this. Also thank you for the warning about
> 'significant caveats and "rough edges"'.

The "rough edges" could surely be smoothed out with some effort. I
haven't been motivated to work on it, partly because until recently,
I've felt quite alone in my preference for using Guix in this way.
However, you are now the second person to express interest in this in
the last couple of months.

Toggle quote (3 lines)
> As a new user of Guix I think I will initially try to use the official
> Guix repository.

That's probably best for now, at least until you have a compelling
reason to do otherwise.

Toggle quote (7 lines)
> However the message from Tobias Geerinckx-Rice in
> https://issues.guix.gnu.org/48213 gives me the idea that your flexible
> approach could be very useful if I find myself in a situation where I
> have an issue that will not be addressed by an upstream project and
> that has too much of a maintenance burden for Guix maintainers to take
> on.

Yes, it enables one to exercise an extraordinary amount of individual
control over one's system, while still benefitting from the work of the
larger Guix community. Several of the commits on my private branch are
reversions of upstream changes in Guix that I disagreed with.

One more important note: regardless of whether you run Guix from a git
checkout or use the official 'master' branch, if you build everything
locally, then it's important to pass "--gc-keep-derivations=yes" and
"--gc-keep-outputs=yes" to the Guix daemon.

Those flags change the way the Guix garbage collector operates, such
that more store items are retained. I've forgotten the precise details,
but roughly, these flags cause not only the run-time requirements of the
currently-installed software to be retained, but also the *build*
requirements of that software. Without these flags, "guix gc" will
delete far too much, and you'll likely end up having to rebuild a great
many packages that are needed at build time only.

I have something close to this in the 'services' field of my OS config:

Toggle snippet (12 lines)
(modify-services %desktop-services
(guix-service-type config =>
(guix-configuration
(inherit config)
(use-substitutes? #f)
(authorize-key? #f)
(authorized-keys '())
(substitute-urls '())
(extra-options '("--gc-keep-derivations=yes"
"--gc-keep-outputs=yes")))))

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
Bengt Richter wrote on 6 May 2021 11:06
20210506090616.GA2528@LionPure
Hi,

On +2021-05-06 09:45:00 +0300, Efraim Flashner wrote:
Toggle quote (34 lines)
> On Wed, May 05, 2021 at 05:15:14PM -0400, Bone Baboon wrote:
> > Efraim Flashner writes:
> > > I looked closer at the bug report and I see they are timing out at 60
> > > and 180 for Bone Baboon as they currently are.
> > >
> > > Bone Baboon: Can you build the attached test-glib.scm file and send back
> > > the build log? I want to make sure I change the timeout to something
> > > long enough.
> > >
> > > You can build it with 'guix build -f test-glib.scm'
> >
> > I ran `guix build --file=test-glib.scm` and I was successful.
>
> That was the plan. I bumped the test timeouts to high enough numbers so
> that I could see how long it took.
>
> > I was having trouble finding the build log.
> >
> > I have instead attached the output of the build command.
>
> It's perfect.
>
> It looks like the two slowest are
> 83/259 glib:glib / 1bit-mutex OK 85.13 s
> 84/259 glib:glib+slow / 1bit-emufutex OK 89.22 s
>
> I was thinking of just tripling the duration but test_timeout_slow would
> likely have been missed since it was moved from 120 to 180, and
> extracting the number so I could multiply it by 3 isn't really the most
> readable and could leave the timeout near the edge. I've gone ahead and
> multiplied it by 10, if a test would hang forever it's still killed and if
> there's high load on a slow machine it should still pass.
>

Couldn't autoconf emit some config info that test scripts could use
to run with appropriate timeouts and memory sizes etc?

Maybe with access similar to pkg-config?

Seems like someone must have thought of scratching that itch?

Toggle quote (7 lines)
>
>
> --
> Efraim Flashner <efraim@flashner.co.il> ????? ?????
> GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
> Confidentiality cannot be guaranteed on emails sent or received unencrypted

--
Regards,
Bengt Richter
B
B
Bone Baboon wrote on 6 May 2021 19:44
(name . Efraim Flashner)(address . efraim@flashner.co.il)
87r1ijhi4w.fsf@disroot.org
Efraim Flashner writes:
Toggle quote (11 lines)
>> > Bone Baboon: Can you build the attached test-glib.scm file and send back
>> > the build log? I want to make sure I change the timeout to something
>> > long enough.
>> >
>> > You can build it with 'guix build -f test-glib.scm'
>>
>> I ran `guix build --file=test-glib.scm` and I was successful.
>
> That was the plan. I bumped the test timeouts to high enough numbers so
> that I could see how long it took.

Thank you.

I can build glib with `guix build --no-subsitutes --file=test-glib.scm`.
How can I use the glib I have built in a system configuration while this
fix or a variation of it makes it's way into the Guix master branch?
B
B
Bone Baboon wrote on 6 May 2021 21:36
(name . Mark H Weaver)(address . mhw@netris.org)
87o8dnhcx8.fsf@disroot.org
Mark H Weaver writes:
Toggle quote (28 lines)
> One more important note: regardless of whether you run Guix from a git
> checkout or use the official 'master' branch, if you build everything
> locally, then it's important to pass "--gc-keep-derivations=yes" and
> "--gc-keep-outputs=yes" to the Guix daemon.
>
> Those flags change the way the Guix garbage collector operates, such
> that more store items are retained. I've forgotten the precise details,
> but roughly, these flags cause not only the run-time requirements of the
> currently-installed software to be retained, but also the *build*
> requirements of that software. Without these flags, "guix gc" will
> delete far too much, and you'll likely end up having to rebuild a great
> many packages that are needed at build time only.
>
> I have something close to this in the 'services' field of my OS config:
>
> --8<---------------cut here---------------start------------->8---
> (modify-services %desktop-services
> (guix-service-type config =>
> (guix-configuration
> (inherit config)
> (use-substitutes? #f)
> (authorize-key? #f)
> (authorized-keys '())
> (substitute-urls '())
> (extra-options '("--gc-keep-derivations=yes"
> "--gc-keep-outputs=yes")))))
> --8<---------------cut here---------------end--------------->8---

Thank you for sharing this.
M
M
Mark H Weaver wrote on 7 May 2021 19:46
87tunel9mt.fsf@netris.org
Hi,

Bone Baboon <bone.baboon@disroot.org> writes:
Toggle quote (3 lines)
> How can I use the glib I have built in a system configuration while this
> fix or a variation of it makes it's way into the Guix master branch?

I guess that you'll need to set up a personal branch of Guix, like I do,
with a patch applied to the 'glib' package, and another patch applied to
'inetutils' (referring to https://bugs.gnu.org/48214#35).

My recommendation, for now, would be to do this:

(1) Set up your own git repository, with a personal branch that's the
same as our official 'master' branch plus the additional patches
that you need, and to periodically rebase this branch on top of our
'master' branch.

(2) On all of your systems that need these customizations, pass the
"--url=URL" and "--branch=BRANCH" options to "guix pull", each time
you use that command.

There _might_ be a nicer way to set this up using channels, but I've
never used channels and am mostly ignorant of them. Maybe someone else
can chime in on that point.

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
Bengt Richter wrote on 8 May 2021 15:26
(name . Mark H Weaver)(address . mhw@netris.org)
20210508132643.GA12344@LionPure
Hi Mark,

tl;dr -- would you by chance have a mhw-bootstrap.sh that could clone
your set-up of a private git repo to use the way you often mention doing?

I am interested in doing it your way ;)

IIRC, Pjotr wrote extensive notes on how to build starting with a git clone,
but ended up advising against doing it unless there was no other way.

Any tips appreciated :)
TIA.

On +2021-05-07 13:46:07 -0400, Mark H Weaver wrote:
Toggle quote (35 lines)
> Hi,
>
> Bone Baboon <bone.baboon@disroot.org> writes:
> > How can I use the glib I have built in a system configuration while this
> > fix or a variation of it makes it's way into the Guix master branch?
>
> I guess that you'll need to set up a personal branch of Guix, like I do,
> with a patch applied to the 'glib' package, and another patch applied to
> 'inetutils' (referring to <https://bugs.gnu.org/48214#35>).
>
> My recommendation, for now, would be to do this:
>
> (1) Set up your own git repository, with a personal branch that's the
> same as our official 'master' branch plus the additional patches
> that you need, and to periodically rebase this branch on top of our
> 'master' branch.
>
> (2) On all of your systems that need these customizations, pass the
> "--url=URL" and "--branch=BRANCH" options to "guix pull", each time
> you use that command.
>
> There _might_ be a nicer way to set this up using channels, but I've
> never used channels and am mostly ignorant of them. Maybe someone else
> can chime in on that point.
>
> Regards,
> Mark
>
> --
> Disinformation flourishes because many people care deeply about injustice
> but very few check the facts. Ask me about <https://stallmansupport.org>.
>
>
>

--
Regards,
Bengt Richter
M
M
Maxim Cournoyer wrote on 18 Mar 2022 03:26
(name . Efraim Flashner)(address . efraim@flashner.co.il)
87tubw6lok.fsf@gmail.com
Hello,

Efraim Flashner <efraim@flashner.co.il> writes:

Toggle quote (33 lines)
> On Wed, May 05, 2021 at 05:15:14PM -0400, Bone Baboon wrote:
>> Efraim Flashner writes:
>> > I looked closer at the bug report and I see they are timing out at 60
>> > and 180 for Bone Baboon as they currently are.
>> >
>> > Bone Baboon: Can you build the attached test-glib.scm file and send back
>> > the build log? I want to make sure I change the timeout to something
>> > long enough.
>> >
>> > You can build it with 'guix build -f test-glib.scm'
>>
>> I ran `guix build --file=test-glib.scm` and I was successful.
>
> That was the plan. I bumped the test timeouts to high enough numbers so
> that I could see how long it took.
>
>> I was having trouble finding the build log.
>>
>> I have instead attached the output of the build command.
>
> It's perfect.
>
> It looks like the two slowest are
> 83/259 glib:glib / 1bit-mutex OK 85.13 s
> 84/259 glib:glib+slow / 1bit-emufutex OK 89.22 s
>
> I was thinking of just tripling the duration but test_timeout_slow would
> likely have been missed since it was moved from 120 to 180, and
> extracting the number so I could multiply it by 3 isn't really the most
> readable and could leave the timeout near the edge. I've gone ahead and
> multiplied it by 10, if a test would hang forever it's still killed and if
> there's high load on a slow machine it should still pass.

It seems a similar change was made in commit
7b7bc91c3d7fba306884cd1681d12b51246c2aea, around the time it was
discussed.

Closing!

Thanks,

Maxim
Closed
?
Your comment

This issue is archived.

To comment on this conversation send an email to 48024@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 48024
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch