Hi Greg,
On 26 July 2017 at 00:48, Greg Kroah-Hartman <gregkh(a)linuxfoundation.org> wrote:
> This is the start of the stable review cycle for the 4.4.79 release.
> There are 83 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses should be made by Thu Jul 27 19:16:34 UTC 2017.
> Anything received after that time might be too late.
>
For ARM64, with hikey patches merged, built and boot tested on the
hikey. No regressions noted.
> The whole patch series can be found in one patch at:
> kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.4.79-rc1.gz
> or in the git tree and branch at:
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-4.4.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h
>
Best regards,
Sumit.
On Tue, Jul 25, 2017 at 12:03:00PM +0000, Linaro QA wrote:
>
> Tests: 1107
I wonder if folks would benefit from having the number of regressions
listed here above the total number of failures. The subject line as
well perhaps, mentioning the number of new failures since the last
ancestor, instead of the total number of failures?
In this case it says there are 12 failures but most of them have never
passed. This makes for an unnecessarily ominous looking report header
and may initially mislead some folks. Most people I imagine just want to
know if they broke something.
> Failed: 12
> Passed: 1092
> Build: next-20170725
> Details: https://qa-reports.linaro.org/lkft/linux-next/build/next-20170725
>
> series: lkft
> kernel-config: https://snapshots.linaro.org/openembedded/lkft/morty/hikey/rpb/linux-next/7…
> build-url: https://ci.linaro.org/job/openembedded-lkft-linux-next/DISTRO=rpb,MACHINE=h…
> kernel-branch: master
> kernel-describe: next-20170725
> kernel-commit: dce9071ab691f33b2e7e9af142cf95e5ec7cd217
> job_status: Complete
Can the job_status line be removed? I'm guessing it'll always say
complete.
thanks,
steve
Hi Greg,
On 19 July 2017 at 16:42, Greg Kroah-Hartman <gregkh(a)linuxfoundation.org> wrote:
> This is the start of the stable review cycle for the 4.4.78 release.
> There are 57 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses should be made by Fri Jul 21 11:12:31 UTC 2017.
> Anything received after that time might be too late.
>
Build and boot-tested for arm64 (with Hikey-patches) on hikey; no
regressions noted.
> The whole patch series can be found in one patch at:
> kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.4.78-rc1.gz
> or in the git tree and branch at:
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-4.4.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h
>
Best,
Sumit.
Hi Greg,
On 13 July 2017 at 21:12, Greg Kroah-Hartman <gregkh(a)linuxfoundation.org> wrote:
> This is the start of the stable review cycle for the 4.4.77 release.
> There are 57 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses should be made by Sat Jul 15 15:39:40 UTC 2017.
> Anything received after that time might be too late.
>
> The whole patch series can be found in one patch at:
> kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.4.77-rc1.gz
> or in the git tree and branch at:
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-4.4.y
> and the diffstat can be found below.
>
For hikey, built- and boot-tested with arm64 defconfig (and hikey
additional patches); no regressions noted.
> thanks,
>
> greg k-h
>
Best,
Sumit.
On Tue, Jun 20, 2017 at 12:03:02AM +0000, Linaro QA wrote:
More feedback on these...
One thing I just noticed is that the reports are being sent to every
recipient individually. This is really bad because it breaks up the
discussion, if someone replies it won't go to everyone who got the
original report which increases confusion and leads to duplication of
work.
> Details: https://qa-reports.linaro.org/lkft/hikey-mainline-rebase-4.4.x/build/f5ec4f…
The web part of things doesn't seem to have any way of getting to logs.
It'd be good to at least have links to the LAVA jobs as a placeholder
for now.
> kernel-describe: v3.19-rc7-71416-gf5ec4ff
This is obvious nonsense, this is v4.4 based not v3.19 based. I suspect
that this can be fixed by adding Linus' tree as a remote to the git tree
used to generate these and keeping it up to date.
> format: Lava-Test Test Definition 1.0
Do we need this in the e-mail? It doesn't seem relevant.
> description: Dummy tests
...
> name: dummy-tests
Having the description before the name seems kind of odd, as does them
not being adjacent.
However looking at the test counts and comparing with the web interface
it seems like this isn't actually the results for a single testsuite but
rather the collected results for all the testsuites that were run for
this tree. If that's the case then probably this can just be removed
but then...
> Failures
> ------------------------------------------------------------------------
>
> hi6220-hikey:
>
> * test_lru_map
...when we list test results we should probably say which testsuite they
are from...
> | kselftest/test_maps | | fail |
...as is done in some parts of the reports.