* next-20170731 build: 2 failures 3 warnings (next-20170731)
@ 2017-08-05 15:30 Build bot for Mark Brown
2017-08-06 13:15 ` Mark Brown
0 siblings, 1 reply; 2+ messages in thread
From: Build bot for Mark Brown @ 2017-08-05 15:30 UTC (permalink / raw)
To: kernel-build-reports, linaro-kernel, linux-next
Tree/Branch: next-20170731
Git describe: next-20170731
Commit: 742f220ee6 Add linux-next specific files for 20170731
Build Time: 2883 min 29 sec
Passed: 8 / 10 ( 80.00 %)
Failed: 2 / 10 ( 20.00 %)
Errors: 0
Warnings: 3
Section Mismatches: 0
Failed defconfigs:
arm64-allmodconfig
Errors:
-------------------------------------------------------------------------------
defconfigs with issues (other than build errors):
1 warnings 0 mismatches : arm64-allmodconfig
2 warnings 0 mismatches : arm-allmodconfig
-------------------------------------------------------------------------------
Warnings Summary: 3
1 ../drivers/staging/media/imx/imx-media-of.c:216:4: warning: 'remote_np' may be used uninitialized in this function [-Wmaybe-uninitialized]
1 ../drivers/iommu/exynos-iommu.c:58:2: warning: #warning "revisit driver if we can enable big-endian ptes" [-Wcpp]
1 ../drivers/crypto/ccp/ccp-ops.c:1856:3: warning: 'sb_count' may be used uninitialized in this function [-Wmaybe-uninitialized]
===============================================================================
Detailed per-defconfig build reports below:
-------------------------------------------------------------------------------
arm64-allmodconfig : FAIL, 0 errors, 1 warnings, 0 section mismatches
Warnings:
../drivers/crypto/ccp/ccp-ops.c:1856:3: warning: 'sb_count' may be used uninitialized in this function [-Wmaybe-uninitialized]
-------------------------------------------------------------------------------
arm-allmodconfig : PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
../drivers/iommu/exynos-iommu.c:58:2: warning: #warning "revisit driver if we can enable big-endian ptes" [-Wcpp]
../drivers/staging/media/imx/imx-media-of.c:216:4: warning: 'remote_np' may be used uninitialized in this function [-Wmaybe-uninitialized]
-------------------------------------------------------------------------------
Passed with no errors, warnings or mismatches:
arm64-allnoconfig
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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: next-20170731 build: 2 failures 3 warnings (next-20170731)
2017-08-05 15:30 next-20170731 build: 2 failures 3 warnings (next-20170731) Build bot for Mark Brown
@ 2017-08-06 13:15 ` Mark Brown
0 siblings, 0 replies; 2+ messages in thread
From: Mark Brown @ 2017-08-06 13:15 UTC (permalink / raw)
To: kernel-build-reports, linaro-kernel, linux-next
[-- Attachment #1: Type: text/plain, Size: 531 bytes --]
On Sat, Aug 05, 2017 at 04:30:50PM +0100, Build bot for Mark Brown wrote:
> Tree/Branch: next-20170731
> Git describe: next-20170731
> Commit: 742f220ee6 Add linux-next specific files for 20170731
>
> Build Time: 2883 min 29 sec
>
> Passed: 8 / 10 ( 80.00 %)
> Failed: 2 / 10 ( 20.00 %)
Sorry, this is noise - the build server decided it was a good idea to
wedge itself at the lowest processor speed which meant that the builds
had effectively hung so I killed and rebooted causing some false
positives.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2017-08-06 13:15 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-08-05 15:30 next-20170731 build: 2 failures 3 warnings (next-20170731) Build bot for Mark Brown
2017-08-06 13:15 ` Mark Brown
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox