try.
>
> Gail
>
> - Original Message -
>> From: "Gunnar Morling"
>> To: "Steve Ebersole" , "Gail Badner"
>>
>> Cc: "hibernate-dev@lists.jboss.org hibernate-dev"
>>
>> Sent: Wednesday, July
sday, July 25, 2012 9:13:28 AM
> Subject: Re: [hibernate-dev] Test failures when entity name is mapped
>
> Hi,
>
> surely you're aware of it, so just in case:
>
> git-bisect [1] is great if you need to identify a bad commit between
> a
> known working one and now.
Hi,
surely you're aware of it, so just in case:
git-bisect [1] is great if you need to identify a bad commit between a
known working one and now.
--Gunnar
[1] http://blog.evan.pro/getting-started-with-git-bisect-in-60-seconds
2012/7/25 Steve Ebersole :
> I guess the bottom line is that we eit
I guess the bottom line is that we either need to accept "regressions"
there or come up with a more reliable way to spot these "regressions"
On Wed 25 Jul 2012 09:19:12 AM CDT, Steve Ebersole wrote:
> Moving population of the JPA metamodel is the most likely culprit as I
> think you already knew
Moving population of the JPA metamodel is the most likely culprit as I
think you already knew.
The problem as we also already discussed, imo, is the test set up on
metamodel branch. For even minor changes you really have to run the
full test suite 3 times and keep track of the number of tests
