You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally reported byChris Adams (Bitbucket: acdha, GitHub: acdha)
I ran into an odd problem using the coverage XML report on our Hudson CI server. It turns out that the xml report will generate inconsistent filenames based on the configuration.
If you call xml_report with a list of module names (e.g. "proj.submod") like this:
Originally reported by Chris Adams (Bitbucket: acdha, GitHub: acdha)
I ran into an odd problem using the coverage XML report on our Hudson CI server. It turns out that the xml report will generate inconsistent filenames based on the configuration.
If you call xml_report with a list of module names (e.g. "proj.submod") like this:
the XML will be generated with module names in the filename attribute:
If you instead filter the report using something like include/omit_prefixes:
the XML will have real filesystem paths in the filename attribute:
The text was updated successfully, but these errors were encountered: