Summary ------------------------------------------------------------------------
kernel: 4.4.88 git repo: https://android.googlesource.com/kernel/hikey-linaro git branch: android-hikey-linaro-4.4 git commit: 9ee2cdb3a43324e1f3168be8a32991c0688742f9 git describe: v4.4.88-568214-g9ee2cdb3a433 Test details: https://qa-reports.linaro.org/lkft/android-hikey-linaro-4.4-oe/build/v4.4.88...
No regressions (compared to build v4.4.87-568205-gaf1c754ce411)
Boards, architectures and test suites: -------------------------------------
hi6220-hikey - arm64 * boot * kselftest * libhugetlbfs * ltp-syscalls-tests
Documentation - https://collaborate.linaro.org/display/LKFT/Email+Reports
On Fri, Sep 22, 2017 at 02:01:23PM +0000, Linaro QA wrote:
Summary
kernel: 4.4.88
Please notice two changes to the email template. First, 'make kernelversion' is listed here as 'kernel'. Second, the subject line:
4.4.88/9ee2cdb3: no regressions found in project lkft/android-hikey-linaro-4.4-oe
The format is <<kernelversion>>/<<short sha>>: <<regressions found|no regressions found>> in project <<project>>
Hopefully this is an improvement, but we know it's still not perfect. Especially, it would be nice to not use the whole project string and instead only show the important parts. For now, we chose to keep the project in the subject to make the emails unique per report. Feedback welcome,
Dan
git repo: https://android.googlesource.com/kernel/hikey-linaro git branch: android-hikey-linaro-4.4 git commit: 9ee2cdb3a43324e1f3168be8a32991c0688742f9 git describe: v4.4.88-568214-g9ee2cdb3a433 Test details: https://qa-reports.linaro.org/lkft/android-hikey-linaro-4.4-oe/build/v4.4.88...
No regressions (compared to build v4.4.87-568205-gaf1c754ce411)
Boards, architectures and test suites:
hi6220-hikey - arm64
- boot
- kselftest
- libhugetlbfs
- ltp-syscalls-tests
Documentation - https://collaborate.linaro.org/display/LKFT/Email+Reports
-- Linaro QA (beta) https://qa-reports.linaro.org _______________________________________________ Lts-dev mailing list Lts-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lts-dev
On Fri, Sep 22, 2017 at 09:33:24AM -0500, Dan Rue wrote:
On Fri, Sep 22, 2017 at 02:01:23PM +0000, Linaro QA wrote:
Summary
kernel: 4.4.88
Please notice two changes to the email template. First, 'make kernelversion' is listed here as 'kernel'. Second, the subject line:
4.4.88/9ee2cdb3: no regressions found in project lkft/android-hikey-linaro-4.4-oeThe format is <<kernelversion>>/<<short sha>>: <<regressions found|no regressions found>> in project <<project>>
Hopefully this is an improvement, but we know it's still not perfect. Especially, it would be nice to not use the whole project string and instead only show the important parts. For now, we chose to keep the project in the subject to make the emails unique per report. Feedback welcome,
That's great, but still, I don't know what "oe" means, nor do I care from a kernel point of view :)
thanks,
greg k-h
On Fri, Sep 22, 2017 at 04:56:05PM +0000, Greg KH wrote:
On Fri, Sep 22, 2017 at 09:33:24AM -0500, Dan Rue wrote:
On Fri, Sep 22, 2017 at 02:01:23PM +0000, Linaro QA wrote:
Summary
kernel: 4.4.88
Please notice two changes to the email template. First, 'make kernelversion' is listed here as 'kernel'. Second, the subject line:
4.4.88/9ee2cdb3: no regressions found in project lkft/android-hikey-linaro-4.4-oeThe format is <<kernelversion>>/<<short sha>>: <<regressions found|no regressions found>> in project <<project>>
Hopefully this is an improvement, but we know it's still not perfect. Especially, it would be nice to not use the whole project string and instead only show the important parts. For now, we chose to keep the project in the subject to make the emails unique per report. Feedback welcome,
That's great, but still, I don't know what "oe" means, nor do I care from a kernel point of view :)
If we don't mention OE then you'll see what will look like duplicate reports for each kernel version because we test each kernel with multiple architectures as well as multiple user spaces. We report /per build/, and since we have different builds for different user spaces (i.e. openembedded, aosp), and sometimes different builds for special hardware support (like 4.4 on hikey), if that data isn't included in the subject then I think it would be more confusing.
Dan
On Fri, Sep 22, 2017 at 12:14:55PM -0500, Dan Rue wrote:
On Fri, Sep 22, 2017 at 04:56:05PM +0000, Greg KH wrote:
On Fri, Sep 22, 2017 at 09:33:24AM -0500, Dan Rue wrote:
On Fri, Sep 22, 2017 at 02:01:23PM +0000, Linaro QA wrote:
Summary
kernel: 4.4.88
Please notice two changes to the email template. First, 'make kernelversion' is listed here as 'kernel'. Second, the subject line:
4.4.88/9ee2cdb3: no regressions found in project lkft/android-hikey-linaro-4.4-oeThe format is <<kernelversion>>/<<short sha>>: <<regressions found|no regressions found>> in project <<project>>
Hopefully this is an improvement, but we know it's still not perfect. Especially, it would be nice to not use the whole project string and instead only show the important parts. For now, we chose to keep the project in the subject to make the emails unique per report. Feedback welcome,
That's great, but still, I don't know what "oe" means, nor do I care from a kernel point of view :)
If we don't mention OE then you'll see what will look like duplicate reports for each kernel version because we test each kernel with multiple architectures as well as multiple user spaces. We report /per build/, and since we have different builds for different user spaces (i.e. openembedded, aosp), and sometimes different builds for special hardware support (like 4.4 on hikey), if that data isn't included in the subject then I think it would be more confusing.
I guess Greg's point is that each kernel tree (stable 4.4, stable 4.9, etc) should have a single stream of reports on qa-reports (what we call "project" in SQUAD), and boards and userspaces should be environments inside there. So you would have a single report for each update of the relevant kernel tree, and inside it you would have information about every board/userspace combination that was tested.
In practice today we have separate streams for each kernel/user space combination due to a limitation of our test infrastructure back when we started with this. Maybe it's possible to revert that now, we can chat at Connect about this.
On Fri, Sep 22, 2017 at 03:45:47PM -0300, Antonio Terceiro wrote:
On Fri, Sep 22, 2017 at 12:14:55PM -0500, Dan Rue wrote:
On Fri, Sep 22, 2017 at 04:56:05PM +0000, Greg KH wrote:
On Fri, Sep 22, 2017 at 09:33:24AM -0500, Dan Rue wrote:
On Fri, Sep 22, 2017 at 02:01:23PM +0000, Linaro QA wrote:
Summary
kernel: 4.4.88
Please notice two changes to the email template. First, 'make kernelversion' is listed here as 'kernel'. Second, the subject line:
4.4.88/9ee2cdb3: no regressions found in project lkft/android-hikey-linaro-4.4-oeThe format is <<kernelversion>>/<<short sha>>: <<regressions found|no regressions found>> in project <<project>>
Hopefully this is an improvement, but we know it's still not perfect. Especially, it would be nice to not use the whole project string and instead only show the important parts. For now, we chose to keep the project in the subject to make the emails unique per report. Feedback welcome,
That's great, but still, I don't know what "oe" means, nor do I care from a kernel point of view :)
If we don't mention OE then you'll see what will look like duplicate reports for each kernel version because we test each kernel with multiple architectures as well as multiple user spaces. We report /per build/, and since we have different builds for different user spaces (i.e. openembedded, aosp), and sometimes different builds for special hardware support (like 4.4 on hikey), if that data isn't included in the subject then I think it would be more confusing.
I guess Greg's point is that each kernel tree (stable 4.4, stable 4.9, etc) should have a single stream of reports on qa-reports (what we call "project" in SQUAD), and boards and userspaces should be environments inside there. So you would have a single report for each update of the relevant kernel tree, and inside it you would have information about every board/userspace combination that was tested.
Yes. And really, you should be testing the kernel, not any special userspace here (at least not yet), so the results _should_ all be the same no matter what userspace you run, as you are just running the same tests everywhere.
Or is there some other stuff that is "special" to "OE" that I, or anyone else here, should be caring about?
In practice today we have separate streams for each kernel/user space combination due to a limitation of our test infrastructure back when we started with this. Maybe it's possible to revert that now, we can chat at Connect about this.
Again, we don't care about userspace combinations as that's not what is changing and needs to be tested, that should be staying the same...
thanks,
greg k-h
On Fri, Sep 22, 2017 at 09:10:08PM +0200, Greg KH wrote:
On Fri, Sep 22, 2017 at 03:45:47PM -0300, Antonio Terceiro wrote:
On Fri, Sep 22, 2017 at 12:14:55PM -0500, Dan Rue wrote:
On Fri, Sep 22, 2017 at 04:56:05PM +0000, Greg KH wrote:
On Fri, Sep 22, 2017 at 09:33:24AM -0500, Dan Rue wrote:
On Fri, Sep 22, 2017 at 02:01:23PM +0000, Linaro QA wrote:
Summary
kernel: 4.4.88
Please notice two changes to the email template. First, 'make kernelversion' is listed here as 'kernel'. Second, the subject line:
4.4.88/9ee2cdb3: no regressions found in project lkft/android-hikey-linaro-4.4-oeThe format is <<kernelversion>>/<<short sha>>: <<regressions found|no regressions found>> in project <<project>>
Hopefully this is an improvement, but we know it's still not perfect. Especially, it would be nice to not use the whole project string and instead only show the important parts. For now, we chose to keep the project in the subject to make the emails unique per report. Feedback welcome,
That's great, but still, I don't know what "oe" means, nor do I care from a kernel point of view :)
If we don't mention OE then you'll see what will look like duplicate reports for each kernel version because we test each kernel with multiple architectures as well as multiple user spaces. We report /per build/, and since we have different builds for different user spaces (i.e. openembedded, aosp), and sometimes different builds for special hardware support (like 4.4 on hikey), if that data isn't included in the subject then I think it would be more confusing.
I guess Greg's point is that each kernel tree (stable 4.4, stable 4.9, etc) should have a single stream of reports on qa-reports (what we call "project" in SQUAD), and boards and userspaces should be environments inside there. So you would have a single report for each update of the relevant kernel tree, and inside it you would have information about every board/userspace combination that was tested.
Yes. And really, you should be testing the kernel, not any special userspace here (at least not yet), so the results _should_ all be the same no matter what userspace you run, as you are just running the same tests everywhere.
Or is there some other stuff that is "special" to "OE" that I, or anyone else here, should be caring about?
In practice today we have separate streams for each kernel/user space combination due to a limitation of our test infrastructure back when we started with this. Maybe it's possible to revert that now, we can chat at Connect about this.
Again, we don't care about userspace combinations as that's not what is changing and needs to be tested, that should be staying the same...
Right, we undertand. Nevertheless we will report the exact environment were the tests were executed, for the sake of completeness.
Collapsing these reports into a single stream requires some effort and coordination on the infra side, however we are working on it. Bear with me for now.
On Fri, Sep 22, 2017 at 03:45:47PM -0300, Antonio Terceiro wrote:
On Fri, Sep 22, 2017 at 12:14:55PM -0500, Dan Rue wrote:
On Fri, Sep 22, 2017 at 04:56:05PM +0000, Greg KH wrote:
That's great, but still, I don't know what "oe" means, nor do I care from a kernel point of view :)
If we don't mention OE then you'll see what will look like duplicate reports for each kernel version because we test each kernel with
I guess Greg's point is that each kernel tree (stable 4.4, stable 4.9, etc) should have a single stream of reports on qa-reports (what we call "project" in SQUAD), and boards and userspaces should be environments
As I've *repeatedly* suggested you should really not be trying to report the information about the userspace distro in the same string as the kernel version, it just looks like you're doing some weird kernel version. I thought we'd come to a good conclusion on how to redo the subjects to make this clearer in discussion last week.
On Mon, Sep 25, 2017 at 04:55:07PM +0100, Mark Brown wrote:
On Fri, Sep 22, 2017 at 03:45:47PM -0300, Antonio Terceiro wrote:
On Fri, Sep 22, 2017 at 12:14:55PM -0500, Dan Rue wrote:
On Fri, Sep 22, 2017 at 04:56:05PM +0000, Greg KH wrote:
That's great, but still, I don't know what "oe" means, nor do I care from a kernel point of view :)
If we don't mention OE then you'll see what will look like duplicate reports for each kernel version because we test each kernel with
I guess Greg's point is that each kernel tree (stable 4.4, stable 4.9, etc) should have a single stream of reports on qa-reports (what we call "project" in SQUAD), and boards and userspaces should be environments
As I've *repeatedly* suggested you should really not be trying to report the information about the userspace distro in the same string as the kernel version, it just looks like you're doing some weird kernel version. I thought we'd come to a good conclusion on how to redo the subjects to make this clearer in discussion last week.
Yes, we got it. It's just not as simple as changing a subject line to make this change, but we will get there.
On Tue, Sep 26, 2017 at 08:56:34AM -0700, Antonio Terceiro wrote:
On Mon, Sep 25, 2017 at 04:55:07PM +0100, Mark Brown wrote:
As I've *repeatedly* suggested you should really not be trying to report the information about the userspace distro in the same string as the kernel version, it just looks like you're doing some weird kernel version. I thought we'd come to a good conclusion on how to redo the subjects to make this clearer in discussion last week.
Yes, we got it. It's just not as simple as changing a subject line to make this change, but we will get there.
So what are the other changes you're talking about here, do they replace or add to what was discussed?
On Tue, Sep 26, 2017 at 02:24:43PM -0700, Mark Brown wrote:
On Tue, Sep 26, 2017 at 08:56:34AM -0700, Antonio Terceiro wrote:
On Mon, Sep 25, 2017 at 04:55:07PM +0100, Mark Brown wrote:
As I've *repeatedly* suggested you should really not be trying to report the information about the userspace distro in the same string as the kernel version, it just looks like you're doing some weird kernel version. I thought we'd come to a good conclusion on how to redo the subjects to make this clearer in discussion last week.
Yes, we got it. It's just not as simple as changing a subject line to make this change, but we will get there.
So what are the other changes you're talking about here, do they replace or add to what was discussed?
Right now we have separate jenkins jobs that submit data to separate projects on SQUAD. So we need to unify the data on SQUAD, or just rename one of the projects and discard the other, and change the jenkins jobs to submit to submit to a single place.
If we simply changed the subjects to match, we would get duplicate notifications with the exact same subject, because ATM we have two independent projects submitting email reports.
-
Antonio Terceiro -
Dan Rue -
Greg KH -
Linaro QA -
Mark Brown