Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use unittest hooks for test execution instead of getting test output via sockets #10119

Closed
karrtikr opened this issue Feb 13, 2020 · 1 comment
Labels
area-testing debt Covers everything internal: CI, testing, refactoring of the codebase, etc.

Comments

@karrtikr
Copy link

karrtikr commented Feb 13, 2020

Solves issues like #2660 #5597

More info: #2660 (comment)

@karrtikr karrtikr added needs PR debt Covers everything internal: CI, testing, refactoring of the codebase, etc. area-testing labels Feb 13, 2020
@karrtikr karrtikr changed the title Use the stdout to scrape test output in unittest framework, rather than sockets, as is done with other frameworks Use unittest hooks for test execution instead of getting test output via sockets Sep 15, 2020
@github-actions github-actions bot removed the needs PR label Aug 9, 2022
@karrtikr karrtikr added the needs PR Ready to be worked on label Aug 9, 2022
@eleanorjboyd
Copy link
Member

fixed by rewrite, the redesign should address this. #17242

@github-actions github-actions bot removed the needs PR Ready to be worked on label Jul 14, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 14, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-testing debt Covers everything internal: CI, testing, refactoring of the codebase, etc.
Projects
None yet
Development

No branches or pull requests

2 participants