Repository navigation
test_verify_tee_expired_attestation_triggers_resharing is flaky #1900
Description
Background
test test_verify_tee_expired_attestation_triggers_resharing was introduced recently in #1725 and seems to be flaky:
thread 'sandbox::tee::test_verify_tee_expired_attestation_triggers_resharing' panicked at crates/contract/tests/sandbox/tee.rs:660:14:
expected Resharing state, got Running(RunningContractState { domains: DomainRegistry { domains: [DomainConfig { id: DomainId(0), scheme: Secp256k1 }], next_domain_id: 2 }, keyset: Keyset { epoch_id: EpochId(5), domains: [KeyForDomain { domain_id: DomainId(0), key: Secp256k1 { near_public_key: PublicKey { data: [1, 228, 165, 129, 33, 42, 127, 18, 178, 247, 71, 203, 41, 192, 7, 227, 100, 119, 95, 206, 53, 191, 29, 130, 8, 79, 246, 116, 250, 191, 9, 17, 174, 93, 201, 170, 28, 121, 198, 103, 113, 72, 177, 156, 100, 123, 35, 30, 68, 168, 50, 115, 47, 62, 39, 235, 4, 165, 2, 138, 210, 39, 17, 71, 44] } }, attempt: AttemptId(0) }] }, parameters: ThresholdParameters { participants: Participants { next_id: ParticipantId(3), participants: [(AccountId("dev-20260129092359-57050154508676.test.near"), ParticipantId(0), ParticipantInfo { url: "127.0.0.1", sign_pk: PublicKey { data: [0, 70, 107, 211, 11, 235, 181, 203, 137, 128, 194, 23, 93, 112, 245, 186, 25, 206, 117, 166, 115, 237, 204, 115, 121, 120, 219, 193, 23, 161, 190, 21, 97] } }), (AccountId("dev-20260129092359-48724867042456.test.near"), ParticipantId(1), ParticipantInfo { url: "127.0.0.1", sign_pk: PublicKey { data: [0, 16, 240, 175, 180, 167, 110, 81, 29, 45, 141, 41, 0, 181, 34, 148, 117, 63, 236, 48, 181, 243, 125, 4, 126, 216, 8, 21, 236, 90, 205, 132, 144] } }), (AccountId("dev-20260129092359-75784008687763.test.near"), ParticipantId(2), ParticipantInfo { url: "127.0.0.1", sign_pk: PublicKey { data: [0, 5, 168, 158, 89, 238, 104, 243, 163, 96, 4, 193, 81, 106, 141, 0, 154, 135, 193, 24, 166, 142, 199, 250, 120, 251, 89, 78, 55, 248, 210, 173, 241] } })] }, threshold: Threshold(2) }, parameters_votes: ThresholdParametersVotes { proposal_by_account: {} }, add_domains_votes: AddDomainsVotes { proposal_by_account: {} }, previously_cancelled_resharing_epoch_id: None })
example runs:
User Story
No response
Acceptance Criteria
The test is fixed so that it is no longer flaky
Resources & Additional Notes
No response
Activity
kevindeforth commentedon Jan 30, 2026
one more:
https://github.com/near/mpc/actions/runs/21516052209/job/61994579399
logs_55907358414.zip
and
mpc-node tests::resharing::test_key_resharing_simple::case_4:https://github.com/near/mpc/actions/runs/21518055689/job/62001436106
logs_55913592894.zip
pbeza commentedon Feb 23, 2026
Reopening this — it’s still flaky as of 23.02.2026:
https://github.com/near/mpc/actions/runs/22303646112/job/64517376434?pr=2169
gilcu3 commentedon Feb 23, 2026
I believe the error for this one is slightly different, sharing here for future reference:
If it begins failing with noticeable frequency I will work on it again, for the moment I will assume it was a one-off. We still could have those at any time, given that our tests have timeouts that might fail in extraordinary cases
netrome commentedon May 4, 2026
Has anyone still seen this? If there are no more notes of this failure in 60 days let's close it.
netrome commentedon May 4, 2026
This might have made the test less flaky #2742