tests: Fix flappiness in DRS tests due to RID Set changing
authorTim Beale <timbeale@catalyst.net.nz>
Tue, 20 Nov 2018 04:30:37 +0000 (17:30 +1300)
committerAndrew Bartlett <abartlet@samba.org>
Fri, 23 Nov 2018 04:00:22 +0000 (05:00 +0100)
commit1a45e5b136bedfed1fa3a8b87b79da759c3958c4
tree28fa23c0c2ea74a7fbda9ace0e1b71d2782e621a
parentb8ff4a0881bd6a12ba43ece27b8d3d9e5750b81f
tests: Fix flappiness in DRS tests due to RID Set changing

The test_link_utdv_hwm test case in getnc_exop has started getting
slightly flappy (8 failures in the last 2 weeks). The problem is the
test case creates a new computer, which can occasionally result in a new
RID pool being allocated.

The problem can be reproduced by running the test case repeatedly (it
usually fails after ~250 times).

This patch updates the _check_ctr6() assertion to filter out the 'CN=RID
Set' object, if it happens to be present.

Signed-off-by: Tim Beale <timbeale@catalyst.net.nz>
Reviewed-by: Andrew Bartlett <abartlet@samba.org>
source4/torture/drs/python/drs_base.py