flathub.org/builds keeps failing to download LibreOffice sources
Stephan Bergmann
sbergman at redhat.com
Fri Oct 15 12:55:26 UTC 2021
I don't know about any better channel to report issues with the Flathub
build service:
Recently, attempts to build LibreOffice on Flathub keep failing to
download the sources, hitting a one hour timeout, blocking my attempt to
publish the latest LibreOffice 7.2.2 there. My most recent attempt is
<https://flathub.org/builds/#/builders/32/builds/63660>, its download
logs
(<https://flathub.org/builds/#/builders/27/builds/62495/steps/3/logs/stdio>)
are
> timeout 1h flatpak-builder --download-only --no-shallow-clone --allow-missing-runtimes --state-dir=/srv/buildbot/sources /srv/buildbot/sources/.builddir org.libreoffice.LibreOffice.json
> in dir /srv/buildbot/worker/download-sources/build (timeout 3600 secs)
> watching logfiles {}
> argv: [b'timeout', b'1h', b'flatpak-builder', b'--download-only', b'--no-shallow-clone', b'--allow-missing-runtimes', b'--state-dir=/srv/buildbot/sources', b'/srv/buildbot/sources/.builddir', b'org.libreoffice.LibreOffice.json']
> using PTY: True
> error: org.freedesktop.Sdk/x86_64/21.08 not installed
> error: org.freedesktop.Sdk/x86_64/21.08 not installed
> error: org.freedesktop.Platform/x86_64/21.08 not installed
> Downloading sources
> ]2;flatpak-builder: Downloading gvfs]2;flatpak-builder: Downloading krb5]2;flatpak-builder: Downloading libreofficehint: Using 'master' as the name for the initial branch. This default branch name
> hint: is subject to change. To configure the initial branch name to use in all
> hint: of your new repositories, which will suppress this warning, call:
> hint:
> hint: git config --global init.defaultBranch <name>
> hint:
> hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
> hint: 'development'. The just-created branch can be renamed via this command:
> hint:
> hint: git branch -m <name>
> Initialized empty Git repository in /srv/buildbot/sources/git/https_gerrit.libreoffice.org_core-XA0IB1/
> Fetching full git repo https://gerrit.libreoffice.org/core
> remote: Counting objects: 1
> remote: Counting objects: 40076
> remote: Counting objects: 74126
[...]
> remote: Counting objects: 2923369
> remote: Counting objects: 2932081
> remote: Counting objects: 2936442, done
> remote: Finding sources: 1% (29352/2935177)
> remote: Finding sources: 2% (58704/2935177)
> remote: Finding sources: 3% (88056/2935177)
[...]
> remote: Finding sources: 99% (2933401/2935177)
> remote: Finding sources: 100% (2935177/2935177)
> remote: Finding sources: 100% (2935177/2935177)
> Receiving objects: 0% (1/8584239)
> Receiving objects: 0% (198/8584239), 67.99 KiB | 100.00 KiB/s
> Receiving objects: 0% (387/8584239), 131.97 KiB | 106.00 KiB/s
> Receiving objects: 0% (966/8584239), 259.93 KiB | 130.00 KiB/s
[...]
> Receiving objects: 33% (2846560/8584239), 893.90 MiB | 295.00 KiB/s
> Receiving objects: 33% (2847213/8584239), 894.28 MiB | 306.00 KiB/s
> Receiving objects: 33% (2847541/8584239), 894.47 MiB | 304.00 KiB/s
> program finished with exit code 124
> elapsedTime=3600.095223
> Receiving objects: 33% (2848734/8584239), 894.90 MiB | 301.00 KiB/s
Whereas, when I do a local `flatpak-builder --verbose output
org.libreoffice.LibreOffice.json` (against the same
<https://github.com/flathub/org.libreoffice.LibreOffice/commit/a56252916d581fb213351b1b319137eb975c76dc>
"Lets see if 'tag' works better than 'branch'" with flatpak-builder
1.0.14 (on Fedora 34), the output starts with
> FB: Running: git config --get user.email
> FB: Running: git config --get user.name
> FB: Running: flatpak info --arch=x86_64 --show-commit org.freedesktop.Sdk 21.08
> FB: Running: flatpak info --show-location --arch=x86_64 org.freedesktop.Sdk 21.08
> FB: Running: flatpak info --arch=x86_64 --show-commit org.freedesktop.Platform 21.08
> Downloading sources
> Downloading https://download.gnome.org/sources/gvfs/1.38/gvfs-1.38.1.tar.xz
> % Total % Received % Xferd Average Speed Time Time Time Current
> Dload Upload Total Spent Left Speed
> 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
> 100 1175k 100 1175k 0 0 1143k 0 0:00:01 0:00:01 --:--:-- 3460k
> Downloading https://kerberos.org/dist/krb5/1.16/krb5-1.16.2.tar.gz
> 100 9426k 100 9426k 0 0 2460k 0 0:00:03 0:00:03 --:--:-- 3092k
> FB: Running: git --version
> FB: Git version: 2.31.1.0
> FB: Running: git init --bare /data/sbergman/github.com/flathub/org.libreoffice.LibreOffice/.flatpak-builder/git/https_gerrit.libreoffice.org_core-ANC3A1
> hint: Using 'master' as the name for the initial branch. This default branch name
> hint: is subject to change. To configure the initial branch name to use in all
> hint: of your new repositories, which will suppress this warning, call:
> hint:
> hint: git config --global init.defaultBranch <name>
> hint:
> hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
> hint: 'development'. The just-created branch can be renamed via this command:
> hint:
> hint: git branch -m <name>
> Initialized empty Git repository in /data/sbergman/github.com/flathub/org.libreoffice.LibreOffice/.flatpak-builder/git/https_gerrit.libreoffice.org_core-ANC3A1/
> FB: Running: git remote add --mirror=fetch origin https://gerrit.libreoffice.org/core
> FB: Running: git cat-file -e libreoffice-7.2.2.2
> FB: Running: git ls-remote origin
> FB: Running: git config transfer.fsckObjects 0
> Fetching git repo https://gerrit.libreoffice.org/core, ref refs/tags/libreoffice-7.2.2.2
> FB: Running: git fetch -p --no-recurse-submodules --depth=1 -f origin '+refs/tags/libreoffice-7.2.2.2:refs/tags/libreoffice-7.2.2.2'
> remote: Counting objects: 122674, done
> remote: Finding sources: 100% (122674/122674)
> Reiving objects: 10% (12268/122674), 19.12 MiB | 927.00 KiB/s
That is, while Flathub does a "Fetching full git repo", my local build
is able to do a more targeted `git fetch --depth=1` of just the
specified tag, which succeeds in substantially less than one hour.
Is there anybody who could look into this issue?
(What also puzzles me is that builds like
<https://flathub.org/builds/#/builders/32/builds/63660> keep progressing
to the "Build all platforms" step even if the "Download sources" step
has failed.)
More information about the Flatpak
mailing list