On Thu, Jul 13, 2017 at 10:57 AM, Greg KH gregkh@google.com wrote:
On Thu, Jul 13, 2017 at 12:03:01PM +0000, Linaro QA wrote:
Summary
• Tests: 0 • Failed: 0 • Passed: 0
Yeah, nothing happened!!!
:(
• Build: v4.9.37
Ok, but why are you comparing against 4.9.35? What happened to 4.9.37?
• See details
• build-url: https://ci.linaro.org/job/openembedded-lkft-linux-stable-4.9/ DISTRO=rpb,MACHINE=hikey,label=docker-jessie-amd64/16/ • kernel-repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/ linux-stable.git • kernel-describe: v4.9.37 • kernel-commit: c48f76d680ad9ad443290ce0f1e8f92db6986bf5 • series: lkft • job_status: Canceled
Why send this out if it was cancelled? What cancelled it?
• kernel-config: https://snapshots.linaro.org/openembedded/lkft/morty/hikey/ rpb/linux-stable-4.9/16/defconfig • kernel-branch: linux-4.9.y
Regressions (compared to build v4.9.35)
(none)
That's not true.
Failures
(none)
Neither is that :(
I'm getting really annoyed by these reports, can you either fix them up to be useful, or just stop sending them until they are useful? Right now they are just noise that I have to read to try to see if I broke something.
Heck, kernel.ci is more useful right now, even when they don't respond to my emails asking them why something broke...
I am sorry for the bogus report. This was a reporting regression caused by a unique situation we found our selves in when testing the new improvements to the infrastructure. To avoid future frustrations, we removed the lts-dev ML from the list of recipients for now.
I hope we can turn them back on in a couple of week's time but only if we are confident in the test reporting.
Cheers! anmar