Bug 5189 - no full path for output files information
Summary: no full path for output files information
Status: VERIFIED FIXED
Alias: None
Product: Toaster
Classification: Build System, Metadata & Runtime
Component: toaster (show other bugs)
Version: 1.5
Hardware: All Multiple
: Medium normal
Target Milestone: 1.6
Assignee: Cristiana Voicu
QA Contact:
URL:
Whiteboard: oecore
Depends on: 5269
Blocks: 5453
  Show dependency tree
 
Reported: 2013-09-13 14:13 UTC by Belen Barros Pena
Modified: 2014-03-25 14:47 UTC (History)
4 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 Belen Barros Pena 2013-09-13 14:13:19 UTC
If a build includes an image recipe between its targets, we need to collect the full path to the output rootfs files. I can't find this information anywhere at the moment.
Comment 1 Belen Barros Pena 2013-09-13 14:42:39 UTC
webhob-poky/master:aa7bec2e9dffd6901ebe3accf748ce458d1481a3
Comment 2 Belen Barros Pena 2013-09-18 11:10:15 UTC
I think this is the file_name in the targets API
Comment 3 Alexandru Damian 2013-11-05 16:33:02 UTC
Please check the event MetadataEvent("ImageFileSize") that contains all the needed infos.
Comment 4 Cristiana Voicu 2013-11-06 12:48:06 UTC
Belen, can you please tell me where should I place this info in UI? Also for the size, because it is related.
Thanks!
Comment 5 Belen Barros Pena 2013-11-06 13:26:08 UTC
In the simple interface, this information lives in /simple/builds/. It is used to generate the information in the "output" column (which should show only the file extension, as it does now).

In the 'real' interface, it will show in a similar manner in the builds table:

http://www.yoctoproject.org/toaster/index.html

and in the build dashboard:

http://www.yoctoproject.org/toaster/build-dashboard.html
Comment 6 Cristiana Voicu 2013-11-12 14:01:08 UTC
I implemented this using  MetadataEvent("ImageFileSize"), but the issue is that if rootfs task is not executed (because it is in cache), this event is not triggered. This is issue exposed in bug #5269, for do_package.

Is there any other way to find output files?
Thanks,
Cristiana
Comment 7 Cristiana Voicu 2014-03-11 14:02:38 UTC
patch sent on the toaster ml
Comment 9 Belen Barros Pena 2014-03-18 12:35:41 UTC
file_name and file_size information is being collected for a .rootfs.manifest file that is created in /build/tmp/deploy/images/ for each image recipe built.

We would like not to collect this. After talking to Alex, his suggested solution is to cross check the information gathered for file_name with the content of the IMAGE_FSTYPES variable. If any of the file_name entries does not match the content of IMAGE_FSTYPES, we do not store it.
Comment 10 Cristiana Voicu 2014-03-18 16:27:15 UTC
patch sent to toaster ml
Comment 12 Belen Barros Pena 2014-03-25 14:47:12 UTC
verified in master:478f1b7afe46c0d6328d4b8db1d32e22aef6759d