coverage job fails even without any code changes
Bug #1797512 reported by
Goutham Pacha Ravi
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Shared File Systems Service (Manila) |
Expired
|
Wishlist
|
Unassigned |
Bug Description
The coverage test (tox -e cover) sometimes fails even without any code changes being committed.
Example Failure: http://
Review in question: https:/
Console Log file attached with this report.
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/609832 /git.openstack. org/cgit/ openstack/ manila/ commit/ ?id=a07c51e8b01 074d8ee8bb936a3 1ad4c1654c4e73
Committed: https:/
Submitter: Zuul
Branch: master
commit a07c51e8b01074d 8ee8bb936a31ad4 c1654c4e73
Author: Goutham Pacha Ravi <email address hidden>
Date: Thu Oct 11 15:00:07 2018 -0700
Make coverage non-voting and fix use of rpc_backend
rpc_backend was an old oslo_messaging option
that was deprecated in stable/newton and removed
in master/stein [2], so stop using it in our
unit tests.
The coverage job in manila was always non-voting, 1682c43d0823d20 09078c2fec zuul-jobs repository. This change
however, a773e31420bfd14
added a common coverage job-template from the
openstack-
inadvertently made the non-voting cover job a
voting job.
Our coverage script isn't perfect, it is known
to fail erroneously on non-code changes, and
some genuine failures are just an indication
to developers and reviewers to make the best
effort to adhere to the script's strict
checks [3].
These changes are unrelated, but must be fixed
together to pass the gate, since we have a
chicken-and-egg problem with both failures
preventing separate fixes from merging
separately.
[1] https:/ /review. openstack. org/#/c/ 317285/ /review. openstack. org/#/c/ 580910/ git.openstack. org/cgit/ openstack/ manila/ tree/tools/ cover.sh
[2] https:/
[3] http://
Closes-Bug: #1796759 4e706369ad67bc1 155f62f2651
Related-Bug: #1797512
Change-Id: Ie349c3866d51ea