Test exists with a failure, but tests log has no details about wycheproof HOT 7 CLOSED

Thanks for reporting this bug.

We're aware of this issue. bazel failed to run the test because it is taking too much time. We'll provide a workaround soon. Please see also https://groups.google.com/forum/#!topic/wycheproof-users/usPJedwMPkw if you're curious about the root cause of this bug.

from wycheproof.

We're still finding a solution, but the workaround that was merged in #28 should allow you to run all tests again.

Could you please try again and tell us what you get?

from wycheproof.

Thanks Thaidn.

I pulled the latest changes in #28 , before running the same command: bazel test BouncyCastleTestLocal.

The tests times out around 915s, which is the same as the last time with 1 failure. The test log is attached, but it's not clear what I'm to conclude.

test.txt

from wycheproof.

Thanks ddfagbemi. Could you please tell us more which version of Bazel you're using?

from wycheproof.

It's build label: 0.4.3

from wycheproof.

@thaidn , any updates on these issue? I'd like to try out the tool, but I seem to be stuck.
Thanks.

from wycheproof.

from wycheproof.