public inbox for nightly-builds@lists.ipfire.org
 help / color / mirror / Atom feed
From: IPFire Nightly Builder <nightly-builds@ipfire.org>
To: nightly-builds@lists.ipfire.org
Subject: [FAILED] Nightly Build of next (ede29dd) for aarch64 on arm64-01.dub.ipfire.org
Date: Mon, 05 Jul 2021 10:00:42 +0000	[thread overview]
Message-ID: <4GJLmB2b3hz1yWq@arm64-01.dub.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2504 bytes --]

https://nightly.ipfire.org/next/2021-07-05%2007%3A45%3A43%20%2B0200-ede29dd5/aarch64

commit ede29dd5564bf370735045135289f764bbac8150
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date:   Mon Jul 5 07:45:43 2021 +0200

    core159: started
    
    this update is based on core-kerneltest in arne_f/kernel-5.10
    
    Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>

https://git.ipfire.org/?p=ipfire-2.x.git;a=shortlog;h=ede29dd5564bf370735045135289f764bbac8150

Packaged toolchain compilation                                          

    Jul  5 10:00:41: Building wpa_supplicant hostapd-581dfcc.tar.gz checksum OK
    hostapd-581dfcc.tar.gz checksum OK
    Jul  5 10:00:41: Building w_scan w_scan-20170107.tar.bz2 checksum OK
    w_scan-20170107.tar.bz2 checksum OK
    Jul  5 10:00:41: Building xfsprogs xfsprogs-5.12.0.tar.xz checksum OK
    xfsprogs-5.12.0.tar.xz checksum OK
    Jul  5 10:00:41: Building xinetd xinetd-2.3.15.tar.gz checksum OK
    xinetd-2.3.15.tar.gz checksum OK
    Jul  5 10:00:41: Building XML-Parser XML-Parser-2.46.tar.gz checksum OK
    XML-Parser-2.46.tar.gz checksum OK
    Jul  5 10:00:41: Building xr819-firmware xr819-firmware-c01.08.0043.tar.xz checksum OK
    xr819-firmware-c01.08.0043.tar.xz checksum OK
    Jul  5 10:00:41: Building xtables-addons xtables-addons-3.13.tar.xz checksum OK
    xtables-addons-3.13.tar.xz checksum OK
    Jul  5 10:00:41: Building xvid xvidcore-1.3.7.tar.gz checksum OK
    xvidcore-1.3.7.tar.gz checksum OK
    Jul  5 10:00:41: Building xz xz-5.2.5.tar.xz checksum OK
    xz-5.2.5.tar.xz checksum OK
    Jul  5 10:00:41: Building yaml yaml-0.2.5.tar.gz checksum OK
    yaml-0.2.5.tar.gz checksum OK
    Jul  5 10:00:41: Building zabbix_agentd zabbix-4.2.6.tar.gz checksum OK
    zabbix-4.2.6.tar.gz checksum OK
    Jul  5 10:00:41: Building zd1211-firmware zd1211-firmware-1.5.tar.bz2 checksum OK
    zd1211-firmware-1.5.tar.bz2 checksum OK
    Jul  5 10:00:41: Building zerofree zerofree-1.1.1.tgz checksum OK
    zerofree-1.1.1.tgz checksum OK
    Jul  5 10:00:41: Building zlib zlib-1.2.11.tar.gz checksum OK
    zlib-1.2.11.tar.gz checksum OK
    Jul  5 10:00:41: Building zstd zstd-1.5.0.tar.gz checksum OK
    zstd-1.5.0.tar.gz checksum OK

ERROR: /build/nightly/next/cache/toolchains/ipfire-2.25-toolchain-20210701-aarch64 md5 did not match, check downloaded package[ FAIL ]
    Check /build/nightly/next/log/_build.preparation.log for errors if applicable[ FAIL ]

             reply	other threads:[~2021-07-05 10:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-05 10:00 IPFire Nightly Builder [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-07-05  9:00 IPFire Nightly Builder
2021-07-05  8:00 IPFire Nightly Builder
2021-07-05  7:00 IPFire Nightly Builder
2021-07-05  6:00 IPFire Nightly Builder

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4GJLmB2b3hz1yWq@arm64-01.dub.ipfire.org \
    --to=nightly-builds@ipfire.org \
    --cc=nightly-builds@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox