On Thu, Jun 12, 2014 at 9:10 AM, Thomas Petazzoni thomas.petazzoni@free-electrons.com wrote:
Dear Kevin Hilman,
On Thu, 12 Jun 2014 08:33:12 -0700, Kevin Hilman wrote:
Tree/Branch: mainline Git describe: v3.15-rc8-70-gc717d15 Failed boot tests (console logs at the end) =========================================== armada-370-mirabox: FAIL: arm-mvebu_v7_defconfig+CONFIG_CPU_BIG_ENDIAN=y
While the multi_v7 + BE is passing, the mvebu + BE is not. What's interesting is that when retrying it works sometimes, but not others.
Below is a full log for the failure case.
Are you guys seeing the BE failure for mvebu_v7_defconfig?
Should we be expecting it to pass? or should I remove it from automation? It's been failing since I added it.
Hum, I'm not sure to understand where the failure is. If I look at:
Subject: mainline boot: 64 boots: 61 pass, 3 fail (v3.15-8981-g5c02c39) Date: Wed, 11 Jun 2014 23:55:53 -0700 (PDT)
I see:
arm-mvebu_v7_defconfig+CONFIG_CPU_BIG_ENDIAN=y
armada-xp-openblocks-ax3-4 0 min 23.7 sec: PASS armada-370-mirabox 0 min 20.6 sec: PASS
So mvebu_v7 + BE in mainline seems to be working fine, no?
Am I missing something?
Nope, my fault.
I was looking at older logs thinking they were recent ones and still failing.
Sorry for the noise.
Kevin