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