Bug 13331 - resulttool log command doesn't work as expected
Summary: resulttool log command doesn't work as expected
Status: RESOLVED FIXED
Alias: None
Product: Tooling
Classification: QA/Testing
Component: tooling (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: High normal
Target Milestone: ---
Assignee: Joshua Watt
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks: 13327
  Show dependency tree
 
Reported: 2019-05-02 14:02 UTC by Richard Purdie
Modified: 2024-01-23 13:52 UTC (History)
2 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 Richard Purdie 2019-05-02 14:02:12 UTC
I'd expected the "resulttool log" command would default to generating the log files the store command generates into the current working directory, maybe printing to stdout a list of the files its created. It doesn't currently do this.

If viewing a specific file was required, that could be an extra parameter specifying to log file to view?

The "write" behavior could trigger off the command "resulttool log write X" where X was the output directory instead of cwd?
Comment 2 Joshua Watt 2019-05-10 02:10:32 UTC
Fix 9a97ea263c571b27283c59e69c880df0fa094052