You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This error is caused by the automatic generation of signatures (arb_proof_setup), as it generates not enough signatures (4 out of the expected 5). The reason why this test completes successfully in the other rounds is because it is extremely unlikely to happen (we have at least 2 signers that are allowed to run 100 lotteries with a probability of wining of ~0.2 (note that all parties for the test are generated with stake = 1).
That particular test that fails has 5 signers! So 500 lotteries to play, and we don't even win 5, so we don't even win a 1%. Extremely unlikely. However, the goal of this function (arb_proof_setup) is to generate a valid signature to then modify it into an invalid signature. Therefore, we are only testing error messages, not associated with the lotteries.
My suggestion is to make the parameters such that lotteries are always won, so that we do not encounter such a scenario again. (I'll open a PR)
which might make us doubt of why it only failed once. However, the 'lottery ticket' depends on the key, the message, the AVK, the party's stake and the total stake.
It looks like a test from the cryptographic library mithril-core is flaky:
stm::tests::test_invalid_proof_path
test incargo test
(associated trace)The text was updated successfully, but these errors were encountered: