I agree with Hongbing that his enhancements would be nicer, but I also agree with Cedric
that implementing them is going to complicate the code. Let's leave it the way it is for
now.
Cheers,
Philip
--On Tuesday, September 20, 2005 11:50 AM -1000 "(Cedric) Qin ZHANG" <[EMAIL PROTECTED]>
wrote:
1. hackyDevSite has no knowledge of what kind of reports are there for each
build
configuration. It just pick up whatever is in the report directory. Reordering
the
reports requires hardcoding of the types of reports available. It's not hard to
do so,
but the problem is whether we really want to go that route.
2. Sorry there is no separate compilation report, you have to search inside the
ant
report which is not that bad because all error messages are at the end of ant
report.
Cheers,
Cedric
Hongbing Kou wrote:
Hi, folks,
There is a unit test failure yesterday on Hackystat-HPC
http://xenia.ics.hawaii.edu/hackyDevSite/configurationBuildReport.do?year=2005&month=9
&day=20&configuration=Hackystat-HPC
The thing is that it is hard to locate unit test report box. How about
move junit box to the top? And we may have these reports in order
of junit, changelog, cvsdiff, checkstyle, locc and others. Is it a hard
thing to change the order on hackydevsite, Cedric?
It is also hard to locate compilation error in antlog file because it is
such a large documentation as in
http://xenia.ics.hawaii.edu/hackyDevSite/build_log/20050920/Hackystat-HPC/ant/antlog/i
ndex.html
and
http://xenia.ics.hawaii.edu/hackyDevSite/build_log/20050920/Hackystat-ALL/ant/antlog/i
ndex.html
Is it possible to put an anchor in the log to avoid needle searching?
Thanks,
Hongbing
