Bug #87449 Test main.parser-big-64bit requires unreasonable amount of RAM under Valgrind
Submitted: 17 Aug 2017 2:34 Modified: 18 Aug 2017 6:20
Reporter: Laurynas Biveinis (OCA) Email Updates:
Status: Verified Impact on me:
None 
Category:Tests: Server Severity:S3 (Non-critical)
Version:8.0.2 OS:Linux
Assigned to: CPU Architecture:Any
Tags: mtr, valgrind

[17 Aug 2017 2:34] Laurynas Biveinis
Description:
Test main.parser-big-64bit requires unreasonable amount of RAM under Valgrind and requires unreasonble testing machine provisioning.

On a 8GB VM, which can otherwise do RPL --big-test tests roughly at about --parallel=3 and non-RPL --big-test ones at maybe --parallel=5, this test gets killed by OOM while running all by itself, nothing in parallel.

It would be a waste of time and  resources to provision an e.g. 16GB (I haven't tested and I only hope this would be enough) machine and then run Valgrind --big-test --parallel=1 so that this one test could manage to complete.

How to repeat:
./mtr --debug-server --big-test --valgrind parser-big-64bit
...
safe_process[6879]: Child process: 6880, killed by signal: 9
----------SERVER LOG END-------------

VM log has

Aug 15 20:35:18 ubuntu-main-1 kernel: [71449.907164] Out of memory: Kill process 6630 (memcheck-amd64-) score 886 or sacrifice child
Aug 15 20:35:18 ubuntu-main-1 kernel: [71449.907394] Killed process 6630 (memcheck-amd64-) total-vm:9503852kB, anon-rss:7546360kB, file-rss:0kB, shmem-rss:0kB
Aug 15 20:35:18 ubuntu-main-1 kernel: [71450.174072] oom_reaper: reaped process 6630 (memcheck-amd64-), now anon-rss:48kB, file-rss:0kB, shmem-rss:0kB

Suggested fix:
Disable the test for Valgrind?
[18 Aug 2017 6:20] Umesh Shastry
Hello Laurynas,

Thank you for the report and and feedback.

Thanks,
Umesh