> On Jul 30, 2019, at 11:48 PM, Weijun Wang <weijun.w...@oracle.com> wrote:
>
>
>
>> On Jul 31, 2019, at 1:11 PM, Xuelei Fan <xuelei....@oracle.com> wrote:
>>
>> I'm fine as well if you want to exclude the test for Solaris platforms (my
>> preference). But please file a new bug if you find something unusual for
>> Solaris platforms.
>
> Why file a new bug if this one already exists?
>
> Since the bug is now in problem list for solaris, and I am quite confident
> this is related to ucrypto. Is it better to leave it open and delay it to a
> future release?
I agreed it is better.
Xuelei
> I can now reproduce the failure on a solaris machine but if I simplify the
> test into only the single method that triggers the error, the test succeeds.
> Maybe many calls into ucrypto has corrupted the internal state and a final
> update call destroys it.
>
> Thanks,
> Max
>
>
