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
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
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
Hi Gunnar,
Thanks for mentioning git-bisect. I'll give it a try.
Gail
- Original Message -
> From: "Gunnar Morling"
> To: "Steve Ebersole" , "Gail Badner"
> Cc: "hibernate-dev@lists.jboss.org hibernate-dev"
>
> Sent: Wednesday, July 25, 2012 9:13:28 AM
> Subject: Re: [hibernate-dev]
John and I discussed an extension to @FailureExpected this morning too
that he is going to implement that should hopefully help alleviate some
of the problems.
On Wed 25 Jul 2012 01:03:48 PM CDT, Gail Badner wrote:
> Hi Gunnar,
>
> Thanks for mentioning git-bisect. I'll give it a try.
>
> Gail
>
