All of lore.kernel.org
 help / color / mirror / Atom feed
* v3.18.104 build: 10 failures 1 warnings (v3.18.104)
@ 2018-04-11 16:12 Build bot for Mark Brown
  2018-04-11 18:24 ` Harsh Shandilya
  0 siblings, 1 reply; 6+ messages in thread
From: Build bot for Mark Brown @ 2018-04-11 16:12 UTC (permalink / raw)
  To: kernel-build-reports, linaro-kernel, stable

Tree/Branch: v3.18.104
Git describe: v3.18.104
Commit: fb625ba702 Linux 3.18.104

Build Time: 0 min 14 sec

Passed:    0 / 10   (  0.00 %)
Failed:   10 / 10   (100.00 %)

Errors: 0
Warnings: 1
Section Mismatches: 0

Failed defconfigs:
	x86_64-allnoconfig
	arm-allnoconfig
	arm64-defconfig

Errors:

-------------------------------------------------------------------------------
defconfigs with issues (other than build errors):
      1 warnings    0 mismatches  : x86_64-allnoconfig
      1 warnings    0 mismatches  : arm-allnoconfig
      1 warnings    0 mismatches  : arm64-defconfig

-------------------------------------------------------------------------------

Warnings Summary: 1
	  3 include/config/auto.conf:4559:warning: override: TICK_CPU_ACCOUNTING changes choice state



===============================================================================
Detailed per-defconfig build reports below:


-------------------------------------------------------------------------------
x86_64-allnoconfig : FAIL, 0 errors, 1 warnings, 0 section mismatches

Warnings:
	include/config/auto.conf:4559:warning: override: TICK_CPU_ACCOUNTING changes choice state

-------------------------------------------------------------------------------
arm-allnoconfig : FAIL, 0 errors, 1 warnings, 0 section mismatches

Warnings:
	include/config/auto.conf:4559:warning: override: TICK_CPU_ACCOUNTING changes choice state

-------------------------------------------------------------------------------
arm64-defconfig : FAIL, 0 errors, 1 warnings, 0 section mismatches

Warnings:
	include/config/auto.conf:4559:warning: override: TICK_CPU_ACCOUNTING changes choice state
-------------------------------------------------------------------------------

Passed with no errors, warnings or mismatches:

arm64-allnoconfig
arm64-allmodconfig
arm-multi_v5_defconfig
arm-multi_v7_defconfig
x86_64-defconfig
arm-allmodconfig
x86_64-allmodconfig

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: v3.18.104 build: 10 failures 1 warnings (v3.18.104)
  2018-04-11 16:12 v3.18.104 build: 10 failures 1 warnings (v3.18.104) Build bot for Mark Brown
@ 2018-04-11 18:24 ` Harsh Shandilya
  2018-04-12 10:03   ` Mark Brown
  0 siblings, 1 reply; 6+ messages in thread
From: Harsh Shandilya @ 2018-04-11 18:24 UTC (permalink / raw)
  To: Build bot for Mark Brown, kernel-build-reports, linaro-kernel, stable



On 11 April 2018 9:42:07 PM IST, Build bot for Mark Brown <broonie@kernel.org> wrote:
>Tree/Branch: v3.18.104
>Git describe: v3.18.104
>Commit: fb625ba702 Linux 3.18.104
>
>Build Time: 0 min 14 sec
>
>Passed:    0 / 10   (  0.00 %)
>Failed:   10 / 10   (100.00 %)
>
>Errors: 0
>Warnings: 1
>Section Mismatches: 0
>
>Failed defconfigs:
>	x86_64-allnoconfig
>	arm-allnoconfig
>	arm64-defconfig
>
>Errors:
>
>-------------------------------------------------------------------------------
>defconfigs with issues (other than build errors):
>      1 warnings    0 mismatches  : x86_64-allnoconfig
>      1 warnings    0 mismatches  : arm-allnoconfig
>      1 warnings    0 mismatches  : arm64-defconfig
>
>-------------------------------------------------------------------------------
>
>Warnings Summary: 1
>	  3 include/config/auto.conf:4559:warning: override:
>TICK_CPU_ACCOUNTING changes choice state
>
>
>
>===============================================================================
>Detailed per-defconfig build reports below:
>
>
>-------------------------------------------------------------------------------
>x86_64-allnoconfig : FAIL, 0 errors, 1 warnings, 0 section mismatches
>
>Warnings:
>	include/config/auto.conf:4559:warning: override: TICK_CPU_ACCOUNTING
>changes choice state
>
>-------------------------------------------------------------------------------
>arm-allnoconfig : FAIL, 0 errors, 1 warnings, 0 section mismatches
>
>Warnings:
>	include/config/auto.conf:4559:warning: override: TICK_CPU_ACCOUNTING
>changes choice state
>
>-------------------------------------------------------------------------------
>arm64-defconfig : FAIL, 0 errors, 1 warnings, 0 section mismatches
>
>Warnings:
>	include/config/auto.conf:4559:warning: override: TICK_CPU_ACCOUNTING
>changes choice state
>-------------------------------------------------------------------------------
>
>Passed with no errors, warnings or mismatches:
>
>arm64-allnoconfig
>arm64-allmodconfig
>arm-multi_v5_defconfig
>arm-multi_v7_defconfig
>x86_64-defconfig
>arm-allmodconfig
>x86_64-allmodconfig

These test results look pretty off, the disk space issue from v4.15.16 hit these as well?
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: v3.18.104 build: 10 failures 1 warnings (v3.18.104)
  2018-04-11 18:24 ` Harsh Shandilya
@ 2018-04-12 10:03   ` Mark Brown
  2018-04-12 11:57     ` Harsh Shandilya
  0 siblings, 1 reply; 6+ messages in thread
From: Mark Brown @ 2018-04-12 10:03 UTC (permalink / raw)
  To: Harsh Shandilya; +Cc: kernel-build-reports, linaro-kernel, stable

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

On Wed, Apr 11, 2018 at 11:54:13PM +0530, Harsh Shandilya wrote:

> These test results look pretty off, the disk space issue from v4.15.16 hit these as well?

I'm guessing it's affected all the builds somehow.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: v3.18.104 build: 10 failures 1 warnings (v3.18.104)
  2018-04-12 10:03   ` Mark Brown
@ 2018-04-12 11:57     ` Harsh Shandilya
  2018-04-12 11:59       ` Mark Brown
  0 siblings, 1 reply; 6+ messages in thread
From: Harsh Shandilya @ 2018-04-12 11:57 UTC (permalink / raw)
  To: Mark Brown; +Cc: kernel-build-reports, linaro-kernel, stable

On 12 April 2018 3:33:41 PM IST, Mark Brown <broonie@kernel.org> wrote:
>On Wed, Apr 11, 2018 at 11:54:13PM +0530, Harsh Shandilya wrote:
>
>> These test results look pretty off, the disk space issue from
>v4.15.16 hit these as well?
>
>I'm guessing it's affected all the builds somehow.

Looks like it, v4.15.17 is broken just like .16 was so clearly the problem has persisted. Is it really a disk space issue?
-- 
Harsh Shandilya, PRJKT Development LLC

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: v3.18.104 build: 10 failures 1 warnings (v3.18.104)
  2018-04-12 11:57     ` Harsh Shandilya
@ 2018-04-12 11:59       ` Mark Brown
  2018-04-12 12:07         ` Harsh Shandilya
  0 siblings, 1 reply; 6+ messages in thread
From: Mark Brown @ 2018-04-12 11:59 UTC (permalink / raw)
  To: Harsh Shandilya; +Cc: kernel-build-reports, linaro-kernel, stable

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

On Thu, Apr 12, 2018 at 05:27:46PM +0530, Harsh Shandilya wrote:
> On 12 April 2018 3:33:41 PM IST, Mark Brown <broonie@kernel.org> wrote:

> >I'm guessing it's affected all the builds somehow.

> Looks like it, v4.15.17 is broken just like .16 was so clearly the problem has persisted. Is it really a disk space issue?

The disk space issue had messed up the git trees and for some reason new
checkouts weren't either repairing them or error; that should be fixed
now.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: v3.18.104 build: 10 failures 1 warnings (v3.18.104)
  2018-04-12 11:59       ` Mark Brown
@ 2018-04-12 12:07         ` Harsh Shandilya
  0 siblings, 0 replies; 6+ messages in thread
From: Harsh Shandilya @ 2018-04-12 12:07 UTC (permalink / raw)
  To: Mark Brown; +Cc: kernel-build-reports, linaro-kernel, stable

On 12 April 2018 5:29:01 PM IST, Mark Brown <broonie@kernel.org> wrote:
>On Thu, Apr 12, 2018 at 05:27:46PM +0530, Harsh Shandilya wrote:
>> On 12 April 2018 3:33:41 PM IST, Mark Brown <broonie@kernel.org>
>wrote:
>
>> >I'm guessing it's affected all the builds somehow.
>
>> Looks like it, v4.15.17 is broken just like .16 was so clearly the
>problem has persisted. Is it really a disk space issue?
>
>The disk space issue had messed up the git trees and for some reason
>new
>checkouts weren't either repairing them or error; that should be fixed
>now.

Awesome! Thanks for your efforts :)
-- 
Harsh Shandilya, PRJKT Development LLC

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2018-04-12 12:07 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-04-11 16:12 v3.18.104 build: 10 failures 1 warnings (v3.18.104) Build bot for Mark Brown
2018-04-11 18:24 ` Harsh Shandilya
2018-04-12 10:03   ` Mark Brown
2018-04-12 11:57     ` Harsh Shandilya
2018-04-12 11:59       ` Mark Brown
2018-04-12 12:07         ` Harsh Shandilya

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.