Skip to content

Failing E2E tests #3019

@thewhaleking

Description

@thewhaleking

Yesterday, the e2e failed blocking the release of async-substrate-interface 1.5.2 to investigate:
https://github.com/opentensor/async-substrate-interface/actions/runs/16985974321/job/48154910075?pr=180

The following failures occurred:

  • bittensor/tests/e2e_tests/test_subtensor_functions.py
  • bittensor/tests/e2e_tests/test_staking.py
  • bittensor/tests/e2e_tests/test_commit_reveal_v3.py

This morning, I reviewed the PR #3016, in which I noticed 13 failed e2e tests, on a PR which simply updated a type annotation.
Failures:

  • tests/e2e_tests/test_commit_reveal_v3.py [3.9, 3.12, 3.13]
  • tests/e2e_tests/test_staking.py [3.9, 3.10, 3.11, 3.12, 3.13]
  • tests/e2e_tests/test_subtensor_functions.py [3.9, 3.10, 3.11, 3.12, 3.13]

I opened #3018 (a no-op PR) to run the tests, and had 11 failed e2e tests:

  • tests/e2e_tests/test_commit_reveal_v3.py [3.9]
  • tests/e2e_tests/test_staking.py [3.9, 3.10, 3.11, 3.12, 3.13]
  • tests/e2e_tests/test_subtensor_functions.py [3.9, 3.10, 3.11, 3.12, 3.13]

We've known about the flakiness of test_commit_reveal_v3 for at least a few days (see: #3015).

But the others appear new.

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions