You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently it's possible for code to introduce resource leaks that occur during tests but the tests do not fail when the leak is detected. This can result in leaks "building up" over time, only to be found much later when someone investigate the logs from test runs and notices leak stacktraces in the log output.
Describe the solution you'd like
A system property can be set which would change the leak detection code to not just log a stacktrace of where the leak occurred but also cause the running test to fail in some way. That way when a leak is detected during GC, RMM shutdown, etc, it's more
likely this will be caught by the premerge builds.
Describe alternatives you've considered
Update the premerge and/or nightly test jobs to scrape the test logs looking for signs of leaks being logged.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Currently it's possible for code to introduce resource leaks that occur during tests but the tests do not fail when the leak is detected. This can result in leaks "building up" over time, only to be found much later when someone investigate the logs from test runs and notices leak stacktraces in the log output.
Describe the solution you'd like
A system property can be set which would change the leak detection code to not just log a stacktrace of where the leak occurred but also cause the running test to fail in some way. That way when a leak is detected during GC, RMM shutdown, etc, it's more
likely this will be caught by the premerge builds.
Describe alternatives you've considered
Update the premerge and/or nightly test jobs to scrape the test logs looking for signs of leaks being logged.
The text was updated successfully, but these errors were encountered: