Red Hat Bugzilla – Bug 1267750
pagedresults - when timed out, search results could have been already freed.
Last modified: 2016-11-03 16:36:12 EDT
This bug is created as a clone of upstream ticket:
Possible to free search results twice.
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see email@example.com with any questions
I've read original bz1267296 and it seems that bug is very rarely reproducible.
Would it be enough just to test simple paged result test suite automation for a clean execution (as you proposed for other rarely reproducible bug)?
Or should I perform some additional steps to verify the bug?
(In reply to Simon Pichugin from comment #3)
> Hi Noriko,
> I've read original bz1267296 and it seems that bug is very rarely
> Would it be enough just to test simple paged result test suite automation
> for a clean execution (as you proposed for other rarely reproducible bug)?
> Or should I perform some additional steps to verify the bug?
I think your test suites would cover the issue. If you could do this with the minimum effort, run the tests with very short timelimit such as 1 second?
Thank you, Noriko. I've set timelimit to 1 second before each test.
============================ test session starts ============================
platform linux2 -- Python 2.7.5, pytest-2.9.2, py-1.4.31, pluggy-0.3.1
rootdir: /mnt/tests/rhds/tests/upstream/ds/dirsrvtests/tests/suites/paged_results, inifile:
plugins: html-1.8.1, cov-2.2.1
collected 24 items
======================== 24 passed in 72.47 seconds ========================
Marking as verified.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.