BIND 10 #2937: The user manager's test_bad_data fails
BIND 10 Development
do-not-reply at isc.org
Tue Apr 30 14:57:08 UTC 2013
#2937: The user manager's test_bad_data fails
-------------------------------------+-------------------------------------
Reporter: | Owner:
vorner | Status: new
Type: | Milestone: Next-Sprint-
defect | Proposed
Priority: high | Keywords:
Component: | Sensitive: 0
Unclassified | Sub-Project: Core
CVSS Scoring: | Estimated Difficulty: 0
Defect Severity: N/A | Total Hours: 0
Feature Depending on Ticket: |
Add Hours to Ticket: 0 |
Internal?: 0 |
-------------------------------------+-------------------------------------
Recently, the test in $SUBJECT started to fail for me:
{{{
...F.......
======================================================================
FAIL: test_bad_data (__main__.TestUserMgr)
----------------------------------------------------------------------
Traceback (most recent call last):
File
"/var/tmp/bind10/bind10-2/bind10-20130221/_build/../src/bin/usermgr/tests/b10
-cmdctl-usermgr_test.py", line 477, in test_bad_data
'add', 'user1', 'pass1'
File
"/var/tmp/bind10/bind10-2/bind10-20130221/_build/../src/bin/usermgr/tests/b10
-cmdctl-usermgr_test.py", line 141, in run_check
self.assertEqual(expected_stdout, stdout.decode())
AssertionError: 'Using accounts file: test_users.csv\nError parsing csv
file: newline inside str [truncated]... != 'Using accounts file:
test_users.csv\n'
Using accounts file: test_users.csv
- Error parsing csv file: newline inside string
}}}
It may be that I upgraded something and it started to output the error
message to stderr instead of stdout (the error is printed, not stored in
the string).
This is annoying, because it breaks the tests every time I do a review. So
I'm putting it to NPP.
--
Ticket URL: <http://bind10.isc.org/ticket/2937>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list