Hi,
Although I have not experienced that particular issue in Agroal (either
locally or in the CI), I was aware that the race condition that was
mitigated in 1.3 could still happen.
I've long reworked the shutdown code so the issue is completely gone. It
just happens that I'm about to release A
I hate to be overly reactionary, but we we may want to consider dropping
that module then. If there is a bug and we cannot get in touch with him to
figure it out then we cannot really suppport it
On Tue, Jan 29, 2019 at 3:31 PM Guillaume Smet
wrote:
> On Tue, Jan 29, 2019 at 9:48 PM Steve Ebers
On Tue, Jan 29, 2019 at 9:48 PM Steve Ebersole wrote:
> Have we gotten any reply about this?
>
No.
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
Have we gotten any reply about this?
On Wed, Jan 23, 2019 at 8:58 AM Guillaume Smet
wrote:
> Hello Luis,
>
> Any chance you could take a look at this one?
>
> I just got it again on my laptop and it happened quite frequently on our CI
> lately.
>
> AFAICS, it's always failing in the setting isol
Hello Luis,
Any chance you could take a look at this one?
I just got it again on my laptop and it happened quite frequently on our CI
lately.
AFAICS, it's always failing in the setting isolation test but it can be
different test methods. Just had it for
AgroalTransactionIsolationConfigTest > tes
Hi Luis,
We talked at some point about a potential issue in Agroal, you said 1.3
should have all the known issues solved but apparently, there is still one
as we have transient test failures on ORM from time to time.
A good example is the following one:
http://ci.hibernate.org/view/ORM/job/hibern
