stable-rc unknown short version/: no regressions found in project stable v4.9.y on OE - sanity
Summary ------------------------------------------------------------------------
git repo: not informed git branch: not informed git commit: not informed git describe: not informed Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.9-oe-sanity/build/v4.9....
No regressions (compared to build v4.9.171-42-ga707069e56d0)
No fixes (compared to build v4.9.171-42-ga707069e56d0)
Boards, architectures and test suites: -------------------------------------
hi6220-hikey * build - pass: 1,
On Thu, May 02, 2019 at 08:56:59AM +0000, Linaro QA wrote:
Summary
git repo: not informed git branch: not informed git commit: not informed git describe: not informed Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.9-oe-sanity/build/v4.9....
No regressions (compared to build v4.9.171-42-ga707069e56d0)
No fixes (compared to build v4.9.171-42-ga707069e56d0)
Boards, architectures and test suites:
hi6220-hikey
- build - pass: 1,
What does this email mean?
confused,
greg k-h
On Thu, May 02, 2019 at 11:04:38AM +0200, Greg KH wrote:
On Thu, May 02, 2019 at 08:56:59AM +0000, Linaro QA wrote:
Summary
git repo: not informed git branch: not informed git commit: not informed git describe: not informed Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.9-oe-sanity/build/v4.9....
No regressions (compared to build v4.9.171-42-ga707069e56d0)
No fixes (compared to build v4.9.171-42-ga707069e56d0)
Boards, architectures and test suites:
hi6220-hikey
- build - pass: 1,
What does this email mean?
Oh, interesting. It's a timing bug related to the change to add build statuses to qa-reports and -sanity runs. The sanity runs are set to send a notification if qa-reports doesn't see any additional data in 5 minutes. In this case, the hikey build finished 11 minutes earlier than the others, and so qa-reports fired its notification before it knew about any other builds or tests - and since it gets all the metadata from the tests, all the fields above are defaulted/unknown.
I'll change the threshold to handle this case. There is still a problem though - if all of the builds fail, the emails will also lack metadata, so I'll look and see how difficult it will be to add the git metadata into the build callback.
Dan
On Thu, May 02, 2019 at 08:32:34AM -0500, Dan Rue wrote:
On Thu, May 02, 2019 at 11:04:38AM +0200, Greg KH wrote:
On Thu, May 02, 2019 at 08:56:59AM +0000, Linaro QA wrote:
Summary
git repo: not informed git branch: not informed git commit: not informed git describe: not informed Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.9-oe-sanity/build/v4.9....
No regressions (compared to build v4.9.171-42-ga707069e56d0)
No fixes (compared to build v4.9.171-42-ga707069e56d0)
Boards, architectures and test suites:
hi6220-hikey
- build - pass: 1,
What does this email mean?
Oh, interesting. It's a timing bug related to the change to add build statuses to qa-reports and -sanity runs. The sanity runs are set to send a notification if qa-reports doesn't see any additional data in 5 minutes. In this case, the hikey build finished 11 minutes earlier than the others, and so qa-reports fired its notification before it knew about any other builds or tests - and since it gets all the metadata from the tests, all the fields above are defaulted/unknown.
I'll change the threshold to handle this case. There is still a problem though - if all of the builds fail, the emails will also lack metadata, so I'll look and see how difficult it will be to add the git metadata into the build callback.
Thanks for the explaination, makes sense.
greg k-h
-
Dan Rue -
Greg KH -
Linaro QA