BIND 10 #3056: MemorySegmentMappedTest.badAllocate fails when run as root user
BIND 10 Development
do-not-reply at isc.org
Thu Jul 18 07:25:30 UTC 2013
#3056: MemorySegmentMappedTest.badAllocate fails when run as root user
-------------------------------------+-------------------------------------
Reporter: muks | Owner: muks
Type: defect | Status:
Priority: medium | reviewing
Component: data source | Milestone:
Keywords: | Sprint-20130723
Sensitive: 0 | Resolution:
Sub-Project: DNS | CVSS Scoring:
Estimated Difficulty: 0 | Defect Severity: N/A
Total Hours: 0 | Feature Depending on Ticket:
| Add Hours to Ticket: 0
| Internal?: 0
-------------------------------------+-------------------------------------
Changes (by vorner):
* owner: vorner => muks
Comment:
About the changelog, I think I agree with Jeremy ‒ if it was noticed by
users, it should have a changelog.
The change looks OK and solves the described problem. But if I run the
complete tests as root, I get this error:
{{{
Running test: cmdctl_test.py
.............................FF......
======================================================================
FAIL: test_check_file (__main__.TestSecureHTTPServer)
----------------------------------------------------------------------
Traceback (most recent call last):
File "/home/vorner/work/bind10/src/bin/cmdctl/tests/cmdctl_test.py",
line 684, in test_check_file
self.assertRaises(CmdctlException, check_file, file_name)
AssertionError: CmdctlException not raised by check_file
======================================================================
FAIL: test_check_key_and_cert (__main__.TestSecureHTTPServer)
----------------------------------------------------------------------
Traceback (most recent call last):
File "/home/vorner/work/bind10/src/bin/cmdctl/tests/cmdctl_test.py",
line 709, in test_check_key_and_cert
keyfile, certfile)
AssertionError: CmdctlException not raised by _check_key_and_cert
----------------------------------------------------------------------
}}}
I don't know if it's related enough or I should create a new ticket. But I
guess it'll be a similar problem.
--
Ticket URL: <http://bind10.isc.org/ticket/3056#comment:6>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list