Steve Ebersole wrote:
I am not really familiar with CruiseControl, so what exactly do you mean
by "emit"?

emit in this case means make it clearly visible at first glance which JDK, Host, JDBC Driver and SQL Server version are being used for the test case run. That seems like a pretty basic requirement to me.



AFAIK, the same box hosts the various runs, correct?  So unless there
are plans to change that, a lot of effort here seems silly.

This presumes everybody with an interest in the test results generated from that box is also kept in the loop with all future changes and upgrades of that box.

This presumes that the person responsible for maintaining the testing box understands all the implications of interactions with the various versions of the components used in the tests.

I'm surprised you think what should amount to a couple of out.println() statements is "a lot of effort".



For example Max wasn't aware 5.0 has gone GA, well it if was clear from looking at the test summary what was actually being tested someone with a better knowledge could have pointed something like that out.

I don't expect everyone to know everything about everything and I also don't expect everyone to go digging at the sight of every test failure. So if something can be done to make the test results a more accurate picture of where things stand is a good thing by me. YMMV



(these are from my local setup).

Great, but of little relevance to the daily testing emailed to the devel list.


Darryl
_______________________________________________
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev

Reply via email to