After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 668040 - gtester-report ignores <message> tags
gtester-report ignores <message> tags
Status: RESOLVED DUPLICATE of bug 592419
Product: glib
Classification: Platform
Component: general
2.30.x
Other Linux
: Normal normal
: ---
Assigned To: gtkdev
gtkdev
Depends on:
Blocks:
 
 
Reported: 2012-01-16 18:16 UTC by Paolo Bonzini
Modified: 2013-02-03 05:38 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Paolo Bonzini 2012-01-16 18:16:04 UTC 
The output of gtester is not enough to reconstruct a complete picture of the test run.

$ gtester --verbose -o bar.xml ./check-qlist
TEST: ./check-qlist... (pid=18603)
  /public/new:                                                         OK
  /public/append:                                                      OK
  /public/to_qlist:                                                    OK
  /public/destroy:                                                     OK
  /public/iter:                                                        OK
$ grep OK bar.xml
$
Comment 1 Paolo Bonzini 2012-01-18 16:16:53 UTC 
Sorry for the bad description.  The subject should say it all though.
Comment 2 Matthias Clasen 2012-01-21 00:37:48 UTC 
Not exactly sure what you mean with <message> tags ?
Maybe grep for "success" instead of "OK" ?
Comment 3 Paolo Bonzini 2012-01-21 07:58:38 UTC 
No, the description was screwed up; I didn't really understand what was going on.  The problem is that what I write with g_test_message or with gtest's log handler ends up in the .xml file as <message> tags, but then is completely ignored by gtester-report when creating the HTML.  Only <error> tags go into the output.
Comment 4 Matthias Clasen 2013-02-03 05:38:14 UTC 

*** This bug has been marked as a duplicate of bug 592419 ***