[root@...1070...: [Inkscape-tester] inkscape build report]
The errors are gone now. :-)
----- Forwarded message from root <root@...1070...> -----
Date: Wed, 05 Apr 2006 05:22:15 -0700 From: root <root@...1070...> To: inkscape-tester@lists.sourceforge.net Subject: [Inkscape-tester] inkscape build report
= Analysis Report for inkscape = Report Time: Wed Apr 5 05:11:42 2006 (Run 1900) Snapshot: inkscape-20060405-0400.tar.bz2 Status: finished
Platform Unpack Config Build Install WRNS ERRS ------------------------------------------------------------------------ debian x86 0 0 0 0 12 0
Test Status Score Info ------------------------------------------------------------------------ sut-1 ??
== Errors ==
none
== Warnings ==
sp-flowtext.cpp:324: warning: `sp_item_bbox_desktop' is deprecated (declared at sp-item.h:215) sp-image.cpp:516:8: warning: extra tokens at end of #endif directive sp-item.cpp:730: warning: `sp_item_bbox_desktop' is deprecated (declared at sp-item.cpp:719) sp-shape.cpp:611: warning: `sp_item_bbox_desktop' is deprecated (declared at sp-item.h:215) sp-text.cpp:472: warning: `sp_item_bbox_desktop' is deprecated (declared at sp-item.h:215) dialogs/export.cpp:644: warning: `sp_item_bbox_desktop' is deprecated (declared at sp-item.h:215) dialogs/export.cpp:723: warning: `sp_item_bbox_desktop' is deprecated (declared at sp-item.h:215) display/canvas-arena.cpp:85: warning: invalid access to non-static data member `SPCanvasArenaClass::arena_event' of NULL object display/canvas-arena.cpp:85: warning: (perhaps the `offsetof' macro was used incorrectly) display/sp-canvas.cpp:132: warning: invalid access to non-static data member `SPCanvasItemClass::event' of NULL object display/sp-canvas.cpp:132: warning: (perhaps the `offsetof' macro was used incorrectly) trace/trace.cpp:196: warning: unused variable `Inkscape::XML::Node*imgRepr'
== Environment Summary ==
------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&da... _______________________________________________ Inkscape-tester mailing list Inkscape-tester@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-tester
----- End forwarded message -----
On Wed, Apr 05, 2006 at 05:03:20PM -0400, MenTaLguY wrote:
Test Status Score Info
sut-1 ??
Incidentally, now that Jon's been fixing up the unit testing situation, is there any chance we can get our unit tests hooked up here?
Yeah definitely. Actually, I'd hooked `make check` up a long time ago, it's strange that this isn't showing up in the reports. I'll tinker with it some more.
Oh, the other thing is that I figure you won't want to see the raw output of the make check command, so there needs to be a parser to summarize it. Do you have an opinion on how this report should look? (E.g., do you want to see just the fails, or both fails plus passes? Do you want to see details about the fails, or just a link to the results?)
Bryce
On Apr 13, 2006, at 11:37 AM, Bryce Harrington wrote:
Oh, the other thing is that I figure you won't want to see the raw output of the make check command, so there needs to be a parser to summarize it. Do you have an opinion on how this report should look? (E.g., do you want to see just the fails, or both fails plus passes? Do you want to see details about the fails, or just a link to the results?)
Once things switch to CxxTest, the output will be a bit different.
By default, successful tests generate a single '.'. When things fail or warn, then more is emitted. Also, if any asserts actually fail, the unit test program will exit with non-zero
On Thu, Apr 13, 2006 at 08:27:26PM -0700, Jon A. Cruz wrote:
On Apr 13, 2006, at 11:37 AM, Bryce Harrington wrote:
Oh, the other thing is that I figure you won't want to see the raw output of the make check command, so there needs to be a parser to summarize it. Do you have an opinion on how this report should look? (E.g., do you want to see just the fails, or both fails plus passes? Do you want to see details about the fails, or just a link to the results?)
Once things switch to CxxTest, the output will be a bit different.
By default, successful tests generate a single '.'. When things fail or warn, then more is emitted. Also, if any asserts actually fail, the unit test program will exit with non-zero
Hmm, well from my end I wouldn't see the individual unit test program exit statuses - I just see the exit code from make, plus whatever output gets emitted. For tracking purposes, it would actually be preferrable to see the test name and its status reported. If it just prints out '.' then it might be difficult to verify that a given unit test ran, and potentially could lead to some ambiguity if, for instance, a failed test printed an error message with periods in it.
Do you have an example of what the CxxTest output looks like? Also, if the test system is going to get reimplemented, then it sounds like it would not be worth the time to finish hooking up to the current tests?
Bryce
participants (3)
-
Bryce Harrington -
Jon A. Cruz -
MenTaLguY