lkft/android-hikey-linaro-4.4-oe: 1117 tests, 23 failed, 1092 passed (build v4.4.80-568085-gc40a9a7)
Tests: 1117 Failed: 23 Passed: 1092 Skipped: 2 Build: v4.4.80-568085-gc40a9a7 Details: https://qa-reports.linaro.org/lkft/android-hikey-linaro-4.4-oe/build/v4.4.80...
series: lkft kernel-describe: v4.4.80-568085-gc40a9a7 kernel-branch: android-hikey-linaro-4.4 build-url: https://ci.linaro.org/job/openembedded-lkft-aosp-4.4/DISTRO=rpb,MACHINE=hike... kernel-repo: https://android.googlesource.com/kernel/hikey-linaro kernel-config: https://snapshots.linaro.org/openembedded/lkft/morty/hikey/rpb/4.4/62/defcon... kernel-commit: c40a9a77daf770cd8ca75572235b015ef6ff6589 job_status: Complete
Regressions (compared to build v4.4.80-568084-g7f6b98c) ------------------------------------------------------------------------
(none)
Failures ------------------------------------------------------------------------
hi6220-hikey:
* kselftest/pstore_tests -- never passed * kselftest/ftracetest -- never passed * kselftest/fw_fallback.sh -- never passed * kselftest/pidns -- never passed * kselftest/breakpoint_test_arm64 -- never passed * kselftest/test_tag -- never passed * kselftest/test_bpf.sh -- never passed * kselftest/run_fuse_test.sh -- never passed * ltp-syscalls-tests/pselect01_64 -- failing since build v4.4.79-568979-g43c93f7, from Aug. 1, 2017, 10:12 p.m. * kselftest/run_vmtests -- failing since build v4.4.77-568946-g4d4632a, from July 21, 2017, 1:28 p.m. * kselftest/test_kmod.sh -- never passed * kselftest/bitmap.sh -- never passed * kselftest/test_maps -- never passed * ltp-syscalls-tests/utimensat01 -- never passed * kselftest/test_lpm_map -- never passed * kselftest/test_align -- never passed * kselftest/gpio-mockup.sh -- never passed * kselftest/test_lru_map -- never passed * kselftest/seccomp_bpf -- never passed * kselftest/run.sh -- never passed * ltp-syscalls-tests/runltp_syscalls -- never passed * kselftest/owner -- never passed * kselftest/inconsistency-check -- never passed
All changes (compared to build v4.4.80-568084-g7f6b98c) ------------------------------------------------------------------------
+--- v4.4.80-568084-g7f6b98c, hi6220-hikey | +--- v4.4.80-568085-gc40a9a7, hi6220-hikey | | pass n/a kselftest/execveat fail n/a kselftest/fw_filesystem.sh fail n/a kselftest/test_verifier
-- Linaro QA (beta) https://qa-reports.linaro.org
Hi all,
As I'm not going to be able to make the meeting today (scheduling conflict with another thing here in Seattle), here's my initial critique of the existing reports:
On Thu, Aug 10, 2017 at 08:59:51PM +0000, Linaro QA wrote:
Tests: 1117 Failed: 23 Passed: 1092 Skipped: 2 Build: v4.4.80-568085-gc40a9a7
That means nothing to me. Especially as this really was a 4.4.81-rc build, right? So here I am thinking that 4.4.80 might have problems?
Why are you not picking up the -rc and other Makefile changes, they are part of the git tree, are you pulling directly from the quilt series instead?
Details: https://qa-reports.linaro.org/lkft/android-hikey-linaro-4.4-oe/build/v4.4.80...
series: lkft
What does "series" mean? What does "lkft" mean? Where can I go to look up these things?
What does "oe" mean? And again, where can I look those things up?
kernel-describe: v4.4.80-568085-gc40a9a7
Same as above? Why repeat it? How will it ever be different?
kernel-branch: android-hikey-linaro-4.4
Shouldn't this be reflected in the kernel version?
Where can I find these branches? What do the different branches mean?
build-url: https://ci.linaro.org/job/openembedded-lkft-aosp-4.4/DISTRO=rpb,MACHINE=hike... kernel-repo: https://android.googlesource.com/kernel/hikey-linaro kernel-config: https://snapshots.linaro.org/openembedded/lkft/morty/hikey/rpb/4.4/62/defcon... kernel-commit: c40a9a77daf770cd8ca75572235b015ef6ff6589
That's already listed above in the describe and version, right? Why list it again?
job_status: Complete
As others said, can this ever not be this? If so, really? How?
Regressions (compared to build v4.4.80-568084-g7f6b98c)
Your compared-to build means nothing to me. Again, the kernel version is off, and still, what does it mean? What can I do with this?
(none)
Nice.
Failures
hi6220-hikey:
- kselftest/pstore_tests -- never passed
- kselftest/ftracetest -- never passed
- kselftest/fw_fallback.sh -- never passed
- kselftest/pidns -- never passed
- kselftest/breakpoint_test_arm64 -- never passed
- kselftest/test_tag -- never passed
- kselftest/test_bpf.sh -- never passed
- kselftest/run_fuse_test.sh -- never passed
- ltp-syscalls-tests/pselect01_64 -- failing since build v4.4.79-568979-g43c93f7, from Aug. 1, 2017, 10:12 p.m.
- kselftest/run_vmtests -- failing since build v4.4.77-568946-g4d4632a, from July 21, 2017, 1:28 p.m.
- kselftest/test_kmod.sh -- never passed
- kselftest/bitmap.sh -- never passed
- kselftest/test_maps -- never passed
- ltp-syscalls-tests/utimensat01 -- never passed
- kselftest/test_lpm_map -- never passed
- kselftest/test_align -- never passed
- kselftest/gpio-mockup.sh -- never passed
- kselftest/test_lru_map -- never passed
- kselftest/seccomp_bpf -- never passed
- kselftest/run.sh -- never passed
- ltp-syscalls-tests/runltp_syscalls -- never passed
- kselftest/owner -- never passed
- kselftest/inconsistency-check -- never passed
You all said you were working on this. What I really want to know is if I broke something, and about these things that are continuing to fail, what the status is for them. Are they build system issues? Upstream kernel issues? Merge issues with your SoC tree? Something else?
All changes (compared to build v4.4.80-568084-g7f6b98c)
+--- v4.4.80-568084-g7f6b98c, hi6220-hikey | +--- v4.4.80-568085-gc40a9a7, hi6220-hikey
Again, build version problems :(
| | pass n/a kselftest/execveat fail n/a kselftest/fw_filesystem.sh fail n/a kselftest/test_verifier
I don't understand this, 2 new things are failing and one new thing is passing? Shouldn't the 2 new failures be listed above as regressions?
And should we have a separate "this is now fixed" category?
thanks,
greg k-h
On Mon, Aug 14, 2017 at 10:36:01AM -0700, Greg KH wrote:
kernel-branch: android-hikey-linaro-4.4
Shouldn't this be reflected in the kernel version?
Why would you expect the branch name to be reflected in the kernel version? It's relatively rare for people to tag everything they do but quite common for a tree to have multiple branches so the normal thing is for versions to just come out with versions based off Linus' tags.
Where can I find these branches? What do the different branches mean?
Perhaps it would help with your confusion here if the thing being tested were displayed as a git URI list in a pull request instead of with the tree and branch separately?
Regressions (compared to build v4.4.80-568084-g7f6b98c)
Your compared-to build means nothing to me. Again, the kernel version is off, and still, what does it mean? What can I do with this?
We probably need both an abbreviated hash and the git describe in here - unfortunately the hash is unintelligable to humans but difficult to translate back into a tree unless it happens to have been tagged.
On Mon, Aug 14, 2017 at 06:58:32PM +0100, Mark Brown wrote:
On Mon, Aug 14, 2017 at 10:36:01AM -0700, Greg KH wrote:
kernel-branch: android-hikey-linaro-4.4
Shouldn't this be reflected in the kernel version?
Why would you expect the branch name to be reflected in the kernel version? It's relatively rare for people to tag everything they do but quite common for a tree to have multiple branches so the normal thing is for versions to just come out with versions based off Linus' tags.
Ah, good point, yes, nevermind.
Where can I find these branches? What do the different branches mean?
Perhaps it would help with your confusion here if the thing being tested were displayed as a git URI list in a pull request instead of with the tree and branch separately?
Sure, that might be a better way to display this whole thing.
But how to find out the branch location, and what it is there for, would be great to know as well.
Some kind of "rubric" somewhere for all of this?
thanks,
greg k-h
Hi Greg,
On 14 August 2017 at 23:06, Greg KH gregkh@google.com wrote:
Hi all,
As I'm not going to be able to make the meeting today (scheduling conflict with another thing here in Seattle), here's my initial critique of the existing reports:
On Thu, Aug 10, 2017 at 08:59:51PM +0000, Linaro QA wrote:
Tests: 1117 Failed: 23 Passed: 1092 Skipped: 2 Build: v4.4.80-568085-gc40a9a7
That means nothing to me. Especially as this really was a 4.4.81-rc build, right? So here I am thinking that 4.4.80 might have problems?
This is actually a 4.4.80-rc based build only - I have been on leave for past 4 days, and the hikey merge of both 4.4 stable and stable-rc is done (for now) manually by me. There is already a request for converting the manual merges into CI loops here, but it's still under progress.
For today, I'm merging the 4.4.82 and 4.4.83-rc branches and pushing them out for testing. (Done with basic build test, but can't do a boot test while on vacation).
Just as a reminder: the 4.4 based hikey branches are 'special' in that hikey is not supported in mainline 4.4, and so we need the merges with hikey out-of-tree patches for validation.
Why are you not picking up the -rc and other Makefile changes, they are part of the git tree, are you pulling directly from the quilt series instead?
Details: https://qa-reports.linaro.org/lkft/android-hikey-linaro-4.4-oe/build/v4.4.80...
Best regards, Sumit.
On Tue, Aug 15, 2017 at 02:48:35PM +0530, Sumit Semwal wrote:
Hi Greg,
On 14 August 2017 at 23:06, Greg KH gregkh@google.com wrote:
Hi all,
As I'm not going to be able to make the meeting today (scheduling conflict with another thing here in Seattle), here's my initial critique of the existing reports:
On Thu, Aug 10, 2017 at 08:59:51PM +0000, Linaro QA wrote:
Tests: 1117 Failed: 23 Passed: 1092 Skipped: 2 Build: v4.4.80-568085-gc40a9a7
That means nothing to me. Especially as this really was a 4.4.81-rc build, right? So here I am thinking that 4.4.80 might have problems?
This is actually a 4.4.80-rc based build only - I have been on leave for past 4 days, and the hikey merge of both 4.4 stable and stable-rc is done (for now) manually by me. There is already a request for converting the manual merges into CI loops here, but it's still under progress.
For today, I'm merging the 4.4.82 and 4.4.83-rc branches and pushing them out for testing. (Done with basic build test, but can't do a boot test while on vacation).
Just as a reminder: the 4.4 based hikey branches are 'special' in that hikey is not supported in mainline 4.4, and so we need the merges with hikey out-of-tree patches for validation.
That's fine, but that needs to be documented somewhere so that everyone remembers this.
thanks,
greg k-h
-
Greg KH -
Linaro QA -
Mark Brown -
Sumit Semwal