From: Build bot for Mark Brown <broonie@kernel.org>
To: kernel-build-reports@lists.linaro.org,
linaro-kernel@lists.linaro.org, stable@vger.kernel.org
Subject: v4.9.95 build: 11 failures 0 warnings (v4.9.95)
Date: Fri, 20 Apr 2018 07:41:11 +0100 [thread overview]
Message-ID: <E1f9PjL-0007vL-9K@optimist> (raw)
Tree/Branch: v4.9.95
Git describe: v4.9.95
Commit: eedaf21fb3 Linux 4.9.95
Build Time: 0 min 26 sec
Passed: 0 / 11 ( 0.00 %)
Failed: 11 / 11 (100.00 %)
Errors: 1
Warnings: 0
Section Mismatches: 0
Failed defconfigs:
arm-allnoconfig
arm64-defconfig
Errors:
arm-allnoconfig
collect2: error: ld returned 1 exit status
arm64-defconfig
collect2: error: ld returned 1 exit status
-------------------------------------------------------------------------------
defconfigs with issues (other than build errors):
-------------------------------------------------------------------------------
Errors summary: 1
2 collect2: error: ld returned 1 exit status
===============================================================================
Detailed per-defconfig build reports below:
-------------------------------------------------------------------------------
arm-allnoconfig : FAIL, 1 errors, 0 warnings, 0 section mismatches
Errors:
collect2: error: ld returned 1 exit status
-------------------------------------------------------------------------------
arm64-defconfig : FAIL, 1 errors, 0 warnings, 0 section mismatches
Errors:
collect2: error: ld returned 1 exit status
-------------------------------------------------------------------------------
Passed with no errors, warnings or mismatches:
arm64-allnoconfig
arm64-allmodconfig
arm-multi_v5_defconfig
arm-multi_v7_defconfig
x86_64-defconfig
arm-allmodconfig
arm-multi_v4t_defconfig
x86_64-allnoconfig
x86_64-allmodconfig
close failed in file object destructor:
sys.excepthook is missing
lost sys.stderr
next reply other threads:[~2018-04-20 6:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-20 6:41 Build bot for Mark Brown [this message]
2018-04-20 6:46 ` v4.9.95 build: 11 failures 0 warnings (v4.9.95) Greg KH
2018-04-20 11:43 ` Mark Brown
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=E1f9PjL-0007vL-9K@optimist \
--to=broonie@kernel.org \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=stable@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).