On 13 September 2017 at 05:28, Tom Gall tom.gall@linaro.org wrote:
Hi,
On Tue, Sep 12, 2017 at 3:12 PM, Greg KH gregkh@google.com wrote:
On Tue, Sep 12, 2017 at 06:50:31PM +0000, Linaro QA wrote:
Summary
kernel-repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git kernel-branch: linux-4.4.y kernel-commit: b8c205d855764e3db05a17ab4d03a19a5d609bdd kernel-describe: v4.4.87-32-gb8c205d85576
Why is this 32 patches after 4.4.87?
It's from the git describe. If you look at kernelci results you'll see exactly the same thing.
That's correct.
As discussed before, it's the output of git describe. Since Greg doesn't push rc tags in the stable rc tree (and doesn't want to), it is expected: i.e. the current head of my "parent" branch is based on v4.4.87, but since it has a few commits on top of that, describe has added the number of additional commits ("32") and an abbreviated object name for the commit itself ("b8c205d85576") at the end.
I agree I also want to see pulling from the Makefile for the proper version. I'll talk to Fathi.
It isn't more accurate than git describe and even lead to incorrect version. It's randomly updated or not by the developers. See previous discussion in the thread "Wrong kernel version string in lkft reports?".
If it has to be implemented, it will be another custom template. The new template applied to Greg's rc trees only due to the lack of rc tags.
WHat is "-rc-4.4-oe"? And why would I remember any of this?
first 2 bits are obvious, next is the user space being used. OE is Open Embedded as you might remember from past meetings.
You snipped the link that describes the report, terms contained within etc.
Can you have a "description of what you are testing" somewhere around here so I have a clue?
Yes, there is supposed to be a link to the test source code used for the tests. That's pending. Guessing the next time we gen reports that'll be there.
Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.4-oe/build/v4.4.87-32-g...
No regressions (compared to build v4.4.87)
Boards, architectures and test suites:
dell-poweredge-r200 - x86_64
- boot
- ltp-syscalls-tests
- libhugetlbfs
- kselftest
So one x86 box built and booted and ran 3 test suites?
My laptop did that :)
dell power edge as your laptop? Must be fun on airplanes!
But ok, baby steps...
Yeah. Seriously, looks like the HiKey 4.4 job didn't fire right. We're on it.
X15s look to be passing health checks so in theory we should start generating 32 bit ARM results PDQ.
greg k-h _______________________________________________ Lts-dev mailing list Lts-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lts-dev
-- Regards, Tom
Director, Linaro Mobile Group Linaro.org │ Open source software for ARM SoCs irc: tgall_foo | skype : tom_gall
"Where's the kaboom!? There was supposed to be an earth-shattering kaboom!" Marvin Martian _______________________________________________ Lts-dev mailing list Lts-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lts-dev