On 7/31/19 1:30 PM, Valerie Peng wrote:
I think it's easier to just skip this test for Solaris if this test runs
fine on all other non-Solaris platforms.
I would leave it in the ProblemList (for solaris-all) and leave 8228431
open -- this way we still have an open issue if someone needs to look
further into the ucrypto issue later on.
--Sean
Just my .02,
Valerie
On 7/30/2019 11:48 PM, Weijun Wang 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 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
