automated: linux: modules: move memory measurement outside iteration loop

Restructure the testing loop to implement cumulative memory leak detection:

- Record memory usage once at the start of all iterations for a module
- Remove per-iteration memory recording and leak checking
- Move leak detection to after all iterations complete
- Record final memory usage after all load/unload cycles

This changes the approach from checking for leaks after each individual
load/unload cycle to checking for cumulative leaks after all cycles
complete. This provides cleaner test results with one pass/fail per
module instead of multiple results per module.

Signed-off-by: Anders Roxell <anders.roxell@linaro.org>
1 file changed
tree: 9edfd1a4264c296697f076ceac7f6fc9316be979
  1. .github/
  2. .reuse/
  3. automated/
  4. docs/
  5. LICENSES/
  6. manual/
  7. mkdocs_plugin/
  8. plans/
  9. test/
  10. .gitignore
  11. .readthedocs.yml
  12. COPYING
  13. COPYRIGHTS
  14. mkdocs.yml
  15. README.md
  16. sanity-check.sh
  17. test.sh
  18. validate.py
README.md

Build Status REUSE Compliance Check

Test Definitions

A set of testing scripts designed to work with LAVA. Also contains test-runner script that allows execution outside LAVA.

More details in docs