python unit test jobs failing due to subunit log being too big
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Brant Knudson | ||
Icehouse |
Fix Released
|
Undecided
|
Unassigned | ||
Juno |
Fix Released
|
Undecided
|
Unassigned | ||
sqlalchemy-migrate |
Fix Committed
|
High
|
Brant Knudson |
Bug Description
2015-01-05 10:20:01.178 | + [[ 72860 -gt 50000 ]]
2015-01-05 10:20:01.178 | + echo
2015-01-05 10:20:01.178 |
2015-01-05 10:20:01.178 | + echo 'sub_unit.log was > 50 MB of uncompressed data!!!'
2015-01-05 10:20:01.178 | sub_unit.log was > 50 MB of uncompressed data!!!
2015-01-05 10:20:01.179 | + echo 'Something is causing tests for this project to log significant amounts'
2015-01-05 10:20:01.179 | Something is causing tests for this project to log significant amounts
2015-01-05 10:20:01.179 | + echo 'of data. This may be writers to python logging, stdout, or stderr.'
2015-01-05 10:20:01.179 | of data. This may be writers to python logging, stdout, or stderr.
2015-01-05 10:20:01.179 | + echo 'Failing this test as a result'
2015-01-05 10:20:01.179 | Failing this test as a result
2015-01-05 10:20:01.179 | + echo
Looks like the subunit log is around 73 MB, this could be due to the new pip because I'm seeing a ton of these:
"DeprecationWar
The latest pip was released on 1/3/15:
https:/
That's also when those warnings showed up:
Changed in nova: | |
importance: | Undecided → Critical |
summary: |
- stable/juno python jobs failing due to subunit log being too big + python unit test jobs failing due to subunit log being too big |
Changed in sqlalchemy-migrate: | |
assignee: | nobody → Brant Knudson (blk-u) |
Changed in nova: | |
status: | In Progress → Fix Committed |
Changed in nova: | |
milestone: | none → kilo-2 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | kilo-2 → 2015.1.0 |
upstream pip bug: https:/ /github. com/pypa/ pip/issues/ 2326