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.

Sign up for GitHub

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

Jump to bottom

[FEA] CI should grep build test logs for memory leak output and fail builds or file issues automatically #7605

Open
gerashegalov opened this issue Jan 27, 2023 · 1 comment
Open

[FEA] CI should grep build test logs for memory leak output and fail builds or file issues automatically #7605

gerashegalov opened this issue Jan 27, 2023 · 1 comment
Labels
build Related to CI / CD or cleanly building feature request New feature or request

Comments

@gerashegalov
Copy link
Collaborator

Is your feature request related to a problem? Please describe.
We often miss memory leaks in the test code or production code as long as the test functionally succeeds.
I wish we had some automated mechanisms tracking this, and at least flagging the newly introduced issues by comparing counts to the previous runs

Additional context
#7603
@gerashegalov gerashegalov added feature request New feature or request ? - Needs Triage Need team to review and classify build Related to CI / CD or cleanly building and removed ? - Needs Triage Need team to review and classify labels Jan 27, 2023
@gerashegalov gerashegalov changed the title [FEA] CI should scan build test logs for memory leak output and fail builds or file issues automatically [FEA] CI should grep build test logs for memory leak output and fail builds or file issues automatically Jan 28, 2023
@jlowe
Copy link
Member

jlowe commented Jan 30, 2023

Also relates to #6947

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
build Related to CI / CD or cleanly building feature request New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jlowe @gerashegalov