debugs are filling screen when launching functests
Bug #1201376 reported by
Chmouel Boudjnah
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| python-swiftclient |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
When launching the swift functional test suite on keystone swiftclient try to enable the debug message when logging.DEBUG is enabled (from nosetests) and due fill up the screen with debug error. Would be nice to find a way to don't have those and only showing when there is errors.
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to python-swiftclient (master) | #1 |
| Changed in python-swiftclient: | |
| status: | New → Fix Committed |
| Changed in python-swiftclient: | |
| milestone: | none → 2.5.0 |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit a4fb70ece189aff
Author: Tim Burke <email address hidden>
Date: Tue Mar 3 12:35:03 2015 -0800
Compare each chunk of large objects when uploading
Previously, we compared the ETag from Swift against the MD5 of the
entire large object. However, the ETag for large objects is generally
the MD5 of the concatenation of the ETags for each segment, unless the
object is a DLO whose segments span more than one page of a container
listing. Rather than worry about ETags, just compare each chunk of the
segmented file. This allows the use of --skip-identical when uploading
SLOs and DLOs.
Additionally, there are several test-related improvements:
* The default arguments for OutputManager are now evaluated on
as a test runner. (See also: bug 1251507)
* An account_username option is now available in the functional tests
config file for auth systems that do not follow the account:username
format.
* CaptureOutput no longer writes to the captured stream, and
MockHttpTest now captures output. These were polluting test output
Change-Id: Ic484e9a0c186c9
Closes-Bug: #1201376
Closes-Bug: #1379252
Related-Bug: #1251507