Running gtester-report on gtester output raises KeyError
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| GLib |
Fix Released
|
Medium
|
|||
| glib2.0 (Ubuntu) |
Triaged
|
Low
|
Unassigned | ||
Bug Description
I'm trying to set up some unit tests on a bunch of C code I'm writing, and decided to use GLib's testing framework.
Running the tests using "gtester test-executable -o output.xml" runs okay, but running gtester-report to generate a html report raises an error. The output is:
...
At the beginning, it outputs valid html, until the beginning of the <body> tag:
...
<body>
<h2>GTester Unit Test Report</h2>
Traceback (most recent call last):
File "/usr/bin/
main()
File "/usr/bin/
HTMLReportW
File "/usr/bin/
self.
File "/usr/bin/
self.oprint ('<h3>Package: %(package)s, version: %(version)s</h3>\n' % self.info)
KeyError: 'package'
| Jason Conti (jconti) wrote | #1 |
| Changed in glib2.0 (Ubuntu): | |
| status: | New → Confirmed |
| Changed in glib: | |
| importance: | Unknown → Medium |
| status: | Unknown → New |
| Changed in glib2.0 (Ubuntu): | |
| importance: | Undecided → Low |
| status: | Confirmed → Triaged |
| Changed in glib: | |
| status: | New → Confirmed |
| Changed in glib: | |
| status: | Confirmed → Fix Released |
Thanks for the bug report. I found an upstream bug here: https:/
You can workaround the issue by manually adding:
<info>
<package>
<version>
<revision>
</info>
to the generated xml. It seems that is exactly what glib does, to collect multiple reports together. (See Makefile.decl in the glib source)