[hibernate-dev] [Fwd: hibernate-mysql50-testsuite Build CompletedWith Testsuite Errors]

[Steve Ebersole]

Um, perhaps if you are going to ask me to do something you could can the
attitude?  Seems like a basic requirement to me...

As far as the box hosting the runs, I did not realize I had presumed
anything.   The point was simply that it seems silly to me to invest a
lot of effort to script this when this could simply be hard-coded info
since they all run on the same exact env.  Is it as easy as a couple of
printlns?  I don't know (again see my qualification that I do not know
CruiseControl).  BTW, nothing is a lot of effort when someone else is
doing all the work ;)

So Max was not aware that MySQL 5.0 had gone GA.  How exactly would us
making these things you ask for more accessible in our testsuite results
have changed that?

I am simply telling Aleksandar that if this takes a lot of effort that I
would much prefer him instead continuing to focus his efforts on getting
more database coverage up and running.  You don't agree with that?
Great!  Let us know when you have your hosted Hibernate test suite up
and running; then you can call the shots.  But to me I am more
interested in the coverage; I can live with 4 clicks to get this other
info in the meantime.


-----Original Message-----
From: Darryl Miles [mailto:darryl-mailinglists at netbauds.net] 
Sent: Monday, December 04, 2006 11:40 AM
To: Steve Ebersole
Cc: Aleksandar Kostadinov; hibernate-dev at lists.jboss.org
Subject: Re: [hibernate-dev] [Fwd: hibernate-mysql50-testsuite Build
CompletedWith Testsuite Errors]

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