Skip to contentSkip to conversation

Fix regression reporting for master-next

PATCH Alexis Lothoré 1 participant 1 message Oct 11, 2023 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw
Quoted 2 lines · Alexis Lothoré via lists.openembedded.org

With those two patches, I have been able to properly generate the regression report from [1] with the following command:

It looks like I forgot to paste the relevant command. Here it is, for documentation purpose:
yocto_testresults_query.py regression-report 561c63e94710a755227357e90004aafa63ec9c7e 2994f51ffc4699970abed42d2e2a6452d04128cd

With 2994f51ffc4699970abed42d2e2a6452d04128cd being the SHA-1 of master-next HEAD at time of sending this series. But the command may not work anymore as-it-is, because master-next has likely been force-pushed since then

Quoted 1 line

[1] https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/6025/steps/29/logs/stdio

Signature · 3 lines
Alexis Lothoré, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com