flask tests fail with older versions of python-werkzeug
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-wsme (Ubuntu) |
Fix Released
|
Medium
|
James Page | ||
Saucy |
Fix Released
|
Medium
|
James Page |
Bug Description
nosetests tests/test_flask.py
.F........
=======
FAIL: test_custom_
-------
Traceback (most recent call last):
File "/home/
assert json.loads(
AssertionError:
-------
{u'debuginfo': None, u'faultcode': u'Server', u'faultstring': u"403: You're not allowed in there!"}
-------
-------
wsme.api: ERROR: Server-side error: "403: You're not allowed in there!". Detail:
Traceback (most recent call last):
File "/home/
result = f(*args, **kwargs)
File "/home/
abort(403, description="You're not allowed in there!")
File "/usr/lib/
raise self.mapping[
Forbidden: 403: You're not allowed in there!
-------
-------
Ran 10 tests in 0.023s
FAILED (failures=1)
This is not an issue per-say in Saucy; however this package is a backport target for the Ubuntu Cloud Archive and the test fails due to different handling of the description keyword in newer versions of python-werkzeug.
Dropping the custom description (which is then ignored in the actual test case) resolved the issues on 13.10 and 12.04.
Related branches
Changed in python-wsme (Ubuntu Saucy): | |
status: | New → Fix Released |
status: | Fix Released → In Progress |
importance: | Undecided → Medium |
assignee: | nobody → James Page (james-page) |
This bug was fixed in the package python-wsme - 0.5b5-1ubuntu2
---------------
python-wsme (0.5b5-1ubuntu2) saucy; urgency=low
* d/p/fix_ 403_test_ case.patch: Fixup test case for 403 error code;
older versions of python-werkzeug handle this differently which
creates issues in the Ubuntu Cloud Archive (LP: #1234291).
-- James Page <email address hidden> Wed, 02 Oct 2013 17:51:52 +0100