Standard output of the Chip Tool command not in test artifacts

[farshidtz]

Looking at the latest run here, I noticed that the chip-tool logs produced as artifacts only include the journal logs. The standard output of the Chip Tool command isn't collected.

Originally posted by @farshidtz in #31 (comment)

[MonicaisHer]

Where is the best place to output the chip tool command's stdout? Directly in the chip-tool test suite when calling utils.Exec(), or as part of the utils .exec()?

[farshidtz]

Where is the best place to output the chip tool command's stdout? Directly in the chip-tool test suite when calling utils.Exec(), or as part of the utils .exec()?

The issue isn't about printing the logs. The utils.exec function executes the command and returns the logs. It already supports printing of the log stream.

[MonicaisHer]

There are two places where the stdout log can be exported—either on the chip-tool test side or on the matter-snap-testing side (similar to SnapDumpLogs). It could probably be placed on the matter-snap-testing side for reusability. However, the current Matter snaps (OTBR snap and GPIO snap) already collect all the syslog using SnapDumpLogs.