mark iptables memory leak test as out of SLO
We don't really care about this test enough to care about
putting even more effort into the debugging it.
Observed flakes:
system/netd/server/IptablesRestoreControllerTest.cpp:382: Failure
Expected: (38) >= (getRssPages(pid6) - pages6), actual: 38 vs 39
ip6tables-restore leaked too many pages
system/netd/server/IptablesRestoreControllerTest.cpp:381: Failure
Expected: (38) >= (getRssPages(pid4) - pages4), actual: 38 vs 219
iptables-restore leaked too many pages
system/netd/server/IptablesRestoreControllerTest.cpp:381: Failure
Expected: (38) >= (getRssPages(pid4) - pages4), actual: 38 vs 216
iptables-restore leaked too many pages
Test: TreeHugger
Signed-off-by: Maciej Żenczykowski <maze@google.com>
Change-Id: I74ed94b6623e870c5a83a76015c1fe965a9b4800
1 file changed