John Anderson wrote:
I'd like to see a log that make it obvious what the error was and
which test caused it.
If the current tinderbox mechanism can't do that -- because of bugs,
limitations, features, etc. as described below -- perhaps we need to
think about how to change the way tinderbox works so that it can
correctly report errors and make them obvious.
John
John,
There is a problem where sometimes the functional test logs don't appear
at all, but when it works, the functional tests will report test
failures like this:
Suite ""ChandlerFunctionalTestSuite"" Failed :: Total Time ""0:06:24.017526"" :: Comment
""None""
<http://builds.osafoundation.org/tinderbox/tbox/gunzip.cgi?tree=Chandler&full-log=1158688105.32168#err6> Test
""TestRecurrenceImporting"" Failed :: Total Time ""0:00:05.560951"" :: Comment ""None
<http://builds.osafoundation.org/tinderbox/tbox/gunzip.cgi?tree=Chandler&full-log=1158688105.32168#err7> Action
""Check_ItemSelected"" Failed :: Total Time ""0:00:00.000156"" :: Comment ""(On Selection Checking)
- item named Weekly Never End is not selected""
<http://builds.osafoundation.org/tinderbox/tbox/gunzip.cgi?tree=Chandler&full-log=1158688105.32168#err8> Report
""(On Selection Checking) - item named Weekly Never End is not selected"" Failed :: Comment
""None""
<http://builds.osafoundation.org/tinderbox/tbox/gunzip.cgi?tree=Chandler&full-log=1158688105.32168#err9>
if there is a stack trace it will be above this message and below this
message will be a list of the pass/ fail status of all tests. Is this
clear enough for you what the error is or are you asking for something more?
Obviously the problem where the logs don't appear at all also needs to
be fixed.
Dan
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
