From: IPFire Nightly Builder <nightly-builds@ipfire.org>
To: nightly-builds@lists.ipfire.org
Subject: [FAILED] Nightly Build of master (db7ef52) for armv6l on arm64-02.dub.ipfire.org
Date: Fri, 09 Jul 2021 23:00:08 +0000 [thread overview]
Message-ID: <4GM7sh5J31z603l@arm64-02.dub.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 607 bytes --]
https://nightly.ipfire.org/master/2021-07-09%2015%3A24%3A33%20%2B0000-db7ef52a/armv6l
commit db7ef52a91e925a5097d064ebea6723d035e28e8
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Fri Jul 9 15:24:33 2021 +0000
core158: Run sshctrl
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
https://git.ipfire.org/?p=ipfire-2.x.git;a=shortlog;h=db7ef52a91e925a5097d064ebea6723d035e28e8
ERROR: Cannot build for architure armv6l [ FAIL ]
Check /build/nightly/master/log/_build.preparation.log for errors if applicable[ FAIL ]
next reply other threads:[~2021-07-09 23:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-09 23:00 IPFire Nightly Builder [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-07-10 15:06 IPFire Nightly Builder
2021-07-10 14:47 IPFire Nightly Builder
2021-07-10 14:00 IPFire Nightly Builder
2021-07-10 13:00 IPFire Nightly Builder
2021-07-10 12:00 IPFire Nightly Builder
2021-07-10 11:00 IPFire Nightly Builder
2021-07-10 10:00 IPFire Nightly Builder
2021-07-10 9:00 IPFire Nightly Builder
2021-07-10 8:00 IPFire Nightly Builder
2021-07-10 7:00 IPFire Nightly Builder
2021-07-10 6:00 IPFire Nightly Builder
2021-07-10 5:00 IPFire Nightly Builder
2021-07-10 4:00 IPFire Nightly Builder
2021-07-10 3:00 IPFire Nightly Builder
2021-07-10 2:00 IPFire Nightly Builder
2021-07-10 1:00 IPFire Nightly Builder
2021-07-10 0:00 IPFire Nightly Builder
2021-07-09 22:00 IPFire Nightly Builder
2021-07-09 21: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=4GM7sh5J31z603l@arm64-02.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