Frequent failure of py35 jobs
Bug #1730518 reported by
Dirk Mueller
This bug report is a duplicate of:
Bug #1728640: py35 unit test subunit.parser failures.
Edit
Remove
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Cinder |
Confirmed
|
Critical
|
Unassigned | ||
| OpenStack Global Requirements |
New
|
Undecided
|
Unassigned | ||
Bug Description
I believe as of the switch to stestr (not sure), the py35 jobs in cinder are frequently failing, see for example:
http://
This is a tracker bug as the global-requirements project used to gate their changes voting against cinder-py35 but due to the failures put that job to non-voting.
Revision history for this message
| Sean McGinnis (sean-mcginnis) wrote | #1 |
| Changed in cinder: | |
| status: | New → Confirmed |
| importance: | Undecided → Critical |
To post a comment you must log in.
Current thought is there is something being output to subunit.trace that is not the type of output expected. Unable to track down where that output is coming from.