At 05:20 PM 3/8/2005, you wrote:
I concur that the problem is now fixed. Yay!
I sort of spoke to soon. I found a couple more issues. By the way.. the
reason why I'm so interested in Jblanket all of a sudden is because I have
to upgrade another large system that uses Jblanket by every developer in
every build. So, I want to ensure that things are ok before starting the
upgrade process.
Each of these problems were check on two different computers.
Problem 1.
Error in the JBlanket Report:
[echo] (hackyBuildUtils) Sending JUnit data to hackystat.
[jblanketreport] [Fatal Error] COVER-MethodSets.xml:86:88: The value of
attribut
e "method" associated with an element type "Method" must not contain the
'<' character.
[jblanketreport] csdl.jblanket.JBlanketException: Unable to transform XML
to HTML
[jblanketreport] at
csdl.jblanket.report.AggregateTransformer.transformXmlToHtml(AggregateTransformer.java:270)
[jblanketreport] at
csdl.jblanket.report.JBlanketReport.createReport(JBlanketReport.java:226)
[jblanketreport] at
csdl.jblanket.report.JBlanketReport.main(JBlanketReport.java:551)
[jblanketreport] at
csdl.jblanket.ant.JBlanketReportTask.execute(JBlanketReportTask.java:270)
[jblanketreport] at
org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
[jblanketreport] at org.apache.tools.ant.Task.perform(Task.java:364)
[jblanketreport] at org.apache.tools.ant.Target.execute(Target.java:341)
[jblanketreport] at
org.apache.tools.ant.Target.performTasks(Target.java:369)
[jblanketreport] at
org.apache.tools.ant.Project.executeTarget(Project.java:1214)
[jblanketreport] at
org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:386)
[jblanketreport] at
org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
[jblanketreport] at org.apache.tools.ant.Task.perform(Task.java:364)
[jblanketreport] at org.apache.tools.ant.Target.execute(Target.java:341)
[jblanketreport] at
org.apache.tools.ant.Target.performTasks(Target.java:369)
[jblanketreport] at
org.apache.tools.ant.Project.executeTarget(Project.java:1214)
[jblanketreport] at
org.apache.tools.ant.Project.executeTargets(Project.java:1062)
[jblanketreport] at org.apache.tools.ant.Main.runBuild(Main.java:673)
[jblanketreport] at org.apache.tools.ant.Main.startAnt(Main.java:188)
[jblanketreport] at
org.apache.tools.ant.launch.Launcher.run(Launcher.java:196)
[jblanketreport] at
org.apache.tools.ant.launch.Launcher.main(Launcher.java:55)
[jblanketreport] Caused by: org.xml.sax.SAXParseException: The value of
attribute
"method" associated with an element type "Method" must not contain the '<'
character.
[jblanketreport] at
org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
[jblanketreport] at
org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
[jblanketreport] at
javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:151)
[jblanketreport] at
csdl.jblanket.report.AggregateTransformer.transformXmlToHtml(AggregateTransformer.java:253)
[jblanketreport] ... 19 more
BUILD FAILED
C:\java\cvs\hackyBuild\build.xml:490: The following error occurred while
executing this line:
C:\java\cvs\hackyBuild\build.utils.xml:611: Error in JBlanket report.
There many entries that look like the following that are causing the problems:
<untestable>
<Method
class="org.hackystat.app.commit.dailyproject.DailyProjectCommit"
method="<clinit>"/>
</untestable>
--------------------------------------------------
Problem 2.
When I sent a previous email, stating that "I concurred that the problem
was fixed" I didn't do a junitAll. Philip did you do one?
Here is another problem that I've found. this is major a one. I've noticed
that when I enable Jblanket the building and testing (freshStart junitAll)
there is an significant increase (more than 80 minutes on my brand new 3.4
Ghz computer) in the testing time. Here is my supporting data.
I built these modules:
hackyKernel.available=true
hackyStatistics.available=true
hackyReport.available=true
hackyStdExt.available=true
hackyTelemetry.available=true
hackyReview.available=true
hackyVCS.available=true
hackyIssue.available=true
hackyDependency.available=true
hackyPRI.available=true
-------------
With JBlanket Disabled:
Aaron's new Dell Desktop:
- freshStart junitAll = 10 minutes and 44 seconds
- see the attached file, NoJblanket-hackyStdExt-overview-summary.html
Aaron's Laptop:
- freshStart junitAll = 23 minutes and 12 seconds
-------------
With JBlanket Enabled:
Aaron's new Dell Desktop:
- freshStart junitAll = 96 minutes and 52 seconds (most of its time was
spent on hackyStdExt).
- see the attached file, Jblanket-hackyStdExt-overview-summary.html. You'll
notice that with Jblanket enabled the junit tests on the analyses take 25
times longer than when it is not enabled. For example the Adoption test
takes 15 minutes instead 30 seconds. The client side tests require 3 or 4
times as long.
Aaron's Laptop:
- freshStart junitAll = 175 minues and 37 seconds (most of its time was
spent on hackyStdExt).
Now, I realize that JBlanket requires a little overhead. And a little
overhead is perfectly fine. But, 80 minutes seems excessive. I'm not sure,
because I never ran the tests with JBlanket enabled, if this was happening
before the upgrade to Jdom 1.0. So, I did a little searching and found out
that, before the upgrade on March 4, 2005, the Daily Build of the
Hackystat-ALL configuration took about 2 hours. I realize that the Daily
Build generates a whole bunch of other things like; locc, performance, etc,
but 2 hours seems excessive for that. Heres the supporting data:
<entry tstamp="1109930924563" tool="Ant" result="Success" failureType=""
failureMessage="" runtimeStamp="1109930924562"
startTimeMillis="1109930924562" endTimeMillis="1109937584828"
buildLocation="C:\CruiseControls\instance-ALL\hacky\hackyBuild"
buildTarget="cruisecontrol"
additionalData="configuration=Hackystat-All,startType=CruiseControl-Auto,checkstyleRan=true,compilationRan=true,unittestRan=true,failureModuleName=N/A"
/>
Start Time: 12:08 AM
End Time: 1:59 AM
Now compare that with Build data for the Hackystat-UH configuration. This
takes only 33 minutes. But, almost contains all the Hackystat modules and
almost generates the same amount of data. The main difference is that we
don't enable jblanket for Hackystat-UH.
<entry tstamp="1109938404157" tool="Ant" result="Success" failureType=""
failureMessage="" runtimeStamp="1109938404156"
startTimeMillis="1109938404156" endTimeMillis="1109940364375"
buildLocation="C:\CruiseControls\instance-UH\hacky\hackyBuild"
buildTarget="cruisecontrol"
additionalData="configuration=Hackystat-UH,startType=CruiseControl-Auto,checkstyleRan=true,compilationRan=true,unittestRan=true,failureModuleName=N/A"
/>
Start Time: 2:13 AM
End Time: 2:46 AM
--------------------------------------------------
I'm going to try to upgrade CLEW (the other large web application) with
Jdom1.0 and the new Jblanket. What's strange is that this web application
did not take forever when running Jblanket before the upgrade. I am
wondering if CLEW's testing time will go up or stay the same.
Sorry for finding more bad news.
thanks, aaron
Title: Unit Test Results: Summary
Unit Test Results
Summary
| Tests | Failures | Errors | Success rate | Time |
| 116 | 0 | 0 | 100.00% | 5168.297 |
|
Note: failures are anticipated and checked for with assertions while errors are unanticipated.
|
Packages
Title: Unit Test Results: Summary
Unit Test Results
Summary
| Tests | Failures | Errors | Success rate | Time |
| 116 | 0 | 0 | 100.00% | 242.330 |
|
Note: failures are anticipated and checked for with assertions while errors are unanticipated.
|
Packages
