| Message ID | 20231208215915.225182-1-alexis.lothore@bootlin.com |
|---|---|
| Headers | show |
| Series | fix mickledore tests reports | expand |
Mickledore is already end-of-life, so no further builds are scheduled. There is a dunfell release that I plan to build this weekend, so a patchset for dunfell would be much appreciated if you would like me to test it with the 3.1.30 build. And a kirkstone release is due shortly thereafter, so we also need it there too! Thanks for looking into this! Steve On Fri, Dec 8, 2023 at 11:59 AM Alexis Lothoré via lists.yoctoproject.org <alexis.lothore=bootlin.com@lists.yoctoproject.org> wrote: > > Hello, > mickledore release 4.2.4-rc3 suffered some tests reporting issue (tests > result not pushed, regression report not generated, etc). This is due to > the fact that the mickledore branch is not properly described in > BUILD_HISTORY_DIRECTPUSH in config.json. This issue has already received > the following fixes: > - add the missing mickledore entry > - then replaced the quickfix with a rework on BUILD_HISTORY_DIRECTPUSH to > prevent the issue from occuring on any new future release branch > > While those fixes made it to any release since Nanbield, we forgot to > backport it on yocto-autobuilder-helper, so the fixed issue still occurs on > this branch > > This series brings the minimal set of patches to be backported **on top of > mickledore branch** on yocto-autobuilder-helper. This is from a bare > cherry-pick session with minimal conflict fixes, and commit tags untouched > > Alexis Lothoré (3): > scripts/utils.py: replace BUILD_HISTORY_DIRECTPUSH with hardcoded > condition > config.json: remove BUILD_HISTORY_DIRECTPUSH > scripts/test_utils.py: update test after BUILD_HISTORY_DIRECTPUSH > removal > > config.json | 1 - > scripts/test_utils.py | 29 +++++++---------------------- > scripts/utils.py | 13 +++++++++++-- > 3 files changed, 18 insertions(+), 25 deletions(-) > > -- > 2.42.1 > > > -=-=-=-=-=-=-=-=-=-=-=- > Links: You receive all messages sent to this group. > View/Reply Online (#61845): https://lists.yoctoproject.org/g/yocto/message/61845 > Mute This Topic: https://lists.yoctoproject.org/mt/103064175/3620601 > Group Owner: yocto+owner@lists.yoctoproject.org > Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [steve@sakoman.com] > -=-=-=-=-=-=-=-=-=-=-=- >
Hello Steve, On 12/8/23 23:39, Steve Sakoman wrote: > Mickledore is already end-of-life, so no further builds are scheduled. Ah, yes, I checked that before sending because I had a doubt about whether this series would still be useful on top of mickledore, but since the 4.2.4.rc3 is still in progress, I was not sure. So ok, feel free to drop this series. > There is a dunfell release that I plan to build this weekend, so a > patchset for dunfell would be much appreciated if you would like me to > test it with the 3.1.30 build. > > And a kirkstone release is due shortly thereafter, so we also need it there too! I am not sure that a backport is really needed on dunfell and kirkstone, because - "dunfell" is properly described in BUILD_HISTORY_DIRECTPUSH in config.json, on dunfell branch - "kirkstone" is properly described in BUILD_HISTORY_DIRECTPUSH in config.json, on kirkstone branch (so yes, the issue was really affecting mickledore specifically) Anyway, the wider issue is that those branches are lacking almost all developments I did since ~January on send-qa-email, so some things may work (test results storage), some other may not (regression reports based on those results). It is also true for poky. A whole backport is of course possible, but that would definitely need some thorough testing before using it for releases. Kind regards, Alexis
Hello, mickledore release 4.2.4-rc3 suffered some tests reporting issue (tests result not pushed, regression report not generated, etc). This is due to the fact that the mickledore branch is not properly described in BUILD_HISTORY_DIRECTPUSH in config.json. This issue has already received the following fixes: - add the missing mickledore entry - then replaced the quickfix with a rework on BUILD_HISTORY_DIRECTPUSH to prevent the issue from occuring on any new future release branch While those fixes made it to any release since Nanbield, we forgot to backport it on yocto-autobuilder-helper, so the fixed issue still occurs on this branch This series brings the minimal set of patches to be backported **on top of mickledore branch** on yocto-autobuilder-helper. This is from a bare cherry-pick session with minimal conflict fixes, and commit tags untouched Alexis Lothoré (3): scripts/utils.py: replace BUILD_HISTORY_DIRECTPUSH with hardcoded condition config.json: remove BUILD_HISTORY_DIRECTPUSH scripts/test_utils.py: update test after BUILD_HISTORY_DIRECTPUSH removal config.json | 1 - scripts/test_utils.py | 29 +++++++---------------------- scripts/utils.py | 13 +++++++++++-- 3 files changed, 18 insertions(+), 25 deletions(-)