mainline boot: 274 boots: 274 passed (v4.0-rc4-48-gc58616580ea5)
Full Boot Summary: http://kernelci.org/boot/all/job/mainline/kernel/v4.0-rc4-48-gc58616580ea5/ Full Build Summary: http://kernelci.org/build/mainline/kernel/v4.0-rc4-48-gc58616580ea5/
Tree: mainline Branch: local/master Git Describe: v4.0-rc4-48-gc58616580ea5 Git Commit: c58616580ea520aab8dacef787d855bea3e81c25 Git URL: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git Tested: 70 unique boards, 22 SoC families, 25 builds out of 125
--- For more info write to info@kernelci.org
On Tue, 2015-03-17 at 06:38PM -0700, kernelci.org bot wrote:
mainline boot: 274 boots: 274 passed (v4.0-rc4-48-gc58616580ea5)
Maybe it's just me, but is it possible to rather report the failures instead of the passed boards? That way humans wouldn't have to correlate the absolute number of boards with the number of passes. A simple non-zero would indicate that something failed.
Sören
Hi Sören,
On Tue, Mar 17, 2015 at 8:29 PM, Sören Brinkmann soren.brinkmann@xilinx.com wrote:
On Tue, 2015-03-17 at 06:38PM -0700, kernelci.org bot wrote:
mainline boot: 274 boots: 274 passed (v4.0-rc4-48-gc58616580ea5)
Maybe it's just me, but is it possible to rather report the failures instead of the passed boards? That way humans wouldn't have to correlate the absolute number of boards with the number of passes. A simple non-zero would indicate that something failed.
Not sure exactly what you're asking for.
The email subject/summary reports total, passed, failed and conflicts (where 2 or more labs have different boot results.) The total is always reported, and the other fields are only present if they are non-zero.
If you're asking for something else, could you be more specific with some examples of how you'd like it to look for various combinations of pass/fail/conflicted boots?
Thanks,
Kevin
On Tue, 2015-03-17 at 10:14PM -0700, Kevin Hilman wrote:
Hi Sören,
On Tue, Mar 17, 2015 at 8:29 PM, Sören Brinkmann soren.brinkmann@xilinx.com wrote:
On Tue, 2015-03-17 at 06:38PM -0700, kernelci.org bot wrote:
mainline boot: 274 boots: 274 passed (v4.0-rc4-48-gc58616580ea5)
Maybe it's just me, but is it possible to rather report the failures instead of the passed boards? That way humans wouldn't have to correlate the absolute number of boards with the number of passes. A simple non-zero would indicate that something failed.
Not sure exactly what you're asking for.
The email subject/summary reports total, passed, failed and conflicts (where 2 or more labs have different boot results.) The total is always reported, and the other fields are only present if they are non-zero.
If you're asking for something else, could you be more specific with some examples of how you'd like it to look for various combinations of pass/fail/conflicted boots?
The subject for this is: mainline boot: 274 boots: 274 passed
So, I always end up having to check a second time whether the number of boots match the number of passed. So, I thought it would probably be a little easier to parse if it was something like: mainline boot: 274 boots: 0 failed, 274 passed
Probably even moving the fails even further to the left to have the essential information first.
Sören
On Wed, Mar 18, 2015 at 4:17 AM, Sören Brinkmann soren.brinkmann@xilinx.com wrote:
On Tue, 2015-03-17 at 10:14PM -0700, Kevin Hilman wrote:
Hi Sören,
On Tue, Mar 17, 2015 at 8:29 PM, Sören Brinkmann soren.brinkmann@xilinx.com wrote:
On Tue, 2015-03-17 at 06:38PM -0700, kernelci.org bot wrote:
mainline boot: 274 boots: 274 passed (v4.0-rc4-48-gc58616580ea5)
Maybe it's just me, but is it possible to rather report the failures instead of the passed boards? That way humans wouldn't have to correlate the absolute number of boards with the number of passes. A simple non-zero would indicate that something failed.
Not sure exactly what you're asking for.
The email subject/summary reports total, passed, failed and conflicts (where 2 or more labs have different boot results.) The total is always reported, and the other fields are only present if they are non-zero.
If you're asking for something else, could you be more specific with some examples of how you'd like it to look for various combinations of pass/fail/conflicted boots?
The subject for this is: mainline boot: 274 boots: 274 passed
So, I always end up having to check a second time whether the number of boots match the number of passed. So, I thought it would probably be a little easier to parse if it was something like: mainline boot: 274 boots: 0 failed, 274 passed
Probably even moving the fails even further to the left to have the essential information first.
I see. Makes sense. So you want the #failed reported always, even if it's zero, and ideally have it be the first. We can implement that easy enough.
Kevin
On Wed, 2015-03-18 at 06:53AM -0700, Kevin Hilman wrote:
On Wed, Mar 18, 2015 at 4:17 AM, Sören Brinkmann soren.brinkmann@xilinx.com wrote:
On Tue, 2015-03-17 at 10:14PM -0700, Kevin Hilman wrote:
Hi Sören,
On Tue, Mar 17, 2015 at 8:29 PM, Sören Brinkmann soren.brinkmann@xilinx.com wrote:
On Tue, 2015-03-17 at 06:38PM -0700, kernelci.org bot wrote:
mainline boot: 274 boots: 274 passed (v4.0-rc4-48-gc58616580ea5)
Maybe it's just me, but is it possible to rather report the failures instead of the passed boards? That way humans wouldn't have to correlate the absolute number of boards with the number of passes. A simple non-zero would indicate that something failed.
Not sure exactly what you're asking for.
The email subject/summary reports total, passed, failed and conflicts (where 2 or more labs have different boot results.) The total is always reported, and the other fields are only present if they are non-zero.
If you're asking for something else, could you be more specific with some examples of how you'd like it to look for various combinations of pass/fail/conflicted boots?
The subject for this is: mainline boot: 274 boots: 274 passed
So, I always end up having to check a second time whether the number of boots match the number of passed. So, I thought it would probably be a little easier to parse if it was something like: mainline boot: 274 boots: 0 failed, 274 passed
Probably even moving the fails even further to the left to have the essential information first.
I see. Makes sense. So you want the #failed reported always, even if it's zero, and ideally have it be the first. We can implement that easy enough.
Yeah, that's the way how I read the subjects. If there is a zero first I can just stop reading :)
Sören
kernel-build-reports@lists.linaro.org
-
kernelci.org bot -
Kevin Hilman -
Sören Brinkmann