Skip to content

Python test handler visually resolved prematurely #21337

Closed

Description

Testing #21306

changed test_subtests.py to range (0, 10k), all visual indicators resolve before output is updated.

edit: was previously testing with range (0, 1mil) which could have bled over -- causing the weirder outputs and issues.

Python output logs continue to print 2023-05-30 14:55:57.210 [info] On data received: Error occurred because the payload UUID is not recognized

image

Activity

  1. eleanorjboyd commented on May 30, 2023

    @eleanorjboyd
    Member

    behavior appears to be different when running on a test class vs the workspace, this should be investigated further.

  2. eleanorjboyd commented on May 31, 2023

    @eleanorjboyd
    Member
    image

    another related issue- the tests in the test output bottom panel didn't end up resolving even though the text explorer UI did and all the tests ran. This occurred when 100k subtests were run so it could be a load issue.

  3. eleanorjboyd commented on Jun 5, 2023

    @eleanorjboyd
    Member

    should be fixed by #21351 as well. Just checked and was not able to repro the behavior anymore.

  4. locked as resolved and limited conversation to collaborators on Jul 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

area-testinginfo-neededIssue requires more information from postertriage-neededNeeds assignment to the proper sub-team

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions