platforms/contents.xml.in: fix Crashscope 'Unsupported' error for Nightly builds - #149
platforms/contents.xml.in: fix Crashscope 'Unsupported' error for Nightly builds#149vivpuar wants to merge 1 commit into
Conversation
…htly builds Crashscope fails to recognize the products in Nightly builds and reports 'Unsupported' because contents.xml.in is missing the required <hlos_type> tag. Add '<hlos_type cmm_var="HLOS_TYPE">LE</hlos_type>' to contents.xml.in for all targets to ensure Crashscope can properly recognize and parse the products. Signed-off-by: Vivek Puar <vpuar@qti.qualcomm.com>
| </product_flavors> | ||
| <product_info> | ||
| <product_name>Glymur.LE.0.0</product_name> | ||
| <hlos_type cmm_var="HLOS_TYPE">LE</hlos_type> |
There was a problem hiding this comment.
What are the other options for this variable? Also, why is hlos type being repeated twice (as a tag name and as an attribute contentes).
There was a problem hiding this comment.
This entry is part of the META's contents.xml file, will ask target team's POC for more details and get back
There was a problem hiding this comment.
Dmitry Baryshkov (@lumag) I checked internally and this is the response I got.
"Other options for the variable can be any HLOS type like “LE/LA/WP/QNX/WA”. This is how HLOS tag is defined in all meta builds."
There was a problem hiding this comment.
You missed the second part of the question. Also, why is the build type important? What is the difference between e.g. LE and LA builds from the crash dump point of view?
2 participants
Crashscope fails to recognize the products in Nightly builds and reports 'Unsupported' because contents.xml.in is missing the required <hlos_type> tag. Add '<hlos_type cmm_var="HLOS_TYPE">LE</hlos_type>' to contents.xml.in for all targets to ensure Crashscope can properly recognize and parse the products.