Some failures have been observed on jobs targeting master-next, with the following logs as an example:
Exception: No reference found for commit 3edb9acca18171894771c36c19b0c2e905852ce5 in /tmp/sendqaemail.dkwg__g9 See [1] for more logs, which is trying to compare master-next results to master results. While master-next results necessarily exist (because they have been generated in the very same build presenting the error), it may not be true for master: current HEAD of master may not have been the object of a build generating test results. To fix that, this series propose to stop blindly searching for test results corresponding to current HEAD on master: instead it reads HEAD on master branch of test results respository, and extract corresponding Poky revision from it, so we are sure that selected revision in Poky is the most recent AND have corresponding tests results The actual fix is in last commits: the first commit aims to re-clarify the naming used for revisions used to comparision, and the second commit is a small refactoring [1] https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/5973/steps/31/logs/stdio Alexis Lothoré (3): scripts/send_qa_email: re-clarify base and target revisions scripts/send-qa-email: define tests results repository url only once scripts/send_qa_email: guess latest tested revision when dealing with branch scripts/send_qa_email.py | 61 ++++++++++++++++++++++------------- scripts/test_send_qa_email.py | 31 ++++++++++-------- scripts/utils.py | 6 ++-- 3 files changed, 58 insertions(+), 40 deletions(-) -- 2.42.0
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#61230): https://lists.yoctoproject.org/g/yocto/message/61230 Mute This Topic: https://lists.yoctoproject.org/mt/101751693/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-