To be able to report issues upstream, we should collect the TAP output of lttng, at least when one of the test fails.
High unassigned. This isn't good. CCing some Wind River people who may be able to help.
Technically an enhancement but we need the info to deal with AB INT problems.
kindly like to ask what a AB INT problem is? And if there are more information about the problem.
Those are intermittent issues that we see on the autobuilders. lttng ptests are failing often and we need to understand whether this is caused by the infrastructure or an issue in the image we build.
The bug tracking the occurrences is 14263
For the lazy: https://bugzilla.yoctoproject.org/show_bug.cgi?id=14263
And the other one is https://bugzilla.yoctoproject.org/show_bug.cgi?id=14854
I did make some progress on this whilst trying to fix a different issue: https://git.yoctoproject.org/poky/commit/?id=2ea27691aa57951aaba3cc1714a080a112d15408 which now captures more info for lttng-tools. Whether it is enough, not sure. I also realised we could do something similar in attr/acl: https://git.yoctoproject.org/poky/commit/?id=2c948fa0250b765bc5f2fbe63c82258601cc77ff
Patches in review I hear.
Patches activating failed ptests artifacts retrieval have been merged and now allows to get ptests files when the corresponding test fails. As an example with a failing valgrind ptest: - https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/6099 - https://autobuilder.yocto.io/pub/non-release/20240218-3/testresults/qemuarm64-ptest/artifacts/usr/lib/valgrind/ptest/ So LTTNG files should also be retrieved on failure now. We could even remove the customizations made by Richard in LTTNG ptest runner. I will wait a few days for any feedback about how it works, and if no issue is raised, I will close the this.