From: Igor Grinberg <grinberg@compulab.co.il>
To: Paul Walmsley <paul@pwsan.com>, linux-omap@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
kernel-build-reports@lists.linaro.org
Subject: Re: OMAP baseline test results for v3.18-rc7
Date: Wed, 03 Dec 2014 09:05:31 +0200 [thread overview]
Message-ID: <547EB63B.5070200@compulab.co.il> (raw)
In-Reply-To: <alpine.DEB.2.02.1412021838410.16734@utopia.booyaka.com>
Hi Paul,
On 12/02/14 20:39, Paul Walmsley wrote:
>
> Here are some basic OMAP test results for Linux v3.18-rc7.
> Logs and other details at:
>
> http://www.pwsan.com/omap/testlogs/test_v3.18-rc7/20141201203859/
>
>
> Test summary
> ------------
>
[...]
> Build: uImage+dtb:
> Pass (13/13): omap2plus_defconfig_am33xx_only/am335x-bone,
> omap2plus_defconfig/omap4-panda,
> omap2plus_defconfig/omap4-panda-es,
> omap2plus_defconfig/omap4-var-som,
> omap2plus_defconfig/omap3-evm-37xx,
> omap2plus_defconfig_n800_only_a/omap2420-n800,
> omap2plus_defconfig/omap2430-sdp,
> omap2plus_defconfig/am3517-evm,
> omap2plus_defconfig/omap3-beagle,
> omap2plus_defconfig/omap3-beagle-xm,
> omap2plus_defconfig/omap3-sbc-t3517,
> omap2plus_defconfig/omap5-uevm,
> omap2plus_defconfig/omap5-sbc-t54
>
[...]
> Boot to userspace:
> FAIL ( 1/16): 2430sdp
> skip ( 2/16): 5912osk, 3517evm
> Pass (13/16): am335xbonelt, am335xbone, 4430es2panda, 4460pandaes,
> 4460varsomom, 37xxevm, 3530es3beagle, 3530es31beagle,
> 3730beaglexm, 3730es12beaglexm, 5430es2uevm,
> 5430es2sbct54, 2420n800
I've looked at the boot log and it seems cm-t3517 is booting just fine...
A problem with the test/report collecting script?
5912osk is not listed by the link above, but there are indeed 16 entries...
[...]
--
Regards,
Igor.
WARNING: multiple messages have this Message-ID (diff)
From: grinberg@compulab.co.il (Igor Grinberg)
To: linux-arm-kernel@lists.infradead.org
Subject: OMAP baseline test results for v3.18-rc7
Date: Wed, 03 Dec 2014 09:05:31 +0200 [thread overview]
Message-ID: <547EB63B.5070200@compulab.co.il> (raw)
In-Reply-To: <alpine.DEB.2.02.1412021838410.16734@utopia.booyaka.com>
Hi Paul,
On 12/02/14 20:39, Paul Walmsley wrote:
>
> Here are some basic OMAP test results for Linux v3.18-rc7.
> Logs and other details at:
>
> http://www.pwsan.com/omap/testlogs/test_v3.18-rc7/20141201203859/
>
>
> Test summary
> ------------
>
[...]
> Build: uImage+dtb:
> Pass (13/13): omap2plus_defconfig_am33xx_only/am335x-bone,
> omap2plus_defconfig/omap4-panda,
> omap2plus_defconfig/omap4-panda-es,
> omap2plus_defconfig/omap4-var-som,
> omap2plus_defconfig/omap3-evm-37xx,
> omap2plus_defconfig_n800_only_a/omap2420-n800,
> omap2plus_defconfig/omap2430-sdp,
> omap2plus_defconfig/am3517-evm,
> omap2plus_defconfig/omap3-beagle,
> omap2plus_defconfig/omap3-beagle-xm,
> omap2plus_defconfig/omap3-sbc-t3517,
> omap2plus_defconfig/omap5-uevm,
> omap2plus_defconfig/omap5-sbc-t54
>
[...]
> Boot to userspace:
> FAIL ( 1/16): 2430sdp
> skip ( 2/16): 5912osk, 3517evm
> Pass (13/16): am335xbonelt, am335xbone, 4430es2panda, 4460pandaes,
> 4460varsomom, 37xxevm, 3530es3beagle, 3530es31beagle,
> 3730beaglexm, 3730es12beaglexm, 5430es2uevm,
> 5430es2sbct54, 2420n800
I've looked at the boot log and it seems cm-t3517 is booting just fine...
A problem with the test/report collecting script?
5912osk is not listed by the link above, but there are indeed 16 entries...
[...]
--
Regards,
Igor.
next prev parent reply other threads:[~2014-12-03 7:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-02 18:39 OMAP baseline test results for v3.18-rc7 Paul Walmsley
2014-12-02 18:39 ` Paul Walmsley
2014-12-03 7:05 ` Igor Grinberg [this message]
2014-12-03 7:05 ` Igor Grinberg
2014-12-03 16:56 ` Paul Walmsley
2014-12-03 16:56 ` Paul Walmsley
2014-12-03 22:25 ` Paul Walmsley
2014-12-03 22:25 ` Paul Walmsley
2014-12-03 22:28 ` OMAP baseline test results for v3.18-rc7 (corrected) Paul Walmsley
2014-12-03 22:28 ` Paul Walmsley
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=547EB63B.5070200@compulab.co.il \
--to=grinberg@compulab.co.il \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
/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.