Repository navigation
flaky pytests since nearcore 2.10 #1606
Description
Background
Recently we have had a few pytests fail with:
AssertionError: {
"jsonrpc": "2.0",
"error": {
"name": "HANDLER_ERROR",
"cause": {
"info": {},
"name": "INVALID_TRANSACTION"
},
"code": -32000,
"message": "Server error",
"data": {
"TxExecutionError": {
"InvalidTxError": {
"InvalidNonce": {
"ak_nonce": 30,
"tx_nonce": 30
}
}
}
}
},
"id": "dontcare"
}
Examples:
- https://github.com/near/mpc/actions/runs/19893409371/job/57017619575?pr=1603
- https://github.com/near/mpc/actions/runs/19927453444/job/57130706678
- https://github.com/near/mpc/actions/runs/20141149427/job/57808757473
- https://github.com/near/mpc/actions/runs/20163080061/job/57879868229?pr=1645
- https://github.com/near/mpc/actions/runs/20177192755/job/57928213036?pr=1645
- https://github.com/near/mpc/actions/runs/20276497537/job/58226661136?pr=1676
My best bet is that it is related to the underlying changes in pytests that happened in that release.
User Story
No response
Acceptance Criteria
The source of the flakiness is found and fixed.
Resources & Additional Notes
No response
Activity
gilcu3 commentedon Dec 6, 2025
maybe related to near/nearcore#14747
gilcu3 commentedon Dec 23, 2025
The PR above was released as part of nearcore 2.10, which we bumped 3 weeks ago, but the issue in our pytests persisted, so there is still something wrong
gilcu3 commentedon Jan 9, 2026
reopening as the same failure was observed in: