nearcore
nearcore copied to clipboard
Need to fix broken NayDuck tests
The following NayDuck tests are currently broken and disabled:
- [x] https://github.com/near/nearcore/issues/5027
-
[x]
expensive integration-tests client test_gc_after_state_sync
-
[x]
expensive integration-tests test_rejoin test::test_4_20_kill2
-
[x]
expensive near-client catching_up tests::test_all_chunks_accepted_1000_slow
-
[x]
expensive near-client catching_up tests::test_chunk_grieving
- [ ]
expensive near-client near_client tests::cross_shard_tx::test_cross_shard_tx
et al -
[x]
expensive nearcore test_tps_regression test::test_highload
- [ ]
pytest adversarial/gc_rollback.py
- [ ]
pytest sanity/garbage_collection_sharding_upgrade.py
(<https://github.com/near/nearcore/issues/5095>) -
[x]
pytest sanity/restaked.py
(<https://github.com/near/nearcore/issues/5503>) -
[x]
pytest sanity/restart.py
-
[x]
pytest sanity/repro_2916.py
-
[x]
pytest sanity/rpc_finality.py
- [ ]
pytest sanity/state_migration.py
- [ ]
pytest sanity/state_sync2.py
- [ ]
pytest sanity/state_sync_fail.py
(nightly only) (<https://github.com/near/nearcore/issues/5182>) - [ ]
pytest sanity/state_sync_late.py
(keeps timing out) -
[x]
pytest sanity/state_sync_massive.py
-
[x]
pytest sanity/sync_chunks_from_archival.py
- [ ]
pytest sanity/sync_ban.py
- [ ]
pytest sanity/validator_switch_key.py
(<https://github.com/near/nearcore/issues/2949>) - [ ]
pytest stress/network_stress.py
They need to be fixed or deleted if they are no longer needed.
This issue has been automatically marked as stale because it has not had recent activity in the last 2 months. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.