Bug 14901 - lttng: collect TAP output
Summary: lttng: collect TAP output
Status: RESOLVED FIXED
Alias: None
Product: Package Testing (ptest)
Classification: QA/Testing
Component: ptest (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: High enhancement
Target Milestone: 5.1
Assignee: Alexis Lothoré
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2022-08-19 09:50 UTC by Alexandre Belloni
Modified: 2024-02-22 16:02 UTC (History)
7 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexandre Belloni 2022-08-19 09:50:54 UTC
To be able to report issues upstream, we should collect the TAP output of lttng, at least when one of the test fails.
Comment 1 Randy MacLeod 2022-08-25 14:44:22 UTC
High unassigned. This isn't good. CCing some Wind River people who may be able to help.
Comment 2 Randy MacLeod 2022-08-25 14:49:23 UTC
Technically an enhancement but we need the info to deal with AB INT problems.
Comment 3 Thomas Roos 2022-09-01 12:45:25 UTC
kindly like to ask what a AB INT problem is?
And if there are more information about the problem.
Comment 4 Alexandre Belloni 2022-09-01 12:59:23 UTC
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.
Comment 5 Alexandre Belloni 2022-09-01 13:00:13 UTC
The bug tracking the occurrences is 14263
Comment 6 Tim Orling 2022-09-29 14:39:09 UTC
For the lazy:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=14263
Comment 7 Alexandre Belloni 2022-09-29 21:59:49 UTC
And the other one is
https://bugzilla.yoctoproject.org/show_bug.cgi?id=14854
Comment 8 Richard Purdie 2023-03-14 08:11:20 UTC
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
Comment 9 Randy MacLeod 2023-06-08 15:14:28 UTC
Patches in review I hear.
Comment 10 Alexis Lothoré 2024-02-20 09:37:43 UTC
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.