From: Greg KH <greg@kroah.com>
To: Build bot for Mark Brown <broonie@kernel.org>
Cc: kernel-build-reports@lists.linaro.org,
linaro-kernel@lists.linaro.org, stable@vger.kernel.org
Subject: Re: v4.15.10 build: 2 failures 0 warnings (v4.15.10)
Date: Fri, 16 Mar 2018 09:02:31 +0100 [thread overview]
Message-ID: <20180316080231.GA13244@kroah.com> (raw)
In-Reply-To: <E1ewXt8-0003n4-KC@optimist>
On Thu, Mar 15, 2018 at 06:46:06PM +0000, Build bot for Mark Brown wrote:
> Tree/Branch: v4.15.10
> Git describe: v4.15.10
> Commit: df57458873 Linux 4.15.10
>
> Build Time: 86 min 3 sec
>
> Passed: 7 / 9 ( 77.78 %)
> Failed: 2 / 9 ( 22.22 %)
What is the failure?
> Errors: 0
> Warnings: 0
> Section Mismatches: 0
>
> Failed defconfigs:
>
> Errors:
>
> -------------------------------------------------------------------------------
> defconfigs with issues (other than build errors):
>
> -------------------------------------------------------------------------------
>
>
>
> ===============================================================================
> Detailed per-defconfig build reports below:
>
> -------------------------------------------------------------------------------
>
> Passed with no errors, warnings or mismatches:
>
> arm64-allnoconfig
> arm64-allmodconfig
> arm-multi_v5_defconfig
> arm-multi_v7_defconfig
> x86_64-defconfig
> arm-allnoconfig
> x86_64-allnoconfig
> arm-multi_v4t_defconfig
> arm64-defconfig
> close failed in file object destructor:
> sys.excepthook is missing
> lost sys.stderr
I don't see any error messages here :(
next prev parent reply other threads:[~2018-03-16 8:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-15 18:46 v4.15.10 build: 2 failures 0 warnings (v4.15.10) Build bot for Mark Brown
2018-03-16 8:02 ` Greg KH [this message]
2018-03-19 0:52 ` 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=20180316080231.GA13244@kroah.com \
--to=greg@kroah.com \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.